Cortex XDR End of Life (EOL) Dates & Support Timeline
Complete end-of-life dates, support windows, and security status for all Cortex XDR versions. Data sourced from endoflife.date and official vendor documentation. Updated at every deploy.
Running an EOL version? Get matched with support options — free ↓| Version | Latest Release | Release Date | EOL Date | Days | Status |
|---|---|---|---|---|---|
| 3.1 | 3.1 | Sep 3, 2014 | Sep 3, 2015 | 3993 days past EOL | EOL |
| 3.2 | 3.2 | Mar 31, 2015 | Mar 31, 2016 | 3783 days past EOL | EOL |
| 3.3 | 3.3 | Nov 10, 2015 | Feb 28, 2017 | 3449 days past EOL | EOL |
| 3.4 | 3.4 | Aug 21, 2016 | Aug 21, 2019 | 2545 days past EOL | EOL |
| 4.0 | 4.0 | Apr 5, 2017 | Apr 5, 2018 | 3048 days past EOL | EOL |
| 4.1 | 4.1 | Sep 15, 2017 | Sep 15, 2019 | 2520 days past EOL | EOL |
| 5.0 | 5.0.12 | Mar 19, 2018 | Jun 1, 2024 | 799 days past EOL | EOL |
| 4.2 | 4.2 | Jun 25, 2018 | Mar 1, 2022 | 1622 days past EOL | EOL |
| 6.0 | 6.0 | Feb 26, 2019 | Feb 26, 2020 | 2356 days past EOL | EOL |
| 6.1 | 6.1.9 | Jul 2, 2019 | Jul 1, 2022 | 1500 days past EOL | EOL |
| 7.0 | 7.0 | Dec 4, 2019 | Jun 4, 2021 | 1892 days past EOL | EOL |
| 7.1 | 7.1 | Apr 22, 2020 | Jun 4, 2021 | 1892 days past EOL | EOL |
| 7.2 | 7.2 | Sep 7, 2020 | Mar 7, 2022 | 1616 days past EOL | EOL |
| 7.3 | 7.3 | Feb 1, 2021 | Feb 1, 2022 | 1650 days past EOL | EOL |
| 7.4 | 7.4.4 | May 24, 2021 | May 24, 2022 | 1538 days past EOL | EOL |
| 7.5 | 7.5.3 | Aug 22, 2021 | Aug 22, 2022 | 1448 days past EOL | EOL |
| 7.6 | 7.6.3 | Dec 5, 2021 | Sep 5, 2022 | 1434 days past EOL | EOL |
| 7.5-ce LTS | 7.5.102-ce | Mar 6, 2022 | Mar 6, 2024 | 886 days past EOL | EOL |
| 7.7 | 7.7.2-HF | Mar 27, 2022 | Dec 27, 2022 | 1321 days past EOL | EOL |
| 7.8 | 7.8.2-HF2 | Jul 24, 2022 | Apr 24, 2023 | 1203 days past EOL | EOL |
| 7.9 | 7.9.101-ce | Dec 4, 2022 | Sep 11, 2023 | 1063 days past EOL | EOL |
| 8.0 | 8.0.2 | Mar 5, 2023 | Dec 19, 2023 | 964 days past EOL | EOL |
| 7.9-ce LTS | 7.9-ce | Mar 19, 2023 | Mar 19, 2025 | 508 days past EOL | EOL |
| 8.1 | 8.1.2 | Jun 25, 2023 | Apr 9, 2024 | 852 days past EOL | EOL |
| 8.2 | 8.2.1 | Oct 29, 2023 | Aug 12, 2024 | 727 days past EOL | EOL |
| 8.3 | 8.3 | Feb 11, 2024 | Nov 25, 2024 | 622 days past EOL | EOL |
| 8.4 | 8.4 | Apr 14, 2024 | Feb 5, 2025 | 550 days past EOL | EOL |
| 8.3-ce | 8.3.101-CE | May 21, 2024 | May 21, 2026 | 80 days past EOL | EOL |
| 8.5 | 8.5.2 | Jun 30, 2024 | Apr 21, 2025 | 475 days past EOL | EOL |
| 8.6 | 8.6.1 | Sep 30, 2024 | Jul 13, 2025 | 392 days past EOL | EOL |
| 7.9.103-ce | 7.9.103-CE | Nov 11, 2024 | Dec 31, 2026 | 144 days remaining | Warning |
| 8.7 | 8.7 | Feb 2, 2025 | Nov 23, 2025 | 259 days past EOL | EOL |
| 8.8 | 8.8 | Apr 28, 2025 | Feb 18, 2026 | 172 days past EOL | EOL |
| 8.9 | 8.9 | Jul 21, 2025 | May 10, 2026 | 91 days past EOL | EOL |
| 9.0 | 9.0.0 | Nov 9, 2025 | Aug 23, 2026 | 14 days remaining | Warning |
| 9.1 | 9.1.0 | Jan 25, 2026 | Nov 22, 2026 | 105 days remaining | Warning |
| 9.2 | 9.2.0 | May 3, 2026 | Feb 28, 2027 | 203 days remaining | Active |
| 9.3 | 9.3.0 | Jul 26, 2026 | May 16, 2027 | 280 days remaining | Active |
Live EOL badge for your README — updates automatically at every build.
[](https://endoflife.ai/cortex-xdr)
What does Cortex XDR end of life mean for your organization?
When a version of Cortex XDR reaches end of life, the maintainers stop issuing security patches. Vulnerabilities discovered after this date are publicly disclosed on the National Vulnerability Database, exploit code appears on GitHub, and your systems remain permanently exposed.
The CVE blind spot: Most vulnerability scanners check for known CVEs but do not flag the accumulation of unpatched vulnerabilities in EOL software. With a zero-day, nobody knows about the vulnerability. With EOL software, the vulnerability is public — listed, rated, and often weaponized — but no patch will ever exist. This is the most dangerous gap in enterprise security posture.
Organizations running EOL Cortex XDR should treat it as a vulnerability class in their risk register, apply compensating controls (network segmentation, enhanced monitoring, access restriction), and prioritize migration to a supported version.
Your options when Cortex XDR reaches end of life
There are four realistic paths. Which one is right depends far more on how long the system needs to keep running than on the version you are on today.
| Option | Best when | Watch out for |
|---|---|---|
| Move to a supported version | The system will outlive the current version's support window and you can schedule the work | Budget for compatibility testing, not just the upgrade itself — that is where the real cost sits |
| Replace the component | The project is unmaintained, or a better-supported alternative exists | The replacement has its own lifecycle and its own end-of-life date — you are changing vendors, not escaping the problem |
| Buy extended support | Migration is genuinely underway but cannot finish before the deadline, or the workload is frozen by certification or a third-party application | A bridge, not a destination — every year purchased is a year the migration still has to happen |
| Document accepted risk | The system is isolated, short-lived, or scheduled for retirement | Only defensible with real compensating controls and a written decision — auditors treat undocumented end-of-life software as a finding |
How to choose, in one question: how many more years does this system need to run? Under a year, extended support (where it exists) is usually cheaper than an emergency migration. One to three years, migrate — support purchased repeatedly costs more than doing the project once, and the project only gets harder as the version ages. Indefinitely, migrate now and plan the next migration before it surprises you.
Worth saying plainly, because vendors selling extended support rarely will: extended support is often the more expensive choice over a multi-year horizon. It is the right answer when a deadline is genuinely unreachable, not as a default. Compare the annual fee against the one-time cost of migrating before committing to either.
Extended Support Options
If you cannot migrate immediately, extended support vendors provide continued security patches for EOL Cortex XDR versions. This is a bridge, not a permanent solution — plan your migration in parallel.
Cortex XDR has 33 versions past end of life — security patches have stopped, but CVE disclosures haven't. The good news: extended support for Cortex XDR exists — vetted vendors ship security patches for years past the official date. Tell us where to reach you and we'll reply with matched options and pricing guidance.