CVE-2026-71429: CWE-407: Inefficient Algorithmic Complexity in uhop stream-json
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.
CVSS v3.1
Score 6.2medium
Affected software
uhop
stream-json
Weaknesses
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
The stream-json library's path filters (pick, ignore, filter, replace) prior to version 3.5.0 recompute the full path string from the nesting stack for every checkable token, resulting in O(D²) processing time for documents with nesting depth D instead of the expected O(D). This inefficiency can be triggered by deeply nested JSON documents, causing the Node.js event loop to block and resulting in denial of service. The problem is related to nesting depth rather than document size. The streamArray, streamObject, and streamValues streamers are unaffected as they use a constant-time depth getter. The vulnerability is resolved in version 3.5.0.
Potential Impact
An attacker can cause denial of service by sending a small but deeply nested JSON document that triggers the inefficient path filter processing, blocking the Node.js event loop. This impacts availability but does not affect confidentiality or integrity.
Mitigation Recommendations
This issue is fixed in stream-json version 3.5.0. Users should upgrade to version 3.5.0 or later to remediate this vulnerability. Patch status is not explicitly confirmed in vendor advisory content, but the fix is stated to be in version 3.5.0. Until upgraded, avoid processing untrusted deeply nested JSON documents with the affected path filters.
Technical Details
- Data Version
- 5.2
- Assigner Short Name
- GitHub_M
- Date Reserved
- 2026-08-06T16:28:51.182Z
- Cvss Version
- 3.1
- State
- PUBLISHED
Threat ID: 6a99d71facd9273b496a6d08
Added to database: 09/03/2026, 20:22:55 UTC
Last enriched: 09/07/2026, 12:03:09 UTC
Last updated: 10/17/2026, 06:48:19 UTC
Views: 82
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Actions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
Need more coverage?
Upgrade to Pro Console for AI refresh and higher limits.
For incident response and remediation, OffSeq services can help resolve threats faster.
Latest Threats
Check if your credentials are on the dark web
Instant breach scanning across billions of leaked records. Free tier available.