VulertSecurity VulertSecurity

Vulnerability Database · npm · Package report

highlight.js: vulnerability history, versions and safety

highlight.js is a package in the npm ecosystem. Vulert records 2 vulnerabilities for it across 76 releases, from Nov 2020 to Dec 2020. Each vulnerability names the versions it affects, the fixed version to move to, and a workaround where no fix has been published.

i
2 vulnerabilities recorded M2
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 highlight.js vulnerabilities

Vulert verdict on highlight.js 11.12.0 i

Updated on 22 Oct 2026

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

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

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

  • Current release 11.12.0 — unaffected i
  • Vulnerabilities on record 2 over 1 year · 0 in the last year i
  • Latest disclosure 04 Dec 2020 i
  • Highest CVSS 5.8 i
  • With no published fix 0 i
  • Depended on by 10,965 packages i
  • Stars 25,004 i
  • OpenSSF scorecard 5/10 i
  • Last release 2 months ago i
  • Licence BSD-3-Clause 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 highlight.js, 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
11.12.0 12 Aug 2026 none BSD-3-Clause — Details →
11.11.2 11 Aug 2026 none BSD-3-Clause — Details →
11.11.1 25 Dec 2024 none BSD-3-Clause — Details →
11.11.0 14 Dec 2024 none BSD-3-Clause — Details →
11.10.0 06 Jul 2024 none BSD-3-Clause — Details →
11.9.0 09 Oct 2023 none BSD-3-Clause — Details →
11.8.0 29 Apr 2023 none BSD-3-Clause — Details →
11.7.0 23 Nov 2022 none BSD-3-Clause — Details →
11.6.0 13 Jul 2022 none BSD-3-Clause — Details →
11.5.1 11 Apr 2022 none BSD-3-Clause — Details →
11.5.0 12 Mar 2022 none BSD-3-Clause — Details →
11.4.0 06 Jan 2022 none BSD-3-Clause — Details →
11.3.1 17 Oct 2021 none BSD-3-Clause — Details →
11.3.0 17 Oct 2021 none BSD-3-Clause — Details →
11.2.0 02 Aug 2021 none BSD-3-Clause — Details →
11.1.0 08 Jul 2021 none BSD-3-Clause — Details →
11.0.1 04 Jun 2021 none BSD-3-Clause — Details →
10.7.3 04 Jun 2021 none BSD-3-Clause — Details →
11.0.0 30 May 2021 none BSD-3-Clause — Details →
11.0.0-beta1 16 May 2021 none BSD-3-Clause — Details →
11.0.0-beta0 04 May 2021 none BSD-3-Clause — Details →
11.0.0-alpha1 22 Apr 2021 none BSD-3-Clause — Details →
11.0.0-alpha0 13 Apr 2021 none BSD-3-Clause — Details →
10.7.2 04 Apr 2021 none BSD-3-Clause — Details →
10.7.1 21 Mar 2021 none BSD-3-Clause — Details →
10.7.0 20 Mar 2021 none BSD-3-Clause — Details →
10.6.0 08 Feb 2021 none BSD-3-Clause — Details →
10.5.0 23 Dec 2020 none BSD-3-Clause — Details →
10.4.1 03 Dec 2020 none BSD-3-Clause — Details →
9.18.5 19 Nov 2020 M1 BSD-3-Clause Yes Details →
9.18.4 18 Nov 2020 M1 BSD-3-Clause Yes Details →
10.4.0 18 Nov 2020 M1 BSD-3-Clause Yes Details →
10.4.0-beta1 15 Nov 2020 M1 BSD-3-Clause Yes Details →
10.4.0-beta0 13 Nov 2020 M1 BSD-3-Clause Yes Details →
10.3.2 29 Oct 2020 M1 BSD-3-Clause Yes Details →
10.3.1 17 Oct 2020 M1 BSD-3-Clause Yes Details →
10.3.0 17 Oct 2020 M1 BSD-3-Clause Yes Details →
10.2.1 01 Oct 2020 M1 BSD-3-Clause Yes Details →
10.2.0 07 Sep 2020 M1 BSD-3-Clause Yes Details →
9.18.3 29 Jul 2020 M1 BSD-3-Clause Yes Details →
9.18.2 28 Jul 2020 M1 BSD-3-Clause Yes Details →
10.1.2 23 Jul 2020 M1 BSD-3-Clause Yes Details →
10.1.1 16 Jun 2020 M1 BSD-3-Clause Yes Details →
10.1.0 11 Jun 2020 M1 BSD-3-Clause Yes Details →
10.0.3 12 May 2020 M1 BSD-3-Clause Yes Details →
10.0.2 03 May 2020 M1 BSD-3-Clause Yes Details →
10.0.1 26 Apr 2020 M1 BSD-3-Clause Yes Details →
10.0.0 21 Apr 2020 M1 BSD-3-Clause Yes Details →
10.0.0-beta.0 10 Mar 2020 M1 BSD-3-Clause Yes Details →
9.18.1 01 Feb 2020 M2 BSD-3-Clause Yes Details →
9.18.0 20 Jan 2020 M2 BSD-3-Clause Yes Details →
9.17.1 12 Dec 2019 M2 BSD-3-Clause Yes Details →
9.17.0 11 Dec 2019 M2 BSD-3-Clause Yes Details →
9.16.2 01 Nov 2019 M2 BSD-3-Clause Yes Details →
9.16.1 31 Oct 2019 M2 BSD-3-Clause Yes Details →
9.15.10 20 Aug 2019 M2 BSD-3-Clause Yes Details →
9.15.9 31 Jul 2019 M2 BSD-3-Clause Yes Details →
9.15.8 29 May 2019 M2 BSD-3-Clause Yes Details →
9.15.7 29 May 2019 M2 BSD-3-Clause Yes Details →
9.15.6 26 Feb 2019 M2 BSD-3-Clause Yes Details →
9.15.5 25 Feb 2019 M2 BSD-3-Clause Yes Details →
9.15.2 25 Feb 2019 M2 BSD-3-Clause Yes Details →
9.15.1 25 Feb 2019 M2 BSD-3-Clause Yes Details →
9.14.2 01 Feb 2019 M2 BSD-3-Clause Yes Details →
9.14.1 30 Jan 2019 M2 BSD-3-Clause Yes Details →
9.13.1 17 Oct 2018 M2 BSD-3-Clause Yes Details →
9.13.0 13 Oct 2018 M2 BSD-3-Clause Yes Details →
9.12.0 31 May 2017 M2 BSD-3-Clause Yes Details →
9.11.0 19 Apr 2017 M2 BSD-3-Clause Yes Details →
9.10.0 08 Mar 2017 M2 BSD-3-Clause Yes Details →
9.9.0 14 Dec 2016 M2 BSD-3-Clause Yes Details →
9.8.0 02 Nov 2016 M2 BSD-3-Clause Yes Details →
9.7.0 21 Sep 2016 M2 BSD-3-Clause Yes Details →
9.6.0 10 Aug 2016 M2 BSD-3-Clause Yes Details →
9.5.0 28 Jun 2016 M2 BSD-3-Clause Yes Details →
9.4.0 17 May 2016 M2 BSD-3-Clause Yes Details →
9.3.0 05 Apr 2016 M2 BSD-3-Clause Yes Details →
9.2.0 23 Feb 2016 M2 BSD-3-Clause Yes Details →
9.1.0 06 Jan 2016 M2 BSD-3-Clause Yes Details →
9.0.0 02 Dec 2015 M2 BSD-3-Clause Yes Details →
8.9.1 19 Oct 2015 M1 BSD-3-Clause Yes Details →
8.9.0 19 Oct 2015 M1 BSD-3-Clause Yes Details →
8.8.0 06 Sep 2015 M1 BSD-3-Clause Yes Details →
8.7.0 28 Jul 2015 M1 BSD-3-Clause Yes Details →
8.6.0 20 May 2015 M1 BSD-3-Clause Yes Details →
8.5.0 03 Apr 2015 M1 BSD-3-Clause Yes Details →
8.4.0 18 Nov 2014 M1 BSD-3-Clause Yes Details →
8.3.0 09 Oct 2014 M1 BSD-3-Clause Yes Details →
8.2.0 20 Aug 2014 M1 BSD-3-Clause Yes Details →
8.1.0 08 Jul 2014 M1 BSD-3-Clause Yes Details →
8.0.0 09 Jan 2014 M1 BSD-3-Clause Yes Details →
7.5.0 20 Nov 2013 M1 BSD-3-Clause Yes Details →
7.4.0 30 Oct 2013 M1 BSD-3-Clause Yes Details →
7.3.0 13 Oct 2012 M1 BSD-3-Clause Yes Details →
7.2.0 28 Aug 2012 M1 BSD-3-Clause Yes Details →
7.1.0 11 Aug 2012 M1 BSD-3-Clause Yes Details →
7.0.1 04 Jun 2012 M1 BSD-3-Clause Yes Details →
1.2.0 24 Apr 2012 M1 BSD-3-Clause Yes Details →
1.1.1 26 Feb 2012 M1 BSD-3-Clause Yes Details →
1.1.0 30 Jan 2012 M1 BSD-3-Clause Yes Details →
1.0.4 26 Jan 2012 M1 — Yes Details →
1.0.3 26 Jan 2012 M1 — Yes Details →
1.0.2 24 Sep 2011 M1 — Yes Details →
1.0.1 18 Sep 2011 M1 — Yes Details →
1.0.0 15 Jul 2011 M1 — Yes Details →

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

02 Disclosure history

How often vulnerabilities are recorded

  • 2020 2

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

03 Vulnerabilities

Recorded vulnerabilities for highlight.js

The 2 most severe of 2 vulnerabilities recorded for this package

Search all 2 in the database →
Vulnerability Severity Fixed version ↓ Disclosed ↓
CVE-2020-26237: Prototype Pollution in highlight.js 5.8 medium 9.18.2 24 Nov 2020
ReDOS Vulnerabilities in highlight.js N/A medium 10.4.1 04 Dec 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: 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 highlight.js

Is highlight.js safe to use?

Vulert records 2 vulnerabilities for highlight.js in npm: 0 critical, 0 high, 2 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 highlight.js's Vulert package health score?

Vulert scores highlight.js 90/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 highlight.js affected?

No. 11.12.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 highlight.js should I use?

11.12.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 highlight.js have?

2 vulnerabilities are recorded for highlight.js in the npm ecosystem: 0 critical, 0 high, 2 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 highlight.js vulnerabilities disclosed?

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

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