ReDOS vulnerabities: multiple grammars
What to do
Vendor fix available. Upgrade each affected package to the fixed version on its release line (highlight.js 10.4.1; @highlightjs/cdn-assets 10.4.1), redeploy, then verify what is actually installed.
This page has no inventory attached, so it cannot say whether you are affected. A vendor fix is not proof that your deployment is fixed.
Affected packages
npm highlight.js
- Affected
- >= 9.0.0, < 10.4.1
- Fixed in
- 10.4.1
- Affected
- < 10.4.1
- Fixed in
- 10.4.1
Sources
- Open Source Vulnerabilities (OSV.dev), including the GitHub Advisory Database
OSV record GHSA-7wwv-vh3v-89cq lists affected ranges: npm highlight.js >=9.0.0 =0 <10.4.1 (fixed)
VerifiedObserved Structured OSV record; GitHub-reviewed advisory.
- GitHub Advisory Database and maintainer security advisories on GitHub
GitHub-reviewed advisory GHSA-7wwv-vh3v-89cq lists affected ranges: npm highlight.js >=9.0.0 =0 <10.4.1
VerifiedObserved Structured GitHub Advisory Database record (type=reviewed) from the GitHub REST API.
Severity and exploitation
- Exploitation
- No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.
- CVSS
- not scored
- EPSS
- No dated EPSS signal available.
Source description
As published by the source; long descriptions are shortened.
Impact: Potential ReDOS vulnerabilities (exponential and polynomial RegEx backtracking) oswasp: The Regular expression Denial of Service (ReDoS) is a Denial of Service attack, that exploits the fact that most Regular Expression implementations may reach extreme situations that cause them to work very slowly (exponentially related to input size). An attacker can then cause a program using a Regular Expression to enter these extreme situations and then hang for a very long time. If are you are using Highlight.js to highlight user-provided data you are possibly vulnerable. On the client-side (in a browser or Electron environment) risks could include lengthy freezes or crashes... On the server-side infinite freezes could occur... effectively preventing users from accessing your app or service (ie, Denial of Service). This is an issue with grammars shipped with the parser (and potentially 3rd party grammars also), not the parser itself. If you are using Highlight.js with any of the…
Dates and revisions
- Published by the source
- Last modified by the source
- Source last checked
- Revision 2 · amended ·
Amended from ghsa record GHSA-7wwv-vh3v-89cq
- Revision 1 · created ·
Published from osv record GHSA-7wwv-vh3v-89cq
Agent brief
Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.
# Patch Next advisory brief: GHSA-7wwv-vh3v-89cq Advisory: ReDOS vulnerabities: multiple grammars IDs: GHSA-7wwv-vh3v-89cq Record: https://patchnext.com/advisories/ghsa-7wwv-vh3v-89cq (revision 2, source checked 26 Oct 2026, 12:15 UTC) Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected. Severity: Unrated Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV. Vendor response: Vendor fix available; fixed versions by package: highlight.js 10.4.1; @highlightjs/cdn-assets 10.4.1. A vendor fix does not mean a deployment is fixed. ## Affected components - npm highlight.js: affected >= 9.0.0, < 10.4.1; fixed in 10.4.1 - npm @highlightjs/cdn-assets: affected < 10.4.1; fixed in 10.4.1 ## Suggested inspection (read-only) - `npm ls highlight.js --all`: lists every installed copy and version, including transitive ones. Run in the project root after `npm ci`. - `npm ls @highlightjs/cdn-assets --all`: lists every installed copy and version, including transitive ones. Run in the project root after `npm ci`. ## Supported action Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version. ## Required regression checks - Run the test suite and a production build. - Exercise the features that depend on highlight.js, @highlightjs/cdn-assets. - Repeat the inspection and confirm that only fixed versions remain installed. ## Rollback considerations - Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward. ## Unresolved questions - Which deployments run an affected version? - Exploitation status can change. Check again before lowering the priority. - Mark the work resolved only after the fixed version is verified in production. ## Sources - Verified: https://osv.dev/vulnerability/GHSA-7wwv-vh3v-89cq (OSV record GHSA-7wwv-vh3v-89cq lists affected ranges: npm highlight.js >=9.0.0 =0 <10.4.1 (fixed)) - Verified: https://github.com/advisories/GHSA-7wwv-vh3v-89cq (GitHub-reviewed advisory GHSA-7wwv-vh3v-89cq lists affected ranges: npm highlight.js >=9.0.0 =0 <10.4.1) Commands are suggestions: review each one before running it.
Loading voting…