# CVE-2026-26148: Microsoft Azure AD SSH Login extension for Linux Elevation of Privilege Vulnerability

> An attacker can elevate privileges locally by exploiting external initialization of trusted variables in the Azure AD SSH Login extension.

- **Severity:** High 8.1 (`CVSS:3.1/AV:L/AC:H/PR:N/UI:N/S:C/C:H/I:H/A:H/E:P/RL:O/RC:C`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 10 Mar 2026
- **Updated:** 19 Jun 2026
- **Also known as:** GHSA-qxwj-8xxc-qwm6

## What is CVE-2026-26148?

CVE-2026-26148 is a high-severity vulnerability in Microsoft Azure AD SSH Login extension for Linux, published on 10 Mar 2026. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

External initialization of trusted variables or data stores in Azure Entra ID allows an unauthorized attacker to elevate privileges locally.

Weakness: CWE-454 (External Initialization of Trusted Variables or Data Stores)

## Which versions are affected by CVE-2026-26148?

It affects 1 product.


Products: Microsoft Azure Ad Ssh Login Extension for Linux.

## How do I fix CVE-2026-26148?

No fix has been published for CVE-2026-26148 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-26148 being exploited?

There is no known exploitation of CVE-2026-26148 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-26148 and fix it if it is affected.

What it is: CVE-2026-26148 is a high-severity vulnerability in Microsoft Azure AD SSH Login extension for Linux, published on 10 Mar 2026. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-26148 in the wild and no public exploit code.

Affected product: Microsoft Azure AD SSH Login extension for Linux. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-26148/ (Markdown: https://insights.sbomify.com/CVE-2026-26148/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-26148
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-26148
- OSV: https://osv.dev/vulnerability/CVE-2026-26148

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-26148/
Summaries are generated and may contain mistakes; the official description above is the record.