CVE-2026-57585

HIGHPre-NVD 7.57.5—
EchelonGraph scoreMEDIUM confidence

This high-severity CVE scores 7.5 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.5%, top 60% of all CVEs by exploit prediction. GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).

Triggered by: NVD CVSS baseline
Sources: epss, secondary
Trending — 3 sources updated this week
7.5EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 7.5Exploit: None knownExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

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.5(medium)
EG Risk
38(Track)
EG Risk 38/100SSVC: Track

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity75% × 45%
Exploitation0% × 40%
Automatability30% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
40%
KEV
Not listed

Published

June 30, 2026

Last Modified

August 6, 2026

Advisory Details (2)

Auto-updated Jun 30, 2026
Patch available. Sources: github_commit, github.
github Patch Available

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

Affected Packages

(5 across 5 ecosystems)
Debian:11(1)
PackageVulnerable rangeFixed inDependents
python-msgpack1.0.0-6 ... 1.1.2-4 (10 versions)——
Debian:12(1)
PackageVulnerable rangeFixed inDependents
python-msgpack1.0.3-2 ... 1.1.2-4 (6 versions)——
Debian:13(1)
PackageVulnerable rangeFixed inDependents
python-msgpack1.0.3-3, 1.1.2-1, 1.1.2-2, 1.1.2-3, 1.1.2-4——
Debian:14(1)
PackageVulnerable rangeFixed inDependents
python-msgpack1.0.3-3, 1.1.2-1, 1.1.2-21.1.2-3—
PyPI(1)
PackageVulnerable rangeFixed inDependents
msgpack0.5.0 ... 1.2.0rc1 (32 versions)1.2.1—

Weakness Classification(1)

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

All Vendor Advisories

(1)

Every vendor that published an advisory referencing this CVE — pulled from our cve_vendor_advisories aggregation. Click any row for the vendor's original advisory page.

Data Freshness Timeline

(refreshed 19× in last 7d / 99× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. 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. Most recent first.

Showing the most recent 100 of 159 total refreshes for this CVE.

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

Related CVEs(same vendor + same CWE)

Frequently asked(5)

What is CVE-2026-57585?
CVE-2026-57585 is a high vulnerability 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 CVE-2026-57585 disclosed?
CVE-2026-57585 was first published in the National Vulnerability Database on June 30, 2026, with the most recent update on August 6, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-57585 actively exploited?
CVE-2026-57585 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0% probability of exploitation in the next 30 days, which ranks it in the top 60.1% of all scored CVEs.
What is the CVSS score of CVE-2026-57585?
CVE-2026-57585 has a CVSS v3 base score of 7.5 (NVD).
How do I remediate CVE-2026-57585?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-57585, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

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.

Start Free Scan →Browse All CVEs