CVE-2026-104874

MEDIUMPre-NVD 5.35.3
EchelonGraph scoreMEDIUM confidence

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

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

Triggered by: GitHub Security Advisory CVSS
Sources: EPSS, GitHub Security Advisory, a secondary CVSS source
Elevated

Also known asEUVD-2026-91800 (ENISA EUVD) · GHSA-54p9-h82j-f925 (GitHub Security Advisories) · PYSEC-2026-4244 (OSV.dev)Source: ENISA EUVD

5.3EG
EchelonGraph verdictPlan a fixRemediate within your standard update timelines at low or medium mission impact and sooner than that at high (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.4%CVSS: 5.3Exploit: No code on recordExposed services: Not assessed

A fix is available — apply it.

Multidict is an implementation of a multidict data structure. From 6.7.0 until 6.9.1, the C extension's items-view reflected union operation, operand | d.items(), in multidict_itemsview_or2_impl and subtraction operation, d.items() - operand, in multidict_itemsview_sub1_impl fail to release new key-identity and value references returned for each operand element. Applications that perform these operations over attacker-influenced sequences can leak two strong references per element, and garbage collection cannot reclaim them, so repeated operations can cause unbounded process memory growth and denial of service. Forward union, intersection, non-tuple operand elements, and pure-Python builds are not affected by this reference leak. This issue is fixed in version 6.9.1.

CVSS v3
5.3
EG Score
5.3MEDIUMmedium confidence
EG Risk
55
EG Risk 55/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)
Severity53% × 45%
Impact severity (EG Severity): CVSS 5.3 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.
Automatability100% × 15%
CISA's SSVC Automatable value: yes (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at low or medium mission impact; Attend at high (mission-essential systems).
Exploitation public PoC (CISA Vulnrichment) · Automatable yes (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 at low or medium mission impact and sooner than that at high.
EPSS PROB
0.4%
EPSS %ILE
39th
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 (5.3): severity, escalated by confirmed exploitation. This CVE's 5.3 is its impact severity (EG Severity), not escalated.

EG Severity
5.3 MEDIUMCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.GitHub Security Advisory CVSS
EG Likelihood
0.4% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-11-04). 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; Attend at high (mission-essential systems).CISA BOD 26-04: 14 days if the affected system is publicly exposed; 60 days 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; Attend at high (mission-essential systems).

A fix is available. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high.

Exploitation public PoC (CISA Vulnrichment) · Automatable yes (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)14 days if the affected system is publicly exposed; 60 days if it is not.

