CVE-2026-71429

MEDIUMPre-NVD 6.26.2
EchelonGraph scoreMEDIUM confidence

This medium-severity CVE scores 6.2 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.1%, top 98% of all CVEs by exploit prediction. GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).

Triggered by: NVD CVSS baseline
Sources: epss, secondary
Elevated
6.2EG
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 6.2Exploit: Elevated riskExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

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
6.2
EG Score
6.2(medium)
EG Risk
44(Track)
EG Risk 44/100SSVC: Track

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity62% × 45%
Exploitation40% × 40%
Automatability0% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
2%
KEV
Not listed

Published

September 3, 2026

Last Modified

September 9, 2026

Advisory Details (2)

Auto-updated Sep 3, 2026
🔬 Proof of concept available. Patch available. Sources: github, github_commit.
github_commit

commit a869fb98aaef (uhop/stream-json)

Fix landed in uhop/stream-json commit a869fb98aaef — awaiting tagged release

https://github.com/uhop/stream-json/commit/a869fb98aaef9225556f49901a8f55954ff856e6
github Patch Available🟡 PoC Available

pick/ignore/filter/replace filters are O(depth²) on nested input — small crafted JSON blocks the event loop for seconds→minutes (DoS) · Advisory · uhop/stream-json · GitHub

Affected: 3.5.0. The path filters now cap JSON nesting depth at 1024 by

https://github.com/uhop/stream-json/security/advisories/GHSA-528h-pc64-c93x

Vendor Advisories for CVE-2026-71429(1)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Affected Packages

(1 across 1 ecosystem)
npm(1)
PackageVulnerable rangeFixed inDependents
stream-json3.5.0

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 10× in last 7d / 24× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

  1. 2026-09-18 19:28 UTCEPSS rescore
  2. 2026-09-18 13:24 UTCEG score recompute
  3. 2026-09-16 15:00 UTCEG score recompute
  4. 2026-09-16 14:08 UTCEPSS rescore
  5. 2026-09-16 05:15 UTCEPSS rescore
  6. 2026-09-15 15:53 UTCEG score recompute
  7. 2026-09-15 03:12 UTCEPSS rescore
  8. 2026-09-13 17:38 UTCEG score recompute
  9. 2026-09-12 18:32 UTCEG score recompute
  10. 2026-09-12 15:02 UTCEPSS rescore
  11. 2026-09-11 19:25 UTCEG score recompute
  12. 2026-09-11 14:53 UTCEPSS rescore
  13. 2026-09-10 20:18 UTCEG score recompute
  14. 2026-09-10 09:35 UTCEPSS rescore
  15. 2026-09-08 23:06 UTCEG score recompute
  16. 2026-09-08 22:01 UTCEPSS rescore
  17. 2026-09-06 17:00 UTCEG score recompute
  18. 2026-09-06 13:48 UTCEPSS rescore
  19. 2026-09-05 17:53 UTCEG score recompute
  20. 2026-09-04 18:41 UTCEG score recompute
  21. 2026-09-04 17:52 UTCEG score recompute
  22. 2026-09-03 21:21 UTCEG score recompute
  23. 2026-09-03 20:24 UTCEG score recompute
  24. 2026-09-03 20:23 UTCMITRE cvelistV5first tracked

Frequently asked(5)

What is CVE-2026-71429?
CVE-2026-71429 is a medium vulnerability published on September 3, 2026. 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.…
When was CVE-2026-71429 disclosed?
CVE-2026-71429 was first published in the National Vulnerability Database on September 3, 2026, with the most recent update on September 9, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-71429 actively exploited?
CVE-2026-71429 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0% probability of exploitation in the next 30 days, which ranks it in the top 98.4% of all scored CVEs.
What is the CVSS score of CVE-2026-71429?
CVE-2026-71429 has a CVSS v3 base score of 6.2 (NVD).
How do I remediate CVE-2026-71429?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-71429, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-71429

Explore →

Is Your Infrastructure Affected by CVE-2026-71429?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.