CVE-2026-104182: uhop stream-json · Inefficient Algorithmic Complexity
Affects uhop stream-jsonSource CVE Database V5
Not known to be exploited · CVSS 6.2 Medium : upgrade to 3.6.0 when convenient.
Data as of 15 Nov 2026, 20:25 UTC
- EPSS
- 0.2% chance of exploitation in 30 days – higher than 10% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
- Patch
- Available – fixed in 3.6.0
CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:HExploitation evidence
Disclosed: evidence found.
CVE published 1 Oct 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 15 Nov 2026.
What to do
Upgrade uhop stream-json to 3.6.0.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| uhopstream-json | Affected
| Fixed in
|
npmstream-jsonpkg:npm/stream-jsonOther threats | Affected
| Fixed in
|
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
AI-suggested
Upgrade the stream-json library to version 3.6.0 or later, where this inefficiency is fixed. Since the vulnerability is local and related to JSONC input processing, ensure that user-controlled or local configuration inputs are validated or sanitized if upgrading is not immediately possible. No other vendor advisory or patch links are provided, so check the official uhop stream-json repository for the fixed version 3.6.0.
Description
CVE-2026-104182 is an inefficient algorithmic complexity vulnerability in the JSONC parser and verifier components of the uhop stream-json library prior to version 3.6.0. The issue arises when processing large valid comments split across many small input chunks, causing quadratic CPU usage and potentially stalling the Node.js event loop. This vulnerability affects only the JSONC parser, not the plain JSON parser. The maintainer notes the attack vector is local, involving user-controlled or locally owned configuration input rather than internet-facing input. The issue is fixed in version 3.6.0.