Complete end-of-life dates, support windows, and security status for all React versions. Data sourced from endoflife.date and official vendor documentation. Updated at every deploy.
| Version | Latest Release | Release Date | EOL Date | Days | Status |
|---|---|---|---|---|---|
| 15 | 15.7.0 | Apr 7, 2016 | Already EOL | Supported | Active |
| 16 | 16.14.0 | Sep 26, 2017 | Already EOL | Supported | Active |
| 17 | 17.0.2 | Oct 20, 2020 | Already EOL | Supported | Active |
| 18 | 18.3.1 | Mar 29, 2022 | Already EOL | Supported | Active |
| 19 | 19.2.6 | Dec 5, 2024 | Already EOL | Supported | Active |
When a React version 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 React 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.
If you cannot migrate immediately, extended support vendors provide continued security patches for EOL React versions. This is a bridge, not a permanent solution — plan your migration in parallel.
Extended support for React beyond EOL — security patches and compliance.
Learn More →Upload your dependency file and scan your entire stack for EOL risk in seconds. Free, no account required.
Stack Scanner →