VulertSecurity VulertSecurity

Vulnerability Database · npm · Package report

jsdom: vulnerability history, versions and safety

jsdom is a package in the npm ecosystem. Vulert records 1 vulnerability for it across 62 releases, first recorded in May 2022. Each vulnerability names the versions it affects, the fixed version to move to, and a workaround where no fix has been published.

i
1 vulnerabilities recorded L1
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 jsdom vulnerabilities

Vulert verdict on jsdom 30.1.3 i

Updated on 22 Oct 2026

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

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

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

  • Current release 30.1.3 — unaffected i
  • Vulnerabilities on record 1 over 1 year · 0 in the last year i
  • Latest disclosure 24 May 2022 i
  • Highest CVSS 0.0 i
  • With no published fix 0 i
  • Depended on by 2,652 packages i
  • Stars 21,720 i
  • OpenSSF scorecard 6/10 i
  • Last release this month i
  • Licence MIT i

Version list, release dates, licence and dependants published by the npm registry, refreshed 22 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 jsdom, 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
30.1.3 15 Oct 2026 none MIT — Details →
30.1.2 04 Oct 2026 none MIT — Details →
30.1.1 22 Sep 2026 none MIT — Details →
30.1.0 17 Sep 2026 none MIT — Details →
30.0.1 29 Jul 2026 none MIT — Details →
30.0.0 27 Jul 2026 none MIT — Details →
29.1.1 30 Apr 2026 none MIT — Details →
29.1.0 27 Apr 2026 none MIT — Details →
29.0.2 07 Apr 2026 none MIT — Details →
29.0.1 20 Mar 2026 none MIT — Details →
29.0.0 15 Mar 2026 none MIT — Details →
28.1.0 15 Feb 2026 none MIT — Details →
28.0.0 02 Feb 2026 none MIT — Details →
27.4.0 26 Dec 2025 none MIT — Details →
27.3.0 08 Dec 2025 none MIT — Details →
27.2.0 12 Nov 2025 none MIT — Details →
27.1.0 31 Oct 2025 none MIT — Details →
27.0.1 18 Oct 2025 none MIT — Details →
27.0.0 13 Sep 2025 none MIT — Details →
27.0.0-beta.3 31 Aug 2025 none MIT — Details →
27.0.0-beta.2 08 Jun 2025 none MIT — Details →
27.0.0-beta.1 06 May 2025 none MIT — Details →
27.0.0-beta.0 19 Apr 2025 none MIT — Details →
26.1.0 13 Apr 2025 none MIT — Details →
26.0.0 09 Jan 2025 none MIT — Details →
25.0.1 22 Sep 2024 none MIT — Details →
25.0.0 25 Aug 2024 none MIT — Details →
24.1.3 25 Aug 2024 none MIT — Details →
24.1.2 25 Aug 2024 none MIT — Details →
24.1.1 21 Jul 2024 none MIT — Details →
24.1.0 26 May 2024 none MIT — Details →
24.0.0 21 Jan 2024 none MIT — Details →
23.2.0 07 Jan 2024 none MIT — Details →
23.1.0 05 Jan 2024 none MIT — Details →
23.0.1 30 Nov 2023 none MIT — Details →
23.0.0 26 Nov 2023 none MIT — Details →
22.1.0 27 May 2023 none MIT — Details →
22.0.0 02 May 2023 none MIT — Details →
21.1.2 01 May 2023 none MIT — Details →
21.1.1 12 Mar 2023 none MIT — Details →
21.1.0 22 Jan 2023 none MIT — Details →
21.0.0 07 Jan 2023 none MIT — Details →
20.0.3 20 Nov 2022 none MIT — Details →
20.0.2 30 Oct 2022 none MIT — Details →
20.0.1 02 Oct 2022 none MIT — Details →
20.0.0 19 Jun 2022 none MIT — Details →
19.0.0 02 Dec 2021 none MIT — Details →
18.1.1 21 Nov 2021 none MIT — Details →
18.1.0 12 Nov 2021 none MIT — Details →
18.0.1 01 Nov 2021 none MIT — Details →
18.0.0 08 Oct 2021 none MIT — Details →
17.0.0 13 Aug 2021 none MIT — Details →
16.7.0 01 Aug 2021 none MIT — Details →
16.6.0 23 May 2021 none MIT — Details →
16.5.3 11 Apr 2021 none MIT — Details →
16.5.2 28 Mar 2021 none MIT — Details →
16.5.1 13 Mar 2021 none MIT — Details →
16.5.0 07 Mar 2021 none MIT — Details →
16.4.0 08 Aug 2020 L1 MIT Yes Details →
16.3.0 10 Jul 2020 L1 MIT Yes Details →
16.2.2 30 Mar 2020 L1 MIT Yes Details →
16.2.1 09 Mar 2020 L1 MIT Yes Details →
16.2.0 16 Feb 2020 L1 MIT Yes Details →
16.1.0 01 Feb 2020 L1 MIT Yes Details →
16.0.1 20 Jan 2020 L1 MIT Yes Details →
16.0.0 13 Jan 2020 L1 MIT Yes Details →
15.2.1 04 Nov 2019 L1 MIT Yes Details →
15.2.0 14 Oct 2019 L1 MIT Yes Details →
15.1.1 28 May 2019 L1 MIT Yes Details →
15.1.0 12 May 2019 L1 MIT Yes Details →
15.0.0 21 Apr 2019 L1 MIT Yes Details →
14.1.0 21 Apr 2019 L1 MIT Yes Details →
14.0.0 10 Mar 2019 L1 MIT Yes Details →
13.2.0 24 Jan 2019 L1 MIT Yes Details →
13.1.0 15 Dec 2018 L1 MIT Yes Details →
13.0.0 29 Oct 2018 L1 MIT Yes Details →
12.2.0 08 Oct 2018 L1 MIT Yes Details →
12.1.0 30 Sep 2018 L1 MIT Yes Details →
12.0.0 19 Aug 2018 L1 MIT Yes Details →
11.12.0 27 Jul 2018 L1 MIT Yes Details →
11.11.0 23 May 2018 L1 MIT Yes Details →
11.10.0 30 Apr 2018 L1 MIT Yes Details →
11.9.0 23 Apr 2018 L1 MIT Yes Details →
11.8.0 16 Apr 2018 L1 MIT Yes Details →
11.7.0 01 Apr 2018 L1 MIT Yes Details →
11.6.2 30 Jan 2018 L1 MIT Yes Details →
11.6.1 25 Jan 2018 L1 MIT Yes Details →
11.6.0 22 Jan 2018 L1 MIT Yes Details →
11.5.1 26 Nov 2017 L1 MIT Yes Details →
11.4.0 19 Nov 2017 L1 MIT Yes Details →
11.3.0 30 Sep 2017 L1 MIT Yes Details →
11.2.0 21 Aug 2017 L1 MIT Yes Details →
11.1.0 03 Jul 2017 L1 MIT Yes Details →
11.0.0 21 May 2017 L1 MIT Yes Details →
10.1.0 01 May 2017 L1 MIT Yes Details →
10.0.0 24 Apr 2017 L1 MIT Yes Details →
9.12.0 12 Mar 2017 L1 MIT Yes Details →
9.11.0 11 Feb 2017 L1 MIT Yes Details →
9.10.0 04 Feb 2017 L1 MIT Yes Details →
9.9.1 19 Dec 2016 L1 MIT Yes Details →
9.9.0 19 Dec 2016 L1 — Yes Details →
9.8.3 25 Oct 2016 L1 — Yes Details →
9.8.2 25 Oct 2016 L1 — Yes Details →
9.8.1 25 Oct 2016 L1 — Yes Details →
9.8.0 16 Oct 2016 L1 — Yes Details →
9.7.1 15 Oct 2016 L1 — Yes Details →
9.7.0 15 Oct 2016 L1 — Yes Details →
9.6.0 02 Oct 2016 L1 — Yes Details →
9.5.0 03 Sep 2016 L1 — Yes Details →
9.4.5 30 Aug 2016 L1 — Yes Details →
9.4.4 30 Aug 2016 L1 — Yes Details →
9.4.3 30 Aug 2016 L1 — Yes Details →
9.4.2 11 Aug 2016 L1 — Yes Details →
9.4.1 05 Jul 2016 L1 — Yes Details →
9.4.0 02 Jul 2016 L1 — Yes Details →
9.3.0 26 Jun 2016 L1 — Yes Details →
9.2.1 28 May 2016 L1 — Yes Details →
9.2.0 24 May 2016 L1 — Yes Details →
9.1.0 15 May 2016 L1 — Yes Details →
9.0.0 06 May 2016 L1 — Yes Details →

