VulertSecurity VulertSecurity

Vulnerability Database · npm · Package report

dompurify: vulnerability history, versions and safety

dompurify is a package in the npm ecosystem. Vulert records 36 vulnerabilities for it across 120 releases, from Aug 2020 to Oct 2026. Each vulnerability names the versions it affects, the fixed version to move to, and a workaround where no fix has been published.

i
36 vulnerabilities recorded C3 H4 M22 L7
i
4 with no fix published

No patched version yet — these are the ones to plan around.

See the unfixed vulnerabilities →
i
28 in the last 12 months

Most recent disclosure 22 Oct 2026.

See the disclosure history →
i
0 malicious-package vulnerabilities

No published version shipped hostile code.

See all dompurify vulnerabilities

Vulert verdict on dompurify 3.4.17 i

Updated on 23 Oct 2026

Careful: 3.4.17 has 4 known vulnerabilities, and 4 have no fix yet. Use an earlier safe version, or the workaround listed for each one.

Package health score 60/100
  • Security Unfixed issues
  • Maintenance Sustainable
  • Popularity Key ecosystem project
  • Community Active

The current release has a vulnerability with no published fix, which caps this score.

What to do: Pin an earlier, unaffected release if you can, and apply the workaround each vulnerability lists until a fix is published. No fix yet: Vulert alerts you the moment one is published. Monitor it with Vulert →

  • Current release 3.4.17 — affected i
  • Vulnerabilities on record 36 over 6 years · 28 in the last year i
  • Latest disclosure 22 Oct 2026 i
  • Highest CVSS 10.0 i
  • With no published fix 4 i
  • Depended on by 16,176 packages i
  • Stars 17,478 i
  • OpenSSF scorecard 9/10 i
  • Last release this month i
  • Licence Apache-2.0 OR MPL-2.0 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 dompurify, 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