The score's inputs: In CISA KEV no (CISA's KEV catalog) · Automatable yes (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 2, 2026

Last Modified

October 6, 2026

Advisory Details (2)

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

commit 350b4a07bf8f (aio-libs/multidict)

Fix landed in aio-libs/multidict commit 350b4a07bf8f — awaiting tagged release

https://github.com/aio-libs/multidict/commit/350b4a07bf8ff851b6d7544e81b1c748bdc74c40
GitHub advisoryMentions a patch (unverified)

Reference leak in CIMultiDict/MultiDict items-view union and subtraction · Advisory · aio-libs/multidict · GitHub

https://github.com/aio-libs/multidict/security/advisories/GHSA-54p9-h82j-f925

Patch Availability(15)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
redhatrhelai3/disk-image-cuda-rhel9:17932067582026-10-29redhat
redhatrhelai3/bootc-rocm-rhel9:17931358632026-10-29redhat
redhatrhelai3/disk-image-cuda-rhel9:17927017962026-10-26redhat
redhatrhelai3/bootc-rocm-rhel9:17926129212026-10-26redhat
redhatrhaii/model-opt-cuda-rhel9:17918571102026-10-14redhat
redhatrhaii/vllm-cpu-rhel9:17918573012026-10-14redhat
redhatrhaii/vllm-cuda-rhel9:17918571832026-10-14redhat
redhatrhaii/vllm-rocm-rhel9:17918567252026-10-14redhat
redhatrhaii/vllm-spyre-rhel9:17918585922026-10-14redhat
redhatrhaii/vllm-gaudi-rhel9:17914271822026-10-13redhat
redhatrhaii/vllm-cpu-rhel9:17914736142026-10-13redhat
redhatrhaii/vllm-cuda-rhel9:17914736312026-10-13redhat
redhatrhaii/vllm-spyre-rhel9:17918183572026-10-13redhat
redhatrhaii/vllm-rocm-rhel9:17914258692026-10-13redhat
pipmultidict @ 6.9.1 (fixes >= 6.7.0, <= 6.9.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)
PyPI(1)
PackageVulnerable rangeFix by version rangeDependents
multidict6.7.0, 6.7.1, 6.8.0, 6.9.0
  • 6.7.0 up to 6.9.1: fixed in 6.9.1
—

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 7× in last 7d / 34× 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 its CVE.org record (CNA or CISA ADP). 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). "EchelonGraph re-scored" is our own recompute of this CVE's score, not an update from a source, and is not counted in the refreshes above. Most recent first.

  1. 2026-11-12 16:32 UTCEPSS rescoreEPSS 0.4% · 39th percentile
  2. 2026-11-11 16:37 UTCEPSS rescoreEPSS 0.4% · 39th percentile
  3. 2026-11-10 16:41 UTCEPSS rescoreEPSS 0.4% · 39th percentile
  4. 2026-11-09 16:34 UTCEPSS rescoreEPSS 0.4% · 39th percentile
  5. 2026-11-08 16:38 UTCEPSS rescoreEPSS 0.4% · 39th percentile
  6. 2026-11-07 16:38 UTCEPSS rescoreEPSS 0.4% · 39th percentile
  7. 2026-11-06 16:35 UTCEPSS rescoreEPSS 0.4% · 39th percentile
  8. 2026-11-05 16:36 UTCEPSS rescoreEPSS 0.4% · 39th percentile
  9. 2026-11-04 23:43 UTCEchelonGraph re-scored
  10. 2026-11-04 23:43 UTCVendor advisory
  11. 2026-11-04 23:43 UTCGHSA enrichmentGHSA-54p9-h82j-f925 · GitHub severity MODERATE · GitHub CVSS 5.3
  12. 2026-11-04 16:34 UTCEPSS rescoreEPSS 0.4% · 39th percentile
  13. 2026-11-03 16:46 UTCEPSS rescoreEPSS 0.4% · 39th percentile
  14. 2026-11-02 16:43 UTCEPSS rescoreEPSS 0.4% · 38th percentile
  15. 2026-11-01 16:33 UTCEPSS rescoreEPSS 0.4% · 38th percentile
  16. 2026-11-01 08:00 UTCGHSA enrichmentGHSA-54p9-h82j-f925 · GitHub severity MODERATE · GitHub CVSS 5.3
  17. 2026-11-01 08:00 UTCEchelonGraph re-scored
  18. 2026-10-31 16:31 UTCEPSS rescoreEPSS 0.4% · 38th percentile
  19. 2026-10-31 11:55 UTCOSV refresh
  20. 2026-10-30 16:33 UTCEPSS rescoreEPSS 0.4% · 38th percentile
  21. 2026-10-29 16:32 UTCEPSS rescoreEPSS 0.4% · 38th percentile
  22. 2026-10-28 16:31 UTCEPSS rescoreEPSS 0.4% · 38th percentile
  23. 2026-10-27 16:31 UTCEPSS rescoreEPSS 0.4% · 38th percentile
  24. 2026-10-26 16:30 UTCEPSS rescoreEPSS 0.4% · 38th percentile
  25. 2026-10-25 16:32 UTCEPSS rescoreEPSS 0.4% · 38th percentile
