dbcve.org
Azure Automation Hybrid Worker Windows ExtensionPlugin / extension · Microsoft

CVE-2026-26141

HIGH · 7.8 CVSS v3.1 Published 2026-03-10
Fix available
A fix is available. Upgrade to 1.3.74 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
Improper authentication 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 an improper authentication vulnerability that allows an already-authorized attacker to escalate their privileges locally on the affected system. The vulnerability stems from insufficient validation during the authentication process.

MitigationApply the Microsoft security patch for Azure Arc when available. Review and limit local administrative access to Azure Arc resources until the patch is deployed.

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 Automation Hybrid Worker Windows ExtensionPlugin / extension
Affected:>= 1.0.0, < 1.3.74

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. Confirm Azure Automation Hybrid Worker Windows Extension is installed
    Open Windows Settings > Apps > Apps & features, or run 'Get-WmiObject -Class Win32_Product' in PowerShell, and look for 'Azure Automation Hybrid Worker' or 'Hybrid Worker for Azure Arc' in the installed programs list
    Affected if The extension does not appear in the installed programs list, meaning the vulnerable component is not present
  2. Retrieve the installed version number
    Check the version in the same location where you confirmed installation (Apps & features page shows version, or check the extension details via Azure Portal if managed remotely), or look in Windows Registry under HKLM\SOFTWARE\Microsoft\HybridWorker or the installation directory for version info
    Affected if The version number is 1.0.0 or higher AND less than 1.3.74 (for example, 1.1.0, 1.2.50, 1.3.0, 1.3.73)
  3. Determine if the extension is actively configured
    Check if the Hybrid Worker is registered and running. In Azure Portal, navigate to the Arc-connected machine resource, go to 'Extensions', and verify the status of the AzureAutomationHybridWorker extension shows as 'Connected' or 'Running'. Alternatively, check the Windows service 'Hybrid Worker for Azure Arc' exists and is running
    Affected if The extension status shows as provisioned, connected, or running - indicating the vulnerable authentication logic is active on this system

Your environment is affected if the Azure Automation Hybrid Worker Windows Extension is installed with a version between 1.0.0 and 1.3.73 inclusive and the extension is actively configured or running on the system.

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.3.74 or later
Fixed in 1.3.74
Interim mitigation

Apply the Microsoft security patch for Azure Arc when available. Review and limit local administrative access to Azure Arc resources until the patch is deployed.

Recommended fix Moderate confidence

Azure Automation Hybrid Worker Windows Extension version 1.3.74 or later

  1. Identify all servers or machines running Azure Automation Hybrid Worker Windows Extension with versions between 1.0.0 and 1.3.74
  2. Locate the Azure Automation account in the Azure portal that manages the Hybrid Worker deployments
  3. Navigate to the Hybrid Worker groups section and select the Windows Hybrid Worker group
  4. Use the 'Update' or 'Upgrade' function provided by Azure Automation to update the extension to version 1.3.74 or latest available version
  5. Alternatively, if using manual installation, download and install the Azure Automation Hybrid Worker Windows Extension version 1.3.74 or later from the Microsoft marketplace or official distribution channels
  6. After upgrade, verify the installed extension version is 1.3.74 or higher by checking the extension properties in Azure Portal or via PowerShell Get-AzureRmAutomationHybridWorker cmdlet
  7. Test the Hybrid Worker functionality to ensure automation runbooks execute correctly after the update

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

Fix this in Azure Automation Hybrid Worker Windows Extension Scoped from the published advisory
  • Consultation4.0 h
  • Implementation4.0 h
  • Testing4.0 h
  • Review / QA2.0 h
14.0 hours of engineering $2,480
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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