CVE-2026-33036: Fast xml parser Fast-xml-parser Affected By Numeric Entity Vulnerability
HIGHCVE-2026-33036 is a HIGH (CVSS 7.5) fast-xml-parser affected by numeric entity vulnerability (CWE-776: Improper Restriction of Recursive Entity References in DTDs ('XML Entity Expansion')) affecting Fast xml parser libraries in the npm ecosystem. The issue involves fast-xml-parser affected by numeric entity expansion bypassing all entity expansion limits (incomplete fix for cve-2026-26278). Remediation is available by upgrading affected packages to version 5.5.6, 4.5.5.
CVE-2026-33036 at a Glance
Security Impact
CVSS: 7.5
The security impact metrics below are parsed directly from the CVSS v3.1 vector string (CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H).
How to Fix CVE-2026-33036
To remediate this vulnerability, upgrade all affected Fast xml parser dependencies to a patched release. Both direct and transitive dependencies should be checked, as frameworks or security libraries may pull in vulnerable versions transitively.
npm install fast-xml-parser@5.5.6
npm install fast-xml-parser@4.5.5
Run the following command in your project directory to verify that all resolved dependencies use the patched release:
npm ls fast-xml-parser
How to Check if You Are Affected
To determine whether your Node.js application is affected by CVE-2026-33036, inspect your project dependencies using npm:
npm ls fast-xml-parser
Analyze the terminal output to locate any version of Fast xml parser in your dependency tree. If any resolved version matches the vulnerable ranges listed in the table below (for example, versions earlier than 5.5.6), your application is affected.
Note: The npm ls fast-xml-parser command inspects dependencies declared in your package.json and lockfile; it does not perform automated runtime dynamic scanning.
Technical Details
Vulnerability Mechanism & Technical Analysis
This vulnerability is classified under CWE-776: Improper Restriction of Recursive Entity References in DTDs ('XML Entity Expansion'), where the product uses xml documents and allows their structure to be defined with a document type definition (dtd), but it does not properly control the number of recursive definitions of entities. In Fast xml parser, software state validation or input boundaries are circumvented during processing. Review the official source advisory statement below for specific affected components, classes, and reproduction details.
Source Advisory Statement
CVE-2026-33036 Affected Fast xml parser Versions
2 component(s)| Product / Package | Ecosystem | Affected Versions | Fixed Version |
|---|---|---|---|
|
fast-xml-parser
|
npm |
≥ 5.0.0
< 5.5.6
|
5.5.6
|
|
fast-xml-parser
|
npm |
≥ 4.0.0-beta.3
< 4.5.5
|
4.5.5
|
References
Frequently Asked Questions
What is CVE-2026-33036?
Which Fast xml parser versions are affected?
What version fixes CVE-2026-33036?
Is fast-xml-parser affected?
What is the CVSS score of CVE-2026-33036?
What CWE is associated with CVE-2026-33036?
How can I check npm dependencies for CVE-2026-33036?
Machine-readable OSV JSON
OSV v1.5 Schema
{
"schema_version" : "1.4.0",
"id" : "GHSA-8gc5-j5rx-235r",
"modified" : "2026-03-25T14:31:39Z",
"published" : "2026-03-17T19:45:41Z",
"aliases" : [ "CVE-2026-33036" ],
"summary" : "fast-xml-parser affected by numeric entity expansion bypassing all entity expansion limits (incomplete fix for CVE-2026-26278)",
"details" : "## Summary\n\nThe fix for CVE-2026-26278 added entity expansion limits (`maxTotalExpansions`, `maxExpandedLength`, `maxEntityCount`, `maxEntitySize`) to prevent XML entity expansion Denial of Service. However, these limits are only enforced for DOCTYPE-defined entities. **Numeric character references** (`&#NNN;` and `&#xHH;`) and standard XML entities (`<`, `>`, etc.) are processed through a separate code path that does NOT enforce any expansion limits.\n\nAn attacker can use massive numbers of numeric entity references to completely bypass all configured limits, causing excessive memory allocation and CPU consumption.\n\n## Affected Versions\n\nfast-xml-parser v5.x through v5.5.3 (and likely v5.5.5 on npm)\n\n## Root Cause\n\nIn `src/xmlparser/OrderedObjParser.js`, the `replaceEntitiesValue()` function has two separate entity replacement loops:\n\n1. **Lines 638-670**: DOCTYPE entities — expansion counting with `entityExpansionCount` and `currentExpandedLength` tracking. This was the CVE-2026-26278 fix.\n2. **Lines 674-677**: `lastEntities` loop — replaces standard entities including `num_dec` (`/&#([0-9]{1,7});/g`) and `num_hex` (`/&#x([0-9a-fA-F]{1,6});/g`). **This loop has NO expansion counting at all.**\n\nThe numeric entity regex replacements at lines 97-98 are part of `lastEntities` and go through the uncounted loop, completely bypassing the CVE-2026-26278 fix.\n\n## Proof of Concept\n\n```javascript\nconst { XMLParser } = require('fast-xml-parser');\n\n// Even with strict explicit limits, numeric entities bypass them\nconst parser = new XMLParser({\n processEntities: {\n enabled: true,\n maxTotalExpansions: 10,\n maxExpandedLength: 100,\n maxEntityCount: 1,\n maxEntitySize: 10\n }\n});\n\n// 100K numeric entity references — should be blocked by maxTotalExpansions=10\nconst xml = `<root>${'A'.repeat(100000)}</root>`;\nconst result = parser.parse(xml);\n\n// Output: 500,000 chars — bypasses maxExpandedLength=100 completely\nconsole.log('Output length:', result.root.length); // 500000\nconsole.log('Expected max:', 100); // limit was 100\n```\n\n**Results:**\n- 100K `A` references → 500,000 char output (5x default maxExpandedLength of 100,000)\n- 1M references → 5,000,000 char output, ~147MB memory consumed\n- Even with `maxTotalExpansions=10` and `maxExpandedLength=100`, 10K references produce 50,000 chars\n- Hex entities (`A`) exhibit the same bypass\n\n## Impact\n\n**Denial of Service** — An attacker who can provide XML input to applications using fast-xml-parser can cause:\n- Excessive memory allocation (147MB+ for 1M entity references)\n- CPU consumption during regex replacement\n- Potential process crash via OOM\n\nThis is particularly dangerous because the application developer may have explicitly configured strict entity expansion limits believing they are protected, while numeric entities silently bypass all of them.\n\n## Suggested Fix\n\nApply the same `entityExpansionCount` and `currentExpandedLength` tracking to the `lastEntities` loop (lines 674-677) and the HTML entities loop (lines 680-686), similar to how DOCTYPE entities are tracked at lines 638-670.\n\n## Workaround\n\nSet `htmlEntities:false`",
"severity" : [ {
"type" : "CVSS_V3",
"score" : "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H"
} ],
"affected" : [ {
"package" : {
"ecosystem" : "npm",
"name" : "fast-xml-parser"
},
"ranges" : [ {
"type" : "ECOSYSTEM",
"events" : [ {
"introduced" : "5.0.0"
}, {
"fixed" : "5.5.6"
} ]
} ]
}, {
"package" : {
"ecosystem" : "npm",
"name" : "fast-xml-parser"
},
"ranges" : [ {
"type" : "ECOSYSTEM",
"events" : [ {
"introduced" : "4.0.0-beta.3"
}, {
"fixed" : "4.5.5"
} ]
} ]
} ],
"references" : [ {
"type" : "WEB",
"url" : "https://github.com/NaturalIntelligence/fast-xml-parser/security/advisories/GHSA-8gc5-j5rx-235r"
}, {
"type" : "ADVISORY",
"url" : "https://nvd.nist.gov/vuln/detail/CVE-2026-33036"
}, {
"type" : "WEB",
"url" : "https://github.com/NaturalIntelligence/fast-xml-parser/commit/bd26122c838e6a55e7d7ac49b4ccc01a49999a01"
}, {
"type" : "PACKAGE",
"url" : "https://github.com/NaturalIntelligence/fast-xml-parser"
}, {
"type" : "WEB",
"url" : "https://github.com/NaturalIntelligence/fast-xml-parser/releases/tag/v4.5.5"
}, {
"type" : "WEB",
"url" : "https://github.com/NaturalIntelligence/fast-xml-parser/releases/tag/v5.5.6"
} ],
"database_specific" : {
"cwe_ids" : [ "CWE-776" ],
"severity" : "HIGH",
"github_reviewed" : true,
"github_reviewed_at" : "2026-03-17T19:45:41Z",
"nvd_published_at" : "2026-03-20T06:16:11Z"
}
}