VulertSecurity VulertSecurity

Vulnerability Database · npm · Package report

sanitize-html: vulnerability history, versions and safety

sanitize-html is a package in the npm ecosystem. Vulert records 17 vulnerabilities for it across 120 releases, from Nov 2018 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
17 vulnerabilities recorded C1 H1 M14 L1
i
1 with no fix published

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

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

Most recent disclosure 21 Oct 2026.

See the disclosure history →
i
0 malicious-package vulnerabilities

No published version shipped hostile code.

See all sanitize-html vulnerabilities

Vulert verdict on sanitize-html 2.18.1 i

Updated on 22 Oct 2026

Careful: 2.18.1 has 1 known vulnerability, and 1 has 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 Moderate

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 2.18.1 — affected i
  • Vulnerabilities on record 17 over 7 years · 9 in the last year i
  • Latest disclosure 21 Oct 2026 i
  • Highest CVSS 9.3 i
  • With no published fix 1 i
  • Depended on by 3,160 packages i
  • Stars 4,653 i
  • OpenSSF scorecard 4/10 i
  • Last release this month 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 sanitize-html, 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
2.18.1 14 Oct 2026 C1 MIT No Details →
2.18.0 30 Sep 2026 C1 M1 MIT No Details →
2.17.7 13 Aug 2026 C1 M2 L1 MIT No Details →
2.17.6 10 Jul 2026 C1 M3 MIT No Details →
2.17.5 10 Jun 2026 C1 M4 MIT No Details →
2.17.5-alpha.1 04 Jun 2026 C1 M5 MIT No Details →
2.17.4 13 May 2026 C1 M5 MIT No Details →
2.17.3 15 Apr 2026 C1 M5 MIT No Details →
2.17.2 18 Mar 2026 C1 M6 MIT No Details →
2.17.1 18 Feb 2026 C1 M5 MIT No Details →
2.17.0 14 May 2025 C1 M5 MIT No Details →
2.16.0 16 Apr 2025 C1 M5 MIT No Details →
2.15.0 19 Mar 2025 C1 M5 MIT No Details →
2.14.0 18 Dec 2024 C1 M5 MIT No Details →
2.13.1 03 Oct 2024 C1 M5 MIT No Details →
2.13.0 20 Mar 2024 C1 M5 MIT No Details →
2.12.1 22 Feb 2024 C1 M5 MIT No Details →
2.12.0 21 Feb 2024 C1 M6 MIT No Details →
2.11.0 21 Jun 2023 C1 M6 MIT No Details →
2.10.0 17 Feb 2023 C1 M6 MIT No Details →
2.9.0 01 Feb 2023 C1 M6 MIT No Details →
2.8.1 21 Dec 2022 C1 M6 MIT No Details →
2.8.0 12 Dec 2022 C1 M6 MIT No Details →
2.7.3 27 Oct 2022 C1 M6 MIT No Details →
2.7.2 15 Sep 2022 C1 M6 MIT No Details →
2.7.1 20 Jul 2022 C1 M6 MIT No Details →
2.7.0 04 Feb 2022 C1 H1 M6 MIT No Details →
2.6.1 08 Dec 2021 C1 H1 M6 MIT No Details →
2.6.0 23 Nov 2021 C1 H1 M6 MIT No Details →
2.5.3 02 Nov 2021 C1 H1 M6 MIT No Details →
2.5.2 13 Oct 2021 C1 H1 M6 MIT No Details →
2.5.1 14 Sep 2021 C1 H1 M6 MIT No Details →
2.5.0 08 Sep 2021 C1 H1 M6 MIT No Details →
2.4.0 20 May 2021 C1 H1 M6 MIT No Details →
2.3.3 19 Mar 2021 C1 H1 M6 MIT No Details →
2.3.2 26 Jan 2021 C1 H1 M6 MIT No Details →
2.3.1 22 Jan 2021 C1 H1 M7 MIT No Details →
2.3.0 16 Dec 2020 C1 H1 M8 MIT No Details →
2.2.0 02 Dec 2020 C1 H1 M8 MIT No Details →
2.1.2 04 Nov 2020 C1 H1 M8 MIT No Details →
2.1.1 21 Oct 2020 C1 H1 M8 MIT No Details →
2.1.0 07 Oct 2020 C1 H1 M8 MIT No Details →
2.0.0 23 Sep 2020 C1 H1 M8 MIT No Details →
1.27.5 23 Sep 2020 C1 H1 M9 MIT No Details →
2.0.0-rc.2 09 Sep 2020 C1 H1 M8 MIT No Details →
2.0.0-rc.1 26 Aug 2020 C1 H1 M8 MIT No Details →
1.27.4 26 Aug 2020 C1 H1 M9 MIT No Details →
1.27.3 12 Aug 2020 C1 H1 M9 MIT No Details →
2.0.0-beta.2 12 Aug 2020 C1 H1 M8 MIT No Details →
1.27.2 29 Jul 2020 C1 H1 M9 MIT No Details →
2.0.0-beta 29 Jul 2020 C1 H1 M8 MIT No Details →
1.27.1 15 Jul 2020 C1 H1 M9 MIT No Details →
1.27.0 17 Jun 2020 C1 H1 M9 MIT No Details →
1.26.0 03 Jun 2020 C1 H1 M9 MIT No Details →
1.25.0 29 May 2020 C1 H1 M9 MIT No Details →
1.24.0 20 May 2020 C1 H1 M9 MIT No Details →
1.23.0 09 Apr 2020 C1 H1 M9 MIT No Details →
1.22.1 12 Mar 2020 C1 H1 M9 MIT No Details →
1.22.0 23 Feb 2020 C1 H1 M9 MIT No Details →
1.21.1 17 Jan 2020 C1 H1 M9 MIT No Details →
1.21.0 17 Jan 2020 C1 H1 M9 MIT No Details →
1.20.1 25 Apr 2019 C1 H1 M9 MIT No Details →
1.20.0 17 Dec 2018 C1 H1 M9 MIT No Details →
1.19.3 05 Dec 2018 C1 H1 M9 MIT No Details →
1.19.2 03 Dec 2018 C1 H1 M9 MIT No Details →
1.19.1 28 Sep 2018 C1 H1 M9 MIT No Details →
1.19.0 12 Sep 2018 C1 H1 M9 MIT No Details →
1.18.5 05 Sep 2018 C1 H1 M9 MIT No Details →
1.18.4 02 Aug 2018 C1 H1 M9 MIT No Details →
1.18.3 01 Aug 2018 C1 H1 M9 MIT No Details →
1.18.2 20 Feb 2018 C1 H1 M9 MIT No Details →
1.18.1 20 Feb 2018 C1 H1 M9 MIT No Details →
1.18.0 20 Feb 2018 C1 H1 M9 MIT No Details →
1.17.0 15 Jan 2018 C1 H1 M8 MIT No Details →
1.16.3 12 Dec 2017 C1 H1 M8 MIT No Details →
1.16.2 12 Dec 2017 C1 H1 M8 MIT No Details →
1.16.1 21 Nov 2017 C1 H1 M8 MIT No Details →
1.16.0 21 Nov 2017 C1 H1 M8 MIT No Details →
1.15.0 30 Oct 2017 C1 H1 M8 MIT No Details →
1.14.3 30 Oct 2017 C1 H1 M8 MIT No Details →
1.14.2 30 Oct 2017 C1 H1 M8 MIT No Details →
1.14.1 13 Jan 2017 C1 H1 M8 MIT No Details →
1.14.0 13 Jan 2017 C1 H1 M8 MIT No Details →
1.13.0 19 Jul 2016 C1 H1 M8 MIT No Details →
1.12.0 16 Jun 2016 C1 H1 M8 MIT No Details →
1.11.4 28 Mar 2016 C1 H1 M8 MIT No Details →
1.11.3 13 Jan 2016 C1 H1 M9 MIT No Details →
1.11.2 01 Dec 2015 C1 H1 M9 MIT No Details →
1.11.1 13 Oct 2015 C1 H1 M9 MIT No Details →
1.11.0 08 Oct 2015 C1 H1 M9 MIT No Details →
1.10.1 28 Sep 2015 C1 H1 M9 MIT No Details →
1.10.0 31 Aug 2015 C1 H1 M9 MIT No Details →
1.9.0 18 Aug 2015 C1 H1 M9 MIT No Details →
1.8.0 10 Aug 2015 C1 H1 M8 MIT No Details →
1.7.2 22 Jul 2015 C1 H1 M8 MIT No Details →
1.7.1 21 Jul 2015 C1 H1 M8 MIT No Details →
1.7.0 03 Jun 2015 C1 H1 M8 MIT No Details →
1.6.1 18 Feb 2015 C1 H1 M8 MIT No Details →
1.6.0 13 Feb 2015 C1 H1 M8 MIT No Details →
1.5.3 06 Feb 2015 C1 H1 M8 MIT No Details →
1.5.2 26 Jan 2015 C1 H1 M8 — No Details →
1.5.1 11 Jan 2015 C1 H1 M8 — No Details →
1.5.0 07 Jan 2015 C1 H1 M8 — No Details →
1.4.3 14 Oct 2014 C1 H1 M8 — No Details →
1.4.2 26 Sep 2014 C1 H1 M9 — No Details →
1.4.1 17 Sep 2014 C1 H1 M9 — No Details →
1.3.0 18 Jul 2014 C1 H1 M9 — No Details →
1.2.3 18 Jul 2014 C1 H1 M9 — No Details →
1.2.2 17 Jul 2014 C1 H1 M10 — No Details →
1.2.1 05 Jul 2014 C1 H1 M10 — No Details →
1.2.0 03 Jul 2014 C1 H1 M10 — No Details →
1.1.8 19 Jun 2014 C1 H1 M10 — No Details →
1.1.7 11 Jun 2014 C1 H1 M10 — No Details →
1.1.5 19 May 2014 C1 H1 M10 — No Details →
1.1.4 16 May 2014 C1 H1 M10 — No Details →
1.1.3 01 Apr 2014 C1 H1 M10 — No Details →
1.1.2 25 Mar 2014 C1 H1 M10 — No Details →
1.1.1 20 Feb 2014 C1 H1 M10 — No Details →
1.1.0 29 Jan 2014 C1 H1 M10 — No Details →
1.0.3 17 Jan 2014 C1 H1 M10 — No Details →

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

