VulertSecurity VulertSecurity

Vulnerability Database · npm · Package report

jquery: vulnerability history, versions and safety

jquery is a package in the npm ecosystem. Vulert records 11 vulnerabilities for it across 50 releases, from Jan 2018 to Jun 2023. Each vulnerability names the versions it affects, the fixed version to move to, and a workaround where no fix has been published.

i
11 vulnerabilities recorded H1 M10
i
0 with no fix published

Every vulnerability has a patched version to move to.

i
0 in the last 12 months

Nothing new recorded in the last year.

See the disclosure history →
i
0 malicious-package vulnerabilities

No published version shipped hostile code.

See all jquery vulnerabilities

Vulert verdict on jquery 4.0.0 i

Updated on 23 Oct 2026

Good news: 4.0.0, the version you would install today, has no known vulnerabilities. Older releases do — the table below lists all 11.

Package health score 85/100
  • Security Minor issues
  • Maintenance Sustainable
  • Popularity Key ecosystem project
  • Community Moderate

What to do: Stay on 4.0.0 or newer. This can change: a vulnerability disclosed tomorrow can affect 4.0.0 too — Vulert watches the package and alerts you if that happens. Monitor it with Vulert →

  • Current release 4.0.0 — unaffected i
  • Vulnerabilities on record 11 over 5 years · 0 in the last year i
  • Latest disclosure 26 Jun 2023 i
  • Highest CVSS 7.5 i
  • With no published fix 0 i
  • Depended on by 5,494 packages i
  • Stars 59,933 i
  • OpenSSF scorecard 6/10 i
  • Last release 9 months ago i
  • Licence MIT i

Version list, release dates, licence and dependants published by the npm registry, refreshed 23 Oct 2026. Licence information is not legal advice.

Concerned about your application's security?

Vulert continues monitoring your dependencies and alerts you when new vulnerabilities are disclosed. No installation and no source-code access required.

01 Versions

Which versions are affected

Every version Vulert tracks for jquery, newest first, with the vulnerabilities recorded against each one. A version showing none has no vulnerability in the Vulert database — open it for the full picture on that release.

i
Version Released Vulert vulnerabilities Licence Fix published Details
4.0.0 18 Jan 2026 none MIT — Details →
4.0.0-rc.2 18 Jan 2026 none MIT — Details →
4.0.0-rc.1 11 Aug 2025 none MIT — Details →
4.0.0-beta.2 17 Jul 2024 none MIT — Details →
4.0.0-beta 06 Feb 2024 none MIT — Details →
3.7.1 28 Aug 2023 none MIT — Details →
3.7.0 11 May 2023 none MIT — Details →
3.6.4 08 Mar 2023 none MIT — Details →
3.6.3 20 Dec 2022 none MIT — Details →
3.6.2 13 Dec 2022 none MIT — Details →
3.6.1 26 Aug 2022 none MIT — Details →
3.6.0 02 Mar 2021 none MIT — Details →
3.5.1 04 May 2020 none MIT — Details →
3.5.0 10 Apr 2020 none MIT — Details →
3.4.1 01 May 2019 M4 MIT Yes Details →
3.4.0 10 Apr 2019 M4 MIT Yes Details →
3.3.1 20 Jan 2018 M6 MIT Yes Details →
3.3.0 19 Jan 2018 M6 MIT Yes Details →
3.2.1 20 Mar 2017 M6 MIT Yes Details →
3.2.0 16 Mar 2017 M6 MIT Yes Details →
3.1.1 22 Sep 2016 M6 MIT Yes Details →
3.1.0 07 Jul 2016 M6 MIT Yes Details →
3.0.0 09 Jun 2016 M6 MIT Yes Details →
3.0.0-rc1 20 May 2016 H1 M6 MIT Yes Details →
2.2.4 20 May 2016 M6 MIT Yes Details →
1.12.4 20 May 2016 M5 MIT Yes Details →
2.2.3 05 Apr 2016 M6 MIT Yes Details →
1.12.3 05 Apr 2016 M5 MIT Yes Details →
2.2.2 17 Mar 2016 M6 MIT Yes Details →
1.12.2 17 Mar 2016 M5 MIT Yes Details →
2.2.1 22 Feb 2016 M6 MIT Yes Details →
1.12.1 22 Feb 2016 M6 MIT Yes Details →
3.0.0-beta1 14 Jan 2016 M6 MIT Yes Details →
2.2.0 08 Jan 2016 M6 MIT Yes Details →
1.12.0 08 Jan 2016 M6 MIT Yes Details →
3.0.0-alpha1 13 Jul 2015 M6 MIT Yes Details →
1.11.3 28 Apr 2015 M6 MIT Yes Details →
2.1.4 28 Apr 2015 M5 MIT Yes Details →
2.1.3 18 Dec 2014 M5 MIT Yes Details →
1.11.2 17 Dec 2014 M6 MIT Yes Details →
2.1.2 17 Dec 2014 M5 MIT Yes Details →
1.9.1 17 Jul 2014 M6 MIT Yes Details →
1.11.1 01 May 2014 M6 MIT Yes Details →
2.1.1 01 May 2014 M5 MIT Yes Details →
1.11.1-rc2 21 Apr 2014 M6 MIT Yes Details →
2.1.1-rc2 21 Apr 2014 M5 MIT Yes Details →
1.11.1-rc1 18 Apr 2014 M6 MIT Yes Details →
2.1.1-rc1 18 Apr 2014 M5 MIT Yes Details →
1.11.1-beta1 24 Mar 2014 M6 MIT Yes Details →
2.1.1-beta1 24 Mar 2014 M5 MIT Yes Details →
2.1.0 23 Jan 2014 M5 MIT Yes Details →
1.11.0 23 Jan 2014 M6 MIT Yes Details →
2.1.0-rc1 17 Jan 2014 M5 MIT Yes Details →
1.11.0-rc1 16 Jan 2014 M6 MIT Yes Details →
1.11.0-beta3 06 Jan 2014 M6 MIT Yes Details →
2.1.0-beta3 20 Dec 2013 M5 MIT Yes Details →
2.1.0-beta2 15 Nov 2013 M5 MIT Yes Details →
1.8.3 01 Dec 2012 M8 MIT Yes Details →
1.8.2 11 Nov 2012 M8 MIT Yes Details →
1.7.3 01 Jul 2012 M8 MIT Yes Details →
1.7.2 01 May 2012 M8 MIT Yes Details →
1.6.3 12 Sep 2011 M8 MIT Yes Details →
1.6.2 06 Jul 2011 M9 MIT Yes Details →
1.5.1 19 Mar 2011 M9 MIT Yes Details →

