---
id: CVE-2026-104182
title: >-
  stream-json is a micro-library of stream components for processing JSON and
  JSONC with a minimal memory footprint
summary: >-
  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 comm…
severity: medium
cvss: 6.2
cvssVector: 'CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H'
cwe:
  - CWE-407
vendor: uhop
product: stream-json
affected:
  - stream-json < 3.6.0
published: '2026-10-01'
updated: '2026-10-01'
sourceUpdated: '2026-10-01T21:17:19.003'
source: NVD
sourceUrl: 'https://nvd.nist.gov/vuln/detail/CVE-2026-104182'
references:
  - url: >-
      https://github.com/uhop/stream-json/commit/c0299dc168ce9455ef5ca5b6a0f6850ee7fa0468
    label: security-advisories@github.com
  - url: 'https://github.com/uhop/stream-json/releases/tag/3.6.0'
    label: security-advisories@github.com
  - url: >-
      https://github.com/uhop/stream-json/security/advisories/GHSA-hqr4-qq8f-hg3x
    label: security-advisories@github.com
tags:
  - nvd
  - cve.org
ingestedAt: '2026-10-01T21:00:32.274Z'
---

## Overview

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.

## Remediation

Refer to the linked advisories for vendor-supplied fixes and affected version ranges.
