Is CVE-2026-50648 exploited in the wild?

No. Junglewise Threat Intelligence has no report of CVE-2026-50648 being exploited in the wild.

How severe is CVE-2026-50648?

High severity, with a CVSS score of 7.5, published 14 July 2026.

Which products and versions are affected?

Microsoft .NET Framework 3.5.0 to 2.0.50727.8983 & 3.0.30729.8978; System.Security.Cryptography.Xml (NuGet) ECOSYSTEM:introduced=10.0.0,fixed=10.0.10.

Is there a fix for CVE-2026-50648?

Yes. System.Security.Cryptography.Xml (NuGet): upgrade to 10.0.10 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.

How is CVE-2026-50648 attacked?

It is attacked over the network, in a software library.

Am I affected by CVE-2026-50648?

Check whether you run Microsoft .NET Framework or System.Security.Cryptography.Xml (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.

CVE-2026-50648: Microsoft .NET Framework denial of service via resource exhaustion

CVE-2026-50648 · Severity: high · CVSS 7.5 · Published 2026-07-14

A security vulnerability has been identified in a Microsoft .NET component used for processing encrypted XML data. An attacker could send specially crafted data to an application, causing it to consume excessive system resources and become unresponsive. This could lead to a service outage, preventing legitimate users from accessing the application.

Technologies: Microsoft .NET Framework, System.Security.Cryptography.Xml (NuGet). Vendors: Microsoft, NuGet.

Quick answers

Is CVE-2026-50648 exploited in the wild?: No. Junglewise Threat Intelligence has no report of CVE-2026-50648 being exploited in the wild.
How severe is CVE-2026-50648?: High severity, with a CVSS score of 7.5, published 14 July 2026.
Which products and versions are affected?: Microsoft .NET Framework 3.5.0 to 2.0.50727.8983 & 3.0.30729.8978; System.Security.Cryptography.Xml (NuGet) ECOSYSTEM:introduced=10.0.0,fixed=10.0.10.
Is there a fix for CVE-2026-50648?: Yes. System.Security.Cryptography.Xml (NuGet): upgrade to 10.0.10 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
How is CVE-2026-50648 attacked?: It is attacked over the network, in a software library.
Am I affected by CVE-2026-50648?: Check whether you run Microsoft .NET Framework or System.Security.Cryptography.Xml (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

System.Security.Cryptography.Xml (NuGet): upgrade to 10.0.10 or later

dotnet add package System.Security.Cryptography.Xml --version 10.0.10

Technical details

A denial of service vulnerability exists in the EncryptedXml implementation within the System.Security.Cryptography.Xml package. The root cause is a failure to properly limit or throttle resource allocation (CWE-770) when processing maliciously crafted encrypted XML documents. A remote, unauthenticated attacker can exploit this over the network by submitting a crafted payload that triggers uncontrolled resource consumption. This affects .NET 8, .NET 9, and .NET 10. Patches are available in versions 8.0.29, 9.0.18, and 10.0.10.

Affected products

Microsoft System.Security.Cryptography.Xml >= 8.0.0, <= 8.0.28; >= 9.0.0, <= 9.0.17; >= 10.0.0, <= 10.0.9

Identifiers

CVE-2026-50648
GHSA-23rf-6693-g89p

Timeline

2026-07-14: disclosed
2026-07-14: advisory
2026-07-20: other: GitHub Advisory published

References

This page as Markdown. Free to reuse under CC BY 4.0 with a link back.