3.4.17 12 Oct 2026 M3 L1 Apache-2.0 OR MPL-2.0 No Details →
3.4.16 23 Sep 2026 C1 H1 M3 L2 Apache-2.0 OR MPL-2.0 No Details →
3.4.15 06 Sep 2026 C1 H1 M3 L4 Apache-2.0 OR MPL-2.0 No Details →
3.4.14 19 Aug 2026 C1 H1 M3 L4 Apache-2.0 OR MPL-2.0 No Details →
3.4.13 03 Aug 2026 C1 H1 M3 L4 Apache-2.0 OR MPL-2.0 No Details →
3.4.12 11 Jul 2026 C1 H1 M4 L3 Apache-2.0 OR MPL-2.0 No Details →
3.4.11 17 Jun 2026 C1 H1 M4 L4 Apache-2.0 OR MPL-2.0 No Details →
3.4.10 12 Jun 2026 C1 H1 M5 L4 Apache-2.0 OR MPL-2.0 No Details →
3.4.9 10 Jun 2026 C1 H1 M5 L4 Apache-2.0 OR MPL-2.0 No Details →
3.4.8 03 Jun 2026 C1 H1 M5 L5 Apache-2.0 OR MPL-2.0 No Details →
3.4.7 27 May 2026 C1 H1 M5 L6 Apache-2.0 OR MPL-2.0 No Details →
3.4.6 26 May 2026 C1 H1 M7 L6 Apache-2.0 OR MPL-2.0 No Details →
3.4.5 18 May 2026 C1 H1 M9 L6 Apache-2.0 OR MPL-2.0 No Details →
3.4.4 17 May 2026 H1 Apache-2.0 OR MPL-2.0 Yes Details →
3.4.3 13 May 2026 H1 M9 L6 Apache-2.0 OR MPL-2.0 No Details →
3.4.2 30 Apr 2026 H1 M9 L6 Apache-2.0 OR MPL-2.0 No Details →
3.4.1 21 Apr 2026 H1 M9 L6 Apache-2.0 OR MPL-2.0 No Details →
3.4.0 14 Apr 2026 H1 M9 L6 Apache-2.0 OR MPL-2.0 No Details →
3.3.3 11 Mar 2026 H1 M13 L6 Apache-2.0 OR MPL-2.0 No Details →
3.3.2 05 Mar 2026 H1 M13 L6 Apache-2.0 OR MPL-2.0 No Details →
2.5.9 05 Mar 2026 H1 M14 L5 Apache-2.0 OR MPL-2.0 No Details →
3.3.1 08 Dec 2025 H1 M16 L6 Apache-2.0 OR MPL-2.0 No Details →
3.3.0 13 Oct 2025 H1 M16 L6 Apache-2.0 OR MPL-2.0 No Details →
3.2.7 17 Sep 2025 H1 M16 L6 Apache-2.0 OR MPL-2.0 No Details →
3.2.6 19 May 2025 H1 M18 L6 Apache-2.0 OR MPL-2.0 No Details →
3.2.5 03 Apr 2025 H1 M18 L6 Apache-2.0 OR MPL-2.0 No Details →
3.2.4 30 Jan 2025 H1 M18 L6 Apache-2.0 OR MPL-2.0 No Details →
3.2.3 09 Dec 2024 H1 M19 L6 Apache-2.0 OR MPL-2.0 No Details →
2.5.8 09 Dec 2024 H1 M14 L5 Apache-2.0 OR MPL-2.0 No Details →
3.2.2 29 Nov 2024 H1 M19 L6 Apache-2.0 OR MPL-2.0 No Details →
3.2.1 20 Nov 2024 H1 M19 L6 Apache-2.0 OR MPL-2.0 No Details →
3.2.0 11 Nov 2024 H1 M19 L6 Apache-2.0 OR MPL-2.0 No Details →
3.1.7 26 Sep 2024 H1 M19 L6 Apache-2.0 OR MPL-2.0 No Details →
2.5.7 26 Sep 2024 H1 M14 L5 Apache-2.0 OR MPL-2.0 No Details →
2.5.6 05 Jul 2024 H1 M14 L5 Apache-2.0 OR MPL-2.0 No Details →
3.1.6 05 Jul 2024 H1 M19 L6 Apache-2.0 OR MPL-2.0 No Details →
3.1.5 31 May 2024 H1 M19 L6 Apache-2.0 OR MPL-2.0 No Details →
2.5.5 31 May 2024 H1 M14 L5 Apache-2.0 OR MPL-2.0 No Details →
3.1.4 20 May 2024 H1 M19 L6 Apache-2.0 OR MPL-2.0 No Details →
2.5.4 20 May 2024 H1 M14 L5 Apache-2.0 OR MPL-2.0 No Details →
3.1.3 11 May 2024 H1 M19 L6 Apache-2.0 OR MPL-2.0 No Details →
2.5.3 11 May 2024 H2 M14 L5 Apache-2.0 OR MPL-2.0 No Details →
3.1.2 30 Apr 2024 H1 M15 L6 Apache-2.0 OR MPL-2.0 No Details →
2.5.2 30 Apr 2024 H2 M14 L5 Apache-2.0 OR MPL-2.0 No Details →
3.1.1 26 Apr 2024 H1 M15 L6 Apache-2.0 OR MPL-2.0 No Details →
2.5.1 26 Apr 2024 H2 M14 L5 Apache-2.0 OR MPL-2.0 No Details →
2.5.0 07 Apr 2024 H2 M14 L5 Apache-2.0 OR MPL-2.0 No Details →
3.1.0 07 Apr 2024 H1 M15 L6 Apache-2.0 OR MPL-2.0 No Details →
3.0.11 21 Mar 2024 H1 M15 L6 Apache-2.0 OR MPL-2.0 No Details →
2.4.9 21 Mar 2024 H3 M14 L5 Apache-2.0 OR MPL-2.0 No Details →
3.0.10 19 Mar 2024 H1 M15 L6 Apache-2.0 OR MPL-2.0 No Details →
2.4.8 19 Mar 2024 H3 M14 L5 Apache-2.0 OR MPL-2.0 No Details →
3.0.9 20 Feb 2024 H1 M15 L6 Apache-2.0 OR MPL-2.0 No Details →
3.0.8 05 Jan 2024 H1 M15 L6 Apache-2.0 OR MPL-2.0 No Details →
3.0.7 04 Jan 2024 H1 M15 L6 Apache-2.0 OR MPL-2.0 No Details →
3.0.6 28 Sep 2023 H1 M15 L6 Apache-2.0 OR MPL-2.0 No Details →
3.0.5 11 Jul 2023 H1 M15 L6 Apache-2.0 OR MPL-2.0 No Details →
2.4.7 11 Jul 2023 H3 M14 L5 Apache-2.0 OR MPL-2.0 No Details →
2.4.6 10 Jul 2023 H3 M14 L5 Apache-2.0 OR MPL-2.0 No Details →
3.0.4 29 Jun 2023 H1 M15 L6 Apache-2.0 OR MPL-2.0 No Details →
3.0.3 06 May 2023 H1 M15 L6 Apache-2.0 OR MPL-2.0 No Details →
3.0.2 14 Apr 2023 H1 M15 L6 Apache-2.0 OR MPL-2.0 No Details →
3.0.1 01 Mar 2023 H1 M15 L6 Apache-2.0 OR MPL-2.0 No Details →
2.4.5 01 Mar 2023 H3 M14 L5 Apache-2.0 OR MPL-2.0 No Details →
3.0.0 13 Feb 2023 H1 M14 L6 Apache-2.0 OR MPL-2.0 No Details →
2.4.4 13 Feb 2023 H3 M14 L5 Apache-2.0 OR MPL-2.0 No Details →
2.4.3 06 Jan 2023 H3 M14 L5 Apache-2.0 OR MPL-2.0 No Details →
2.4.2 05 Jan 2023 H3 M14 L5 Apache-2.0 OR MPL-2.0 No Details →
2.4.1 10 Nov 2022 C1 H3 M14 L5 Apache-2.0 OR MPL-2.0 No Details →
2.4.0 24 Aug 2022 C1 H3 M14 L5 Apache-2.0 OR MPL-2.0 No Details →
2.3.12 23 Aug 2022 C1 H3 M14 L5 Apache-2.0 OR MPL-2.0 No Details →
2.3.11 23 Aug 2022 C1 H3 M14 L5 Apache-2.0 OR MPL-2.0 No Details →
2.3.10 18 Jul 2022 C1 H3 M14 L5 Apache-2.0 OR MPL-2.0 No Details →
2.3.9 11 Jul 2022 C1 H3 M14 L5 Apache-2.0 OR MPL-2.0 No Details →
2.3.8 13 May 2022 C1 H3 M14 L5 Apache-2.0 OR MPL-2.0 No Details →
2.3.7 11 May 2022 C1 H3 M14 L5 Apache-2.0 OR MPL-2.0 No Details →
2.3.6 16 Feb 2022 C1 H3 M14 L5 Apache-2.0 OR MPL-2.0 No Details →
2.3.5 26 Jan 2022 C1 H3 M14 L5 Apache-2.0 OR MPL-2.0 No Details →
2.3.4 07 Dec 2021 C1 H3 M14 L5 Apache-2.0 OR MPL-2.0 No Details →
2.3.3 20 Sep 2021 C1 H3 M14 L5 Apache-2.0 OR MPL-2.0 No Details →
2.3.2 15 Sep 2021 C1 H3 M14 L5 Apache-2.0 OR MPL-2.0 No Details →
2.3.1 13 Aug 2021 C1 H3 M14 L5 Apache-2.0 OR MPL-2.0 No Details →
2.3.0 06 Jul 2021 C1 H3 M14 L5 Apache-2.0 OR MPL-2.0 No Details →
2.2.9 01 Jun 2021 C1 H3 M14 L5 Apache-2.0 OR MPL-2.0 No Details →
2.2.8 28 Apr 2021 C1 H3 M14 L5 Apache-2.0 OR MPL-2.0 No Details →
2.2.7 12 Mar 2021 C1 H3 M14 L5 Apache-2.0 OR MPL-2.0 No Details →
2.2.6 18 Dec 2020 C1 H3 M14 L5 Apache-2.0 OR MPL-2.0 No Details →
2.2.5 18 Dec 2020 C1 H3 M14 L5 Apache-2.0 OR MPL-2.0 No Details →
2.2.4 15 Dec 2020 C1 H3 M14 L5 Apache-2.0 OR MPL-2.0 No Details →
2.2.3 07 Dec 2020 C1 H3 M14 L5 Apache-2.0 OR MPL-2.0 No Details →
2.2.2 02 Nov 2020 C1 H3 M14 L5 Apache-2.0 OR MPL-2.0 No Details →
2.2.1 02 Nov 2020 C1 H3 M14 L5 Apache-2.0 OR MPL-2.0 No Details →
2.2.0 21 Oct 2020 C1 H3 M14 L5 Apache-2.0 OR MPL-2.0 No Details →
2.1.1 25 Sep 2020 C1 H3 M14 L5 Apache-2.0 OR MPL-2.0 No Details →
2.1.0 23 Sep 2020 C1 H3 M14 L5 Apache-2.0 OR MPL-2.0 No Details →
2.0.17 20 Sep 2020 C1 H3 M14 L5 Apache-2.0 OR MPL-2.0 No Details →
2.0.16 18 Sep 2020 C1 H3 M15 L5 Apache-2.0 OR MPL-2.0 No Details →
2.0.15 03 Sep 2020 C1 H3 M15 L5 Apache-2.0 OR MPL-2.0 No Details →
2.0.14 27 Aug 2020 C1 H3 M15 L5 Apache-2.0 OR MPL-2.0 No Details →
2.0.13 27 Aug 2020 C1 H3 M15 L5 Apache-2.0 OR MPL-2.0 No Details →
2.0.12 24 Jun 2020 C1 H3 M15 L5 — No Details →
2.0.11 06 May 2020 C1 H3 M15 L5 — No Details →
2.0.10 23 Apr 2020 C1 H3 M15 L5 — No Details →
2.0.9 22 Apr 2020 C1 H3 M15 L5 — No Details →
2.0.8 03 Feb 2020 C1 H3 M15 L5 — No Details →
2.0.7 21 Oct 2019 C1 H3 M15 L5 — No Details →
2.0.6 10 Oct 2019 C2 H3 M15 L5 — No Details →
2.0.5 08 Oct 2019 C2 H3 M15 L5 — No Details →
2.0.4 07 Oct 2019 C2 H3 M15 L5 — No Details →
2.0.3 25 Sep 2019 C2 H3 M15 L5 — No Details →
2.0.2 23 Sep 2019 C2 H3 M16 L5 — No Details →
2.0.1 19 Sep 2019 C2 H3 M16 L5 — No Details →
2.0.0 12 Sep 2019 C2 H3 M16 L5 — No Details →
1.0.11 18 Jun 2019 C2 H3 M16 L5 — No Details →
1.0.10 19 Feb 2019 C2 H3 M17 L5 — No Details →
1.0.9 14 Jan 2019 C2 H3 M16 L5 — No Details →
1.0.8 08 Sep 2018 C2 H3 M16 L5 — No Details →
1.0.7 29 Jul 2018 C2 H3 M16 L5 — No Details →
1.0.6 16 Jul 2018 C2 H3 M16 L5 — No Details →
1.0.5 16 Jun 2018 C2 H3 M16 L5 — No Details →

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

