# CVE-2025-2184: Cortex XDR Broker VM: Secrets Shared Across Multiple Broker VM Images

> Attackers with network access can use shared default credentials to access internal services on other Broker VM installations.

- **Severity:** Medium 5.3 (`CVSS:4.0/AV:P/AC:L/AT:P/PR:N/UI:N/VC:H/VI:H/VA:N/SC:N/SI:N/SA:N/AU:Y/R:U/V:C/RE:M/U:Amber`)
- **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:** 13 Aug 2025
- **Updated:** 13 Aug 2025
- **Also known as:** GHSA-5vh9-rp4f-879m

## What is CVE-2025-2184?

CVE-2025-2184 is a medium-severity vulnerability in Palo Alto Networks Cortex XDR Broker VM, published on 13 Aug 2025. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

A credential management flaw in Palo Alto Networks Cortex XDR® Broker VM causes different Broker VM images to share identical default credentials for internal services. Users knowing these default credentials could access internal services on other Broker VM installations.

The attacker must have network access to the Broker VM to exploit this issue.

Weakness: CWE-1392 (Use of Default Credentials)

## Which versions are affected by CVE-2025-2184?


## How do I fix CVE-2025-2184?

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

## Is CVE-2025-2184 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2025-2184 and fix it if it is affected.

What it is: CVE-2025-2184 is a medium-severity vulnerability in Palo Alto Networks Cortex XDR Broker VM, published on 13 Aug 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-2184 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-2025-2184/ (Markdown: https://insights.sbomify.com/CVE-2025-2184/index.md)
```

## Sources

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

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