stream-json: FlexAssembler string/RegExp path filters join the full key stack per container start, giving O(depth^2) CPU denial of service

Why it is Yellow

• CVSS 6.2 medium
• Public exploit or proof of concept referenced
• On your watchlist: npm

Affected packages

References

• https://github.com/advisories/GHSA-jj87-hc4r-jwfw
• https://github.com/uhop/stream-json/security/advisories/GHSA-jj87-hc4r-jwfw
• https://nvd.nist.gov/vuln/detail/CVE-2026-114129
• https://github.com/uhop/stream-json/commit/1929fd80495d45b47e8f8cb1d4e132f915aef012
• https://github.com/uhop/stream-json/commit/c06c9a3c02adef89543e26ecebb45837cb284512
• https://github.com/uhop/stream-json/releases/tag/3.7.0
• https://github.com/advisories/GHSA-jj87-hc4r-jwfw

Original description

stream-json is a micro-library of stream components for processing JSON and JSONC with a minimal memory footprint. From 2.0.0 until 3.7.0, FlexAssembler compiles string and regular-expression path filters into matchers that join the full key stack on every container start. Because the key stack grows with unbounded object or array nesting, a document nested to depth D causes D joins whose cost grows with the current depth, resulting in quadratic CPU consumption on the single-threaded event loop. The join occurs before the rule match decision, so the attacker does not need to know the target schema. Consumers using only function filters or no rules are not affected. A crafted nested document can stall all concurrent work in a process that feeds it to an affected FlexAssembler. This issue is fixed in 3.7.0, which adds a default maximum depth.