CVE-2026-48109

HIGHPre-NVD 8.28.2—
EchelonGraph scoreMEDIUM confidence

This high-severity CVE scores 8.2 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.3%, top 79% 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
8.2
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS: 0%CVSS: 8.2Exploit: 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, A vulnerability exists in the optional LZ4 decompression path used by MessagePack compression modes Lz4Block and Lz4BlockArray. The decoder implementation is based on a deprecated fast-decompression algorithm that does not take a source-length bound. A remote attacker can send a crafted MessagePack payload with manipulated LZ4 token/length fields to force out-of-bounds reads from the compressed input buffer. In affected environments, this can trigger an AccessViolationException during decompression, causing process termination (denial of service). Under some conditions, limited unintended memory disclosure from over-read data may also be possible before failure. This vulnerability is fixed in 2.5.301 and 3.1.7.

CVSS v3
8.2
EG Score
8.2(medium)
EPSS
21.4%
KEV
Not listed

Published

June 11, 2026

Last Modified

June 23, 2026

Advisory Details (1)

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

LZ4 decompression may fail with AccessViolationException after dereferencing memory from bad input · Advisory · MessagePack-CSharp/MessagePack-CSharp · GitHub

https://github.com/MessagePack-CSharp/MessagePack-CSharp/security/advisories/GHSA-hv8m-jj95-wg3x

Vendor Advisories for CVE-2026-48109(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)
PackageVulnerable rangeFixed inDependents
MessagePack3.0.300 ... 3.1.6 (9 versions)3.1.7—

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 18× in last 7d / 65× 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 01:40 UTCEG score recompute
  2. 2026-07-06 16:27 UTCEPSS rescore
  3. 2026-07-06 02:35 UTCEG score recompute
  4. 2026-07-06 02:23 UTCEPSS rescore
  5. 2026-07-05 13:23 UTCEG score recompute
  6. 2026-07-05 02:30 UTCEPSS rescore
  7. 2026-07-05 00:17 UTCEG score recompute
  8. 2026-07-04 11:17 UTCEG score recompute
  9. 2026-07-04 06:31 UTCEPSS rescore
  10. 2026-07-03 20:46 UTCEG score recompute
  11. 2026-07-03 07:41 UTCEG score recompute
  12. 2026-07-02 17:49 UTCEG score recompute
  13. 2026-07-02 04:35 UTCEG score recompute
  14. 2026-07-01 15:36 UTCEG score recompute
  15. 2026-07-01 15:07 UTCEPSS rescore
  16. 2026-07-01 02:36 UTCEG score recompute
  17. 2026-06-30 23:22 UTCEPSS rescore
  18. 2026-06-30 13:34 UTCEG score recompute
  19. 2026-06-29 21:05 UTCEG score recompute
  20. 2026-06-29 14:06 UTCEPSS rescore
  21. 2026-06-29 14:06 UTCEPSS rescore
  22. 2026-06-29 08:06 UTCEG score recompute
  23. 2026-06-28 18:52 UTCEG score recompute
  24. 2026-06-28 14:07 UTCEPSS rescore
  25. 2026-06-28 05:53 UTCEG score recompute
Show 40 more
  1. 2026-06-28 04:56 UTCEPSS rescore
  2. 2026-06-28 04:56 UTCEPSS rescore
  3. 2026-06-27 16:47 UTCEG score recompute
  4. 2026-06-27 03:48 UTCEG score recompute
  5. 2026-06-27 03:08 UTCEPSS rescore
  6. 2026-06-26 14:49 UTCEG score recompute
  7. 2026-06-26 01:38 UTCEG score recompute
  8. 2026-06-25 13:49 UTCEPSS rescore
  9. 2026-06-25 12:39 UTCEG score recompute
  10. 2026-06-24 23:40 UTCEG score recompute
  11. 2026-06-24 14:05 UTCEPSS rescore
  12. 2026-06-24 10:41 UTCEG score recompute
  13. 2026-06-23 21:33 UTCEPSS rescore
  14. 2026-06-23 21:33 UTCEPSS rescore
  15. 2026-06-23 21:25 UTCEG score recompute
  16. 2026-06-23 08:22 UTCEG score recompute
  17. 2026-06-22 18:51 UTCEG score recompute
  18. 2026-06-22 05:51 UTCEG score recompute
  19. 2026-06-21 16:50 UTCEG score recompute
  20. 2026-06-21 02:54 UTCEG score recompute
  21. 2026-06-20 13:35 UTCEG score recompute
  22. 2026-06-20 00:36 UTCEG score recompute
  23. 2026-06-19 11:36 UTCEG score recompute
  24. 2026-06-18 22:36 UTCEG score recompute
  25. 2026-06-18 09:37 UTCEG score recompute
  26. 2026-06-17 20:09 UTCEG score recompute
  27. 2026-06-17 07:10 UTCEG score recompute
  28. 2026-06-16 17:57 UTCEG score recompute
  29. 2026-06-16 04:49 UTCEG score recompute
  30. 2026-06-15 15:49 UTCEG score recompute
  31. 2026-06-15 02:50 UTCEG score recompute
  32. 2026-06-14 23:18 UTCEPSS rescore
  33. 2026-06-14 13:51 UTCEG score recompute
  34. 2026-06-14 00:52 UTCEG score recompute
  35. 2026-06-13 23:00 UTCEPSS rescore
  36. 2026-06-13 11:53 UTCEG score recompute
  37. 2026-06-12 23:12 UTCEPSS rescore
  38. 2026-06-12 22:54 UTCEG score recompute
  39. 2026-06-12 09:56 UTCEG score recompute
  40. 2026-06-11 20:56 UTCEG score recompute

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2026-48109?
CVE-2026-48109 is a high vulnerability published on June 11, 2026. MessagePack for C# is a MessagePack serializer for C#. Prior to 2.5.301 and 3.1.7, A vulnerability exists in the optional LZ4 decompression path used by MessagePack compression modes Lz4Block and Lz4BlockArray. The decoder implementation is based on a deprecated fast-decompression algorithm that…
When was CVE-2026-48109 disclosed?
CVE-2026-48109 was first published in the National Vulnerability Database on June 11, 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-48109 actively exploited?
CVE-2026-48109 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 21.4% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2026-48109?
CVE-2026-48109 has a CVSS v3 base score of 8.2 (NVD).
How do I remediate CVE-2026-48109?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-48109, 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-48109

Explore →

Is Your Infrastructure Affected by CVE-2026-48109?

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

Start Free Scan →Browse All CVEs