React EOL: end-of-life dates and support for every React version
React has no end-of-life date: the React team publishes none, and endoflife.date lists none. Its versioning policy says security fixes are backported to every affected major, but the last releases were 18.3.1 (April 2024), 17.0.2 (March 2021) and 16.14.0 (October 2020). OSSeva patches React 18 after upstream stops releasing and assesses 16 and 17 case by case. Checked 19 November 2026.
- Latest release
- 19.3.1
- Supported lines
- 5
- End-of-life lines
- 0
- Next end of life
- None scheduled
React publishes no EOL dates
Upgrade to React 19, or keep React 18 patched
Most applications should move to React 19, and the upgrade guides list the work. When a framework version, a dependency or a release freeze holds an application on React 18, OSSeva patches it. React 16, 17 and other versions are assessed case by case. Critical fixes ship within 48 hours and High within 7 days.
React release timeline
All React versions, release dates and end-of-life dates
| Version | Released | Active Support | Security Support | Latest | OSSeva |
|---|---|---|---|---|---|
| 19 | 2 years ago(5 Dec 2024) | Yes | Yes | 19.3.1 | – |
| 18 | 4 years and 8 months ago(29 Mar 2022) | Ended 2 years ago(5 Dec 2024) | Yes | 18.3.1 | – |
| 17 | 6 years and 1 month ago(20 Oct 2020) | Ended 4 years and 8 months ago(29 Mar 2022) | Yes | 17.0.2 | – |
| 16 | 9 years and 2 months ago(26 Sept 2017) | Ended 6 years and 1 month ago(20 Oct 2020) | Yes | 16.14.0 | – |
| 15 | 10 years and 7 months ago(7 Apr 2016) | Ended 6 years and 1 month ago(14 Oct 2020) | Yes | 15.7.0 | – |
Lifecycle data from endoflife.date (MIT licence), refreshed 21 Nov 2026. Upstream policy: react.dev. “Patched” marks end-of-life lines OSSeva ships signed, backported builds for.
React versions: release dates and last releases
React has no LTS release and no end-of-life calendar. The versioning policy on react.dev describes semver releases and three channels (Latest, Canary and Experimental), and the table below shows what that has meant for each major. The end-of-life column is empty because neither the React team nor endoflife.date publishes a date, not because a date was left out. The release timeline and version table above read endoflife.date, which marks every React line as still supported for the same reason; the last-release column below is the better signal of what is maintained.
Sources: react.dev/versions and endoflife.date, read on 19 November 2026.
| Version | Released | Last release | End-of-life date |
|---|---|---|---|
| React 19 | 5 Dec 2024 | Patch releases on 19.0, 19.1, 19.2 and 19.3 (19.3.0 on 9 Sep 2026) | None published |
| React 18 | 29 Mar 2022 | 18.3.1 (April 2024) | None published |
| React 17 | 20 Oct 2020 | 17.0.2 (March 2021) | None published |
| React 16 | 26 Sep 2017 | 16.14.0 (October 2020) | None published |
What the React team backports to old majors
The versioning policy says that when the team learns of a security vulnerability in React, it releases a backported fix for all major versions that are affected. The table lists three advisories checked on cveawg.mitre.org and in the GitHub advisory on 19 November 2026, with the same affected range and fixed versions in both. A search of GitHub's advisory database for the react and react-dom packages on that day returns entries from 2013 and 2018 only; the 2025 and 2026 advisories are in the react-server-dom packages, whose affected ranges start at 19.0.0.
Security fixes and the versions that carry them.
| CVE | What it is | Fixed in |
|---|---|---|
| CVE-2018-6341 | react-dom: ReactDOMServer did not escape user-supplied attribute names (cross-site scripting) | 16.0.1, 16.1.2, 16.2.1, 16.3.3, 16.4.2 |
| CVE-2025-55182 | Pre-authentication remote code execution in the React Server Components packages (CVSS 10.0), on CISA's Known Exploited Vulnerabilities list since 5 Dec 2025 | 19.0.1, 19.1.2, 19.2.1 |
| CVE-2026-126187 | Unauthenticated remote code execution in the same packages, rare typed-array case (CVSS 9.5 on version 4.0) | 19.0.9, 19.1.10, 19.2.9, 19.3.1 |
What this shows: the team patched every affected minor in each case, including five 16.x minors in 2018. What it does not show: a commitment to cut a release for a major that has already stopped getting them. A future react-dom flaw that reaches 18 depends on the team doing so, and that is the gap OSSeva covers.
Who patches React after upstream stops releasing?
Two companies sell security patches for React lines that no longer get releases: HeroDevs and OSSeva. The table lists what each says, with HeroDevs' row taken from its own React page, read on 19 November 2026.
Facts from each provider's own page, read on 19 November 2026. Nothing here comes from a third party.
| Provider | React versions the page lists | Fix timing the page states |
|---|---|---|
| HeroDevs (NES for React) | 16 and 17, covering react and react-dom | CVE fixes across all severity levels under contractual SLAs mapped to severity and exploit risk; no fix times stated on the page |
| OSSeva | 18 after upstream stops releasing. 16, 17 and other versions case by case | Critical within 48 hours, High within 7 days |
How we compared: each row uses only what the provider's own page states. Where HeroDevs is the better fit: its page lists React 16 and 17 as supported versions, while OSSeva assesses those case by case. Check each vendor's page for current terms.
Upgrade React or keep patching it?
Upgrade when you can. Going from 17 to 18, ReactDOM.render keeps working with a warning and React 17 behaviour until you switch to createRoot, so roots can move one at a time. Going from 18 to 19, the modern JSX transform is required, propTypes checks and defaultProps on function components are removed, and errors thrown in render are no longer re-thrown, so error reporting that relied on that needs the onUncaughtError and onCaughtError options (both from the react.dev upgrade guides). Next.js 15 and later set React 19 as the minimum.
Keep an older line patched when a dependency pinned to a React peer range, a framework release or a release freeze holds the application there, and use the time to plan the move. That is a judgement about your estate, not a statement that React 18 is unsafe: no 2025 or 2026 advisory in GitHub's database lists a version below 19.0.0 for react or react-dom.
Running an end-of-life React version?
OSSeva keeps end-of-life React patched with signed builds and backported CVE fixes, documents it for your auditor, and can run it for you, so the upgrade happens on your schedule rather than the project’s.
React extended supportIs React 18 end of life?
React has not declared an end of life for React 18, and neither the versioning policy nor endoflife.date gives a date. Its last release was 18.3.1 in April 2024, and react.dev lists 19.3 as the latest version. OSSeva patches React 18 where upstream does not.
Is React 17 end of life?
React has not declared an end of life for React 17. Its last release was 17.0.2 in March 2021. OSSeva assesses React 17 case by case through a version coverage check.
Is React 16 end of life?
React has not declared an end of life for React 16. Its last release was 16.14.0 in October 2020, and the one react-dom advisory in GitHub's database that affects 16.x is CVE-2018-6341, fixed in 16.4.2. OSSeva assesses React 16 case by case through a version coverage check.
Does React have an LTS version?
No. React's versioning policy describes semver releases on a Latest channel plus Canary and Experimental channels, and publishes no LTS releases or support windows. It says security fixes are backported to every affected major version.
When does React 19 reach end of life?
No date is published. React 19 is the current major, with patch releases continuing on 19.0, 19.1, 19.2 and 19.3 per react.dev/versions.
What happens when a vulnerability affects an old React version?
The versioning policy says the team backports a fix to all affected majors. In 2018 that meant patches to each of five 16.x minors. If a flaw reaches a major that has stopped getting releases and the team does not cut one, a third-party provider such as OSSeva can backport the fix.
What is the latest React version?
19.3.1, released 14 Oct 2026, on the 19 line. Other supported lines: 18, 17, 16 and 15.
Which React versions are still supported?
19, 18, 17, 16 and 15. Every other line has reached end of life, per the dates in the table above.
Can I get security patches for an end-of-life React version?
Yes. OSSeva provides React extended support after upstream support ends, on the Patch, Assure and Operate tiers. See React extended support for the versions covered.
Get a quote
Still running an end-of-life React?
Tell us the versions and the estate size. We will tell you whether to upgrade or keep it patched, and what each costs.
Prefer to talk or read more first?