CVE-2026-48506

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.3%, top 81% 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
7.5
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS: 0%CVSS: 7.5Exploit: NoneExposed: 0

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

MessagePack for C# is a MessagePack serializer for C#. Prior to 2.5.301 and 3.1.7, MessagePackReader.TrySkip() recursively descends into nested arrays and maps without incrementing the reader depth or calling the configured depth checks. This bypasses MessagePackSecurity.MaximumObjectGraphDepth, the library's documented protection against deeply nested object graphs. Many generated and dynamic formatters call reader.Skip() when they encounter unknown map keys, unknown array members, ignored fields, or data that should be skipped for forward compatibility. A deeply nested value in one of these skipped positions can therefore cause unbounded recursion and an uncatchable StackOverflowException. This vulnerability is fixed in 2.5.301 and 3.1.7.

CVSS v3
7.5
EG Score
7.5(medium)
EPSS
19.3%
KEV
Not listed

Published

June 22, 2026

Last Modified

June 23, 2026

Advisory Details (1)

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

MessagePackReader.Skip can recurse without enforcing maximum object graph depth · Advisory · MessagePack-CSharp/MessagePack-CSharp · GitHub

https://github.com/MessagePack-CSharp/MessagePack-CSharp/security/advisories/GHSA-vh6j-jc39-fggf

Vendor Advisories for CVE-2026-48506(1)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Weakness Classification(1)

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

Data Freshness Timeline

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

  1. 2026-07-07 02:46 UTCEG score recompute
  2. 2026-07-06 16:27 UTCEPSS rescore
  3. 2026-07-06 15:51 UTCEG score recompute
  4. 2026-07-06 04:56 UTCEG score recompute
  5. 2026-07-06 02:23 UTCEPSS rescore
  6. 2026-07-05 17:52 UTCEG score recompute
  7. 2026-07-05 06:57 UTCEG score recompute
  8. 2026-07-05 02:30 UTCEPSS rescore
  9. 2026-07-04 19:59 UTCEG score recompute
  10. 2026-07-04 09:04 UTCEG score recompute
  11. 2026-07-04 06:31 UTCEPSS rescore
  12. 2026-07-03 22:07 UTCEG score recompute
  13. 2026-07-03 11:11 UTCEG score recompute
  14. 2026-07-03 00:17 UTCEG score recompute
  15. 2026-07-02 13:21 UTCEG score recompute
  16. 2026-07-02 02:27 UTCEG score recompute
  17. 2026-07-01 15:33 UTCEG score recompute
  18. 2026-07-01 15:07 UTCEPSS rescore
  19. 2026-07-01 04:38 UTCEG score recompute
  20. 2026-06-30 23:22 UTCEPSS rescore
  21. 2026-06-30 17:41 UTCEG score recompute
  22. 2026-06-30 06:46 UTCEG score recompute
  23. 2026-06-29 19:50 UTCEG score recompute
  24. 2026-06-29 14:06 UTCEPSS rescore
  25. 2026-06-29 14:06 UTCEPSS rescore
Show 24 more
  1. 2026-06-29 08:56 UTCEG score recompute
  2. 2026-06-28 22:01 UTCEG score recompute
  3. 2026-06-28 14:07 UTCEPSS rescore
  4. 2026-06-28 11:06 UTCEG score recompute
  5. 2026-06-28 04:56 UTCEPSS rescore
  6. 2026-06-28 04:56 UTCEPSS rescore
  7. 2026-06-28 00:12 UTCEG score recompute
  8. 2026-06-27 13:18 UTCEG score recompute
  9. 2026-06-27 03:08 UTCEPSS rescore
  10. 2026-06-27 02:23 UTCEG score recompute
  11. 2026-06-26 15:28 UTCEG score recompute
  12. 2026-06-26 04:34 UTCEG score recompute
  13. 2026-06-25 17:37 UTCEG score recompute
  14. 2026-06-25 13:49 UTCEPSS rescore
  15. 2026-06-25 06:42 UTCEG score recompute
  16. 2026-06-24 19:46 UTCEG score recompute
  17. 2026-06-24 14:05 UTCEPSS rescore
  18. 2026-06-24 08:50 UTCEG score recompute
  19. 2026-06-23 21:56 UTCEG score recompute
  20. 2026-06-23 21:33 UTCEPSS rescore
  21. 2026-06-23 21:33 UTCEPSS rescore
  22. 2026-06-23 10:58 UTCEG score recompute
  23. 2026-06-23 00:04 UTCEG score recompute
  24. 2026-06-23 00:00 UTCMITRE cvelistV5first tracked

Frequently asked(5)

What is CVE-2026-48506?
CVE-2026-48506 is a high vulnerability published on June 22, 2026. MessagePack for C# is a MessagePack serializer for C#. Prior to 2.5.301 and 3.1.7, MessagePackReader.TrySkip() recursively descends into nested arrays and maps without incrementing the reader depth or calling the configured depth checks. This bypasses MessagePackSecurity.MaximumObjectGraphDepth,…
When was CVE-2026-48506 disclosed?
CVE-2026-48506 was first published in the National Vulnerability Database on June 22, 2026, with the most recent update on June 23, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-48506 actively exploited?
CVE-2026-48506 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 19.3% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2026-48506?
CVE-2026-48506 has a CVSS v3 base score of 7.5 (NVD).
How do I remediate CVE-2026-48506?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-48506, 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

Explore the affected products and dependency analysis for CVE-2026-48506

Explore →

Is Your Infrastructure Affected by CVE-2026-48506?

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