Skip to content
Fencer Intel
medium 6.8

CVE-2026-118746 json

.NET Security Feature Bypass Vulnerability

published yesterday modified 17h ago also EUVD-2026-122252

cvss
6.8
version 3.1, CNA
cisa kev
Not listed
not in CISA's catalog
epss
0.7%
EPSS 0.7% chance of exploitation in 30 days, percentile 51%
public exploits
0
none known

Summary

Not failing securely ('failing open') in .NET allows an unauthorized attacker to bypass a security feature over a network.

Patch / fix

  • Microsoft .NET 11.0 installed on Linux 11.0.0
  • Microsoft .NET 11.0 installed on Mac OS 11.0.0

Is CVE-2026-118746 in your stack? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.

Check with Fencer

Vendor advisories

What the vendors themselves say about their products: affected, fixed or not affected, and what to do.

red hat product security vex CVE-2026-118746 updated cvss 6.8

dotnet11.0: .NET Security Feature Bypass Vulnerability

  • Red Hat Enterprise Linux 8 dotnet, dotnet11.0, dotnet-host, dotnet-sdk-11.0, dotnet-hostfxr-11.0, dotnet-runtime-11.0, +10 more Red Hat Enterprise Linux 9 dotnet-host, dotnet-sdk-11.0, dotnet-hostfxr-11.0, dotnet-runtime-11.0, dotnet-sdk-aot-11.0, dotnet-sdk-dbg-11.0, +8 more Red Hat Enterprise Linux 10 dotnet11.0
    affected: no fix available

Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf

CISA SSVC

Exploitation
none
Automatable
no
Technical impact
total
Assessed
yesterday

Exploit prediction

0.66% chance of exploitation in the next 30 days, higher than 51% of all scored CVEs (FIRST EPSS, 2026-11-11).

CVSS scores

assigned by version score vector
CNA 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
CNA 3.1 6.8 CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:U/C:H/I:H/A:N

Affected products

  • Microsoft .NET 11.0 installed on Linux
  • Microsoft .NET 11.0 installed on Mac OS

Classification

Weakness

References

Sources

Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.