02 Disclosure history

How often vulnerabilities are recorded

  • 2020 3
  • 2023 1
  • 2024 3
  • 2025 1
  • 2026 28

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

03 Vulnerabilities

Recorded vulnerabilities for dompurify

The 5 most severe of 36 vulnerabilities recorded for this package

Search all 36 in the database →
Vulnerability Severity Fixed version ↓ Disclosed ↓
CVE-2024-47875: DOMPurify Nesting-Based mXSS Vulnerability 10.0 high 2.5.0 11 Oct 2024
GHSA-cg2g-xh64-v4q7: DOMPurify template-expression bypass in attached shadow roots 9.2 critical 3.4.17 22 Oct 2026
CVE-2024-48910: DOMPurify Prototype Pollution Vulnerability 9.1 critical 2.4.2 31 Oct 2024
CVE-2026-47423: DOMPurify XSS Vulnerability via selectedcontent Re-clone 8.2 high 3.4.5 01 Jun 2026
GHSA-mrv2-3pqr-j5jr: DOMPurify IN_PLACE hooks can leave detached event handlers active 7.6 high 3.4.17 22 Oct 2026

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 dompurify

Is dompurify safe to use?

Vulert records 36 vulnerabilities for dompurify in npm: 3 critical, 4 high, 22 medium and 7 low. 4 of them have no published fix yet, so those are the ones to avoid or mitigate.

What is dompurify's Vulert package health score?

Vulert scores dompurify 60/100, which reads as usable, but worth attention. 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). The current release has a vulnerability with no published fix, which caps this score.

Is the latest version of dompurify affected?

Yes. 3.4.17, the version you would install today, has 4 known vulnerabilities, and 4 has no published fix yet. Use an earlier unaffected release, or the workaround each vulnerability lists.

How many vulnerabilities does dompurify have?

36 vulnerabilities are recorded for dompurify in the npm ecosystem: 3 critical, 4 high, 22 medium and 7 low. The ledger on this page lists the same counts next to the date of the most recent disclosure.

How often are new dompurify vulnerabilities disclosed?

28 vulnerabilities were recorded for dompurify in the last 12 months, and the oldest entry in this database dates to 28 Aug 2020. 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 dompurify 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 dompurify for upcoming vulnerabilities?

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