# CVE-2026-0276: Cortex XDR Broker VM: Privilege Escalation (PE) Vulnerability

> A local authenticated user can escalate privileges to root in Palo Alto Networks Cortex XDR Broker VM.

- **Severity:** Low 1.1 (`CVSS:4.0/AV:L/AC:L/AT:N/PR:L/UI:N/VC:L/VI:L/VA:L/SC:N/SI:N/SA:N/E:U/AU:N/R:U/V:D/RE:M/U:Amber`)
- **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 Jul 2026
- **Updated:** 14 Jul 2026
- **Also known as:** GHSA-8fv5-24p8-44h5

## What is CVE-2026-0276?

CVE-2026-0276 is a low-severity vulnerability in Palo Alto Networks Cortex XDR Broker VM, published on 9 Jul 2026. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

A privilege escalation vulnerability in Palo Alto Networks Cortex® XDR Broker VM enables a locally authenticated user to perform actions as the root user.

Weakness: CWE-269 (Improper Privilege Management)

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

It affects 1 product.


Products: Paloaltonetworks Cortex Xdr Broker Vm.

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

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

## Is CVE-2026-0276 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-0276 is a low-severity vulnerability in Palo Alto Networks Cortex XDR Broker VM, published on 9 Jul 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-0276 in the wild and no public exploit code.

Affected product: Palo Alto Networks Cortex XDR Broker VM. 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-0276/ (Markdown: https://insights.sbomify.com/CVE-2026-0276/index.md)
```

## Sources

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

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