VulertSecurity VulertSecurity

Vulnerability Database · Debian · Package report

node-prismjs: vulnerability history, versions and safety

node-prismjs is a package in the Debian ecosystem. Vulert records 9 vulnerabilities for it across 8 releases, from Aug 2020 to Mar 2025. Each vulnerability names the versions it affects, the fixed version to move to, and a workaround where no fix has been published.

i
9 vulnerabilities recorded U9
i
1 with no fix published

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

See the unfixed vulnerabilities →
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 node-prismjs vulnerabilities

Vulert verdict on node-prismjs i

Updated on 23 Oct 2026

Careful: one of the 9 vulnerabilities Vulert records for this package has no fix yet. Plan around that one, or apply its workaround. The rest have a fixed version to move to.

Long-term outlook: usable, but needs attention 9 vulnerabilities on record across 4 years, none in the last year.

What to do: Plan around the 1 vulnerability with no published fix: each lists the affected range and any workaround that reduces exposure. No fix yet: Vulert alerts you the moment one is published. Monitor it with Vulert →

  • Vulnerabilities on record 9 over 4 years · 0 in the last year i
  • Latest disclosure 03 Mar 2025 i
  • Highest CVSS 7.5 i
  • With no published fix 1 i

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 holds for node-prismjs, newest first, with the vulnerabilities that name it. A version with a count of zero has no recorded vulnerabilities; open a version to see the vulnerabilities it is exposed to.

Newest 8 of 8 versions on record. Severity counts are the vulnerabilities recorded against that exact release.

02 Disclosure history

How often vulnerabilities are recorded

  • 2020 2
  • 2021 4
  • 2022 2
  • 2025 1

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

03 Vulnerabilities

Recorded vulnerabilities for node-prismjs

The 5 most severe of 9 vulnerabilities recorded for this package

Search all 9 in the database →
Vulnerability Severity Fixed version ↓ Disclosed ↓
Cross-Site Scripting Vulnerability in Prism Package (CVE-2020-15138) 7.5 high 1.11.0+dfsg-4 07 Aug 2020
Regular Expression Denial of Service (ReDoS) Vulnerability in node-prismjs Package 7.5 high 1.23.0+dfsg-1 18 Feb 2021
Inefficient Regular Expression Complexity in node-prismjs - CVE-2021-3801 6.5 medium 1.23.0+dfsg-1+deb11u1 15 Sep 2021
Cross-Site Scripting Vulnerability in Prism's Command Line Plugin 6.1 medium 1.23.0+dfsg-1+deb11u2 18 Feb 2022
DOM Clobbering Vulnerability in node-prismjs - CVE-2024-53382 5.4 medium No fix published 03 Mar 2025

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 node-prismjs

Is node-prismjs safe to use?

Vulert records 9 vulnerabilities for node-prismjs in Debian: 0 critical, 0 high, 0 medium and 0 low, plus 9 not yet rated. 1 of them has no published fix yet, so that is the one to avoid or mitigate.

How many vulnerabilities does node-prismjs have?

9 vulnerabilities are recorded for node-prismjs in the Debian ecosystem: 0 critical, 0 high, 0 medium and 0 low, plus 9 not yet rated. The ledger on this page lists the same counts next to the date of the most recent disclosure.

How often are new node-prismjs vulnerabilities disclosed?

0 vulnerabilities were recorded for node-prismjs in the last 12 months, and the oldest entry in this database dates to 07 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 node-prismjs 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 node-prismjs for upcoming vulnerabilities?

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