Bug 2568453 (CVE-2026-118746)

Summary: CVE-2026-118746 dotnet11.0: .NET Security Feature Bypass Vulnerability
Product: [Other] Security Response Reporter: Charles Timko <ctimko>
Component: vulnerabilityAssignee: Product Security <prodsec-ir-bot>
Status: NEW --- QA Contact:
Severity: high Docs Contact:
Priority: high    
Version: unspecifiedCC: rhel-process-autobot, security-response-team, watson-tool-maintainers
Target Milestone: ---Keywords: Security
Target Release: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: ---
Doc Text:
Not failing securely ('failing open') in .NET allows an unauthorized attacker to bypass a security feature over a network. What kind of security feature could be bypassed by successfully exploiting this vulnerability? The authentication feature could be bypassed as this vulnerability allows impersonation. According to the CVSS metric, the attack complexity is high (AC:H). What does that mean for this vulnerability? The attacker must inject themselves into the logical network path between the target and the resource requested by the victim to read or modify network communications. This is called a machine-in-the-middle (MITM) attack.
Story Points: ---
Clone Of: Environment:
Last Closed: Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Deadline: 2026-11-10   

Description Charles Timko 2026-11-06 19:06:41 UTC
Not failing securely ('failing open') in .NET allows an unauthorized attacker to bypass a security feature over a network.

CNA: microsoft
CNA impact: Security Feature Bypass
CWE: CWE-636
Platforms: linux, macos
Architectures: all
CVSS 3.1: 6.8 (CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:U/C:H/I:H/A:N/E:U/RL:O/RC:C)

Affected products:
- .NET Runtime Libraries (release 11.0): 11.0.0-preview.1.26104.118 - 11.0.0-rc.3.26522.148; fixed 11.0.0