Machine-written summary
Summary written by Claude Haiku from the source advisory. Not reviewed by a person.
Versions of stream-json before 3.6.0 re-scan a JSONC comment from its start on every input chunk, so a long comment costs quadratic CPU time. The reporter says an unauthenticated remote sender can block a service's event loop, while the maintainer says JSONC is meant for user-owned input and not the open internet. Upgrade to stream-json 3.6.0, which scans comments in linear time.
Not analysed yet
We haven’t published our analysis of this Advisory yet. Once a person has reviewed it, this page will say what’s vulnerable, what has to be true for your app to be affected, and how to check.
Severity and exploitation
| Score | Rating | CVSS | Vector | Source |
|---|---|---|---|---|
| 6.2 | Medium | 3.1 | CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H | CNA (GitHub_M) |
- CISA KEV Not listed.
- EPSS 0.0020, the 10th percentile, on 12 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.
Timeline
- 31 Oct 2026, 13:34 UTC First seen by agentprime
- 31 Oct 2026, 13:34 UTC Confirmed by OSV
Sources
- GitHub Advisory Database: GHSA-hqr4-qq8f-hg3x
- OSV: GHSA-hqr4-qq8f-hg3x
- github.com/uhop/stream-json/security/advisories/GHSA-hqr4-qq8f-hg3x
- nvd.nist.gov/vuln/detail/CVE-2026-104182
- github.com/uhop/stream-json/commit/c0299dc168ce9455ef5ca5b6a0f6850ee7fa0468
- github.com/uhop/stream-json
- github.com/uhop/stream-json/releases/tag/3.6.0