CVE-2026-32284

HIGHPre-NVD 7.57.5—
EchelonGraph scoreMEDIUM confidence

Score 7.5 from GitHub Security Advisory (severity: HIGH) published 2026-03-18. CISA-ADP (Vulnrichment) CVSS v3.1 baseline 7.5; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: cisa-adp, epss, ghsa
Trending — 3 sources updated this weekElevated
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.7%CVSS: 7.5Exploit: Elevated riskExposed services: Not assessed

A fixed version is listed under Patch Availability — apply it.

The msgpack decoder fails to properly validate the input buffer length when processing truncated fixext data (format codes 0xd4-0xd8). This can lead to an out-of-bounds read and a runtime panic, allowing a denial of service attack.

CVSS v3
7.5
EG Score
7.5HIGHmedium confidence
EG Risk
65
EG Risk 65/100CISA SSVC

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%
Exploitation40% × 40%
Automatability100% × 15%
CISA SSVC: Track at low or medium mission impact; Attend at high (mission-essential systems).
Action: A fixed version is listed under Patch Availability. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high.
EPSS PROB
0.7%
EPSS %ILE
51st
KEV
Not listed

CISA SSVCTrack at low or medium mission impact; Attend at high (mission-essential systems).

A fixed version is listed under Patch Availability. 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). Mission impact is CISA's Mission & Well-being decision point, and only you can judge it: high means the affected system is essential to your organisation's mission, or its compromise could cause irreversible harm to people. CISA's decision table

Published

March 26, 2026

Last Modified

October 7, 2026

Advisory Details (4)

Auto-updated Jun 10, 2026
🔬 Proof of concept available. Fixed version listed under Patch Availability.
generic🟡 PoC Available

Unpatched DoS in shamaton/msgpack v2 and v3: Single-Byte Panic via Truncated Fixext Input | SecurityInfinity

https://securityinfinity.com/research/shamaton-msgpack-oob-panic-fixext-dos-2026
generic

GO-2026-4513 - Go Packages

https://pkg.go.dev/vuln/GO-2026-4513
generic

Uncontrolled panic (DoS) in shamaton/msgpack v2 and v3 via malformed MessagePack fixext data · Issue #59 · shamaton/msgpack · GitHub

https://github.com/shamaton/msgpack/issues/59
generic

x/vulndb: potential Go vuln in github.com/shamaton/msgpack · Issue #4513 · golang/vulndb · GitHub

https://github.com/golang/vulndb/issues/4513

Patch Availability(2)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
gogithub.com/shamaton/msgpack/v2—ghsa
gogithub.com/shamaton/msgpack/v3—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

(3 across 1 ecosystem)
Go(3)
PackageVulnerable rangeFix by version rangeDependents
github.com/shamaton/msgpack—
  • every version on: no fix on record
—
github.com/shamaton/msgpack/v2—
  • every version through 2.4.0: no fix on record
  • every version on: no fix on record
—
github.com/shamaton/msgpack/v3—
  • every version through 3.1.0: no fix on record
  • every version on: no fix on record
—

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 10× in last 7d / 28× 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 192 total refreshes for this CVE.

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

Related CVEs(same product + same CWE)

Same product

1 shown

Go:github.com/shamaton/msgpack/v2

Frequently asked(5)

What is CVE-2026-32284?
CVE-2026-32284 is a high vulnerability published on March 26, 2026. The msgpack decoder fails to properly validate the input buffer length when processing truncated fixext data (format codes 0xd4-0xd8). This can lead to an out-of-bounds read and a runtime panic, allowing a denial of service attack.
When was CVE-2026-32284 disclosed?
CVE-2026-32284 was first published on March 26, 2026, with the most recent update on October 7, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-32284 actively exploited?
CVE-2026-32284 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.7% probability of exploitation in the next 30 days (51st percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-32284?
CVE-2026-32284 has a CVSS v3.1 base score of 7.5 (CISA-ADP / Vulnrichment enrichment; NVD's own analysis pending).
How do I remediate CVE-2026-32284?
A fixed version for CVE-2026-32284 is listed under Patch Availability on this page: update to the version listed for your package.

Dependency Blast Radius

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

Explore →

Is Your Infrastructure Affected by CVE-2026-32284?

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

Book a Demo →Browse All CVEs