CVE-2025-26627
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 · uneditedImproper neutralization of special elements used in a command ('command injection') 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 confidenceCommand injection vulnerability in Azure Arc where improper neutralization of special elements in commands allows an authorized attacker to inject malicious commands and elevate privileges locally. The attacker needs existing authorized access to the system but can escape their current privilege context through the injection flaw.
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< 1.0.10CVSS 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
- High
- Privileges
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:L/AC:H/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 checksWork through these to decide whether this CVE applies to you.
-
Confirm Azure Arc agent is installedRun the Azure Arc Connected Machine agent command to check its presence, such as 'azcmagent --version' or check the installed agent service statusAffected if The Azure Arc Connected Machine agent is installed and running on the system
-
Determine installed Azure Arc versionRetrieve the version of the Azure Arc agent using 'azcmagent --version' or the appropriate version command for your installationAffected if The returned version number is lower than 1.0.10 (for example, 1.0.9, 1.0.8, etc.)
-
Compare against vulnerable version rangeCompare your installed version to the affected range: any version prior to 1.0.10 is within the vulnerable rangeAffected if Your installed version is below 1.0.10
You are affected if the Azure Arc Connected Machine agent is installed and its version is lower than 1.0.10, as this version threshold is where the command injection vulnerability begins.
Generated from the published advisory. Verify against your own configuration.
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 · scoped1.0.10
Apply Microsoft security patches for Azure Arc when available; until then, restrict Azure Arc component access to minimal necessary principals and monitor for suspicious command execution patterns.
Azure Arc version 1.0.10 or later
- Check the current Azure Arc version using 'az connectedk8s show' or 'az arck8s show' commands
- Review Azure Arc release notes at https://learn.microsoft.com/azure/azure-arc/kubernetes/release-notes for version 1.0.10 details
- Upgrade Azure Arc agents on affected Kubernetes clusters using 'az connectedk8s upgrade --name <cluster-name> --resource-group <resource-group>'
- Verify the upgrade completed successfully by checking the agent version
- Confirm the new version is 1.0.10 or later using 'az connectedk8s show'
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation8.0 h
- Testing6.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,600.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-26627 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2025-26627 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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