Skip to main content
Menu
CVEs

parse5 denial of service in HTML preprocessor

Affects parse5 7.0.0 up to but not including 8.1.1 when input contains two consecutive low surrogates. Fixed in 8.1.1.

CVE-2026-133245EUVD-2026-130311Published November 19, 2026, updated

8.7HighCNA
Exploited
No known exploitation
Fix
Fixed in 8.1.1
Who is exposed
Not reported

Summary

parse5 is a JavaScript HTML parsing library, and versions from 7.0.0 before 8.1.1 contain a flaw in how the preprocessor handles two consecutive low surrogate characters. An attacker can remotely, without logging in, send such input so that parsing throws an uncaught error and crashes the Node.js process.

Written by a model

Original description

parse5 7.0.0 before 8.1.1 contains an uncaught exception vulnerability in Preprocessor#_processSurrogate that allows remote attackers to crash applications by supplying two consecutive low surrogates. Attackers can submit input such as U+DC00 U+DC00, which decodes to out-of-range code point 0x110000 and throws a RangeError from parse, parseFragment, or streaming parsers, crashing Node.js processes.

Who should check

Teams running parse5 7.0.0 through 8.1.0 that parse untrusted input in Node.js services, since a crafted input can crash the process

“parse5 7.0.0 before 8.1.1”

vulncheck.com

What to do

Upgrade to a fixed version: 8.1.1.

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-133245 (parse5 7.0.0 before 8.1.1 Denial of Service via Preprocessor#_processSurrogate), 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-133245 (entry last updated 2026-11-19):
Affected:
- npm package parse5: from 7.0.0, fixed in 8.1.1
Fixed versions: 8.1.1.
Vendor patches: 9b57bf87 (source: https://www.vulncheck.com/advisories/parse5-7.0.0-before-8.1.1-denial-of-service-via-preprocessor-processsurrogate). Check each asset for these patch ids, not only its version.
Conditions (all must be true for the bug to be hit):
- parse5 version 7.0.0 up to but not including 8.1.1 (source: https://www.vulncheck.com/advisories/parse5-7.0.0-before-8.1.1-denial-of-service-via-preprocessor-processsurrogate)
- Input contains two consecutive low surrogates, such as U+DC00 U+DC00 (source: https://www.vulncheck.com/advisories/parse5-7.0.0-before-8.1.1-denial-of-service-via-preprocessor-processsurrogate)
Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory.
Attacker needs: network access, no login, no user action.
CISA KEV: CVE-2026-133245 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-133245 only. If you also check another CVE, look up its own KEV status; never assume it from this one.

How to check:
- Packages (npm): find every lockfile in each project and run the stack.check operation of the cve.now MCP server (execute) on each one. Compare the resolved versions, not the ranges a manifest declares, with the affected versions above. Include transitive dependencies.

Verify against the linked advisories before concluding, and cite the date you read each one:
- https://github.com/inikulin/parse5/pull/1921
- https://github.com/inikulin/parse5/commit/9b57bf87db292b54337554d2fd21b2a54f0f1a36
- https://github.com/inikulin/parse5/releases/tag/v8.1.1
- https://github.com/inikulin/parse5/blob/v8.1.0/packages/parse5/lib/tokenizer/preprocessor.ts#L80-L93
- https://github.com/inikulin/parse5
- https://www.vulncheck.com/advisories/parse5-7.0.0-before-8.1.1-denial-of-service-via-preprocessor-processsurrogate
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-133245
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-133245"}.

Affected versions

cve.now Index

49Pof 100 · provisional · methodology v3
  • Exploitation0/40No signal
  • Exposure20/25No login or user action needed, CISA rates it automatable · Unknown: Advisories don't say whether default setups are affected
  • Reach20/20parse5: 252.8M downloads a week
  • Severity8.7/10CVSS 8.7
  • No patch0/5No signal

What would change the score

  • Would score about 94 if added to CISA KEV
  • Would score about 89 if CISA's SSVC rates exploitation active
  • Would score about 54 if advisories confirm default setups are exposed

Impact

Timeline

  1. CVE published
  2. First seen by cve.now
  3. CISA SSVC assessment

    Exploitation: none · Automatable: yes · Technical impact: partial

  4. Record last updated

Evidence 8

Questions about CVE-2026-133245

Is CVE-2026-133245 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

What does this mean?

When parse5 receives input containing two consecutive low surrogates, such as U+DC00 U+DC00, it throws an uncaught RangeError during parsing. That error can crash the application, including Node.js processes.

Source: vulncheck.com

Which versions are affected by CVE-2026-133245?

parse5 (npm): from 7.0.0 before 8.1.1.

Source: cve.now feed data

Am I affected, and how do I check?

parse5 versions 7.0.0 up to but not including 8.1.1 are affected. To check a project, look at the parse5 version it resolves to, for example with npm ls parse5, and note whether its input can contain two consecutive low surrogates.

Source: vulncheck.com

How do I fix CVE-2026-133245?

Upgrade parse5 to 8.1.1 or later. The vendor's patch is identified as 9b57bf87.

Source: vulncheck.com

No corrections so far. Something wrong on this page? Report an error.