CVE-2026-50528 — dotnet
CVE-2026-50528 is a CWE-302 vulnerability in dotnet. A fix is available for dotnet — see the affected versions and patch details below.
.NET Security Feature Bypass 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-50528.
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
Incorrect authorization in .NET allows an unauthorized attacker to bypass a security feature over a network.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| 📦Bitnami | dotnet | ≥ 8.0.0&&< 8.0.29 | 8.0.29 |
Affected Products
.netmicrosoftvisual studio 2022microsoftvisual studio 2026microsoftDetection & 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 8.0.29 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2026-50528 is resolved across your whole dependency graph.
Workarounds
Put an independent control in front of the weakness: restrict the affected endpoint or interface to trusted networks, require an additional authentication factor or proxy-level check, and invalidate existing sessions and credentials in case the flaw has already been used.
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.
| Product | Fixed in | Advisory |
|---|---|---|
| Red Hat Enterprise Linux 10 | dotnet8.0-0:8.0.129-1.el10_2 | RHSA-2026:41893 |
| Red Hat Enterprise Linux 10 | dotnet9.0-0:9.0.119-1.el10_2 | RHSA-2026:41895 |
| Red Hat Enterprise Linux 10 | dotnet10.0-0:10.0.110-1.el10_2 | RHSA-2026:41897 |
| Red Hat Enterprise Linux 10.0 Extended Update Support | dotnet8.0-0:8.0.130-1.el10_0 | RHSA-2026:58566 |
| Red Hat Enterprise Linux 10.0 Extended Update Support | dotnet9.0-0:9.0.120-1.el10_0 | RHSA-2026:58567 |
| Red Hat Enterprise Linux 8 | dotnet9.0-0:9.0.119-1.el8_10 | RHSA-2026:41899 |
| Red Hat Enterprise Linux 8 | dotnet10.0-0:10.0.110-1.el8_10 | RHSA-2026:41900 |
| Red Hat Enterprise Linux 8 | dotnet8.0-0:8.0.129-1.el8_10 | RHSA-2026:41901 |
Frequently Asked Questions
Is CVE-2026-50528 in your dependencies?
Find it across Bitnami, including transitive dependencies.