All 64 versions Vulert tracks for this package. Severity counts are the vulnerabilities recorded against that exact release.

02 Disclosure history

How often vulnerabilities are recorded

  • 2018 2
  • 2019 2
  • 2020 4
  • 2022 1
  • 2023 2

Counted by the year Vulert recorded each vulnerability — the same date the table below shows as disclosed. 0 of the 11 were recorded in the last 12 months.

03 Vulnerabilities

Recorded vulnerabilities for jquery

The 5 most severe of 11 vulnerabilities recorded for this package

Search all 11 in the database →
Vulnerability Severity Fixed version ↓ Disclosed ↓
CVE-2016-10707: Denial of Service in jquery 7.5 high 3.0.0 22 Jan 2018
CVE-2020-11022: Potential XSS vulnerability in jQuery 6.9 medium 3.5.0 29 Apr 2020
CVE-2020-11023: Potential XSS vulnerability in jQuery 6.9 medium 3.5.0 29 Apr 2020
CVE-2019-11358: XSS in jQuery as used in Drupal, Backdrop CMS, and other products 6.1 medium 3.4.0 26 Apr 2019
CVE-2020-7656: Cross-Site Scripting in jquery 6.1 medium 1.9.0 20 May 2020

Vulnerability wrong, a fix missing, or a package we should cover? Report it and we will fix the record. Report Vulnerability Provide Feedback

Updated: 23/Oct/2026 · Vulnerabilities in our DB: 524315

Subscribe to Vulert on Telegram
Daily digest of new CVEs, critical and high severity, affected packages and fixes — plus a weekly roundup.
Join the channel →

Questions

About jquery

Is jquery safe to use?

Vulert records 11 vulnerabilities for jquery in npm: 0 critical, 1 high, 10 medium and 0 low. Every one of them has a published fix, so the practical answer is to run a supported release and keep it patched.

What is jquery's Vulert package health score?

Vulert scores jquery 85/100, which reads as healthy. The score weighs the vulnerability record (40), maintenance and release cadence (25), adoption from dependents and stars (20) and community signals such as the OpenSSF scorecard and forks (15).

Is the latest version of jquery affected?

No. 4.0.0, the version you would install today, has no vulnerabilities on record against it. Earlier releases do — the version table above lists each release with what affects it.

Which version of jquery should I use?

4.0.0 is the version Vulert recommends for the affected releases. The version table above lists every release with the vulnerabilities recorded against it, so you can confirm the range you actually run.

How many vulnerabilities does jquery have?

11 vulnerabilities are recorded for jquery in the npm ecosystem: 0 critical, 1 high, 10 medium and 0 low. The ledger on this page lists the same counts next to the date of the most recent disclosure.

How often are new jquery vulnerabilities disclosed?

0 vulnerabilities were recorded for jquery in the last 12 months, and the oldest entry in this database dates to 22 Jan 2018. Recency matters more than a lifetime total: it shows how actively new issues are being disclosed for the package you are considering.

Which versions of jquery are affected?

Each vulnerability on this page lists the affected version range and the fixed version to move to. Open the vulnerability for the version you actually run — fixes are specific to a release line, not to the package as a whole.

How do I monitor jquery for upcoming vulnerabilities?

Upload the manifest or SBOM for your application at vulert.com/scanner and Vulert keeps checking the jquery version you actually run against new disclosures, then alerts you when one affects it. There is no installation and no source-code access required.