highlight.js denial of service via ReDoS in LiveScript grammar
- Exploited
- No known exploitation
- Fix
- Fix or patch referenced
- Who is exposed
- Not reported
Summary
The highlight.js library from highlight has a flaw in its LiveScript grammar: a crafted text argument passed to hljs.highlight can make its regular expressions take excessive processing time. An attacker can reach this remotely, without logging in, and use it to slow down or stall the affected software.
Written by a model
Original description
A flaw has been found in highlight highlight.js up to 11.12.0. The affected element is the function hljs.highlight of the file src/languages/livescript.js of the component Language Grammar Handler. Executing a manipulation of the argument text can lead to inefficient regular expression complexity. The attack can be launched remotely. The exploit has been published and may be used. The pull request to fix this issue awaits acceptance.
What to do
Apply the patch listed under Evidence.
Check your systems with an agent
Paste this into a coding or ops agent. It checks your systems read-only and reports a table per asset.
Check whether my systems are affected by CVE-2026-133937 (highlight highlight.js Language Grammar livescript.js hljs.highlight redos), using the cve.now data below.
Rules: work read-only. Do not run exploit code, proof-of-concept scripts or scanners that send attack payloads, and do not change any configuration, package, image or deployment. Report findings only.
What cve.now has for CVE-2026-133937 (entry last updated 2026-11-20):
Affected:
- highlight highlight.js: versions 11.0, 11.1, 11.2, 11.3, 11.4, 11.5, 11.6, 11.7, 11.8, 11.9, 11.10, 11.11 and 1 more
Fixed versions: none listed yet.
Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory.
CISA KEV: CVE-2026-133937 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-133937 only. If you also check another CVE, look up its own KEV status; never assume it from this one.
How to check:
- Installed software: check what is actually running, not what a repo declares. Read the version from each host, container image and Kubernetes node (the binary's version output, the OS package database, image layers), and check whether the conditions above hold there. Distribution packages may carry a backported fix under an older version number; confirm against the distribution's own advisory.
Verify against the linked advisories before concluding, and cite the date you read each one:
- https://github.com/highlightjs/highlight.js/pull/4575
- https://vuldb.com/vuln/441503
- https://vuldb.com/vuln/441503/cti
- https://vuldb.com/cve/CVE-2026-133937
- https://vuldb.com/submit/1052004
Do not conclude an asset is unaffected unless you checked it and the evidence covers both its version and the conditions above. If you could not check something, mark it unknown and say what is missing.
Report a table with one row per asset and these columns: Asset | Version or build | Status (affected, fixed, not applicable, unknown) | Compensating controls | Exposure (internet-facing, internal, none) | Evidence | Next action.
Entry: https://cve.now/CVE-2026-133937
For follow-up questions, use the cve.now MCP server at https://mcp.cve.now/mcp (no authentication), for example execute with name cve.get and arguments {"id": "CVE-2026-133937"}.Affected versions
- highlight highlight.js11.0, 11.1, 11.2, 11.3, 11.4, 11.5, 11.6, 11.7, 11.8, 11.9, 11.10, 11.11, 11.12.0
cve.now Index
- Exploitation?/40Unknown. No CISA SSVC exploitation rating yet
- Exposure17/25No login or user action needed per the CVSS vector, reachable over the network without a login · Unknown: No advisory context yet
- Reach?/20Unknown. No tracked technology or package matched
- Severity6.9/10CVSS 6.9
- No patch0/5No signal
What would change the score
- Would score about 69 if added to CISA KEV
- Would score about 64 if CISA's SSVC rates exploitation active
- Would score about 29 if advisories confirm default setups are exposed
Timeline
- CVE published
- First seen by cve.now
Evidence 8
| Kind | Source |
|---|---|
| CVE record 2Establishes: The identifier and description. | |
| Record | CVE List · CVE-2026-133937 |
| Record | NVD · CVE-2026-133937 |
| Public exploit code 1Establishes: Public exploit code exists (Exploit-DB, Metasploit, Nuclei and GitHub). | |
| Exploit | GitHub · highlightjs/highlight.js · Issue #4529 |
| Other links 5 | |
| Advisory | VulDB · Advisory #441503 |
| Advisory | VulDB · Threat intelligence #441503 |
| Advisory | VulDB · CVE-2026-133937 record |
| Advisory | VulDB · Submission #1052004 |
| Patch | GitHub · highlightjs/highlight.js · Pull request #4575 |
Questions about CVE-2026-133937
Is CVE-2026-133937 being exploited?
It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.
Source: cve.now feed data
Which versions are affected by CVE-2026-133937?
highlight.js: versions 11.0, 11.1, 11.2, 11.3, 11.4 and 8 more.
Source: cve.now feed data
Related
- CVE-2023-33187highlight vulnerable to cleartext transmission of sensitive information
- CVE-2026-104199aMQTT: Inefficient Regular Expression Complexity and Uncontrolled Resource Consumption and Improper Input Validation
- CVE-2026-132275svglib: Exponential resource consumption via nested <use> references in svg2rlg
- CVE-2026-63202netty-incubator-codec-ohttp BinaryHttpParser: Unauthenticated CPU-exhaustion DoS via infinite loop in field-section decoding
- CVE-2026-63124netty-incubator-codec-ohttp: Binary HTTP parser infinite loop on known-length field section boundary
- CVE-2026-128139NLTK: XMLCorpusView comment and CDATA parsing permits quadratic CPU denial of service
No corrections so far. Something wrong on this page? Report an error.