# CVE-2025-24049: Azure Command Line Integration (CLI) Elevation of Privilege Vulnerability > An attacker can exploit command injection in Azure CLI to elevate privileges locally, requiring users to apply vendor patches. - **Severity:** High 8.4 (`CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H/E:U/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:** Yes - **Published:** 11 Mar 2025 - **Updated:** 13 Feb 2026 - **Also known as:** BIT-azure-cli-2025-24049, CLEANSTART-2026-TB31974, GHSA-qjf4-cfqr-rj5j, SUSE-SU-2025:1019-1, SUSE-SU-2025:1182-1, SUSE-SU-2026:0273-1, openSUSE-SU-2026:10211-1 ## What is CVE-2025-24049? CVE-2025-24049 is a high-severity command injection vulnerability in Microsoft Azure CLI, published on 11 Mar 2025. It can only be exploited from the same machine or local network, with no action from the victim. ### Official description Improper neutralization of special elements used in a command ('command injection') in Azure Command Line Integration (CLI) allows an unauthorized attacker to elevate privileges locally. Weakness: CWE-77 (Improper Neutralization of Special Elements used in a Command) ## Which versions are affected by CVE-2025-24049? 1 open source package ship an affected version, including azure-cli. It affects 1 product. | Package | Ecosystem | Affected | Fixed in | | --- | --- | --- | --- | | `azure-cli` | Bitnami | All versions | 2.69.0 | | `azure-cli-core` | SUSE:Linux Enterprise Module for Public Cloud 12 | All versions | 2.17.1-2.25.1 | | `azure-cli-core` | SUSE:Linux Enterprise Module for Public Cloud 15 SP3 | All versions | 2.36.0-150200.9.6.1 | | `azure-cli-core` | SUSE:Linux Enterprise Module for Public Cloud 15 SP4 | All versions | 2.58.0-150400.14.6.1 | | `azure-cli-core` | SUSE:Linux Enterprise Module for Public Cloud 15 SP5 | All versions | 2.58.0-150400.14.6.1 | | `azure-cli-core` | SUSE:Linux Enterprise Module for Public Cloud 15 SP6 | All versions | 2.58.0-150400.14.6.1 | | `azure-cli-core` | openSUSE:Leap 15.6 | All versions | 2.58.0-150400.14.6.1 | | `azure-cli-core` | openSUSE:Tumbleweed | All versions | 2.83.0-2.1 | Products: Microsoft Azure Command-Line Interface. ## How do I fix CVE-2025-24049? Upgrade azure-cli to 2.69.0 or later. ## Is CVE-2025-24049 being exploited? There is no known exploitation of CVE-2025-24049 in the wild and no public exploit code. ## Other vulnerabilities in Microsoft Azure CLI - [CVE-2024-43591](https://insights.sbomify.com/CVE-2024-43591/): Azure Command Line Integration (CLI) Elevation of Privilege Vulnerability (high 8.7) - [CVE-2023-36052](https://insights.sbomify.com/CVE-2023-36052/): Azure CLI REST Command Information Disclosure Vulnerability (high 8.6) - [CVE-2022-39327](https://insights.sbomify.com/CVE-2022-39327/): Improper Control of Generation of Code ('Code Injection') in Azure CLI (high 8.1) ## Fix prompt for AI coding agents ```text Check this codebase for CVE-2025-24049 and fix it if it is affected. What it is: CVE-2025-24049 is a high-severity command injection vulnerability in Microsoft Azure CLI, published on 11 Mar 2025. 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-2025-24049 in the wild and no public exploit code. Affected packages and fixed versions: - azure-cli (Bitnami): affected all versions; fixed in 2.69.0 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-2025-24049/ (Markdown: https://insights.sbomify.com/CVE-2025-24049/index.md) ``` ## Sources - CVE record: https://www.cve.org/CVERecord?id=CVE-2025-24049 - NVD: https://nvd.nist.gov/vuln/detail/CVE-2025-24049 - OSV: https://osv.dev/vulnerability/CVE-2025-24049 --- From sbomify Insights: https://insights.sbomify.com/CVE-2025-24049/ Summaries are generated and may contain mistakes; the official description above is the record.