The newest 120 of 289 versions Vulert tracks. Severity counts are the vulnerabilities recorded against that exact release.

02 Disclosure history

How often vulnerabilities are recorded

  • 2022 1

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

03 Vulnerabilities

Recorded vulnerabilities for jsdom

The 1 most severe of 1 vulnerabilities recorded for this package

Search all 1 in the database →
Vulnerability Severity Fixed version ↓ Disclosed ↓
CVE-2021-20066: Insufficient Granularity of Access Control in JSDom 0.0 low 16.5.0 24 May 2022

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

Updated: 22/Oct/2026 · Vulnerabilities in our DB: 524173

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 jsdom

Is jsdom safe to use?

Vulert records 1 vulnerabilities for jsdom in npm: 0 critical, 0 high, 0 medium and 1 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 jsdom's Vulert package health score?

Vulert scores jsdom 91/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 jsdom affected?

No. 30.1.3, 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.

How many vulnerabilities does jsdom have?

1 vulnerability is recorded for jsdom in the npm ecosystem: 0 critical, 0 high, 0 medium and 1 low. The ledger on this page lists the same counts next to the date of the most recent disclosure.

How often are new jsdom vulnerabilities disclosed?

0 vulnerabilities were recorded for jsdom in the last 12 months, and the oldest entry in this database dates to 24 May 2022. 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 jsdom 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 jsdom for upcoming vulnerabilities?

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