CVE-2026-27942: NaturalIntelligence fast-xml-parser · Classic Buffer Overflow
Affects NaturalIntelligence fast-xml-parserSource CVE Database V5
Not known to be exploited · CVSS 2.7 Low : upgrade to 5.3.8 when convenient.
Data as of 29 Oct 2026, 19:04 UTC
- EPSS
- 0.5% chance of exploitation in 30 days – higher than 45% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
- Patch
- Available – fixed in 5.3.8
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:N/VA:L/SC:N/SI:N/SA:N/E:UExploitation evidence
Disclosed: evidence found.
CVE published 26 Feb 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 29 Oct 2026.
What to do
Upgrade NaturalIntelligence fast-xml-parser to 5.3.8.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| NaturalIntelligencefast-xml-parser | Affected
| Fixed in
|
npmfast-xml-parserpkg:npm/fast-xml-parserOther threats | Affected
| Fixed in
|
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
AI-suggested
Upgrade to fast-xml-parser version 5.3.8 or later, which contains the official fix for this vulnerability. As a temporary workaround, avoid using the XML builder with preserveOrder:true or validate input data before passing it to the builder to prevent triggering the overflow.
Description
fast-xml-parser allows users to validate XML, parse XML to JS object, or build XML from JS object without C/C++ based libraries and no callback. Prior to version 5.3.8, the application crashes with stack overflow when user use XML builder with `preserveOrder:true`. Version 5.3.8 fixes the issue. As a workaround, use XML builder with `preserveOrder:false` or check the input data before passing to builder.