REACT COVERAGE
React has no end-of-life date. Old React lines still stop getting releases.
React extended support from OSSeva: React publishes no end-of-life date, but React 18 has had no release since 18.3.1 in April 2024, and the React team backports security fixes only to majors it judges affected. OSSeva patches React 18 after upstream stops releasing and assesses React 16, 17 and other versions case by case. Critical fixes ship within 48 hours and High within 7 days.
| Who it is for | Teams running React 18, or 16 and 17, where a scanner or auditor flags an unmaintained major and the move to React 19 is not scheduled |
|---|---|
| What you get | Patched react and react-dom builds for the line you run, with a documented patch history. Assure adds an upgrade path assessment and 24/7 reactive support. |
| How it is priced | Per application, not per developer or per component. Ask for a quote. |
| What happens next | You send your work email, we confirm your React version and framework, and you get a coverage plan. |
Reply within 1 business day · No commitment · or book a 15-minute call
Last reviewed
Trusted globally by enterprises





What the React team says about support
React's versioning policy describes semver releases and three release channels (Latest, Canary and Experimental). It states no end-of-life dates and no LTS programme. On security it says that when the team learns of a vulnerability in React, it releases a backported fix for all major versions affected. Release data below is from react.dev/versions and endoflife.date, read on 19 November 2026.
| Line | Released | Last release (react.dev) | Replaced by next major (endoflife.date) | End-of-life date |
|---|---|---|---|---|
| 19 | 5 Dec 2024 | Patch releases on 19.0 to 19.3 (19.3.0 on 9 Sep 2026) | Not yet | None published |
| 18 | 29 Mar 2022 | 18.3.1 (April 2024) | 5 Dec 2024 | None published |
| 17 | 20 Oct 2020 | 17.0.2 (March 2021) | 29 Mar 2022 | None published |
| 16 | 26 Sep 2017 | 16.14.0 (October 2020) | 20 Oct 2020 | None published |
OSSeva reads "past support" for React as: the line has no release in the react.dev list for years and the team has not announced one. That is a judgement, not a vendor-declared end of life.
React versioning policy (react.dev) →React versions and releases (react.dev) →
How the backport policy has played out
Each CVE below was checked on cveawg.mitre.org and in the GitHub advisory on 19 November 2026, and both give the same affected range and fixed versions. A search of the GitHub advisory database for the react and react-dom packages on the same day returns entries from 2013 and 2018 only. The 2025 and 2026 advisories are in react-server-dom-webpack, react-server-dom-parcel and react-server-dom-turbopack, and none lists a version below 19.0.0.
| CVE | What it is | Fixed in |
|---|---|---|
| CVE-2018-6341 | react-dom: ReactDOMServer did not escape user-supplied attribute names, giving cross-site scripting (Medium, 6.1 in the GitHub advisory) | 16.0.1, 16.1.2, 16.2.1, 16.3.3 and 16.4.2, one patch for each affected 16.x minor |
| 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 and 19.2.1 |
| CVE-2026-126187 | Unauthenticated remote code execution in the same packages in a rare typed-array case (Critical, 9.5 on CVSS 4.0) | 19.0.9, 19.1.10, 19.2.9 and 19.3.1 |
What this shows: in each case above the team patched every affected minor, including five 16.x minors in 2018. What it does not show: any promise for a major that has already stopped releasing. A future react-dom flaw that reaches 18 depends on the team choosing to cut an 18.x release.
React blog on CVE-2025-55182 (3 Dec 2025) →GitHub advisory for CVE-2026-126187 →GitHub advisory for CVE-2018-6341 →
What a move to React 19 involves
Migration is often the right long-term answer, and OSSeva sells patches rather than rewrites. These are the steps the React upgrade guides list, so you can size the project before choosing.
- 17 to 18: ReactDOM.render still runs on 18 but logs a warning and keeps React 17 behaviour until you switch to createRoot, so roots can move one at a time (React 18 upgrade guide).
- 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 new onUncaughtError and onCaughtError options (React 19 upgrade guide).
- Frameworks: the Next.js 15 upgrade guide sets React 19 as the minimum version, which is why a Next.js 14 estate and a React 18 estate are often the same project.
Next.js extended support →React EOL dates and last releases →Node.js extended support, for the build and server runtime →
Why now
React 18 has had no release since April 2024
react.dev lists 18.3.1 (April 2024) as the last 18.x release, 17.0.2 (March 2021) for 17 and 16.14.0 (October 2020) for 16. React publishes no end-of-life dates, and endoflife.date shows none for any React line.
Fixes are backported only to majors the team judges affected
React's versioning policy says a vulnerability fix is backported to every affected major version. The 2025 and 2026 advisories so far sit in the react-server-dom packages, whose affected ranges start at 19.0.0, so no 18.x release has been needed. A flaw in react-dom itself that reached 18 is the case OSSeva covers.
A React major upgrade touches every component tree
The React upgrade guides list the work: switch ReactDOM.render to createRoot going from 17 to 18, and adopt the modern JSX transform, drop propTypes and defaultProps checks on function components and rework render-error handling going from 18 to 19.
Versions covered
All versions below receive active CVE patches from OSSeva. Version numbers in monospace are exact release identifiers.
| Version | Status | Active CVEs |
|---|---|---|
| 18(No EOL date published; last release 18.3.1) | Extended | Clean |
Running a React version or build not listed here?
What you get
Three tiers — pick the level of engagement that matches your team's operational needs and compliance requirements.
OSSeva Patch
Security patches for React 18 after upstream stops releasing.
- Backported security fixes for React 18 (react and react-dom)
- Critical CVEs fixed within 48 hours, High within 7 days
- Signed artifacts (GPG + Sigstore)
- CVE disclosure notifications
- Architecture review
- 24/7 managed operations
OSSeva Assure
Patch plus compliance documentation and upgrade planning.
- Everything in Patch
- SOC 2 / HIPAA attestation package
- React upgrade path assessment
- 24/7 reactive support
OSSeva Operate
Full MSP: 24/7 monitoring, 15-min P1 response, named engineers.
- Everything in Assure
- 24/7 application and runtime monitoring
- 15-minute P1 incident response SLA
- Named senior engineer on your account
All tiers priced per cluster/application — not per core.
Which React versions does OSSeva patch?
React 18 after upstream stops releasing for it; its last release was 18.3.1 in April 2024. React 16, 17 and other versions are assessed case by case through a version coverage check.
Is React end of life?
React publishes no end-of-life dates, and endoflife.date lists none for any line. The versioning policy on react.dev says vulnerability fixes are backported to every affected major version, and react.dev lists the last release of each major. A line that has stopped getting releases is what this page means by past support.
How fast are React vulnerabilities patched?
Critical vulnerabilities (CVSS 9.0 or higher) within 48 hours and High within 7 days. Everything else goes into a scheduled batch.
Does OSSeva migrate or rewrite React applications?
No. OSSeva sells security patches for the React version you run. Moving to React 19 is often the right long-term step, and Assure includes an upgrade path assessment, but the engineering stays with your team.
How is OSSeva React support priced?
It is priced per application. Request a quote and a senior engineer replies within 1 business day.
Get a quote
Ready to get React patched and supported?
Tell us your React versions and an engineer replies within 1 business day with coverage and a price. Prefer a call? It takes 15 minutes.
Prefer to talk or read more first?