stream-json: JSONC parser and verifier re-scan the whole accumulated comment on every input chunk

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-hqr4-qq8f-hg3x
• https://github.com/uhop/stream-json/security/advisories/GHSA-hqr4-qq8f-hg3x
• https://nvd.nist.gov/vuln/detail/CVE-2026-104182
• https://github.com/uhop/stream-json/commit/c0299dc168ce9455ef5ca5b6a0f6850ee7fa0468
• https://github.com/uhop/stream-json/releases/tag/3.6.0
• https://github.com/advisories/GHSA-hqr4-qq8f-hg3x

Original description

stream-json is a micro-library of stream components for processing JSON and JSONC with a minimal memory footprint. Prior to 3.6.0, the JSONC parser at stream-json/jsonc/parser.js and verifier at stream-json/jsonc/verifier.js restart comment-terminator scanning from the opening slash whenever a block or line comment spans an input chunk, while retaining the accumulated comment buffer. Delivering a large valid comment across many small chunks therefore causes quadratic CPU work and can stall the Node.js event loop. The maintainer characterizes the attack vector as local because the documented JSONC input is locally owned or user-controlled configuration, rather than input intended for the open internet. This JSONC-only scope does not include the plain JSON parser, which advances through and discards consumed string and number data. This issue is fixed in version 3.6.0.