jQuery 1 End of Life Date
jQuery 1 end-of-life date, support status, and CVE risk. Data reconciled from official vendor documentation and endoflife.date at every build; the source of each date is on the product page.
jQuery 1 was released on August 31, 2006. Its most recent patch is 1.12.4, published May 20, 2016.
Extended support for jQuery exists: vetted vendors ship security patches past the official date. Right now that coverage spans jQuery 1.3.x, 1.5.x, 1.6.x, 1.7.x, 1.12.x, 2.1.x, 2.2.x, 3.5.x, with 10+ post-EOL CVE fixes documented in vendor release notes across the jQuery ecosystem. Whether it covers jQuery 1 is part of what we check. Leave an email and we reply within one business day with matched options and pricing guidance, or an honest "no vendor covers this version." Free, no obligation; vendors do not pay for placement.
What does jQuery 1 end of life mean?
When jQuery 1 reaches end of life, the maintainers stop issuing security patches for this version. CVEs discovered after the EOL date are publicly disclosed on the National Vulnerability Database with no patch available. Exploit code frequently appears on GitHub within days of disclosure.
The CVE blind spot: A CVE-based scan does not show the ongoing accumulation of unpatched vulnerabilities in EOL software versions. Some scanners flag unsupported versions of common products, but coverage varies, and none of them give you the date in advance. Running jQuery 1 past its EOL date creates a growing attack surface that a clean scan result does not rule out.
Migrate to jQuery 4 or implement compensating controls — network segmentation, enhanced monitoring, restricted access — while migration is underway.