JQUERY COVERAGE
jQuery 1.x and 2.x are unsupported. Your patching does not have to be.
jQuery extended support from OSSeva: jquery.com says the 1.x and 2.x branches are no longer supported, with last releases on 20 May 2016, and that 3.x gets critical security fixes only. 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 and assesses other versions case by case. Critical fixes ship within 48 hours and High within 7 days.
| Who it is for | Teams running jQuery 1.x or 2.x in applications, CMS themes, admin consoles or plugins that a scanner flags and that cannot move to 3.5 or later yet |
|---|---|
| What you get | Patched jQuery 1.x and 2.x builds as a drop-in file or package, with a documented patch history. Assure adds an upgrade path assessment and 24/7 reactive support. |
| How it is priced | Per application, not per page or per developer. Ask for a quote. |
| What happens next | You send your work email, we confirm which jQuery versions your pages load, 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





jQuery support status by branch
jquery.com states that only the latest version is supported, that 1.x and 2.x are no longer supported, and that 3.x receives critical security patches and bug fixes only. It publishes no end-of-life dates. Release data is from endoflife.date, read on 19 November 2026.
| Branch | First release | Latest release | Status on jquery.com |
|---|---|---|---|
| 4.x | 17 Jan 2026 | 4.1.0 (17 Nov 2026) | Current branch |
| 3.x | 9 Jun 2016 | 3.8.0 (17 Nov 2026) | Critical security patches and bug fixes only |
| 2.x | 18 Apr 2013 | 2.2.4 (20 May 2016) | No longer supported |
| 1.x | 31 Aug 2006 | 1.12.4 (20 May 2016) | No longer supported |
jQuery version support (jquery.com) →jQuery EOL dates for every branch →
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 range and on the first fixed version, and 1.x and 2.x have no fix at all, so the only fix is moving to the fixed branch.
| CVE | What it is | Severity | Affected | Fixed in |
|---|---|---|---|---|
| CVE-2020-11022 | Cross-site scripting when HTML from an untrusted source, even after sanitizing, is passed to .html(), .append() and similar methods | 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 a source object that has an enumerable __proto__ property | Medium (GitHub advisory) | Before 3.4.0 (1.1.4 and later in the GitHub advisory) | 3.4.0 |
GitHub advisory for CVE-2020-11022 →GitHub advisory for CVE-2020-11023 →GitHub advisory for CVE-2019-11358 →
Why the jQuery fix is hard to take
Upgrading is often the right long-term answer. OSSeva sells patches, not rewrites, so these are the facts from the jQuery upgrade guides to size the project honestly.
- 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>. Code that builds HTML with self-closing tags on non-void elements breaks (jQuery 3.5 upgrade guide).
- Reverting that behaviour brings the vulnerability back. The same guide says that redefining htmlPrefilter to the old version loses the 3.5.0 security fix, and that ordinary HTML sanitizing is then not enough.
- 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). The jQuery Migrate plugin exists to surface these.
React extended support →Node.js extended support, for the build and server runtime →
Why now
jQuery 1.x and 2.x are no longer supported
The jQuery support page says only the latest version is supported and that the 1.x and 2.x branches are no longer supported. Their last releases were 1.12.4 and 2.2.4 on 20 May 2016.
CVE-2020-11022 and CVE-2020-11023: no fix below jQuery 3.5.0
Both CVE records and both GitHub advisories give the same fix: jQuery 3.5.0. 1.x and 2.x never received it. CVE-2020-11023 has been on CISA's Known Exploited Vulnerabilities list since 23 January 2025.
Even jQuery 3.x is on critical fixes only
jquery.com says jQuery 3.x receives only critical security patches and bug fixes, and recommends upgrading to 4.x, released on 17 January 2026. Older 3.x versions below 3.5.0 are in the same affected range as 1.x and 2.x.
Versions covered
All versions below receive active CVE patches from OSSeva. Version numbers in monospace are exact release identifiers.
| Version | Status | Active CVEs |
|---|---|---|
| 1.x(No longer supported; last release 1.12.4) | EOL | Clean |
| 2.x(No longer supported; last release 2.2.4) | EOL | Clean |
Running a jQuery 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 jQuery 1.x and 2.x after end of life.
- Backported security fixes for jQuery 1.x and 2.x
- 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
- jQuery 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 jQuery versions does OSSeva patch?
jQuery 1.x and 2.x after end of life. 3.x and other versions are assessed case by case through a version coverage check.
Is jQuery 1.x or 2.x end of life?
Yes. jquery.com says the 1.x and 2.x branches are no longer supported. The last releases were 1.12.4 and 2.2.4, both on 20 May 2016. The project gives no end-of-life date.
How fast are jQuery 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 upgrade jQuery code to 3.x or 4.x?
No. OSSeva sells security patches for the jQuery version you run. Moving to a current jQuery is often the right long-term step, and Assure includes an upgrade path assessment, but the code changes stay with your team.
How is OSSeva jQuery 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 jQuery patched and supported?
Tell us your jQuery 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?