Improperly Controlled Sequential Memory Allocation Affecting dotnet-sdk-aot-10.0 package, versions <0:10.0.113-1.el10_2


Severity

Recommended
critical

Based on AlmaLinux security rating.

Threat Intelligence

EPSS
0.65% (50th percentile)

Do your applications use this vulnerable package?

In a few clicks we can analyze your entire application and see what components are vulnerable in your application, and suggest you quick fixes.

Test your applications
  • Snyk IDSNYK-ALMALINUX10-DOTNETSDKAOT100-21375937
  • published21 Oct 2026
  • disclosed20 Oct 2026

Introduced: 20 Oct 2026

NewCVE-2026-92707  (opens in a new tab)
CWE-1325  (opens in a new tab)

How to fix?

Upgrade AlmaLinux:10 dotnet-sdk-aot-10.0 to version 0:10.0.113-1.el10_2 or higher.
This issue was patched in ALSA-2026:86195.

NVD Description

Note: Versions mentioned in the description apply only to the upstream dotnet-sdk-aot-10.0 package and not the dotnet-sdk-aot-10.0 package as distributed by AlmaLinux. See How to fix? for AlmaLinux:10 relevant fixed versions and status.

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.

CVSS Base Scores

version 3.1