dbcve.org
Arc Enabled Servers Azure Connected Machine AgentApplication · Microsoft

CVE-2026-26117

HIGH · 7.8 CVSS v3.1 Published 2026-03-10
Fix available
A fix is available. Upgrade to 1.61 or later.
See remediation →
80/100
Remediation priority · High
Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
Authentication bypass using an alternate path or channel in Azure Windows Virtual Machine Agent allows an authorized attacker to elevate privileges locally.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · moderate confidence

Authentication bypass vulnerability in Azure Windows Virtual Machine Agent allows a locally authorized attacker to bypass normal authentication mechanisms and elevate privileges to higher permission levels via an alternate path or channel.

MitigationApply available security patches for Azure VM Agent through Azure Update Manager or manual update procedures; review VM fleet for affected agents and validate patch deployment.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Arc Enabled Servers Azure Connected Machine AgentApplication
Affected:>= 1.0.0, < 1.61

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Local
Complexity
Low
Privileges
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

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

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Verify Azure Connected Machine Agent is installed
    Open Services (services.msc) and look for 'Azure Connected Machine Agent' or 'Arc Connected Machine Agent' service, or run 'Get-Service | Where-Object {$_.Name -like '*connected*machine*'}' in PowerShell
    Affected if The service exists on the system
  2. Retrieve the installed agent version
    Run 'azcmagent --version' from command prompt or PowerShell, or check the service properties via services.msc for the version information
    Affected if The command returns a version number less than 1.61.0 or the displayed version falls within >= 1.0.0 and < 1.61.0
  3. Confirm the agent service is running
    Check the service status in Services (should show 'Running') or run 'Get-Service -Name '*connected*machine*' | Select-Object Status' in PowerShell
    Affected if The service is installed and running with a vulnerable version as determined in step 2
  4. Check for specific vulnerable component presence
    Inspect the agent installation directory (typically C:\Program Files\AzureConnectedMachineAgent) for the presence of azcmagent.exe and verify authentication-related modules exist by examining the agent logs in C:\ProgramData\AzureConnectedMachineAgent\Logs
    Affected if The agent binaries are present and the agent has been operational (indicated by log files), combined with a version in the affected range

The system is affected if Azure Connected Machine Agent is installed with a version greater than or equal to 1.0.0 and less than 1.61.0, and the service is running.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to 1.61 or later
Fixed in 1.61
Interim mitigation

Apply available security patches for Azure VM Agent through Azure Update Manager or manual update procedures; review VM fleet for affected agents and validate patch deployment.

Recommended fix Moderate confidence

Azure Connected Machine Agent version 1.61 or later

  1. Identify the currently installed version of Azure Connected Machine Agent on affected servers using PowerShell: Get-ItemProperty -Path 'HKLM:\SOFTWARE\Microsoft\Azure Connected Machine Agent' -Name Version
  2. Alternatively, check via the Az.ConnectedMachine PowerShell module: Get-AzConnectedMachine
  3. Download the latest Azure Connected Machine Agent version 1.61 or later from the official Microsoft download center or Azure Portal
  4. Deploy the updated agent to all affected Arc-enabled servers using your preferred deployment method (Azure Update Manager, Group Policy, or manual installation)
  5. Verify successful installation by confirming the agent version is now 1.61 or higher

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Arc Enabled Servers Azure Connected Machine Agent Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA1.0 h
10.0 hours of engineering $1,750
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,800.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-26117 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-26117 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data