stream-json: pick/ignore/filter/replace filters are O(depth²) on nested input — small crafted JSON blocks the event loop for seconds→minutes (DoS)
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.
- Products
- Not specified
- Affected versions
- Not specified
- Fixed versions
- Not specified
- CVEs
- CVE-2026-71429
- Confirmed fixed CVEs
- Not specified
- Updated in this feed
- 4 Nov 2026, 18:35 UTC · Revision 1
Source evidence
stream-json: pick/ignore/filter/replace filters are O(depth²) on nested input — small crafted JSON blocks the event loop for seconds→minutes (DoS)
core-osv · Original sourcePublished 3 Sept 2026, 20:15 UTC
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.
osv:CVE-2026-71429
Complete source record
{
"id": "6ee322ce8c268bcec081cb6ee3e4c689e191ba4e01290704fb562dbff8850a9d",
"url": "https://osv.dev/vulnerability/CVE-2026-71429",
"method": "structured",
"payload": {
"kind": "advisory",
"title": "stream-json: pick/ignore/filter/replace filters are O(depth²) on nested input — small crafted JSON blocks the event loop for seconds→minutes (DoS)",
"summary": "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.",
"evidence": "osv:CVE-2026-71429",
"products": [],
"severity": "medium",
"structured": {
"id": "CVE-2026-71429",
"aliases": [
"CVE-2026-71429",
"GHSA-528h-pc64-c93x"
],
"metrics": [
{
"type": "CVSS_V3",
"score": "CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H"
}
],
"affected": [
{
"ranges": [
{
"repo": "https://github.com/uhop/stream-json",
"type": "GIT",
"events": [
{
"introduced": "0"
},
{
"fixed": "4b41d269a35bc96334e84baec7f420ef8c344ba6"
},
{
"fixed": "a869fb98aaef9225556f49901a8f55954ff856e6"
}
],
"database_specific": {
"extracted_events": [
{
"range": [
{
"introduced": "0"
},
{
"fixed": "3.5.0"
}
],
"source": "AFFECTED_FIELD",
"strategy": "StringRangeExpression"
},
{
"range": [
{
"fixed": "a869fb98aaef9225556f49901a8f55954ff856e6"
}
],
"source": "REFERENCES_COMMIT"
}
]
}
}
],
"versions": [
"3.4.0",
"3.3.0",
"3.2.0",
"3.1.0",
"3.0.0",
"2.1.0",
"2.0.0",
"1.9.0",
"1.8.0",
"1.7.5",
"1.7.4",
"1.7.3",
"1.7.2",
"1.7.1",
"1.7.0",
"1.6.1",
"1.6.0",
"1.5.0",
"1.4.1",
"1.4.0",
"1.3.3",
"1.3.2",
"1.3.1",
"1.3.0",
"1.2.1",
"1.2.0",
"1.1.4",
"1.1.3",
"1.1.2",
"1.1.1",
"1.1.0",
"1.0.3",
"1.0.2",
"1.0.1",
"1.0.0",
"0.6.1",
"0.6.0",
"0.5.3",
"0.5.2",
"0.5.1",
"0.5.0",
"0.4.2",
"0.4.1",
"0.3.0",
"0.2.2",
"0.2.1",
"0.2.0",
"0.1.0",
"0.0.5",
"0.0.4",
"0.0.3",
"0.0.2",
"0.0.1"
],
"database_specific": {
"source": "https://storage.googleapis.com/cve-osv-conversion/osv-output/CVE-2026-71429.json"
}
}
],
"modified": "2026-10-28T02:30:38.492051859Z",
"provider": "osv",
"references": [
"https://github.com/CVEProject/cvelistV5/tree/main/cves/2026/71xxx/CVE-2026-71429.json",
"https://github.com/uhop/stream-json/security/advisories/GHSA-528h-pc64-c93x",
"https://nvd.nist.gov/vuln/detail/CVE-2026-71429",
"https://github.com/uhop/stream-json/commit/a869fb98aaef9225556f49901a8f55954ff856e6"
],
"provider_metadata": {
"cwe_ids": [
"CWE-407"
],
"cna_assigner": "GitHub_M",
"osv_generated_from": "https://github.com/CVEProject/cvelistV5/tree/main/cves/2026/71xxx/CVE-2026-71429.json"
}
},
"related_cves": [
{
"value": "CVE-2026-71429",
"evidence": "/id"
}
],
"security_relevant": true,
"severity_evidence": "/severity/0/score"
},
"source_id": "core-osv",
"document_id": 505738,
"published_at": "2026-09-03T20:15:19.721+00:00"
}