CVE-2026-32141: flatted: Unbounded recursion DoS in parse() revive phase
flatted is a circular JSON parser. Prior to 3.4.0, flatted's parse() function uses a recursive revive() phase to resolve circular references in deserialized JSON. When given a crafted payload with deeply nested or self-referential $ indices, the recursion depth is unbounded, causing a stack overflow that crashes the Node.js process. This vulnerability is fixed in 3.4.0.
Security readout for executives and security teams
Plain-English summary
Applications using flatted before version 3.4.0 may crash when parsing maliciously structured input. An unauthenticated remote attacker could cause service disruption if attacker-controlled data reaches flatted.parse(). The issue affects availability; the supplied CVSS assessment indicates no confidentiality or integrity impact.
Executive priority
Prioritize internet-facing or multi-tenant services where untrusted data reaches flatted.parse(), because one request may terminate a Node.js process. Expedite upgrading those services and confirm deployed artifacts contain 3.4.0 or later. Lower priority is reasonable only after documenting that the vulnerable parser is unreachable from untrusted input.
Technical view
During parse() reference revival, affected flatted versions recursively resolve deeply nested or self-referential $ indices without a safe depth bound. Crafted serialized input can exhaust the JavaScript call stack and terminate the Node.js process. The issue is classified as CWE-674 and CWE-770 and is fixed in flatted 3.4.0.
Likely exposure
Highest exposure exists in network-facing Node.js services that pass untrusted request, message, file, or stored content to flatted.parse(). Risk may also arise through a transitive dependency. Installation alone does not prove exploitability; confirm the affected function is reachable from attacker-controlled data.
Exploitation context
The supplied CVSS 3.1 score is 7.5, reflecting remotely triggerable, low-complexity, unauthenticated denial of service without user interaction. The source bundle marks KEV false and provides no evidence of active exploitation. Repeated triggering could cause recurring outages where process supervision automatically restarts the service.
Researcher notes
Reachability is the key qualifier: determine whether the vulnerable revive phase processes adversary-controlled serialized data. Review direct and transitive dependency resolution, bundled output, and container contents. The supplied material establishes a crash condition and upstream fix, but does not establish exploitation in the wild or impact beyond availability.
Mitigation direction
Upgrade flatted to version 3.4.0 or later.
Update lockfiles and rebuild deployed artifacts to remove affected versions.
Restrict untrusted input from reaching flatted.parse() until upgrades are deployed.
Apply relevant Red Hat advisories where flatted is supplied through affected Red Hat products.
Validation and detection
Inventory direct and transitive flatted versions across source, lockfiles, images, and deployed artifacts.
Trace whether attacker-controlled data can reach flatted.parse().
Confirm production resolves flatted 3.4.0 or later after rebuilding.
Run isolated regression tests confirming malformed input cannot terminate the service.
Monitor process crashes and stack-overflow errors for attempted or accidental triggering.
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Potential ATT&CK relevance
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
cwe · low confidence lookup
CWE-674: Exact CWE lookup
Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
CWE-674 · source CWE mapping
Uncontrolled Recursion
Uncontrolled Recursion represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.
Allocation of Resources Without Limits or Throttling
Allocation of Resources Without Limits or Throttling represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.