Skip to content

CVE-2026-71429 stream-json: pick/ignore/filter/replace filters are O(depth²) on nested input — small crafted JSON blocks the event loop for seconds→minutes (DoS)

MediumCVSS 6.2 EPSS 0.16%
Published
Updated
Exploit status
No public exploit known
CISA SSVC
Proof of concept public · automatable: no · technical impact: partial
Technology
Red Hat

Description

stream-json is a micro-library of stream components for processing JSON and JSONC with a minimal memory footprint. Prior to 3.5.0, the path filters pick, ignore, filter, and replace in src/core/filters/filter-base.js recompute the full path string from the nesting stack for every checkable token. Because the stack length equals the current nesting depth and a checkable token is emitted at every level, a depth D document costs O(D²) rather than O(D) to process. The issue is triggered by nesting depth rather than byte volume, including the documented pick({filter: 'data'}) traversal-until-match path, so an application that sends untrusted JSON through a string or RegExp filter can block the Node.js event loop and cause denial of service with a small deeply nested document. The streamArray, streamObject, and streamValues streamers are not affected because they use the constant-time asm.depth getter. This issue is fixed in version 3.5.0.

Upgrade path

3 packages: 1 fixed, 1 with no fix yet.

PackageAffectedFixed inStatus
redhat/rh-podman-desktop.git(Red Hat podman_desktop 1) All versions No fix listed No fix yet
npm stream-json(npm) < 3.5.0; <= 3.4.0 3.5.0 Fixed
uhop stream-json = < 3.5.0 No fix listed Versions listed

Affected products

ProductAffected versionsFixed in
uhop stream-json = < 3.5.0 No fix listed
redhat/rh-podman-desktop.git(Red Hat:podman_desktop:1) All versions No fix listed
npm stream-json(npm) <= 3.4.0 No fix listed
npm stream-json(npm) < 3.5.0 3.5.0

References