CVE-2026-104182

MEDIUMPre-NVD 6.26.2
EchelonGraph scoreHIGH confidence

“—” beside the score: it is equal to the CVSS score beside it.

Score 6.2 from GitHub Security Advisory (severity: MODERATE) published 2026-10-05. A secondary CVSS source baseline 6.2; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: EPSS, GitHub Security Advisory, a secondary CVSS source
Trending — 4 sources updated this weekElevated

Also known asEUVD-2026-91056 (ENISA EUVD) · GHSA-hqr4-qq8f-hg3x (GitHub Security Advisories)Source: ENISA EUVD

6.2EG
EchelonGraph verdictPlan a fixRemediate within your standard update timelines (the SSVC decision on this page).
  • CISA's Vulnrichment rates exploitation as PoC; EchelonGraph holds no exploit-code reference for it
CISA-KEV: Not listedEPSS PROB: 0.2%CVSS: 6.2Exploit: No code on recordExposed services: Not assessed

A fix is available — apply it.

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.

CVSS v3
6.2
EG Score
6.2MEDIUMhigh confidence
EG Risk
44
EG Risk 44/100

EG Risk is EchelonGraph's 0–100 priority score. It fuses impact severity (EG Severity, the CVSS base score, never the KEV-floored or EPSS-lifted EG Score) with real-world exploitation and automatability, under weights EchelonGraph set by hand, so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner.

How it’s computed (value × EchelonGraph’s weight)
Severity62% × 45%
Impact severity (EG Severity): CVSS 6.2 of 10. Never the KEV-floored or EPSS-lifted EG Score.
Exploitation40% × 40%
EchelonGraph's fixed weight for EG-KEV Tier 3 (Elevated): a constant, not a probability.
Automatability0% × 15%
CISA's SSVC Automatable value: no (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at low or medium mission impact; Track* at high (mission-essential systems).
Exploitation public PoC (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE.
Action: A fix is available. Apply it within your standard update timelines.
EPSS PROB
0.2%
EPSS %ILE
10th
KEV
Not listed

What the EG score is made of (scorer v4.0: the three questions the 0–10 score mixes, published apart · methodology)

The EG score (6.2): severity, escalated by confirmed exploitation. This CVE's 6.2 is its impact severity (EG Severity), not escalated.

EG Severity
6.2 MEDIUMCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.GitHub Security Advisory CVSS
EG Likelihood
0.2% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-10-31). FIRST's exploitation probability, not an EchelonGraph model.
Confirmed exploitation
None on record (CISA KEV, EG-KEV Tier 1)Reported apart from the likelihood: an observed fact, not a probability.
EG Priority
SSVC Track at medium mission impactTrack at low or medium mission impact; Track* at high (mission-essential systems).CISA BOD 26-04: 60 days if the affected system is publicly exposed; Fix on system upgrade if it is not.Each input and its source, and whom BOD 26-04 binds: the SSVC and BOD 26-04 blocks below.

