On this page (7 sections)
CVE-2026-114146 is a newly published vulnerability in ASP.NET Core. According to the NVD record, it is an incorrect authorization flaw that allows an authorized attacker to elevate privileges over a network. The record carries a CVSS score of 9 and a critical severity rating.
If you run web applications, APIs or internal portals on ASP.NET Core, this is worth tracking today. The public record is short, so this article separates what is confirmed from what is still unknown, and covers what you can do while full details are pending.
What is confirmed so far
The NVD entry, published on 2026-11-10, describes the flaw in one sentence: incorrect authorization in ASP.NET Core lets an authorized attacker elevate privileges over a network. The only other reference is the Microsoft Security Response Center entry for the same CVE.
At the time of writing, only a single independent publisher covers this story, and the available record does not include affected version ranges, fixed versions, an attack vector string, or any report of exploitation. Whether a fix has been released is also not stated in the record. Treat anything beyond the points above as unconfirmed until Microsoft's advisory says otherwise.
What incorrect authorization means in plain terms
CWE-863 describes software that checks whether a user may perform an action, but performs that check wrongly. Authentication answers who you are. Authorization answers what you are allowed to do. When the second check is flawed, a signed-in user may reach data or functions meant for a higher role, such as an administrator.
The wording matters here. An authorized attacker means the person already has some valid access, for example a regular account. Over a network means the attempt does not need local access to the server. Together, that points to a low-privileged account being turned into a more powerful one. The record does not say which ASP.NET Core component is involved or how the check fails, so we cannot say which application designs are most at risk.
Who is realistically exposed
Until Microsoft publishes version details, assume any internet-facing or internal ASP.NET Core application could be in scope. Risk is higher where an attacker can easily obtain a low-privilege account:
- Sites with open self-registration, free trials or customer portals.
- Multi-tenant SaaS products where one tenant must never see another's data.
- Admin panels and APIs that rely on roles, policies or claims for access decisions.
- Internal tools exposed through a VPN or reverse proxy that many staff accounts can reach.
Applications with no user accounts at all are less likely to be affected by a flaw that requires an authorized attacker, but confirm that against the vendor advisory rather than assuming.
How to check your exposure
Start by finding out which ASP.NET Core runtime each application uses, so you can compare against the fixed versions once Microsoft names them. On a server with the .NET CLI installed, this read-only command lists installed runtimes, including Microsoft.AspNetCore.App, and their versions:
dotnet --list-runtimesLook for lines starting with Microsoft.AspNetCore.App and note the version numbers. Applications published as self-contained carry their own runtime, so also check your build and deployment records, not just the server. Containers need the same check against the base image tag they were built from.
What to do now
Because the available record does not confirm affected versions or a fix, the steps below focus on preparation and risk reduction. Once Microsoft publishes fixed versions, updating to them is the expected remedy.
- Open the Microsoft advisory for CVE-2026-114146 and note the affected and fixed versions as soon as they are listed.
- Inventory every ASP.NET Core application, including containers, self-contained deployments and staging systems, and record the runtime version of each.
- Prioritize internet-facing apps and any app with multiple roles or tenants.
- When Microsoft lists a fixed version, apply it, then rebuild and redeploy containers and self-contained apps, which do not pick up a server-wide runtime update.
- Review who holds accounts on your apps. Remove unused accounts and tighten open registration where it is not needed.
- Audit your own authorization rules: confirm sensitive endpoints enforce role or policy checks on the server side, not only in the user interface.
- Review recent logs for users performing actions outside their normal role, and for unexpected role or permission changes.
Detection and monitoring
Privilege escalation often leaves traces in application data rather than at the network edge. Watch for accounts whose role or permissions change without a matching admin action, standard users requesting admin-only URLs and getting successful responses, and unusual access to other users' or tenants' records. If you do not log authorization decisions today, add that logging now, since it helps with this issue and with future ones.
A website firewall can add a layer of filtering in front of an application, but it is unlikely to reliably compensate for a logic flaw inside the authorization code, so fixing the application itself is the real remedy once an update exists. For background, see what a WAF is. Outside-in checks are also limited here, as explained in what outside-in malware detection can and cannot see.
If you manage many sites, Webforta Monitor can alert you to certificate, DNS and header changes, which helps you notice unexpected changes after an incident. It does not detect or block this specific flaw.
Timeline
| Date | Event |
|---|---|
| 2026-11-10 | CVE published in NVD; Microsoft MSRC entry referenced |
| 2026-11-10 | No CISA KEV listing in the research data |
We will not guess at exploit availability or patch timing. Check the MSRC page directly for the current status of CVE-2026-114146.
Sources
This article is based on the public sources below. Details can change as vendors and researchers publish more; check the original advisories before acting on version numbers.
