Low

fast-xml-parser: Quadratic CPU consumption scanning unterminated stop-node tags

  • Disclosed: 10.11.2026
  • Updated: 10.11.2026 23:17

Summary

With the non-default stopNodes option, a stop node's body with many "<a " fragments and no closing ">" anywhere after makes readStopNodeData() rescan the entire remaining input from every "<". The failed lookahead is neither cached nor bounded, so n fragments cost O(n²) before the parser throws. Availability-only (CPU exhaustion), needs the non-default stopNodes option — not benchmarked yet, see Proof of Concept.

Details

CWE-407 — Inefficient Algorithmic Complexity

Code

  • OrderedObjParser.js:520 — parseXml() calls readStopNodeData() after a matching stop node opens
  • OrderedObjParser.js:810 — calls readTagExp() for every non-special <
  • OrderedObjParser.js:688-722 — tagExpWithClosingIndex() scans to end-of-input and returns undefined when no > exists
  • OrderedObjParser.js:812-818 — on failure, i isn't advanced, so the next < repeats the same full scan
  • OrderedObjParser.js:423 — the main parse loop throws immediately on the same failure; only the stop-node path retries

Root cause: a failed closing-> lookahead is neither cached nor bounded — n copies of <a with no later > means n scans over the remaining input, O(n²) work, before it finally throws.

Fix

  1. Throw immediately in readStopNodeData() when readTagExp() returns undefined
  2. Or break the loop on the first failed scan
  3. Or find the next > once and reuse/bound that result
  4. Add a test asserting near-linear scaling when payload size doubles

Proof of concept

Not benchmarked — static-analysis finding, confidence 0.5.

To confirm: configure stopNodes matching a root element. Build input as '<stop>' + '<a '.repeat(n). Time parse() until it throws Unexpected end of <tag>. Start around n=10,000 and double it — quadratic should show ~4x time per doubling, linear ~2x. Control: same input with a > present, or stopNodes unset.

Impact

CPU-exhaustion DoS in Node.js services parsing untrusted XML with stopNodes enabled. A ~100KB payload is estimated at ~10⁹ character operations (roughly a second or more of blocked event loop) — analytical estimate, not a benchmark. No confidentiality/integrity impact. CVSS 3.1: AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:N/A:L (3.7, Low).

Affected software

Click a technology to see all vulnerabilities affecting it.

PlatformPackageVulnerable versionsFixed in
npm package fast-xml-parser < 5.12.0 5.12.0

References

CVSS score 3.7/10
CVSS vector
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:N/A:L
Weakness (CWE)
CWE-407
Platform
npm
Package
fast-xml-parser
Disclosed
10.11.2026
Updated
10.11.2026 23:17

Sources and licenses

OSV / GitHub Advisory Database - GHSA-474x-hrwr-fgx4 - CC BY 4.0

Vulnerability history: fast-xml-parser

All published vulnerabilities of this package (npm package), newest first. Shows whether this is a one-off slip or a package that needs watching.

All (13) in the archive
Total entries
13
First → latest
08.2021 11.2026
Without a fix
0
Exploited in attacks
0

Severity breakdown

  • Critical 1
  • High 6
  • Medium 3
  • Low 3

Disclosures per year

  1. 2021: 1
  2. 2022: 0
  3. 2023: 2
  4. 2024: 1
  5. 2025: 0
  6. 2026: 9
Severity:
  1. fast-xml-parser: Quadratic CPU consumption scanning unterminated stop-node tags this entry
    Low · 3.7 CVE-2026-126066 < 5.12.0 5.12.0
  2. High · 7.5 CVE-2026-33036 >= 5.0.0, < 5.5.6, >= 4.0.0-beta.3, < 4.5.5 5.5.6, 4.5.5
  3. Critical · 9.3 CVE-2026-25896 >= 5.0.0, < 5.3.5, >= 4.1.3, < 4.5.4 5.3.5, 4.5.4
  4. High · 7.5 CVE-2026-26278 >= 4.1.3, < 4.5.4, >= 5.0.0, < 5.3.6 4.5.4, 5.3.6
  5. High · 7.5 CVE-2026-25128 >= 5.0.9, < 5.3.4 5.3.4
  6. High · 7.5 CVE-2024-41818 >= 4.3.5, < 4.4.1 4.4.1
  7. High · 7.5 CVE-2023-34104 >= 4.1.3, < 4.2.4 4.2.4

Know which vulnerabilities affect your application

With the DockRay integration and software inventory enabled, DockRay checks reported component versions against known vulnerabilities and notifies you about confirmed matches. Coverage depends on the supported technology and available advisory data.

Connect your application
DockRay newsletter

Application security in your inbox

Important vulnerabilities, actionable guidance and practical advice for your applications. Choose your technologies and follow what matters to your project.

  • A daily digest of new vulnerabilities, critical ones included.
  • Notifications about important updates.
  • Practical advice on application security and monitoring.

Leave empty to receive updates for every technology.

Free to subscribe. Unsubscribe with one click in any email.