CVE-2026-48517
Analyzed Analyzed - Analysis Complete

MessagePack-CSharp Typeless Deserialization Type Confusion

Vulnerability report for CVE-2026-48517, including description, CVSS score, EPSS score, affected products, exploitability, helpful resources, and attack-flow context.

Publication date: 2026-06-22

Last updated on: 2026-06-25

Assigner: GitHub, Inc.

Description

MessagePack for C# is a MessagePack serializer for C#. Prior to 2.5.301 and 3.1.7, MessagePack-CSharp's typeless deserialization includes MessagePackSerializerOptions.ThrowIfDeserializingTypeIsDisallowed(Type) as a safety check for dangerous types. The default implementation checks the outer type name, but it does not recursively inspect array element types or generic type arguments. As a result, a type that would be blocked directly can be wrapped inside an array or constructed generic type and pass the outer type check. The formatter machinery can then materialize formatters for the inner blocked type. This vulnerability is fixed in 2.5.301 and 3.1.7.

CVSS Scores

EPSS Scores

Probability:
Percentile:

Meta Information

Published
2026-06-22
Last Modified
2026-06-25
Generated
2026-07-13
AI Q&A
2026-06-23
EPSS Evaluated
2026-07-11
NVD

Affected Vendors & Products

Showing 2 associated CPEs
Vendor Product Version / Range
messagepack messagepack to 2.5.301 (exc)
messagepack messagepack From 3.0.3 (inc) to 3.1.7 (exc)

Helpful Resources

Exploitability

CWE
CWE Icon
KEV
KEV Icon
CWE ID Description
CWE-470 The product uses external input with reflection to select which classes or code to use, but it does not sufficiently prevent the input from selecting improper classes or code.
CWE-502 The product deserializes untrusted data without sufficiently ensuring that the resulting data will be valid.

Attack-Flow Graph

AI Quick Actions

Instant insights powered by AI
Executive Summary

This vulnerability exists in MessagePack for C#, a serializer for C#. Before versions 2.5.301 and 3.1.7, the typeless deserialization feature included a safety check to block dangerous types. However, this check only examined the outer type name and did not recursively inspect types inside arrays or generic type arguments. Consequently, a type that should have been blocked could be hidden inside an array or generic type and bypass the check, allowing the deserialization process to materialize formatters for these inner blocked types.

Impact Analysis

The vulnerability allows potentially dangerous types to be deserialized despite safety checks, which can lead to unexpected or unsafe behavior during deserialization. This could be exploited to execute malicious code or cause application instability by bypassing type restrictions.

Mitigation Strategies

To mitigate this vulnerability, you should upgrade MessagePack for C# to version 2.5.301 or 3.1.7 or later, where the issue with typeless deserialization and unsafe type checks has been fixed.

Compliance Impact

This vulnerability in MessagePack-CSharp's typeless deserialization can allow attackers to bypass type restrictions and instantiate blocked types during deserialization. Such behavior may lead to the processing of untrusted or malicious data, potentially causing unauthorized actions or data exposure.

While the provided information does not explicitly mention compliance with standards like GDPR or HIPAA, vulnerabilities that allow unsafe deserialization and potential data manipulation or exposure can negatively impact compliance with these regulations, which require protection of sensitive data and secure processing.

Therefore, organizations using affected versions of MessagePack-CSharp without applying patches or mitigations might face increased risk of non-compliance due to potential data integrity and security issues.

Detection Guidance

This vulnerability affects applications using MessagePack-CSharp's typeless deserialization feature, specifically when using untrusted payloads with methods like MessagePackSerializer.Typeless or TypelessObjectResolver.

To detect this vulnerability on your system, you should first identify if your application uses vulnerable versions of MessagePack-CSharp (prior to 2.5.301 and 3.1.7) and if it employs typeless deserialization.

There are no specific network detection commands provided in the resources. However, you can check the installed MessagePack-CSharp package version in your project dependencies.

  • For .NET projects using NuGet, run: dotnet list package | findstr MessagePack
  • Alternatively, inspect your project files (e.g., .csproj) for the MessagePack package version.

To detect exploit attempts on the network, monitor for suspicious deserialization payloads targeting typeless deserialization endpoints, but no specific command or signature is provided.

The recommended mitigation is to upgrade MessagePack-CSharp to version 2.5.301 or 3.1.7 or later, or avoid typeless deserialization with untrusted data.

Chat Assistant

Ask questions about this CVE
Hi! I’m here to help you understand CVE-2026-48517. Ask me anything about the vulnerability, its impact, or mitigation strategies.
0/70

EPSS Chart