jQuery EOL: support status and end of life for every jQuery version
jQuery 1.x and 2.x are no longer supported, per jquery.com, and their last releases were 1.12.4 and 2.2.4 on 20 May 2016. jQuery 3.x gets critical security patches and bug fixes only, and 4.x is the current branch. CVE-2020-11023 affects jQuery 1.0.3 up to 3.5.0, and CVE-2020-11022 affects 1.12.0 up to 3.5.0. OSSeva patches jQuery 1.x and 2.x after end of life. Checked 19 November 2026.
- Latest release
- 4.1.0
- Supported lines
- 2
- End-of-life lines
- 2
- Next end of life
- None scheduled
jQuery 1.x and 2.x are unsupported
Upgrade to 3.5 or later, or keep 1.x and 2.x patched
Most pages should move to a current jQuery. When a plugin, a CMS theme or a legacy admin console pins the page to 1.x or 2.x, OSSeva patches both. Other jQuery versions are assessed case by case. Critical fixes ship within 48 hours and High within 7 days.
Who patches jQuery after end of life
OSSeva provides jQuery extended support: patched, signed builds for jQuery 2 and 1 after upstream support ends, plus 24/7 operations on the Operate tier.
jQuery release timeline
All jQuery versions, release dates and end-of-life dates
| Version | Released | Active Support | Security Support | Latest | OSSeva |
|---|---|---|---|---|---|
| 4 | 10 months ago(17 Jan 2026) | Yes | Yes | 4.1.0 | – |
| 3 | 10 years and 5 months ago(9 Jun 2016) | Ended 10 months ago(17 Jan 2026) | Yes | 3.8.0 | – |
| 2 | 13 years and 7 months ago(18 Apr 2013) | Ended | Ended | 2.2.4 | Patched |
| 1 | 20 years and 3 months ago(31 Aug 2006) | Ended | Ended | 1.12.4 | Patched |
Lifecycle data from endoflife.date (MIT licence), refreshed 22 Nov 2026. Upstream policy: jquery.com. “Patched” marks end-of-life lines OSSeva ships signed, backported builds for.
jQuery support status by branch
jquery.com publishes no end-of-life dates. Its support page says only the latest version is supported, that the 1.x and 2.x branches are no longer supported, and that 3.x receives only critical security patches and bug fixes. The table adds the release dates from endoflife.date.
Sources: jquery.com/support and endoflife.date, read on 19 November 2026.
| Branch | First release | Latest release | Status on jquery.com |
|---|---|---|---|
| jQuery 4.x | 17 Jan 2026 | 4.1.0 (17 Nov 2026) | Current branch |
| jQuery 3.x | 9 Jun 2016 | 3.8.0 (17 Nov 2026) | Critical security patches and bug fixes only |
| jQuery 2.x | 18 Apr 2013 | 2.2.4 (20 May 2016) | No longer supported |
| jQuery 1.x | 31 Aug 2006 | 1.12.4 (20 May 2016) | No longer supported |
jQuery CVEs that scanners flag
Each CVE below was checked on cveawg.mitre.org and in the GitHub advisory for the npm package on 19 November 2026. Both agree on the affected range and on the first fixed version. jQuery 1.x and 2.x never received a fix, so the only upstream fix is moving to the fixed branch.
Affected ranges and fixes from the CVE records and GitHub advisories.
| CVE | What it is | Severity | Affected | Fixed in |
|---|---|---|---|---|
| CVE-2020-11022 | Cross-site scripting when HTML from an untrusted source, even after sanitizing, reaches .html(), .append() or similar | Medium (6.9, CVSS 3.1) | 1.12.0 to before 3.5.0 | 3.5.0 |
| CVE-2020-11023 | The same, for HTML containing option elements. On CISA's Known Exploited Vulnerabilities list since 23 Jan 2025. | Medium (6.9, CVSS 3.1) | 1.0.3 to before 3.5.0 | 3.5.0 |
| CVE-2019-11358 | Prototype pollution through jQuery.extend(true, {}, ...) with an enumerable __proto__ property | Medium (GitHub advisory) | Before 3.4.0 (1.1.4 and later per GitHub) | 3.4.0 |
Who patches jQuery after end of life?
jquery.com's support page itself names two commercial providers for unsupported versions, HeroDevs and TuxCare, and says the OpenJS Foundation's Ecosystem Sustainability Program gives a framework for commercial support of end-of-life open source, read on 19 November 2026. HeroDevs' own jQuery page lists the versions below. OSSeva is a third option.
Facts from jquery.com and HeroDevs' own page, read on 19 November 2026. Nothing here comes from a third party.
| Provider | jQuery versions the page lists | Fix timing the page states |
|---|---|---|
| HeroDevs (NES for jQuery) | 1.3.x, 1.5.x, 1.6.x, 1.7.x, 1.12.x, 2.1.x, 2.2.x and 3.5.x | FAQ says security issues are top priority and fixed the same day where possible; SLA on request |
| OSSeva | 1.x and 2.x. 3.x and other versions case by case | Critical within 48 hours, High within 7 days |
How we compared: HeroDevs' row uses only its own jQuery page, read on 19 November 2026. We did not read TuxCare's own page, so it appears only as jquery.com's statement above. Where HeroDevs is the better fit: it lists specific old lines such as 1.3.x and 1.7.x, and 3.5.x, by name; OSSeva names 1.x and 2.x and assesses others case by case.
Upgrade jQuery or keep patching it?
Upgrade when you can, but know why it is hard. The 3.5.0 fix is a behaviour change: jQuery.htmlPrefilter now returns its input unchanged, so a string such as <div/><span/> no longer expands to <div></div><span></span>, and code that builds HTML with self-closing tags on non-void elements breaks (jQuery 3.5 upgrade guide). The same guide says redefining htmlPrefilter to restore the old behaviour loses the security fix.
From 1.x or 2.x the jump also crosses the 3.0 breaking changes: .load(), .unload() and .error() are removed, .size() is removed, document-ready handlers run asynchronously and jQuery.Deferred follows Promises/A+ (jQuery 3.0 upgrade guide). Keep 1.x or 2.x patched when a plugin or theme is pinned to them, and use the jQuery Migrate plugin to find what breaks while you plan the move.
Running an end-of-life jQuery version?
OSSeva keeps end-of-life jQuery 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.
jQuery extended supportIs jQuery 1.x end of life?
Yes. jquery.com says the 1.x branch is no longer supported, and the last release was 1.12.4 on 20 May 2016. The project gives no end-of-life date. OSSeva patches jQuery 1.x after end of life.
Is jQuery 2.x end of life?
Yes. jquery.com says the 2.x branch is no longer supported, and the last release was 2.2.4 on 20 May 2016. OSSeva patches jQuery 2.x after end of life.
Is jQuery 3.x end of life?
Not formally. jquery.com says jQuery 3.x will only receive critical security patches and bug fixes, and encourages upgrading to 4.x, released on 17 January 2026. endoflife.date lists no end date for 3.x.
Which jQuery version fixes CVE-2020-11022 and CVE-2020-11023?
jQuery 3.5.0. Both CVE records and both GitHub advisories list affected versions up to but not including 3.5.0, and name 3.5.0 as the fix. jQuery 1.x and 2.x have no fixed release.
What is the latest jQuery version?
jQuery 4.1.0, released on 17 November 2026, on the 4.x branch. The latest 3.x release is 3.8.0 on the same day, per endoflife.date.
Who provides jQuery support after end of life?
The jQuery project fixes only the latest version, plus critical fixes on 3.x. jquery.com names HeroDevs and TuxCare as commercial providers for unsupported versions. OSSeva patches jQuery 1.x and 2.x after end of life.
Which jQuery versions are still supported?
4 and 3. 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 jQuery version?
Yes. OSSeva ships signed builds with backported CVE fixes for jQuery 2 and 1 after upstream support ends, on the Patch, Assure and Operate tiers, so you can stay on the version you run while you plan the upgrade.
Get a quote
Still running an end-of-life jQuery?
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?