CVE Tools

CVE-2026-65816

Azure Arc Elevation of Privilege Vulnerability

No known exploitation. EPSS puts it in the 60th percentile. A vendor fix is available.

Published Updated Sources: CVE.org, NVD

What to do

The vendor has published a fix. Version details are below where the sources state them.

Steps

Written by AI from the record
  1. Check whether you use Azure Arc in connection with your Azure Web Apps (Arc-enabled management of your web-app resources or Arc-based hosting/connectivity).
  2. Open Microsoft’s Update Guide for CVE-2026-65816 and review the “fixed in” versions and scope that apply to your Web Apps setup.
  3. Upgrade/patch your Azure Arc/Azure Web Apps components to the fixed version(s) listed by Microsoft for CVE-2026-65816 (do not rely on partial updates).
  4. If you cannot patch immediately, implement Microsoft’s workaround guidance from the same Update Guide and restrict any network paths that could reach the affected Azure Arc-managed endpoints.

What it is

From the CVE record

Use of incorrectly-resolved name or reference in Azure Arc allows an unauthorized attacker to elevate privileges over a network.

In plain language

Written by AI from the record

This vulnerability in Azure Arc-linked Azure Web Apps could let an attacker gain higher privileges on your system; because it’s rated critical and has security pressure, most small businesses should treat it as urgent and apply Microsoft’s fix.

CVE-2026-65816 is an elevation of privilege issue in the Azure Arc integration where an incorrectly-resolved name or reference can let an unauthorized attacker elevate privileges over a network path affecting Azure Web Apps.

If you're affected

  • Full access escalation within environment
  • Service disruption risk
  • Data and admin control exposure
  • Attackers may install persistent control

Exploitation

Where each signal puts this CVE on the scale from published to confirmed exploited.

EPSS60th
CISA KEV

Not in the catalog. CISA has not confirmed exploitation.

Public exploits

No public exploit or proof of concept found in the sources we track.

EPSS

1.0% chance of exploitation activity in the next 30 days, which ranks it in the 60th percentile of scored CVEs.

Exploit Prediction Scoring System, FIRST.org. A probability, not a confirmation.

Lifecycle

8 events over 4 days, from the signal feeds we watch.

  1. Patch availablerecord updated
  2. Record updated
  3. Record updatedrecord updated
  4. Publishedweakness classified, record updated

Affected products

And 1 more affected product. See all after sign-in

Technical detail

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:H

Scored 10.0 by NVD.

How it is reached

  • Attack Vector NetworkExploitable remotely over the network without any special conditions
  • Attack Complexity LowNo special conditions — the attack can be reliably reproduced
  • Privileges Required NoneNo authentication required — anyone can exploit this
  • User Interaction NoneNo user interaction needed — fully automated exploitation

Scope

  • Scope ChangedThe exploit can affect other components (e.g. sandbox escape, host compromise from VM)

Impact if exploited

  • Confidentiality HighTotal information disclosure — all data in the component is compromised
  • Integrity HighTotal loss of integrity — attacker can modify any data in the component
  • Availability HighTotal denial of service — the component is completely unavailable

Weaknesses

Sources

Watch the software you run.

My Stack ranks new CVEs for your products by real-world exploitation, so the next serious one reaches you without reading every advisory.

We'll flag the next CVE, public exploit or patch for Azure Web Apps, not every advisory.

We use analytics cookies to see which pages and articles actually help people. Decline and none of them run — the site works the same. What we store