Not failing securely ('failing open') in .NET allows an unauthorized attacker to bypass a security feature over a network.
Not failing securely ('failing open') in .NET allows an unauthorized attacker to bypass a security feature over a network.
Read at NIST National Vulnerability Database (CVE API 2.0)
- Vendor
- Microsoft
- Product
- .NET 11.0 installed on Linux, .NET 11.0 installed on Mac OS
- CVSS v3.1
- 6.8 AV:N/AC:H/PR:N/UI:R/S:U/C:H/I:H/A:N
- Exploitation
- SSVC none, automatable no, impact total
- Weakness
- CWE-636
- NVD status
- Awaiting Analysis
Why it ranks 18 (Routine)
- CVSS v3.1 6.8 medium
- SSVC: total technical impact
- Widely deployed vendor product (Microsoft)
- Recency: items published within 24 hours gain 15, within 72 hours 6, within 7 days 2.
Links
- NIST National Vulnerability Database (CVE API 2.0) (nvd.nist.gov)
- CVE-2026-118746 on this site · NVD · CVE.org · Vulnpedia
Related coverage
Other items that share a CVE or were clustered with this one.