CVE-2026-73569
CVE-2026-73569 — fast-xml-parser: Repeated DOCTYPE declarations reset entity expansion limits
fast-xml-parser allows users to process XML from JS object without C/C++ based libraries or callbacks. From 5.9.3 until 5.10.1, src/xmlparser/OrderedObjParser.js processes multiple DOCTYPE declarations within a single XML document and passes each declaration's entities through addInputEntities(). addInputEntities() resets maxTotalExpansions and maxExpandedLength every time it is called, allowing additional DOCTYPE declarations to repeatedly reset the configured entity-expansion limits during one parse operation. A crafted XML document can then cause excessive CPU use, event-loop blocking, memory exhaustion, and process termination. This issue is fixed in version 5.10.1.
Published Updated Sources: NVD, NaturalIntelligence (CNA), GitHub, GitHub Security Advisory, SOCRadar CTI
Triage
Is it exploited, how likely is exploitation, what does it touch, and how severe do the scoring sources call it.
Exploitation
Exploit code
public exploit, none observed
EPSS
0%
ahead of 0% of scored CVEs
CVSS base
8.7
high
CISA SSVC assessment
Three decision points CISA publishes for the CVEs it assesses · SSVC 2.0.3. A stakeholder decision, not a severity score.
Exploitation
None
none · proof-of-concept · active
Automatable
Yes
can an attacker script all four kill-chain steps
Technical impact
Partial
partial · total control of the vulnerable component
Remediation
The vendor's own words where we have them.
Upgrade fast-xml-parser to 5.10.1 or later (npm advisory GHSA-8r6m-32jq-jx6q).
First 24 hours
Ordered from the record's own fields — exposure first, because you cannot patch what you have not found.
- Identify exposed assets running affected vendor/product/version combinations.
- Prioritize based on EPSS, PoC availability, and external exposure.
- Search available logs for exploit probes, errors, authentication anomalies, or suspicious child processes matching the vulnerability class.
Affected scope
Vendor, product and version as the advisories word them.
| Vendor | Product | Versions | Status |
|---|---|---|---|
| NaturalIntelligence | fast-xml-parser | >= 5.9.3, < 5.10.1 | Vulnerable |
| npm | fast-xml-parser | >= 5.9.3, < 5.10.1 | Vulnerable |
Attack characteristics
The CVSS vector, decoded. It describes the attack, not your exposure to it.
Scope
X
Attack Complexity
Low
Attack Vector
Network
Privileges Req
None
User Interaction
None
Every base score collected
Sources score independently and disagree; each row says who scored it and under which version.
| Score | Version | Severity | Expl. | Impact | Source |
|---|---|---|---|---|---|
| 8.7 | CVSS 4.0 | high | — | — | NaturalIntelligence (CNA) |
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:N/VA:H/SC:N/SI:N/SA:N
What this weakness leads to
MITRE's own consequences and mitigations for the weakness class — the authority's wording, not guidance derived from the CVSS vector.
CWE-776 · Improper Restriction of Recursive Entity References in DTDs ('XML Entity Expansion')
- DoS: Resource Consumption (Other)
Mitigation: If possible, prohibit the use of DTDs or use an XML parser that limits the expansion of recursive DTD entities.
Weakness & attack patterns
- CWE-776
Inferred from the weakness class — not observed against this CVE.
Public exploit
Capability, not use: code existing is a different claim from anyone running it.
Repositories
1
Detection
Read off the CVSS vector and the weakness class. Starting points, not rules we have tested.
- Search application, proxy, and WAF logs for requests touching /C++, /xmlparser/OrderedObjParser.js.
- Prioritize edge telemetry for network-reachable fast-xml-parser.
- Monitor for scanner or exploit-pattern traffic after 1 public PoC repositories were reported.
Timeline
What happened to this CVE, newest first — with the readings a source repeats on a schedule counted underneath rather than listed.
- 2026
Added · CVSS 3.1 8.7 (AV:N)
Aug 13, 2026 · NVD
Initial · CVE published
Aug 13, 2026 · NVD
Added · GHSA-8r6m-32jq-jx6q published (high)
Jul 21, 2026 · GitHub Security Advisory
Source activity
Readings a source repeats on a schedule, counted rather than listed.
- 2×ModifiedAug 13, 2026 · SOCRadar CTI
References
4 on the record
- github.com/NaturalIntelligence/fast-xml-parser/commit/4e546e03987662de5495d050b5fba26bea65383f
Exploit, Third Party Advisory, NIST, Mitre
- github.com/NaturalIntelligence/fast-xml-parser/releases/tag/v5.10.1
Exploit, Third Party Advisory, NIST, Mitre
- github.com/NaturalIntelligence/fast-xml-parser/security/advisories/GHSA-8r6m-32jq-jx6q
Exploit, Third Party Advisory, NIST, Mitre
- github.com/advisories/GHSA-8r6m-32jq-jx6q
Exploit, Third Party Advisory
Elsewhere on this site
- NaturalIntelligenceevery CVE for this vendor
- npmevery CVE for this vendor
- Remote Code Execsame class
- CWE-776other pages naming this weakness
Not in any source we poll
Listed rather than left blank: an empty field and an unmeasured one look identical on screen, and only one is a reason to look elsewhere.
- No confirmed IOCs, IP addresses, domains, file hashes, or malware artifacts supplied.
- No organization-specific asset inventory, compensating-control status, or patch deployment evidence supplied.
- No exploit packet captures, log samples, or incident case IDs supplied.
Answered from this record1
What should defenders know first?
CVE-2026-73569 is fast-xml-parser: Repeated DOCTYPE declarations reset entity expansion limits, a high vulnerability affecting fast-xml-parser from NaturalIntelligence, npm. The current evidence does not list it in CISA KEV, and the exploit status is: Active exploitation is not confirmed from current sources for CVE-2026-73569. Public exploit evidence is: 1 public PoC repositories reported; 0 marked weaponized in current dataset. The affected-version evidence is listed in the key facts and affected products tables. Defenders should first verify whether exposed or business-critical assets run those versions, then apply vendor patches or mitigations, restrict reachable attack surface, and preserve logs for detection review. CVSS 8.7 describes technical severity, while EPSS 0% helps estimate near-term exploit likelihood; neither replaces asset context. Unknown fields should remain explicit in tickets, and threat actor, IOC, victimology, or payload claims should not be added unless a cited source supports them. Monitor CISA KEV, vendor advisories, NVD changes, public PoC repositories, and internal telemetry for update triggers.