dbcve.org
Azure Ad Ssh Login Extension For LinuxPlugin / extension · Microsoft

CVE-2026-26148

HIGH · 8.1 CVSS v3.1 Published 2026-03-10
Fix available
A fix is available. Upgrade to 1.0.033370002 or later.
See remediation →
86/100
Remediation priority · High
No privileges 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 initialization of trusted variables or data stores in Azure Entra ID allows an unauthorized 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

This vulnerability in Azure Entra ID involves improper handling of external initialization data for trusted variables or data stores. An unauthorized attacker can exploit this to elevate privileges locally within the affected Entra ID environment, potentially gaining higher-level access than intended.

MitigationApply Microsoft security updates for Azure Entra ID as they become available. Monitor Microsoft's security response center for patch release and implementation guidance.

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 Ad Ssh Login Extension For LinuxPlugin / extension
Affected:>= 1.0.0, < 1.0.033370002

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
High
Privileges
None
User interaction
None
Scope
Changed
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:L/AC:H/PR:N/UI:N/S:C/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. Check if Azure AD SSH Login Extension is installed
    List installed packages or search for the extension in common installation directories. On RHEL/CentOS: rpm -qa | grep -i 'azure.*ssh'. On Debian/Ubuntu: dpkg -l | grep -i 'azure.*ssh'. Alternatively, search for file 'aad-ssh-login' or similar in /opt, /var/opt, or /usr/local.
    Affected if The extension is not installed on the system
  2. Identify the installed version number
    Run the version command for the extension if available, or inspect the package metadata. For package-based installs: rpm -qi <package_name> or dpkg -s <package_name>. Look for the 'Version' field in the output.
    Affected if Cannot determine the version from installed packages or files
  3. Compare version against vulnerable range
    If version is obtained, check if it falls within >= 1.0.0 and < 1.0.033370002. Version comparison should treat 1.0.033370002 as the patched boundary. Any version from 1.0.0 up to but not including 1.0.033370002 is vulnerable.
    Affected if Installed version is 1.0.0 or higher but lower than 1.0.033370002
  4. Verify the extension is configured and active
    Check for configuration files in /etc/ssh/ or /etc/azure/ related to Azure AD SSH login. Look for files named aad-ssh* or azure-ad* in sshd_config or in /etc/ssh/sshd_config.d/. Confirm the extension is referenced in sshd configuration.
    Affected if The extension is installed but not configured or actively used in SSH authentication flow

The system is affected if the Azure AD SSH Login Extension for Linux is installed with a version >= 1.0.0 and < 1.0.033370002 and is configured for use in the SSH authentication chain.

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.0.033370002 or later
Fixed in 1.0.033370002
Interim mitigation

Apply Microsoft security updates for Azure Entra ID as they become available. Monitor Microsoft's security response center for patch release and implementation guidance.

Recommended fix High confidence

Upgrade to version 1.0.033370002 or later of Azure AD SSH Login Extension for Linux

  1. 1. Identify the currently installed version of Azure AD SSH Login Extension for Linux by running: cat /opt/msft/linux-opencloud-id/extensions/aad-login-for-linuxLinuxExt/version.txt or checking your package manager
  2. 2. If the installed version is less than 1.0.033370002, proceed with the upgrade
  3. 3. For systems with the extension installed via package manager (e.g., apt, yum, dnf), run: sudo apt update && sudo apt install aad-login-for-linux (or corresponding package manager command)
  4. 4. Alternatively, download the latest version from the official Microsoft repository or Azure portal
  5. 5. After upgrading, verify the new version is 1.0.033370002 or later using: cat /opt/msft/linux-opencloud-id/extensions/aad-login-for-linuxLinuxExt/version.txt
  6. 6. Test SSH login functionality to ensure the update does not break existing authentication workflows

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

Fix this in Azure Ad Ssh Login Extension For Linux Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA4.0 h
22.0 hours of engineering $3,860
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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