# CVE-2022-33646: Azure Batch Node Agent Elevation of Privilege Vulnerability

> An attacker can exploit the Azure Batch Node Agent to escalate privileges within the cloud environment.

- **Severity:** High 7.0 (`CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H/E:P/RL:O/RC:C`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 9 Aug 2022
- **Updated:** 5 Jun 2025
- **Also known as:** GHSA-cjxf-hqc4-wp33

## What is CVE-2022-33646?

CVE-2022-33646 is a high-severity vulnerability in Microsoft Azure Batch, published on 9 Aug 2022. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

Azure Batch Node Agent Elevation of Privilege Vulnerability

Weakness: CWE-269 (Improper Privilege Management)

## Which versions are affected by CVE-2022-33646?

It affects 1 product.


Products: Microsoft Azure Batch.

## How do I fix CVE-2022-33646?

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

## Is CVE-2022-33646 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2022-33646 and fix it if it is affected.

What it is: CVE-2022-33646 is a high-severity vulnerability in Microsoft Azure Batch, published on 9 Aug 2022. 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-2022-33646 in the wild and no public exploit code.

Affected product: Microsoft Azure Batch. 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-2022-33646/ (Markdown: https://insights.sbomify.com/CVE-2022-33646/index.md)
```

## Sources

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

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