On this page (7 sections)

CVE-2026-114162 is a critical vulnerability in Microsoft Graph, published on 2026-11-10. The NVD entry describes it as incorrect authorization that allows an authorized attacker to elevate privileges over a network. It carries a CVSS score of 9.1.

If your website, store or internal tools call Microsoft Graph to read mail, files, users or directory data, this is worth your attention. Be aware that the public record is extremely short right now: the research behind this article contains a single one-sentence description and a link to Microsoft's advisory page, so many questions below are open.

What is confirmed so far

The only confirmed facts come from the NVD record: the flaw is an incorrect authorization problem in Microsoft Graph, it can be reached over a network, and it lets an attacker who is already authorized gain higher privileges. The CVE was published on 2026-11-10 and the record points to Microsoft's update guide entry as its reference.

The research does not say whether Microsoft has shipped a fix, whether any action is required from customers, whether the issue is being exploited, or whether it is listed in CISA's Known Exploited Vulnerabilities catalog (the CVE data shows no KEV entry). Only one independent publisher covers this story so far, so treat details from secondary posts with caution until Microsoft's page is clear.

What incorrect authorization means in plain terms

CWE-863 describes a system that checks who you are but then makes a wrong decision about what you are allowed to do. Authentication succeeds, yet the permission check that should limit the action is missing, flawed or bypassable. The result is privilege escalation: an identity with limited rights ends up performing actions reserved for a more powerful one.

The phrase "authorized attacker" matters. It suggests the attacker needs some valid access first, such as a low-privileged account, a user token or an app registration. That lowers the risk compared with an anonymous attack, but it is still serious. Stolen credentials, phished accounts and over-shared app secrets are common, and a privilege escalation flaw turns any of them into a much bigger problem. The exact preconditions for this CVE are not described in the research, so do not assume more or less than that.

Who is realistically exposed

Microsoft Graph is the API behind much of Microsoft 365 and Entra ID. You are in scope if any of the following is true:

  • Your website or web app signs users in with Microsoft accounts or calls Graph for profile, mail, calendar, files or directory data.
  • You have automation, plugins or integrations (CRM, ticketing, backup, e-commerce, HR tools) registered as apps in your Microsoft tenant.
  • You run scripts or services with application permissions that can read or change tenant data.
  • You manage a tenant for clients as an agency or managed service provider.

Whether the flaw sits in the cloud service itself or in something customers must update is not stated in the research. If it is service-side, Microsoft would remediate it centrally. Confirm this on the advisory instead of guessing.

How to check your exposure

Start with the vendor page, then review your own Graph footprint so you know what an escalation could reach.

  1. Open the Microsoft advisory for CVE-2026-114162 and note whether it lists affected products, a fix, or required customer action.
  2. In the Microsoft Entra admin center, list every app registration and enterprise application in your tenant and note who owns each one.
  3. For each app, review the Graph permissions granted. Separate delegated permissions (acting as a signed-in user) from application permissions (acting as the app itself).
  4. Flag anything with broad write or directory-wide permissions, and anything nobody can explain or that has not been used recently.
  5. Review sign-in and audit logs for unusual token use, new consent grants, new app secrets or role assignments you did not make.
These are review steps in the Microsoft admin portals, not commands from the advisory. Menu names change over time, so follow Microsoft's current documentation for your tenant.

What to do now

  1. Read Microsoft's advisory today and follow any fix or mitigation it gives; do not rely on third-party summaries.
  2. Apply any update or configuration change the advisory lists, and record the date you did.
  3. Remove unused app registrations and revoke consent for integrations you no longer need.
  4. Reduce Graph permissions to the least privilege each app actually requires.
  5. Rotate client secrets and certificates for high-privilege apps, and store them outside code repositories and web roots.
  6. Require multi-factor authentication for all accounts, especially administrators, since this flaw needs an already authorized identity.
  7. Turn on alerting for new role assignments, new consent grants and new credentials on app registrations.
Tip. If you run a WordPress or other CMS site that connects to Microsoft 365, check the plugin or integration for stored Graph secrets and tokens, and rotate them if the site has ever been compromised. The WordPress security checklist covers wider hardening.

Detection and monitoring afterwards

A privilege escalation usually leaves traces as changes: a role that was not there yesterday, a new secret on an app, a consent grant from an unexpected user. Watch your Microsoft audit logs for these events and keep them long enough to look back if Microsoft later confirms exploitation.

On the website side, Webforta's certificate, DNS and header-change monitoring can alert you when something about your public site changes unexpectedly, and the free security headers checker shows how your site responds. These look at your site from the outside and cannot see inside your Microsoft tenant, so they complement, not replace, a review of your Graph permissions. If you suspect a compromise, follow the steps in website hacked: what to do.

What we do not know yet

  • Which Graph components, endpoints or versions are affected.
  • Whether a fix exists and whether customers must act.
  • What access level counts as "authorized" for an attacker.
  • Whether anyone is exploiting the flaw. The research contains no exploitation report and no CISA KEV listing.
  • Who assigned the 9.1 CVSS score and the exact vector.

We will not guess at these. Check the Microsoft advisory for updates, and see our security news and analysis for further coverage as more details are published.

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.

  1. CVE-2026-114162: Incorrect authorization in Microsoft Graph allows an authorized attacker to elevate privileges over a network.nvd.nist.gov ·
  • Microsoft Graph
  • CVE-2026-114162
  • privilege escalation
  • CWE-863
  • Microsoft 365