cve.bz

CVE-2026-96229 microsoft: Permissive List of Allowed Inputs

6.5 mediumEPSS 0.9%Fix available

Medium (6.5) in microsoft. EPSS 0.9% estimated probability of exploitation activity in the next 30 days. Fixed in Microsoft.WindowsDesktop.App.Runtime.win-arm64 10.0.13, 11.0.0-rc.2, 8.0.32.

On this page
Permissive list of allowed inputs in .NET allows an unauthorized attacker to disclose information over a network.

Severity

CVSS 3.1

6.5 medium
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:N/A:N
EPSS
0.9% (unchanged from 0.9% a week ago; 0.8% 30 days ago) estimated probability of exploitation activity in the next 30 days; 62nd percentile. Scored 2026-11-17. A forecast for this CVE across the internet, not for your own systems.
CISA's assessment (SSVC)
Exploitation: none · Automatable: no · Technical impact: partial, assessed 2026-10-13. From CISA's Vulnrichment in the CVE List: whether it is exploited, whether exploiting it can be automated, and how much control it gives.
CWE
CWE-183 Permissive List of Allowed Inputs
OWASP Top 10
A06:2025 Insecure Design
Published
Modified
Assigned by
microsoft (CNA)
NVD analysis
Awaiting analysis
Record from
the NVD, synced

Fix and patched versions

  • Microsoft.WindowsDesktop.App.Runtime.win-arm64 (NuGet): fixed in 9.0.21, 10.0.13, 11.0.0-rc.2, 8.0.32
  • Microsoft.WindowsDesktop.App.Runtime.win-x64 (NuGet): fixed in 9.0.21, 10.0.13, 11.0.0-rc.2, 8.0.32
  • Microsoft.WindowsDesktop.App.Runtime.win-x86 (NuGet): fixed in 9.0.21, 10.0.13, 11.0.0-rc.2, 8.0.32
  • Alpine: fixed package versions per release

Ask an AI about this CVE

Show the promptExplain CVE-2026-96229 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2026-96229?via=ask-ai-copy and https://cve.bz/cve/CVE-2026-96229?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2026-96229 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.

Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.

Affected

  • microsoft:.net 10.0 runtime
  • microsoft:.net 11.0 runtime
  • microsoft:.net 8.0 runtime
  • microsoft:.net 9.0 runtime
  • microsoft:microsoft visual studio 2022 version 17.14
  • microsoft:microsoft visual studio 2026 version 18.10

Versions

From the CNA's record in the CVE List.

ProductAffected
Microsoft .NET 10.0 runtimefrom 10.0.0 before 10.0.13
Microsoft .NET 11.0 runtimefrom 11.0.0 before 11.0.0-rc.2
Microsoft .NET 8.0 runtimefrom 8.0.0 before 8.0.32
Microsoft .NET 9.0 runtimefrom 9.0.0 before 9.0.21
Microsoft Visual Studio 2022 version 17.14from 17.14.0 before 17.14.42
Microsoft Visual Studio 2026 version 18.10from 18.10.0 before 18.10.4

Packages (OSV)

AdvisoryEcosystemPackageAffectedFixed in
GHSA-5qr9-xxm9-6cmqNuGetMicrosoft.WindowsDesktop.App.Runtime.win-arm64>=9.0.0 <9.0.219.0.21
GHSA-5qr9-xxm9-6cmqNuGetMicrosoft.WindowsDesktop.App.Runtime.win-x64>=9.0.0 <9.0.219.0.21
GHSA-5qr9-xxm9-6cmqNuGetMicrosoft.WindowsDesktop.App.Runtime.win-x86>=9.0.0 <9.0.219.0.21
GHSA-5qr9-xxm9-6cmqNuGetMicrosoft.WindowsDesktop.App.Runtime.win-arm64>=10.0.0 <10.0.1310.0.13
GHSA-5qr9-xxm9-6cmqNuGetMicrosoft.WindowsDesktop.App.Runtime.win-x64>=10.0.0 <10.0.1310.0.13
GHSA-5qr9-xxm9-6cmqNuGetMicrosoft.WindowsDesktop.App.Runtime.win-x86>=10.0.0 <10.0.1310.0.13
GHSA-5qr9-xxm9-6cmqNuGetMicrosoft.WindowsDesktop.App.Runtime.win-arm64>=11.0.0-preview.1 <11.0.0-rc.211.0.0-rc.2
GHSA-5qr9-xxm9-6cmqNuGetMicrosoft.WindowsDesktop.App.Runtime.win-x64>=11.0.0-preview.1 <11.0.0-rc.211.0.0-rc.2
GHSA-5qr9-xxm9-6cmqNuGetMicrosoft.WindowsDesktop.App.Runtime.win-x86>=11.0.0-preview.1 <11.0.0-rc.211.0.0-rc.2
GHSA-5qr9-xxm9-6cmqNuGetMicrosoft.WindowsDesktop.App.Runtime.win-arm64>=8.0.0 <8.0.328.0.32
GHSA-5qr9-xxm9-6cmqNuGetMicrosoft.WindowsDesktop.App.Runtime.win-x64>=8.0.0 <8.0.328.0.32
GHSA-5qr9-xxm9-6cmqNuGetMicrosoft.WindowsDesktop.App.Runtime.win-x86>=8.0.0 <8.0.328.0.32

Linux distributions

DistributionReleasePackageFixed inAdvisory
Ubuntu22.04:LTSdotnet7no fix listedUBUNTU-CVE-2026-96229
Alpinev3.22, v3.23, v3.24dotnet8-runtime8.0.32-r0ALPINE-CVE-2026-96229
Alpinev3.22, v3.23, v3.24dotnet9-runtime9.0.21-r0ALPINE-CVE-2026-96229
Alpinev3.23, v3.24dotnet10-runtime10.0.13-r0ALPINE-CVE-2026-96229

From the distributions' data via OSV.dev: Ubuntu Security Notices © Canonical Ltd., CC BY-SA 4.0; the Alpine secdb, CC BY-SA 4.0. Modified: reformatted and linked to CVE records. Credits. On the distributions' own pages: Ubuntu · Alpine.

Red Hat

Red Hat rates this Moderate.

Red Hat's statement

This vulnerability is rated as Moderate severity for Red Hat because, while an unauthenticated remote attacker could expose sensitive data across the network, successful exploitation requires user interaction and does not allow arbitrary code execution or privilege escalation. In standard Red Hat Enterprise Linux and container deployments executing .NET workloads, exposure is limited to data processed within the interacting user's application session. System integrity and service availability remain unaffected.

ProductPackageStateAdvisory
Red Hat Hardened Imagesdotnet8.0Not affected

Contains Red Hat Security Data © Red Hat, Inc., licensed under CC BY 4.0. Source: https://access.redhat.com/security/data. Modified: reformatted. Red Hat's page for CVE-2026-96229.

Attack patterns (CAPEC)

  • CAPEC-3 Using Leading 'Ghost' Character Sequences to Bypass Input Filters Likelihood: Medium · Severity: Medium
  • CAPEC-43 Exploiting Multiple Input Interpretation Layers Likelihood: Medium · Severity: High
  • CAPEC-71 Using Unicode Encoding to Bypass Validation Logic Likelihood: Medium · Severity: High
  • CAPEC-120 Double Encoding Likelihood: Low · Severity: Medium

The attack patterns MITRE's CAPEC relates to this record's weaknesses, as MITRE names them. Credits.

References

Check your stackJSON