SSVC (CISA's decision table, applied by EchelonGraph)Track at low or medium mission impact; Track* at high (mission-essential systems).

A fix is available. Apply it within your standard update timelines.

Exploitation public PoC (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE. Mission impact is CISA's Mission & Well-being decision point, and only you can judge it. CISA's table makes it high when Mission Prevalence is Essential — the vulnerable component "directly provides capabilities that constitute at least one MEF for at least one entity" (MEF: mission essential function) — or when Public Well-Being Impact is Irreversible: "multiple fatalities are likely", the cyber-physical system "is likely lost or destroyed", "extreme or serious externalities" are imposed on other parties, or social systems such as elections or the financial grid "are destabilized and potentially collapse". CISA's decision table

BOD 26-04 (CISA's remediation timeline, Table 1)60 days if the affected system is publicly exposed; Fix on system upgrade if it is not.

The score's inputs: In CISA KEV no (CISA's KEV catalog) · Automatable no (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). Whether your system is publicly exposed is yours to answer. BOD 26-04 binds US Federal Civilian Executive Branch agencies; for anyone else it is CISA's published timeline, a reference rather than an obligation. The directive · how EchelonGraph applies it

Published

October 1, 2026

Last Modified

October 5, 2026

Advisory Details (2)

Auto-updated Oct 1, 2026
Patch available. Sources: github, github_commit.
GitHub commit

commit c0299dc168ce (uhop/stream-json)

Fix landed in uhop/stream-json commit c0299dc168ce — awaiting tagged release

https://github.com/uhop/stream-json/commit/c0299dc168ce9455ef5ca5b6a0f6850ee7fa0468
GitHub advisoryMentions a patch (unverified)

JSONC parser and verifier re-scan the whole accumulated comment on every input chunk, so a large block or line comment delivered across chunks costs O(n^2) CPU and stalls the event loop (remote unauthenticated DoS) · Advisory · uhop/stream-json · GitHub

https://github.com/uhop/stream-json/security/advisories/GHSA-hqr4-qq8f-hg3x

Vendor Advisories for CVE-2026-104182(1)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Patch Availability(1)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
npmstream-json @ 3.6.0 (fixes <= 3.5.0)—ghsa

Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.

Affected Packages

(1 across 1 ecosystem)
npm(1)
PackageVulnerable rangeFix by version rangeDependents
stream-json—
  • every version up to 3.6.0: fixed in 3.6.0
—

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 10× in last 7d / 49× in last 30d)

Each row is a time one of our pipelines fetched, updated or re-scored this CVE. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. An arrow marks a change the record states ("CVSS v3 → 9.1"); EPSS and GHSA rows show the values recorded at that time, not what changed (EPSS values are rounded; hover one for the exact figures). Most recent first.

  1. 2026-11-01 16:33 UTCEPSS rescoreEPSS 0.2% · 10th percentile
  2. 2026-11-01 08:00 UTCGHSA enrichmentGHSA-hqr4-qq8f-hg3x · GitHub severity MODERATE · GitHub CVSS 6.2
  3. 2026-11-01 08:00 UTCEG score recompute
  4. 2026-10-31 16:31 UTCEPSS rescoreEPSS 0.2% · 10th percentile
  5. 2026-10-31 11:55 UTCOSV refresh
  6. 2026-10-30 16:33 UTCEPSS rescoreEPSS 0.2% · 10th percentile
  7. 2026-10-29 16:32 UTCEPSS rescoreEPSS 0.2% · 10th percentile
  8. 2026-10-28 16:31 UTCEPSS rescoreEPSS 0.2% · 10th percentile
  9. 2026-10-27 16:31 UTCEPSS rescoreEPSS 0.2% · 10th percentile
  10. 2026-10-26 16:30 UTCEPSS rescoreEPSS 0.2% · 10th percentile
  11. 2026-10-25 16:32 UTCEPSS rescoreEPSS 0.2% · 10th percentile
  12. 2026-10-25 14:56 UTCEG score recompute
  13. 2026-10-24 16:31 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  14. 2026-10-23 16:31 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  15. 2026-10-23 09:17 UTCEG score recompute
  16. 2026-10-22 16:33 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  17. 2026-10-21 16:31 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  18. 2026-10-20 16:31 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  19. 2026-10-19 16:31 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  20. 2026-10-18 16:31 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  21. 2026-10-18 05:09 UTCEG score recompute
  22. 2026-10-17 16:33 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  23. 2026-10-16 16:40 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  24. 2026-10-15 16:31 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  25. 2026-10-14 16:31 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
Show 28 more
  1. 2026-10-13 16:33 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  2. 2026-10-12 16:40 UTCEG score recompute
  3. 2026-10-12 16:33 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  4. 2026-10-11 20:15 UTCEG score recompute
  5. 2026-10-11 18:27 UTCEG score recompute
  6. 2026-10-11 15:01 UTCEG score recompute
  7. 2026-10-11 13:47 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  8. 2026-10-11 09:33 UTCEG score recompute
  9. 2026-10-10 19:59 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  10. 2026-10-10 07:05 UTCEG score recompute
  11. 2026-10-09 20:06 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  12. 2026-10-09 04:40 UTCEG score recompute
  13. 2026-10-08 17:11 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  14. 2026-10-08 02:16 UTCEG score recompute
  15. 2026-10-07 23:47 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  16. 2026-10-06 23:50 UTCEG score recompute
  17. 2026-10-06 15:17 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  18. 2026-10-05 21:27 UTCEG score recompute
  19. 2026-10-05 21:13 UTCEG score recompute
  20. 2026-10-05 17:42 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  21. 2026-10-04 23:38 UTCEG score recompute
  22. 2026-10-04 23:21 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  23. 2026-10-03 21:15 UTCEG score recompute
  24. 2026-10-03 14:25 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  25. 2026-10-02 18:51 UTCEG score recompute
  26. 2026-10-01 21:20 UTCEG score recompute
  27. 2026-10-01 20:22 UTCEG score recomputeFirst assessed: 6.2 MEDIUM
  28. 2026-10-01 20:20 UTCMITRE cvelistV5first tracked

Related CVEs(same product + same CWE)

Frequently asked(5)

What is CVE-2026-104182?
CVE-2026-104182 is a medium-severity vulnerability; its CVE record was published on October 1, 2026. 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…
When was the CVE record for CVE-2026-104182 published?
The CVE record for CVE-2026-104182 was published on October 1, 2026. That is the record's publication date; the vulnerability itself may have been made public earlier. EchelonGraph's copy of the record carries a last-modified date of October 5, 2026; the record at its source may have been updated since.
Is CVE-2026-104182 actively exploited?
CVE-2026-104182 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.2% probability of exploitation in the next 30 days (10th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-104182?
CVE-2026-104182 has a CVSS base score of 6.2 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-104182?
A fix for CVE-2026-104182 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-104182 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-104182

Explore →

Is Your Infrastructure Affected by CVE-2026-104182?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Book a Demo →Browse All CVEs