02 Disclosure history

How often vulnerabilities are recorded

  • 2018 2
  • 2020 1
  • 2021 2
  • 2022 1
  • 2024 1
  • 2025 1
  • 2026 9

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

03 Vulnerabilities

Recorded vulnerabilities for sanitize-html

The 5 most severe of 17 vulnerabilities recorded for this package

Search all 17 in the database →
Vulnerability Severity Fixed version ↓ Disclosed ↓
CVE-2026-44990: Critical XSS Vulnerability in sanitize-html Package 9.3 critical No fix published 14 May 2026
CVE-2022-25887: Vulnerability in sanitize-html Package 7.5 high 2.7.1 31 Aug 2022
CVE-2016-1000237: Cross-Site Scripting in sanitize-html 6.1 medium 1.4.3 16 Apr 2020
CVE-2026-40186: sanitize-html Package Allows Bypass of allowedTags via Entity-Decoded Text 6.1 medium 2.17.3 16 Apr 2026
CVE-2017-16017: Cross-Site Scripting in sanitize-html 6.1 medium 1.2.3 09 Nov 2018

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 sanitize-html

Is sanitize-html safe to use?

Vulert records 17 vulnerabilities for sanitize-html in npm: 1 critical, 1 high, 14 medium and 1 low. 1 of them has no published fix yet, so that is the one to avoid or mitigate.

What is sanitize-html's Vulert package health score?

Vulert scores sanitize-html 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 sanitize-html affected?

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

Which version of sanitize-html should I use?

2.18.1 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 sanitize-html have?

17 vulnerabilities are recorded for sanitize-html in the npm ecosystem: 1 critical, 1 high, 14 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 sanitize-html vulnerabilities disclosed?

9 vulnerabilities were recorded for sanitize-html in the last 12 months, and the oldest entry in this database dates to 09 Nov 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 sanitize-html 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 sanitize-html for upcoming vulnerabilities?

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