Quick answers
- Is CVE-2026-48512 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-48512 being exploited in the wild.
- How severe is CVE-2026-48512?
- Medium severity, with a CVSS score of 4, published 22 June 2026.
- Which products and versions are affected?
- MessagePack-CSharp MessagePack for C# < 2.5.301, >= 3.0 < 3.1.7; MessagePack-CSharp < 2.5.301, >= 3.0, < 3.1.7; MessagePack (NuGet) ECOSYSTEM:introduced=0,fixed=2.5.301.
- Is there a fix for CVE-2026-48512?
- Yes. MessagePack (NuGet): upgrade to 2.5.301 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-48512 attacked?
- It is attacked over the network, in a software library.
- Am I affected by CVE-2026-48512?
- Check whether you run MessagePack-CSharp MessagePack for C#, MessagePack-CSharp or MessagePack (NuGet) at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
How to fix
- MessagePack (NuGet): upgrade to 2.5.301 or later
dotnet add package MessagePack --version 2.5.301
Technical details
The vulnerability consists of three uncontrolled recursion issues within the JSON conversion component of MessagePack-CSharp. Specifically, 'MessagePackSerializer.ConvertFromJson' fails to consult depth limits during nested object processing, 'TinyJsonReader.ReadNextToken' recursively consumes separators, and 'MessagePackSerializer.ConvertToJson' lacks depth enforcement for typeless extension branches. An attacker can exploit these by providing deeply nested JSON or malformed separator runs, triggering an uncatchable 'StackOverflowException'. This bypasses 'MessagePackSecurity.UntrustedData' protections. Patches are available in versions 2.5.301 and 3.1.7.
Affected products
- MessagePack-CSharp MessagePack-CSharp < 2.5.301, >= 3.0, < 3.1.7
Identifiers
- CVE-2026-48512
- GHSA-cj9g-3mj2-g8vv
Timeline
- 2026-06-09: disclosed: Advisory published by maintainer
- 2026-06-22: advisory: NVD publication date
- 2026-06-25: advisory: GitHub Advisory Database publication date