NIST deprecates RSA-2048 from 2030. Find every one of them before attackers do.
📦 Bitnami
Not in CISA KEV

CVE-2026-62871 — dotnet

CVE-2026-62871 is a CWE-122 vulnerability in dotnet. A fix is available for dotnet — see the affected versions and patch details below.

.NET Elevation of Privilege Vulnerability

Also known asBIT-dotnet-sdk-2026-62871GHSA-vg44-h755-9hw7
Published
Updated
Affected
1 pkg
Patched
1 / 1
Exploits
None indexed
Exploitation data as of Nov 12, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

Exploitation Status

No confirmed exploitation observed yet

  • A successful exploit gives an attacker total control of the affected component, not partial access.
  • CISA’s own triage has not observed active exploitation or public proof-of-concept code for this CVE as of its last assessment.

Exploitation and automatability from CISA’s SSVC triage for CVE-2026-62871.

EPSS Exploitation Probability

via FIRST.org ↗
0.5%probability of exploitation in next 30 days
Lower Risk0.00%
Lower risk than most CVEs41th percentile — riskier than 41% of all scored CVEsHighest risk
0.00%0.32%0.64%0.97%0.4%0.5%0.5%0.5%Sep 26Nov 26Nov 26

Probability of exploitation in the next 30 days, from FIRST.org EPSS.

Real-World Exposure

1 pkg affected
📦dotnet

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects Bitnami packages — download data is not available via public APIs for these ecosystems.

Description

Out-of-bounds write in .NET allows an unauthorized attacker to execute code locally.

Affected Packages

1 total 1 fixed
EcosystemPackageVulnerable rangeFix
📦Bitnamidotnet≥ 8.0.0&&< 8.0.308.0.30

Affected Products

3 products · 5 configurations
Application
.netmicrosoft
≥ 10.0.0 && < 10.0.11
range
Application
visual studio 2022microsoft
≥ 17.14.0 && < 17.14.38
range
Application
visual studio 2026microsoft
≥ 18.8.0 && < 18.8.3
range

Detection & mitigation playbook

Open-source dependency
  1. Detect

    Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for dotnet, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

  2. Fix

    Update dotnet to 8.0.30 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2026-62871 is resolved across your whole dependency graph.

  3. Workarounds

    Constrain what reaches the vulnerable code: limit the size and shape of untrusted input, isolate the affected component in a sandboxed or least-privileged process, and enable the platform's memory-safety mitigations (ASLR, stack protector, hardened allocator) so an out-of-bounds access is more likely to fail closed than to be exploitable.

Fixing This On Your OS

If you run this on a Linux distribution, patch through your package manager against the distro's own security advisory below — it tracks the exact backported fix for your release, which can ship on a different timeline (and sometimes a different severity) than the upstream project.

Red HatImportant

Red Hat's .NET packages ship only the cross-platform runtime (Microsoft.NETCore.App.Runtime). CVE-2026-62871 affects exclusively Microsoft.WindowsDesktop.App.Runtime.win-* — the WinForms and WPF GUI subsystem, which is Windows-only and not included in any Red Hat .NET build. No Red Hat product is affected.

Workaround published by Red Hat
No mitigation is required. Red Hat's .NET packages do not ship the Windows Desktop runtime components (Microsoft.WindowsDesktop.App.Runtime) that contain the vulnerability.
Source: Red Hat security advisory for CVE-2026-62871 (CC BY 4.0)

Frequently Asked Questions

Out-of-bounds write in .NET allows an unauthorized attacker to execute code locally.
O3 Security · Impact-Aware SCA

Is CVE-2026-62871 in your dependencies?

Find it across Bitnami, including transitive dependencies.

CVE-2026-62871: dotnet — Fixed in 8.0.30