MessagePack for C# is a MessagePack serializer for C#. Prior to 2.5.301 and 3.1.7, MessagePackReader.ReadDateTime() can allocate stack memory based on an attacker-controlled MessagePack extension length. In the slow path for timestamp extension parsing, the computed tokenSize includes the extension body length from the wire and is used in a stackalloc operation before the extension length is validated as one of the valid timestamp sizes. A very small payload can claim a large timestamp extension body and cause a stack allocation large enough to trigger an uncatchable StackOverflowException, terminating the host process. This vulnerability is fixed in 2.5.301 and 3.1.7.
CVE-2026-48502
This high-severity CVE scores 7.5 under NVD CVSS v3. EPSS exploit probability: 0.3%, top 83% 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).
- High severity, but no confirmed exploitation yet
No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.
- CVSS v3
- 7.5
- EG Score
- 7.5(medium)
- EG Risk
- —
- EPSS
- 17.1%
- KEV
- Not listed
Published
June 22, 2026
Last Modified
June 23, 2026
Advisory Details (1)
Auto-updated Jun 23, 2026Attacker-controlled DateTime extension length causes stack overflow · Advisory · MessagePack-CSharp/MessagePack-CSharp · GitHub
https://github.com/MessagePack-CSharp/MessagePack-CSharp/security/advisories/GHSA-382j-8mxh-c7x2Vendor Advisories for CVE-2026-48502(1)
These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.
Affected Packages
(1 across 1 ecosystem)
NuGet(1)
| Package | Vulnerable range | Fixed in | Dependents |
|---|---|---|---|
| MessagePack | 3.0.111-alpha ... 3.1.6 (15 versions) | 3.1.7 | — |
Weakness Classification(9)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
- CWE-1188Insecure Default Initialization of Resource
- CWE-125Out-of-bounds Read
- CWE-190Integer Overflow or Wraparound
- CWE-407Inefficient Algorithmic Complexity
- CWE-409Improper Handling of Highly Compressed Data (Data Amplification)
- CWE-470Use of Externally-Controlled Input to Select Classes or Code (Unsafe Reflection)
- CWE-502Deserialization of Untrusted Data
- CWE-674Uncontrolled Recursion
- CWE-789Memory Allocation with Excessive Size Value
Data Freshness Timeline
(refreshed 6× in last 7d / 33× 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.
- 2026-07-22 14:08 UTCEPSS rescore
- 2026-07-21 15:25 UTCEPSS rescore
- 2026-07-20 17:08 UTCEPSS rescore
- 2026-07-19 02:29 UTCEPSS rescore
- 2026-07-18 10:04 UTCEPSS rescore
- 2026-07-16 17:03 UTCEPSS rescore
- 2026-07-15 16:57 UTCEPSS rescore
- 2026-07-15 02:00 UTCEPSS rescore
- 2026-07-13 22:30 UTCEPSS rescore
- 2026-07-13 06:13 UTCEPSS rescore
- 2026-07-12 05:46 UTCEPSS rescore
- 2026-07-11 08:27 UTCEPSS rescore
- 2026-07-09 19:10 UTCEPSS rescore
- 2026-07-08 15:16 UTCEPSS rescore
- 2026-07-07 13:46 UTCEPSS rescore
- 2026-07-06 16:27 UTCEPSS rescore
- 2026-07-06 02:23 UTCEPSS rescore
- 2026-07-05 02:30 UTCEPSS rescore
- 2026-07-04 06:31 UTCEPSS rescore
- 2026-07-01 15:07 UTCEPSS rescore
- 2026-06-30 23:22 UTCEPSS rescore
- 2026-06-29 14:06 UTCEPSS rescore
- 2026-06-29 14:06 UTCEPSS rescore
- 2026-06-28 14:07 UTCEPSS rescore
- 2026-06-28 04:56 UTCEPSS rescore
Show 10 moreShow fewer
- 2026-06-28 04:56 UTCEPSS rescore
- 2026-06-27 03:08 UTCEPSS rescore
- 2026-06-25 13:49 UTCEPSS rescore
- 2026-06-24 14:05 UTCEPSS rescore
- 2026-06-23 22:38 UTCEG score recompute▼ 0.70
- 2026-06-23 21:33 UTCEPSS rescore
- 2026-06-23 21:33 UTCEPSS rescore
- 2026-06-23 17:33 UTCNVD updateCVSS v3 → 7.5
- 2026-06-23 00:01 UTCEG score recompute
- 2026-06-23 00:00 UTCMITRE cvelistV5first tracked
Related CVEs(same CWE)
Same CWE
10 shownCWE-190 · CWE-502 · CWE-125
- CVE-2009-0947EG 9.8CRITICAL
- CVE-2005-1141EG 9.8CRITICAL
- CVE-2005-0102EG 9.8CRITICAL
- CVE-2003-0791EG 9.8CRITICAL
- CVE-2002-0391EG 9.8EPSS 99%CRITICAL
- CVE-2002-0639EG 9.8EPSS 97%CRITICAL
- CVE-1999-0006EG 9.8EPSS 96%CRITICAL
- CVE-2011-1823NVD 7.8EG 9.0 KEVEPSS 99%HIGH
- CVE-2011-0663EG 8.8EPSS 98%HIGH
- CVE-2010-2753EG 8.8EPSS 93%HIGH
Frequently asked(5)
What is CVE-2026-48502?
When was CVE-2026-48502 disclosed?
Is CVE-2026-48502 actively exploited?
What is the CVSS score of CVE-2026-48502?
How do I remediate CVE-2026-48502?
Dependency Blast Radius
See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-48502
Is Your Infrastructure Affected by CVE-2026-48502?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.