CVE-2026-104182
stream-json is a micro-library of stream components for processing …
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.
What to do now
- Check your exposureFind out whether the affected software runs anywhere in your environment, including systems of suppliers.
- UpdateInstall the version in which the vendor fixed the vulnerability. The references lead to the advisory.
- Set the orderSystems that can be reached from the internet come first, then the rest.
References
- github.com/uhop/stream-json/commit/c0299dc168ce9455ef5ca5b6a0f6850ee7fa0468
- github.com/uhop/stream-json/releases/tag/3.6.0
- github.com/uhop/stream-json/security/advisories/GHSA-hqr4-qq8f-hg3x
- nvd.nist.gov/vuln/detail/CVE-2026-104182
- github.com/advisories/GHSA-hqr4-qq8f-hg3x
- nvd.nist.gov/vuln/detail/CVE-2026-104182
- cve.org/CVERecord?id=CVE-2026-104182
Data: CVE list and the NVD. This product uses data from the NVD API but is not endorsed or certified by the NVD.