Show 40 more
  1. 2026-10-25 14:55 UTCEchelonGraph re-scored
  2. 2026-10-24 16:32 UTCEPSS rescoreEPSS 0.3% · 21st percentile
  3. 2026-10-23 16:31 UTCEPSS rescoreEPSS 0.3% · 21st percentile
  4. 2026-10-23 09:16 UTCEchelonGraph re-scored
  5. 2026-10-23 09:16 UTCVendor advisory
  6. 2026-10-22 16:33 UTCEPSS rescoreEPSS 0.3% · 21st percentile
  7. 2026-10-21 16:32 UTCEPSS rescoreEPSS 0.3% · 21st percentile
  8. 2026-10-20 16:31 UTCEPSS rescoreEPSS 0.3% · 21st percentile
  9. 2026-10-19 16:31 UTCEPSS rescoreEPSS 0.3% · 21st percentile
  10. 2026-10-18 05:09 UTCEchelonGraph re-scored
  11. 2026-10-17 16:33 UTCEPSS rescoreEPSS 0.3% · 20th percentile
  12. 2026-10-16 16:40 UTCEPSS rescoreEPSS 0.3% · 20th percentile
  13. 2026-10-15 16:31 UTCEPSS rescoreEPSS 0.3% · 20th percentile
  14. 2026-10-14 16:31 UTCEPSS rescoreEPSS 0.3% · 20th percentile
  15. 2026-10-13 16:33 UTCEPSS rescoreEPSS 0.3% · 20th percentile
  16. 2026-10-12 16:40 UTCEchelonGraph re-scored
  17. 2026-10-12 16:33 UTCEPSS rescoreEPSS 0.3% · 20th percentile
  18. 2026-10-11 20:15 UTCEchelonGraph re-scored
  19. 2026-10-11 18:27 UTCEchelonGraph re-scored
  20. 2026-10-11 15:01 UTCEchelonGraph re-scored
  21. 2026-10-11 13:47 UTCEPSS rescoreEPSS 0.3% · 20th percentile
  22. 2026-10-11 11:28 UTCEchelonGraph re-scored
  23. 2026-10-10 19:59 UTCEPSS rescoreEPSS 0.3% · 20th percentile
  24. 2026-10-10 12:50 UTCEchelonGraph re-scored
  25. 2026-10-09 20:06 UTCEPSS rescoreEPSS 0.3% · 20th percentile
  26. 2026-10-09 14:08 UTCEchelonGraph re-scored
  27. 2026-10-08 17:11 UTCEPSS rescoreEPSS 0.3% · 20th percentile
  28. 2026-10-08 15:29 UTCEchelonGraph re-scored
  29. 2026-10-07 23:47 UTCEPSS rescoreEPSS 0.3% · 20th percentile
  30. 2026-10-06 16:07 UTCEchelonGraph re-scored
  31. 2026-10-06 15:17 UTCEPSS rescoreEPSS 0.3% · 20th percentile
  32. 2026-10-05 17:42 UTCEPSS rescoreEPSS 0.3% · 20th percentile
  33. 2026-10-05 17:29 UTCEchelonGraph re-scored
  34. 2026-10-05 16:32 UTCEchelonGraph re-scored
  35. 2026-10-04 23:21 UTCEPSS rescoreEPSS 0.3% · 20th percentile
  36. 2026-10-03 20:00 UTCEchelonGraph re-scored
  37. 2026-10-03 14:25 UTCEPSS rescoreEPSS 0.3% · 20th percentile
  38. 2026-10-02 21:22 UTCEchelonGraph re-scored
  39. 2026-10-02 20:28 UTCEchelonGraph re-scoredFirst assessed: 5.3 MEDIUM
  40. 2026-10-02 20:25 UTCMITRE cvelistV5first tracked

Frequently asked(5)

What is CVE-2026-104874?
CVE-2026-104874 is a medium-severity vulnerability; its CVE record was published on October 2, 2026. Multidict is an implementation of a multidict data structure. From 6.7.0 until 6.9.1, the C extension's items-view reflected union operation, operand | d.items(), in multidict_itemsview_or2_impl and subtraction operation, d.items() - operand, in multidict_itemsview_sub1_impl fail to release new…
When was the CVE record for CVE-2026-104874 published?
The CVE record for CVE-2026-104874 was published on October 2, 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 6, 2026; the record at its source may have been updated since.
Is CVE-2026-104874 actively exploited?
CVE-2026-104874 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.4% probability of exploitation in the next 30 days (39th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-104874?
CVE-2026-104874 has a CVSS base score of 5.3 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-104874?
A fix for CVE-2026-104874 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-104874 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-104874

Explore →

Is Your Infrastructure Affected by CVE-2026-104874?

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