Summary iPlain-English security verdict for JQuery, generated from its current health score, actively-exploited vulnerabilities, and latest supported version.
JQuery's security status could not be assessed at the last sync — vulnerability data was unavailable.
Disclosure trend iNew CVEs published for JQuery each year (NVD). A higher bar means more disclosures that year — more scrutiny, not necessarily less safe.
Patch priority — what to act on iThe issues to fix first — actively exploited (CISA KEV) first, then by exploitation probability (EPSS), then severity. Each row's "→ fixed in" is the earliest version that patches it; "see advisory" means no fixed version is published.
No urgent unpatched issues identified. ✓
Get alerted about JQuery
Be emailed the moment JQuery gets a newly exploited vulnerability (CISA KEV) or a release reaches end of life. Free · double opt-in · unsubscribe anytime.
We email only on real events for JQuery — no marketing, no sharing, and we never know what you run. Track your whole stack →
Frequently asked
Is JQuery safe and patched?
JQuery's security status could not be assessed at the last sync — vulnerability data was unavailable.
What should I do about JQuery now?
Review the patch-priority list, apply the available fixes (or move to the latest release), and confirm against JQuery's official advisory.
Why is JQuery listed on IsItPatched?
JQuery was added automatically because CISA's Known Exploited Vulnerabilities (KEV) catalog flagged it as actively exploited in the wild. IsItPatched tracks its known CVEs, severity (CVSS), exploitation probability (EPSS) and KEV status from public data; its version and lifecycle mapping is verified over time.
Informational only, from public data (NVD · CISA KEV · EPSS · endoflife.date), and can lag or miss vendor-specific fixes. Always confirm against JQuery's official advisory before you patch or upgrade.