Skip to main content
Mallory
HighPublic exploitVulnerability

CVE-2026-114148: ASP.NET Core Incorrect Default Permissions Local Privilege Escalation

Published Oct 29, 2026 · Updated today
Trending this weekNot trendingOutside this week’s top 100
Mention activity · 30 days101 mentions · peak 17 in a dayToday
CVSS7.8High · v3.1
EPSS0.36%30th percentile
CISA KEVNoNot listed
In the wildNonePublic exploit, no exploitation reported
Vendor
Microsoft Corporation
IdentifiersCVE-2026-114148CWE-276 · Incorrect Default Permissions

CVE-2026-114148 is an incorrect default permissions vulnerability in ASP.NET Core involving improper file-ownership handling. An authorized attacker with low-privileged local access can exploit the flaw to elevate privileges, potentially obtaining the highest privileges on the system. Affected package streams include .NET 8, 9, 10, and 11. The specific vulnerable function and affected filesystem objects have not been identified. The vulnerability has a CVSS v3.1 base score of 7.8.

Do you run this?See affected versions in your environment and whether adversaries are exploiting this vulnerability against assets like yours.
Check your exposure
Analyst brief

Impact, mitigation & remediation

What it means and what to do now: patch path, interim mitigations, and the assume-compromise checklist.

Impact

What an attacker gets, and what they’ve been doing with it.

Successful exploitation can result in local privilege escalation to the highest system privileges, with high confidentiality, integrity, and availability impacts. An attacker could gain privileged access to sensitive information, modify protected resources, and disrupt system operation. Microsoft rates the vulnerability Important and assesses exploitation as less likely; active exploitation is not established.

Mitigation

If you can’t patch tonight, do this now.

No vulnerability-specific temporary workaround is specified. Install the applicable security updates.

Remediation

Patch, then assume compromise.

Install the security updates applicable to the operating system and every installed affected .NET stream. Distribution advisories identify corrected updates including .NET 8 SDK 8.0.133 and Runtime 8.0.33, .NET 9 SDK 9.0.123 and Runtime 9.0.22, .NET 10 SDK 10.0.114 and Runtime 10.0.14, and .NET 11 Release Candidate 3 updates. Use the platform-specific package builds rather than assuming these version labels alone establish remediation. Applicable guidance includes Ubuntu USN-8958-1, Red Hat RHSA-2026:92438, RHSA-2026:98627 and RHSA-2026:99170, and the corresponding Oracle Linux, Rocky Linux, Fedora, or MiracleLinux advisories. Consult Microsoft's CVE guidance for any additional required customer action.

Public exploits

Exploits

1 exploit validated by Mallory's analysis.

View more in app →
DotNet-Tarball-CVE-2026-114148The supplied repository listing contains README.md and two standalone Python scripts, exploit.py and poc.py, with substantial decorative terminal-banner code. Both Python files are truncated in the supplied content, preventing a complete implementation review. No exploit framework is identified. The listed file sizes total 26,786 bytes; the original repository URL, revision and archive size were not supplied, so empty strings and zero represent unavailable repository metadata. exploit.py exposes cache replacement, pipeline archive generation, a configurable archive-member name, and an installed-file SUID check. Its documentation describes replacing a .NET archive with one containing a root-owned SUID copy of Bash. The visible main function dispatches these modes, but the replacement and payload-generation implementations are omitted. The visible SUID checker tests only the SUID bit: it does not establish root ownership, executable validity or successful elevation. Extraction monitoring is advertised in the docstring, but --monitor-extract is absent from the visible argument parser. poc.py exposes archive inspection, installation inspection, executable-version checking and demonstration archive generation. The visible generator creates a benign shell script with mode 0755 and root ownership metadata, not a SUID shell. Its documentation uses --check-version --path, whereas the visible parser accepts a path directly through --check-version and defines no --path option. The claimed CVE, affected releases and fixes are not independently established by the supplied material. Root ownership in an archive is not itself evidence of a product vulnerability: privileged extraction of attacker-controlled executable content is a generic archive-trust problem. Ownership and mode restoration are performed by the extraction program through filesystem operations, rather than automatically by the kernel interpreting archive metadata. The suggested --no-same-owner mitigation alone does not prevent root-owned output when extraction runs as root and does not by itself guarantee removal of SUID permissions. The claimed Bash-based shell also needs privilege-preserving behavior not demonstrated here. Accordingly, this is an intended operational exploit with a basic documented payload, not a verified .NET-specific privilege-escalation implementation. No clear evidence of a malicious decoy is visible, but authenticity and successful exploitation remain unverified. No network communication, callback address, exfiltration destination or remote exploitation implementation is visible. HTTP/MITM and compromised artifact repositories are described as possible delivery scenarios, not implemented capabilities. README URLs are attribution and references only.Ghost-Bx1 · Disclosed Oct 27, 2026 · python · sh · local · file · supply_chainOperational
Exposure surface

