CVE-2026-26127 — dotnet
CVE-2026-26127 is a Out-of-bounds Read vulnerability in dotnet. A fix is available for dotnet — see the affected versions and patch details below.
.NET Denial of Service Vulnerability
Exploitation Status
No confirmed exploitation observed yet
- CISA assesses this as automatable — exploitation doesn’t require manual, per-target effort, which raises the odds of mass scanning and opportunistic attacks.
- 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-26127.
EPSS Exploitation Probability
Probability of exploitation in the next 30 days, from FIRST.org EPSS.
Real-World Exposure
dotnetReal-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 read in .NET allows an unauthorized attacker to deny service over a network.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| 📦Bitnami | dotnet | ≥ 9.0.0&&< 9.0.14 | 9.0.14 |
Affected Products
.netmicrosoftbcl.memorymicrosoftDetection & mitigation playbook
Open-source dependencyDetect
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.
Fix
Update dotnet to 9.0.14 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2026-26127 is resolved across your whole dependency graph.
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.
To mitigate this issue, restrict network access to applications utilizing affected .NET components to only trusted clients or networks using firewall rules. This will limit the exposure of the vulnerable service to potential attackers. After applying firewall rules, ensure to reload or restart the network service for changes to take effect.Source: Red Hat security advisory for CVE-2026-26127 (CC BY 4.0)
| Product | Fixed in | Advisory |
|---|---|---|
| Red Hat Enterprise Linux 10 | dotnet9.0-0:9.0.115-1.el10_1 | RHSA-2026:4450 |
| Red Hat Enterprise Linux 10 | dotnet10.0-0:10.0.104-1.el10_1 | RHSA-2026:4453 |
| Red Hat Enterprise Linux 10.0 Extended Update Support | dotnet9.0-0:9.0.115-1.el10_0 | RHSA-2026:10083 |
| Red Hat Enterprise Linux 8 | dotnet9.0-0:9.0.115-1.el8_10 | RHSA-2026:4443 |
| Red Hat Enterprise Linux 8 | dotnet10.0-0:10.0.104-1.el8_10 | RHSA-2026:4458 |
| Red Hat Enterprise Linux 9 | dotnet10.0-0:10.0.104-1.el9_7 | RHSA-2026:4445 |
| Red Hat Enterprise Linux 9 | dotnet9.0-0:9.0.115-1.el9_7 | RHSA-2026:4456 |
| Red Hat Enterprise Linux 9.6 Extended Update Support | dotnet9.0-0:9.0.115-1.el9_6 | RHSA-2026:10085 |
Frequently Asked Questions
Is CVE-2026-26127 in your dependencies?
Find it across Bitnami, including transitive dependencies.