CVE-2026-96957: .NET Security Feature Bypass Vulnerability
Noroxi assessment
Priority: Monitor (action score 35/100)
- The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
- Probability of exploitation in the next 30 days: 0.59% (FIRST EPSS).
- Anyone who can reach it over the internet can trigger it. No account or password is required. A user must open a link or visit a page. No special conditions are required; it is repeatable.
- Fixed version: .NET 10.0 runtime installed on Linux 10.0.402; .NET 10.0 runtime installed on Mac OS 10.0.402; .NET 10.0 runtime installed on Windows 10.0.402.
Low priority for now. Upgrade to .NET 10.0 runtime installed on Linux 10.0.402; .NET 10.0 runtime installed on Mac OS 10.0.402; .NET 10.0 runtime installed on Windows 10.0.402 or later.
Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it
Primary sources: NVD · CVE.org · FIRST EPSS
Improper verification of cryptographic signature in .NET allows an unauthorized attacker to bypass a security feature over a network.
- Published
- Oct 13, 2026
- Updated
- Nov 10, 2026
- EPSS
- 0.5% · 48th percentile
- CWE
- CWE-347
Report tools
Action score
35
Low priority for now.
- CVSS
- 35 / 40 · 8.8 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.5%
CISA SSVC decision
- Exploitation
- none
- Automatable
- no
- Technical impact
- total
Vulnrichment: CISA's decision-tree inputs.
CNA vs NVD score
- NVD
- —
- CNA · microsoft
- 8.8
- NVD has not scored this yet; the score shown is the CNA’s.
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H/E:U/RL:O/RC:C
The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.
Get told when this record changes
- Not in KEV: no record of exploitation in the wild
- No public exploit code on record
- A fix has been released
If any of these changes, we'll tell you in the daily email digest.
Is your version affected? Check itNoroxi analysis
What does it mean in your environment?
The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.
We use this product, ask for helpAffected systems
Is your version affected?
Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.
| Vendor | Product | CPE |
|---|---|---|
| microsoft | .net | cpe:2.3:a:microsoft:.net |
| microsoft | windows | cpe:2.3:o:microsoft:windows |
| microsoft | visual studio 2022 | cpe:2.3:a:microsoft:visual_studio_2022 |
| microsoft | visual studio 2026 | cpe:2.3:a:microsoft:visual_studio_2026 |
| apple | macos | cpe:2.3:o:apple:macos |
| linux | linux kernel | cpe:2.3:o:linux:linux_kernel |
Versions reported by the vendor
Affected version ranges reported by the assigning authority (microsoft). Independent of NVD's CPE analysis and usually ahead of it.
Microsoft .NET 10.0 runtime
- 10.0.0 and later · before 10.0.402affected
Microsoft .NET 11.0 runtime
- 11.0.0 and later · before 11.0.100-rc.2affected
Microsoft Microsoft Visual Studio 2022 version 17.14
- 17.14.0 and later · before 17.14.42affected
Microsoft Microsoft Visual Studio 2026 version 18.10
- 18.10.0 and later · before 18.10.4affected
Affected versions · NVD (4)
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- microsoft .net10.0.0 and later · before 10.0.13
- microsoft .net11.0.0
- microsoft visual studio 202217.14.0 and later · before 17.14.42
- microsoft visual studio 202618.10.0 and later · before 18.10.4
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| Alpine:v3.23 | dotnet10-runtime | before 10.0.13-r0 | 10.0.13-r0 |
| Red Hat:hummingbird:1 | dotnet-sdk-10.0 | before 0:10.0.113-1.hum1 | 0:10.0.113-1.hum1 |
| Red Hat:hummingbird:1 | dotnet-sdk-10.0-source-built-artifacts | before 0:10.0.113-1.hum1 | 0:10.0.113-1.hum1 |
| Red Hat:hummingbird:1 | dotnet-sdk-aot-10.0 | before 0:10.0.113-1.hum1 | 0:10.0.113-1.hum1 |
| Red Hat:hummingbird:1 | dotnet-sdk-dbg-10.0 | before 0:10.0.113-1.hum1 | 0:10.0.113-1.hum1 |
| Red Hat:hummingbird:1 | dotnet-templates-10.0 | before 0:10.0.113-1.hum1 | 0:10.0.113-1.hum1 |
| Red Hat:hummingbird:1 | dotnet10.0 | before 0:10.0.113-1.hum1 | 0:10.0.113-1.hum1 |
Same product
microsoft: all recordsOther highest-scoring records for the same primary product.
- CVE-2023-38180.NET and Visual Studio Denial of Service VulnerabilityKEV64This week
- CVE-2023-38171Microsoft QUIC Denial of Service Vulnerability51Plan
- CVE-2021-26701.NET Core Remote Code Execution Vulnerability41Plan
Published before and after this one in the same product
- ← EarlierCVE-2026-69439Sep 8, 2026 · .NET and Visual Studio Elevation of Privilege Vulnerability35Monitor
- ← EarlierCVE-2026-69806Sep 8, 2026 · .NET Elevation of Privilege Vulnerability28Monitor
- Later →CVE-2026-96958Oct 13, 2026 · .NET Denial of Service Vulnerability30Monitor
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
| Product / package | Fixed version | Source |
|---|---|---|
| .NET 10.0 runtime installed on Linux | 10.0.402 · KB5130036 | Microsoft (MSRC) |
| .NET 10.0 runtime installed on Mac OS | 10.0.402 · KB5130036 | Microsoft (MSRC) |
| .NET 10.0 runtime installed on Windows | 10.0.402 · KB5130036 | Microsoft (MSRC) |
| .NET 11.0 runtime installed on Linux | 11.0.100-rc.2 · Release Notes | Microsoft (MSRC) |
| .NET 11.0 runtime installed on Mac OS | 11.0.100-rc.2 · Release Notes | Microsoft (MSRC) |
| .NET 11.0 runtime installed on Windows | 11.0.100-rc.2 · Release Notes | Microsoft (MSRC) |
| Microsoft Visual Studio 2022 version 17.14 | 17.14.42 · Release Notes | Microsoft (MSRC) |
| Microsoft Visual Studio 2026 version 18.10 | 18.10.4 · Release Notes | Microsoft (MSRC) |
| alpine:dotnet10-runtime | 10.0.13-r0 · Alpine:v3.23 | Package registry (OSV) |
| red hat:dotnet-sdk-10.0 | 0:10.0.113-1.hum1 · Red Hat:hummingbird:1 | Package registry (OSV) |
| red hat:dotnet-sdk-10.0-source-built-artifacts | 0:10.0.113-1.hum1 · Red Hat:hummingbird:1 | Package registry (OSV) |
| red hat:dotnet-sdk-aot-10.0 | 0:10.0.113-1.hum1 · Red Hat:hummingbird:1 | Package registry (OSV) |
| red hat:dotnet-sdk-dbg-10.0 | 0:10.0.113-1.hum1 · Red Hat:hummingbird:1 | Package registry (OSV) |
| red hat:dotnet-templates-10.0 | 0:10.0.113-1.hum1 · Red Hat:hummingbird:1 | Package registry (OSV) |
| red hat:dotnet10.0 | 0:10.0.113-1.hum1 · Red Hat:hummingbird:1 | Package registry (OSV) |
Exploit status
No known public exploit
No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
- Published
- Fix recordedsame day
- TodayNov 16, 2026+34 d
FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).
Not on record for this CVE: patch commit or PR link · researcher credit · variant or chain candidate · public bounty program.
Technical details
Attack conditions
- Anyone who can reach it over the internet can trigger it.
- No account or password is required.
- A user must open a link or visit a page.
- No special conditions are required; it is repeatable.
If successful
- Confidentiality
- high · data can be read
- Integrity
- high · data or configuration can be modified
- Availability
- high · the service can be disrupted
- Attack vector
- Network
- Attack complexity
- Low
- Privileges required
- None
- User interaction
- Required
- Scope
- Unchanged
- Confidentiality impact
- High
- Integrity impact
- High
- Availability impact
- High
Weakness class (CWE)
CWE-347 · Improper Verification of Cryptographic SignatureCVSS vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H
nvd-secondary
Root cause
The verifier takes the algorithm to verify with from the token’s own header. Untrusted data ends up deciding its own verification rule.
The bug in code
The whole CWE-347 classA representative example of this vulnerability class. Not the vendor's source code; it shows the faulty pattern and its fix.
Vulnerable
const claims = jwt.verify(token, publicKey);Fixed
const claims = jwt.verify(token, publicKey, {
algorithms: ["RS256"],
issuer: "https://id.example.com",
audience: "portal",
});Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
Attack patterns (CAPEC)
ATT&CK techniques
—
Change log
- Fix✗ → ✓
- SSVC exploitation— → none
- Exploit maturity— → none
For records you follow, these changes also arrive as notifications. →
References
Vendor advisories and official records. Exploit/PoC links are deliberately left out.