MessagePack-CSharp · .NET · published 2026-10-15

CVE-2026-92707MessagePack: Nested arrays can blow past buffer length limits

Routine No exploitation evidence; EPSS 0.7%.

CVE-2026-92707 is not known to be exploited in the wild. EPSS estimates a 0.7% chance of exploitation in the next 30 days, higher than 53% of all CVEs. This .NET vulnerability: CVSS 5.3 (v3.1), attacks can be automated. Fixed upstream in .NET 10.0.13. Routine: patch when convenient.

Share this

Remediation#

Fixed upstream in .NET 10.0.13.

Patch events

  1. This monthSecurity release

    Language runtime.NET

    .NET security release: 10.0.13

    Upgrade to 10.0.13

    Why: CVE-2026-105016: EPSS 1.7% with high severity (CVSS 9.8).

Exploit intelligence#

SignalValueSource
Known exploitedNoCISA KEV
Ransomware use—CISA KEV
EPSS (30-day exploitation probability)0.7% (53th pct)FIRST EPSS v2026.06.15
CVSS base score5.3 (v3.1)
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L
CNA / CISA ADP
SSVC exploitationnoneCISA Vulnrichment
SSVC automatableYesCISA Vulnrichment
SSVC technical impactpartialCISA Vulnrichment

Affected versions (from the CVE record)#

Description (from the CVE record)#

MessagePack for C# is a MessagePack serializer for C#. Prior to 2.5.303 and 3.1.9, deserializing attacker-controlled MessagePack data as System.Object through PrimitiveObjectFormatter can cause excessive memory allocation. The formatter allocates an object[] from each declared array length before the configured object-graph depth limit rejects the input, while nested array headers can reuse the same trailing unread bytes to satisfy per-header length validation. A comparatively small payload can therefore keep many large arrays alive at once. When an attacker can submit such data repeatedly, the allocations can cause severe managed-heap pressure, excessive garbage collection, process termination, or loss of service. Exposure requires an application to deserialize untrusted data through the affected formatter path and permit repeated attacker-controlled submissions, such as a reachable ASP.NET Core SignalR hub method with an object parameter and AddMessagePackProtocol() enabled. This issue is fixed in versions 2.5.303 and 3.1.9.

Quoted from the CVE Program record.

Elsewhere#

Distro status: Debian · Ubuntu · Red Hat · Alpine

Something wrong on this page?
Anonymous. Reports are checked against the primary source.

Also on today's list

See today's list → · Coming up →