Affected products & vendors

Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.

VendorProductType
Microsoft Corporation.Net 10.0 Installed On Linuxapplication
Microsoft Corporation.Net 10.0 Installed On Mac Osapplication
Microsoft Corporation.Net 10.0 Installed On Windowsapplication
Microsoft Corporation.Net 11.0 Installed On Linuxapplication
Microsoft Corporation.Net 11.0 Installed On Mac Osapplication
Microsoft Corporation.Net 11.0 Installed On Windowsapplication
Microsoft Corporation.Net 8.0 Installed On Linuxapplication
Microsoft Corporation.Net 8.0 Installed On Mac Osapplication
Microsoft Corporation.Net 8.0 Installed On Windowsapplication
Microsoft Corporation.Net 9.0 Installed On Linuxapplication
Microsoft Corporation.Net 9.0 Installed On Mac Osapplication
Microsoft Corporation.Net 9.0 Installed On Windowsapplication
Microsoft Corporation.Net Source-Build Linux Tarballs All Archive Typesapplication
Microsoft CorporationAsp Net Core Runtime And Targeting-Pack Linux Tarballs Microsoft Publishedapplication
FAQ

Frequently asked questions

Is CVE-2026-114148 exploited in the wild?
As of Nov 17, 2026, Mallory has no reports of CVE-2026-114148 being exploited in the wild. It is not listed in CISA KEV.
Is there a public exploit for CVE-2026-114148?
Yes. Mallory tracks 1 public exploit or proof of concept for CVE-2026-114148, the earliest disclosed Oct 27, 2026.
Is there a patch for CVE-2026-114148?
Install the security updates applicable to the operating system and every installed affected .NET stream. Distribution advisories identify corrected updates including .NET 8 SDK 8.0.133 and Runtime 8.0.33, .NET 9 SDK 9.0.123 and Runtime 9.0.22, .NET 10 SDK 10.0.114 and Runtime 10.0.14, and .NET 11 Release Candidate 3 updates.
What products are affected by CVE-2026-114148?
Microsoft Corporation Asp Net Core Runtime And Targeting-Pack Linux Tarballs Microsoft Published, Microsoft Corporation .Net 10.0 Installed On Linux, Microsoft Corporation .Net 10.0 Installed On Mac Os, Microsoft Corporation .Net 10.0 Installed On Windows, Microsoft Corporation .Net 11.0 Installed On Linux, and 9 more.
How severe is CVE-2026-114148?
CVE-2026-114148 has a CVSS v3.1 score of 7.8 (High) and an EPSS score of 0.36% (30th percentile) as of Nov 17, 2026.
Mallory platform

The version that knows your environment.

This page is what’s public. Mallory adds the parts that aren’t: which of your assets are affected, which adversaries are exploiting it right now, and which detections to deploy tonight.
Exposure mappingQuery your assets running an affected version, and investigate the blast radius.
Threat actor evidenceEvery report linking this CVE to a named adversary.
Associated malwareMalware families linked to this CVE, with evidence and IOCs.
Detection signaturesYARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Vendor-by-vendor mappingCross-references every affected SKU, including bundled OEM variants.
Social activity9Community discussion across Reddit, Mastodon, and other social sources.