CVE-2026-126066: fast-xml-parser: Quadratic CPU consumption scanning unterminated stop-node tags
Summary With the non-default stopNodes option, a stop node's body with many " " anywhere after makes readStopNodeData() rescan the entire remaining input from every " exists - OrderedObjParser.js:812-818 — on failure, i isn't advanced, so the next lookahead is neither cached nor bounded — n copies of means n scans over the remaining input, O(n²) work, before it finally throws. Fix 1.
Published Nov 10, 2026
Affected packages
fast-xml-parser
- Ecosystem
- npm
- Affected
- <= 5.11.2
- Fixed in
- 5.12.0
- Check
npm ls fast-xml-parser
Advisory details
From the GitHub Advisory Database (CC BY 4.0).
Summary
With the non-default stopNodes option, a stop node's body with many "" 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()callsreadStopNodeData()after a matching stop node opensOrderedObjParser.js:810— callsreadTagExp()for every non-special<OrderedObjParser.js:688-722—tagExpWithClosingIndex()scans to end-of-input and returnsundefinedwhen no>existsOrderedObjParser.js:812-818— on failure,iisn't advanced, so the next<repeats the same full scanOrderedObjParser.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 ` means n` scans over the remaining input, O(n²) work, before it finally throws.
Fix
- Throw immediately in
readStopNodeData()whenreadTagExp()returnsundefined - Or break the loop on the first failed scan
- Or find the next
>once and reuse/bound that result - 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>' + '. 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).
Credited to S31ZUR3, amitguptagwl.
References
- https://github.com/NaturalIntelligence/fast-xml-parser/security/advisories/GHSA-474x-hrwr-fgx4
- https://github.com/NaturalIntelligence/fast-xml-parser/commit/0c3659348364959da62954b73728fb3bd05ebcb4
- https://github.com/NaturalIntelligence/fast-xml-parser/releases/tag/v5.12.0
- https://github.com/advisories/GHSA-474x-hrwr-fgx4
How this page is made: the data panel comes from the GitHub Advisory Database, CISA’s KEV catalog, the NVD and FIRST EPSS, and updates twice a day. No analysis has been written for this entry yet. Methodology
More npm vulnerabilities
All npm entriesCVE-2026-73569
fast-xml-parser: Repeated DOCTYPE declarations reset entity expansion limits
high8.7Jul 21, 2026CVE-2026-41650
fast-xml-parser XMLBuilder: XML Comment and CDATA Injection via Unescaped Delimiters
medium6.1Apr 22, 2026CVE-2026-33349
Entity Expansion Limits Bypassed When Set to Zero Due to JavaScript Falsy Evaluation in fast-xml-parser
medium5.9Mar 19, 2026CVE-2026-33036
fast-xml-parser affected by numeric entity expansion bypassing all entity expansion limits (incomplete fix for CVE-2026-26278)
high7.5Mar 17, 2026CVE-2026-27942
fast-xml-parser has stack overflow in XMLBuilder with preserveOrder
low2.7Feb 26, 2026CVE-2026-25896
fast-xml-parser has an entity encoding bypass via regex injection in DOCTYPE entity names
critical9.3Feb 20, 2026
