Advisory record · GHSA-hqr4-qq8f-hg3x

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

CVSS 6.2 MediumEPSS 0.0020 · 10th percentile

Published by the GitHub Advisory Database at 5 Oct 2026, 22:49 UTC. agentprime has not analysed this yet, so whether it affects any app is not known.

PackageEcosystemAffectedFixed in
stream-jsonnpm<3.6.03.6.0
Identifiers
GHSA-hqr4-qq8f-hg3x · CVE-2026-104182
Weakness (CWE)
CWE-407
Published
5 Oct 2026
Updated
5 Oct 2026

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.

Written 31 Oct 2026.

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

ScoreRatingCVSSVectorSource
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

  1. 31 Oct 2026, 13:34 UTC First seen by agentprime
  2. 31 Oct 2026, 13:34 UTC Confirmed by OSV

Sources

Facts on this page come from the GitHub Advisory Database (CC-BY 4.0), OSV and the other sources listed, as published. We don’t reproduce full advisory descriptions, which can contain exploit code.