Cortex XDR 3.2 · Version Status
Cortex XDR 3.2 End of Life Date
Cortex XDR 3.2 end-of-life date, support status, and CVE risk. Data reconciled from official vendor documentation and endoflife.date at every build; the source of each date is on the product page.
⚠
Cortex XDR 3.2 is past end of life. This version no longer receives security patches. 3850 days past EOL — migrate to a supported version immediately.
EOL Date
Mar 31, 2016
3850 days past EOL
Latest Release
3.2
Standard release
Release Date
Mar 31, 2015
Cortex XDR 3.2 series
Lifecycle detail
Cortex XDR 3.2 was released on March 31, 2015 and support ended on March 31, 2016 — a supported lifespan of 1 year, in line with the 1 year median for Cortex XDR releases. It was not an LTS release; Cortex XDR reserves longer patch windows for its LTS versions. The last patch it will ever receive is 3.2, published March 31, 2015 — 1 year before support ended. It has been without security patches for 10 years and 7 months. 35 newer Cortex XDR releases have shipped since.
Attack Surface
10/30 Medium tier
CISA KEV Exposure
0/20 Not in KEV
Extended Support
0/10 Available
EOL Risk Score™ — proprietary methodology by endoflife.ai. Factors: EOL recency, attack surface breadth, CISA KEV catalog presence, extended support availability. Updated at every build.
Methodology → ·
View score card →
Extended Support
Extended Cortex XDR 3.2 support is available
Commercial vendors offer security patches beyond EOL. Compare your options.
Compare Options →
| Version | Latest | EOL Date | Status |
|---|
| 3.1 |
3.1 |
Sep 3, 2015 |
EOL |
| → 3.2 |
3.2 |
Mar 31, 2016 |
EOL |
| 3.3 |
3.3 |
Feb 28, 2017 |
EOL |
| 3.4 |
3.4 |
Aug 21, 2019 |
EOL |
| 4.0 |
4.0 |
Apr 5, 2018 |
EOL |
| 4.1 |
4.1 |
Sep 15, 2019 |
EOL |
| 5.0 |
5.0.12 |
Jun 1, 2024 |
EOL |
| 4.2 |
4.2 |
Mar 1, 2022 |
EOL |
What does Cortex XDR 3.2 end of life mean?
When Cortex XDR 3.2 reaches end of life, the maintainers stop issuing security patches for this version. CVEs discovered after the EOL date are publicly disclosed on the National Vulnerability Database with no patch available. Exploit code frequently appears on GitHub within days of disclosure.
The CVE blind spot: A CVE-based scan does not show the ongoing accumulation of unpatched vulnerabilities in EOL software versions. Some scanners flag unsupported versions of common products, but coverage varies, and none of them give you the date in advance. Running Cortex XDR 3.2 past its EOL date creates a growing attack surface that a clean scan result does not rule out.
Migrate to Cortex XDR 9.3 or implement compensating controls — network segmentation, enhanced monitoring, restricted access — while migration is underway.
Frequently Asked Questions
When does Cortex XDR 3.2 reach end of life?
Cortex XDR 3.2 reached end of life on March 31, 2016. This version is no longer receiving security patches.
Is Cortex XDR 3.2 still supported?
No. Cortex XDR 3.2 reached end of life on March 31, 2016 and is no longer receiving security patches.
What should I upgrade to from Cortex XDR 3.2?
The recommended upgrade from Cortex XDR 3.2 is
Cortex XDR 9.3 — the latest actively supported version. Check the
Cortex XDR full timeline for all supported versions.
What are the security risks of running Cortex XDR 3.2 past EOL?
When Cortex XDR 3.2 reaches end of life, the maintainers stop issuing security patches. Any CVEs disclosed after the EOL date accumulate with no vendor fix. A CVE-based scan does not show this — it is the CVE blind spot; some scanners flag unsupported versions of common products, but coverage varies and none give the date in advance. Organizations running EOL Cortex XDR should migrate immediately or implement compensating controls.