dbcve.org
Azure Connected Machine AgentApplication · Microsoft

CVE-2025-55316

HIGH · 7.8 CVSS v3.1 Published 2025-09-09
Fix available
A fix is available. Upgrade to 1.56 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
External control of file name or path in Azure Arc 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

Azure Arc contains a path traversal vulnerability where an authorized user can manipulate file paths to gain elevated local privileges. The flaw allows controlled file path input to be used in privileged operations without proper sanitization, enabling local privilege escalation from an authorized baseline.

MitigationApply Microsoft-provided patches for Azure Arc when available, and review and restrict file system ACLs on systems running Azure Arc components to limit exploitation surface.

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
Azure Connected Machine AgentApplication
Affected:< 1.56

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
    On Windows, check for the service 'Azure Connected Machine Agent' in Services or look for the installation at C:\Program Files\AzureConnectedMachineAgent. On Linux, check for package installation via dpkg -l | grep azcmagent or rpm -qa | grep azcmagent, or check for /opt/azcmagent directory.
    Affected if The Azure Connected Machine Agent service or package exists on the system
  2. Determine the installed agent version
    Run the command 'azcmagent --version' from the installation directory (C:\Program Files\AzureConnectedMachineAgent\azcmagent.exe on Windows, or /opt/azcmagent/bin/azcmagent on Linux). Alternatively on Windows, check the file version property of azcmagent.exe.
    Affected if Command returns a version number lower than 1.56, or version cannot be determined (indicating older install)
  3. Confirm the agent service is running
    On Windows, run 'Get-Service -Name AzureConnectedMachineAgent' or check status in Services.msc. On Linux, run 'systemctl status azcmagent' or check if process azcmagent is running.
    Affected if The Azure Connected Machine Agent service is active or running on the system

If the Azure Connected Machine Agent is installed and running with a version lower than 1.56, the system is affected by this path traversal vulnerability that could allow local privilege escalation.

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.56 or later
Fixed in 1.56
Interim mitigation

Apply Microsoft-provided patches for Azure Arc when available, and review and restrict file system ACLs on systems running Azure Arc components to limit exploitation surface.

Recommended fix Moderate confidence

Azure Connected Machine Agent version 1.56

  1. Navigate to the Microsoft Security Response Center (msrc.microsoft.com) to obtain the security update for Azure Connected Machine Agent
  2. Download the Azure Connected Machine Agent version 1.56 or later from the official Microsoft download sources
  3. Stop the Azure Connected Machine Agent service if running
  4. Install the updated agent version using standard Azure installation procedures
  5. Verify the installed version is 1.56 or later using azcmagent --version or Get-AzConnectedMachine
  6. Restart the Azure Connected Machine Agent service
Caveat Review Azure Arc documentation for any agent update requirements or breaking changes between versions

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

Fix this in Azure Connected Machine Agent Scoped from the published advisory
  • Consultation6.0 h
  • Implementation12.0 h
  • Testing10.0 h
  • Review / QA4.0 h
32.0 hours of engineering $5,580
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-55316 — 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-2025-55316 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