CVE-2026-57585

HIGHPre-NVD 7.57.5
EchelonGraph scoreMEDIUM confidence

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

This high-severity CVE scores 7.5 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.5% (41st percentile of EPSS-scored CVEs). No GitHub Security Advisory CVSS is on record for this CVE.

Triggered by: Headline CVSS from a secondary CVSS source
Sources: EPSS, a secondary CVSS source
Trending — 3 sources updated this week
7.5EG
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).
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0.5%CVSS: 7.5Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

MessagePack is the serializer implementation for Python msgpack.org. Prior to 1.2.1, there is an Out-of-bounds read/crash on Unpacker reuse after a caught error, potentially leading to a DoS attack. If the Unpacker is used repeatedly after an error occurs, the process may crash with a SEGV. This issue has been fixed in version 1.2.1.

CVSS v3
7.5
EG Score
7.5HIGHmedium confidence
EG Risk
49
EG Risk 49/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)
Severity75% × 45%
Impact severity (EG Severity): CVSS 7.5 of 10. Never the KEV-floored or EPSS-lifted EG Score.
Exploitation0.5% × 40%
FIRST EPSS: the 30-day exploitation probability when EchelonGraph scored this CVE.
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 none (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.5%
EPSS %ILE
41st
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 (7.5): severity, escalated by confirmed exploitation. This CVE's 7.5 is its impact severity (EG Severity), not escalated.

EG Severity
7.5 HIGHCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.a secondary CVSS source · CVSS v3.0 or v3.1
EG Likelihood
0.5% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-10-17). 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: 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 none (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.

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

June 30, 2026

Last Modified

August 6, 2026

Advisory Details (2)

Auto-updated Jun 30, 2026
Patch available. Sources: github_commit, github.
GitHub advisoryMentions a patch (unverified)

Out-of-bounds read / crash on Unpacker reuse after a caught error · Advisory · msgpack/msgpack-python · GitHub

https://github.com/msgpack/msgpack-python/security/advisories/GHSA-6v7p-g79w-8964
GitHub commit Patch Available

commit 2c56ddb5d002 (msgpack/msgpack-python)

Patch available: msgpack/msgpack-python v1.2.1 (contains commit 2c56ddb5d002)

https://github.com/msgpack/msgpack-python/commit/2c56ddb5d0025ed481d962c0f5d62d19dec7476d

Patch Availability(5)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
redhatrhaiis/vllm-rocm-rhel9:17906217132026-09-30redhat
redhatrhaiis/vllm-cuda-rhel9:17906217182026-09-30redhat
redhatrhaii/vllm-cpu-rhel9:17900757932026-09-23redhat
redhatrhaii/vllm-cuda-rhel9:17900901312026-09-23redhat
redhatrhaii/vllm-rocm-rhel9:17901096202026-09-23redhat

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

(5 across 5 ecosystems)
Debian:11(1)
PackageVulnerable rangeFix by version rangeDependents
python-msgpack1.0.0-6 ... 1.1.2-4 (10 versions)
  • every version on: no fix on record
—
Debian:12(1)
PackageVulnerable rangeFix by version rangeDependents
python-msgpack1.0.3-2 ... 1.2.1-1 (7 versions)
  • every version on: no fix on record
—
Debian:13(1)
PackageVulnerable rangeFix by version rangeDependents
python-msgpack1.0.3-3 ... 1.2.1-1 (6 versions)
  • every version on: no fix on record
—
Debian:14(1)
PackageVulnerable rangeFix by version rangeDependents
python-msgpack1.0.3-3, 1.1.2-1, 1.1.2-2
  • every version up to 1.1.2-3: fixed in 1.1.2-3
—
PyPI(1)
PackageVulnerable rangeFix by version rangeDependents
msgpack0.5.0 ... 1.2.0rc1 (32 versions)
  • every version up to 1.2.1: fixed in 1.2.1
—

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 10× in last 7d / 38× 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.

Showing the most recent 100 of 229 refreshes on record for this CVE.

A repeat, a row identical to one the same pipeline wrote less than 10 seconds earlier, is not a separate refresh and is not counted. None are among the latest 100 rows. The 129 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

  1. 2026-10-21 16:33 UTCEPSS rescoreEPSS 0.5% · 41st percentile
  2. 2026-10-20 16:33 UTCEPSS rescoreEPSS 0.5% · 40th percentile
  3. 2026-10-19 16:32 UTCEPSS rescoreEPSS 0.5% · 40th percentile
  4. 2026-10-18 16:32 UTCEPSS rescoreEPSS 0.5% · 40th percentile
  5. 2026-10-18 03:28 UTCEG score recompute
  6. 2026-10-17 16:34 UTCEPSS rescoreEPSS 0.5% · 40th percentile
  7. 2026-10-16 16:42 UTCEPSS rescoreEPSS 0.5% · 40th percentile
  8. 2026-10-16 13:23 UTCEG score recompute
  9. 2026-10-16 13:23 UTCVendor advisory
  10. 2026-10-15 16:32 UTCEPSS rescoreEPSS 0.5% · 40th percentile
  11. 2026-10-14 16:33 UTCEPSS rescoreEPSS 0.5% · 40th percentile
  12. 2026-10-13 18:24 UTCOSV refresh
  13. 2026-10-13 16:34 UTCEPSS rescoreEPSS 0.5% · 40th percentile
  14. 2026-10-12 16:34 UTCEPSS rescoreEPSS 0.5% · 40th percentile
  15. 2026-10-12 15:54 UTCEG score recompute
  16. 2026-10-11 19:37 UTCEG score recompute
  17. 2026-10-11 16:52 UTCEG score recompute
  18. 2026-10-11 14:15 UTCEG score recompute
  19. 2026-10-11 13:49 UTCEPSS rescoreEPSS 0.5% · 40th percentile
  20. 2026-10-10 20:00 UTCEPSS rescoreEPSS 0.5% · 40th percentile
  21. 2026-10-09 20:07 UTCEPSS rescoreEPSS 0.5% · 40th percentile
  22. 2026-10-08 17:13 UTCEPSS rescoreEPSS 0.5% · 40th percentile
  23. 2026-10-07 23:48 UTCEPSS rescoreEPSS 0.5% · 40th percentile
  24. 2026-10-06 15:18 UTCEPSS rescoreEPSS 0.5% · 39th percentile
  25. 2026-10-05 17:43 UTCEPSS rescoreEPSS 0.5% · 39th percentile
Show 75 more
  1. 2026-10-04 23:22 UTCEPSS rescoreEPSS 0.5% · 39th percentile
  2. 2026-10-03 14:26 UTCEPSS rescoreEPSS 0.5% · 39th percentile
  3. 2026-10-02 17:56 UTCEPSS rescoreEPSS 0.5% · 39th percentile
  4. 2026-10-01 19:50 UTCEPSS rescoreEPSS 0.5% · 39th percentile
  5. 2026-09-30 15:03 UTCEPSS rescoreEPSS 0.5% · 39th percentile
  6. 2026-09-29 15:22 UTCEPSS rescoreEPSS 0.5% · 39th percentile
  7. 2026-09-28 13:51 UTCEPSS rescoreEPSS 0.5% · 39th percentile
  8. 2026-09-27 13:48 UTCEPSS rescoreEPSS 0.5% · 39th percentile
  9. 2026-09-26 15:59 UTCEPSS rescoreEPSS 0.5% · 39th percentile
  10. 2026-09-24 14:04 UTCEPSS rescoreEPSS 0.5% · 39th percentile
  11. 2026-09-23 17:54 UTCEPSS rescoreEPSS 0.5% · 41st percentile
  12. 2026-09-23 07:16 UTCEG score recompute
  13. 2026-09-23 07:16 UTCVendor advisory
  14. 2026-09-20 20:16 UTCEPSS rescoreEPSS 0.5% · 41st percentile
  15. 2026-09-18 19:28 UTCEPSS rescoreEPSS 0.5% · 41st percentile
  16. 2026-09-18 06:47 UTCEG score recompute
  17. 2026-09-18 06:47 UTCVendor advisory
  18. 2026-09-17 19:31 UTCEPSS rescoreEPSS 0.5% · 40th percentile
  19. 2026-09-16 14:08 UTCEPSS rescoreEPSS 0.5% · 40th percentile
  20. 2026-09-16 05:15 UTCEPSS rescoreEPSS 0.5% · 40th percentile
  21. 2026-09-15 03:11 UTCEPSS rescoreEPSS 0.5% · 40th percentile
  22. 2026-09-14 00:46 UTCEG score recompute
  23. 2026-09-14 00:46 UTCVendor advisory
  24. 2026-09-13 16:47 UTCEPSS rescoreEPSS 0.5% · 40th percentile
  25. 2026-09-13 09:15 UTCVendor advisory
  26. 2026-09-12 15:08 UTCEG score recompute
  27. 2026-09-12 15:08 UTCVendor advisory
  28. 2026-09-11 14:53 UTCEPSS rescoreEPSS 0.5% · 40th percentile
  29. 2026-09-10 09:35 UTCEPSS rescoreEPSS 0.5% · 40th percentile
  30. 2026-09-08 22:01 UTCEPSS rescoreEPSS 0.5% · 40th percentile
  31. 2026-09-07 16:01 UTCEPSS rescoreEPSS 0.5% · 40th percentile
  32. 2026-09-06 14:34 UTCEG score recompute
  33. 2026-09-06 14:34 UTCVendor advisory
  34. 2026-09-06 13:47 UTCEPSS rescoreEPSS 0.5% · 40th percentile
  35. 2026-09-04 05:07 UTCEPSS rescoreEPSS 0.5% · 40th percentile
  36. 2026-09-02 14:12 UTCEPSS rescoreEPSS 0.5% · 40th percentile
  37. 2026-09-01 13:54 UTCEPSS rescoreEPSS 0.5% · 40th percentile
  38. 2026-09-01 04:40 UTCEPSS rescoreEPSS 0.5% · 40th percentile
  39. 2026-08-30 19:17 UTCEPSS rescoreEPSS 0.5% · 40th percentile
  40. 2026-08-30 17:54 UTCEG score recompute
  41. 2026-08-30 17:54 UTCVendor advisory
  42. 2026-08-30 01:22 UTCEPSS rescoreEPSS 0.5% · 39th percentile
  43. 2026-08-28 21:42 UTCEPSS rescoreEPSS 0.5% · 39th percentile
  44. 2026-08-27 22:38 UTCEG score recompute
  45. 2026-08-27 22:38 UTCVendor advisory
  46. 2026-08-27 14:25 UTCEPSS rescoreEPSS 0.5% · 39th percentile
  47. 2026-08-26 14:46 UTCEPSS rescoreEPSS 0.5% · 39th percentile
  48. 2026-08-25 13:49 UTCEPSS rescoreEPSS 0.5% · 39th percentile
  49. 2026-08-24 23:52 UTCEG score recompute
  50. 2026-08-24 23:52 UTCVendor advisory
  51. 2026-08-24 11:31 UTCEG score recompute
  52. 2026-08-24 11:31 UTCVendor advisory
  53. 2026-08-23 21:11 UTCVendor advisory
  54. 2026-08-23 08:51 UTCEG score recompute
  55. 2026-08-23 08:51 UTCVendor advisory
  56. 2026-08-23 00:19 UTCEPSS rescoreEPSS 0.3% · 20th percentile
  57. 2026-08-22 20:29 UTCVendor advisory
  58. 2026-08-22 08:08 UTCEG score recompute
  59. 2026-08-22 08:08 UTCVendor advisory
  60. 2026-08-21 23:49 UTCEPSS rescoreEPSS 0.3% · 20th percentile
  61. 2026-08-21 06:07 UTCEG score recompute
  62. 2026-08-21 06:07 UTCVendor advisory
  63. 2026-08-20 22:55 UTCEPSS rescoreEPSS 0.3% · 20th percentile
  64. 2026-08-20 17:44 UTCVendor advisory
  65. 2026-08-20 05:23 UTCEG score recompute
  66. 2026-08-19 17:04 UTCEPSS rescoreEPSS 0.3% · 20th percentile
  67. 2026-08-19 11:25 UTCVendor advisory
  68. 2026-08-18 22:59 UTCEG score recompute
  69. 2026-08-18 22:59 UTCVendor advisory
  70. 2026-08-18 13:48 UTCEPSS rescoreEPSS 0.3% · 20th percentile
  71. 2026-08-18 05:01 UTCEG score recompute
  72. 2026-08-17 13:47 UTCEPSS rescoreEPSS 0.3% · 20th percentile
  73. 2026-08-17 11:53 UTCVendor advisory
  74. 2026-08-16 23:33 UTCEG score recompute
  75. 2026-08-16 23:33 UTCVendor advisory

Frequently asked(5)

What is CVE-2026-57585?
CVE-2026-57585 is a high-severity vulnerability; its CVE record was published on June 30, 2026. MessagePack is the serializer implementation for Python msgpack.org. Prior to 1.2.1, there is an Out-of-bounds read/crash on Unpacker reuse after a caught error, potentially leading to a DoS attack. If the Unpacker is used repeatedly after an error occurs, the process may crash with a SEGV. This…
When was the CVE record for CVE-2026-57585 published?
The CVE record for CVE-2026-57585 was published on June 30, 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 August 6, 2026; the record at its source may have been updated since.
Is CVE-2026-57585 actively exploited?
CVE-2026-57585 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.5% probability of exploitation in the next 30 days (41st percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-57585?
CVE-2026-57585 has a CVSS base score of 7.5 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-57585?
A fix for CVE-2026-57585 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-57585 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-57585

Explore →

Is Your Infrastructure Affected by CVE-2026-57585?

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