Is jQuery Still Supported? End-of-Life Dates (2026)
Short answer
jQuery is supported and new versions continue to ship. CISA’s Known Exploited Vulnerabilities catalog lists 1 vulnerability in jQuery.
The jQuery project supports only its current 4.x branch: 1.x and 2.x are unsupported and 3.x gets critical security patches and bug fixes only, so the version you load matters more than whether you use jQuery at all.
Legacy Technology Tracker · Status as of 16 Oct 2026. Data checked 7 Oct 2026; refreshed monthly, with quarterly snapshots kept unchanged.
Risk rating
Low: supported, with new release lines continuing; no licence change recorded in the last 24 months; 1 vulnerability on CISA's KEV list (supported versions receive security fixes). How ratings work
Key facts
Every value links to its source and shows when we last checked or retrieved it. Data checked 7 Oct 2026; status as of 16 Oct 2026.
| Fact | Value | Source | Checked |
|---|---|---|---|
| Support status | SupportedjQuery releases. The HTTP Archive version-scoped count covers jQuery 1.x and 2.x (end-of-life lines). | ||
| Support end date | No end date announced | ||
| Extended support offer | HeroDevs Never-Ending Support (NES) for jQuery (third party), no end date publishedPricing basis: Per developer who commits code to the project repository (vendor-stated; no list price published) | ||
| Extended support offer | TuxCare Endless Lifecycle Support for jQuery (third party), no end date published | ||
| Known exploited vulnerabilities (CISA KEV) | 1 CVE all time; 1 added in the last 24 monthsNewest added 23 Jan 2025Matched by vendor and product name in the KEV catalog. | ||
| Home pages using jQuery, all versions (HTTP Archive, mobile) | 5,753,989 (64.6% of the crawl), Aug 2026 | ||
| Home pages using jQuery, all versions (HTTP Archive, desktop) | 3,632,266 (67.5% of the crawl), Aug 2026 | ||
| Same measure 12 months earlier (mobile) | 6,622,053 (71.2% of the crawl), Aug 2025 | ||
| Home pages on the versions in scope (HTTP Archive, mobile) | 1,631,648 (18.3% of the crawl), Aug 2026Version-scoped count = jQuery 1.x and 2.x. | ||
| npm weekly downloads (jquery) | 14,841,469 in the week to 6 Oct 202615,397,745 a year earlier | ||
| Last release | 4.0.0, 18 Jan 2026Maintainer: OpenJS Foundation | ||
| Job postings and salaries | Not tracked for this entry | — | — |
Versions in scope
jQuery releases. The HTTP Archive version-scoped count covers jQuery 1.x and 2.x (end-of-life lines). Dates per version, each with its source.
| Version | Status | Standard support ends | Extended support ends | Latest release | Source | Checked |
|---|---|---|---|---|---|---|
| 1 | Unsupported | — | — | 1.12.4 (20 May 2016) | ||
| 2 | Unsupported | — | — | 2.2.4 (20 May 2016) | ||
| 3 | Supported | — | — | 3.7.1 (28 Aug 2023) | ||
| 4 | Supported | — | — | 4.0.0 (17 Jan 2026) |
If you still run jQuery
The deadline depends on the branch. jQuery 1.x and 2.x are already unsupported, and 3.x receives only critical security patches and bug fixes. The project supports 4.x. Within 3.x, anything older than 3.5.0 is missing a cross-site scripting fix that later releases include.
The realistic options:
- Upgrade. Move 1.x or 2.x to the latest 3.x or to 4.x. jQuery publishes upgrade guides and the jQuery Migrate plugin to flag APIs that were removed or changed. Most of the work is usually in plugins written against old versions, each of which has to be tested or replaced.
- Buy commercial patches. HeroDevs and TuxCare both sell security support for end-of-life jQuery versions, and jQuery's own support page lists them. These are vendor offerings: they patch the versions you run, they do not make the application current.
- Remove jQuery. If the front end is being rebuilt on a modern framework, drop jQuery as part of that move rather than upgrading it first. Frontend modernization companies lists suppliers, and modernization costs gives budget context.
Where jQuery is loaded by a CMS theme or a third-party widget you do not control, check which version it pulls in. The update may be someone else's to make.
Frequently asked questions
Is jQuery still supported?
Only the current branch. Under jQuery's support policy, jQuery 4.x is current, 3.x receives only critical security patches and bug fixes, and the 1.x and 2.x branches are no longer supported.
Is jQuery 1.x or 2.x safe to keep using?
No fixes are issued for either branch, so vulnerabilities found in them stay open. Within 3.x, releases up to 3.4.1 lack the cross-site scripting fix shipped in jQuery 3.5.0, so update to the latest 3.x at minimum.
How do I upgrade from jQuery 1.x or 2.x?
jQuery recommends upgrading to the latest version and publishes upgrade guides and the jQuery Migrate plugin to help find removed or changed APIs (support policy). Plugins written against old versions need to be tested or replaced as part of the move.
Can I get extended support for old jQuery versions?
Yes, from commercial providers. jQuery's support page names HeroDevs and TuxCare as providers of security support for end-of-life versions under the OpenJS Foundation's Ecosystem Sustainability Program. HeroDevs states its pricing is per code-committing developer and does not publish a price.