CVE-2025-0119
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedA command injection vulnerability in the Palo Alto Networks Cortex XDR® Broker VM allows an authenticated user to execute arbitrary OS commands with root privileges on the host operating system running Broker VM.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · moderate confidenceCVE-2025-0119 is a command injection vulnerability in Palo Alto Networks Cortex XDR Broker VM that allows an authenticated user to execute arbitrary operating system commands with root privileges on the host running the Broker VM. The vulnerability stems from improper input validation in the Broker VM's command processing logic, enabling malicious actors to escape intended command boundaries and execute OS-level commands outside the sandboxed environment.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Local
- Complexity
- Low
- Privileges
- Low
- Authentication
- None
- User interaction
- None
- Scope
- X
CVSS:4.0/AV:L/AC:L/AT:N/PR:L/UI:N/VC:L/VI:L/VA:L/SC:H/SI:H/SA:H/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:N/R:U/V:D/RE:M/U:Amber
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Confirm Cortex XDR Broker VM is installedIdentify the Broker VM installation on the host. Check for PAN software directories, services, or the management interface. On Linux, look for /opt/paloaltonetworks/ or systemctl status for broker-vm related services.Affected if Cortex XDR Broker VM software is present on the host
-
Determine installed Broker VM versionRun the appropriate command to retrieve the Broker VM version. On Linux, check /opt/paloaltonetworks/cortex_xdr/broker_vm_version or use the management CLI tool if available: 'broker-vm --version' or inspect the RPM/DEB package version.Affected if Installed version is lower than the patched version (the vendor has released a fix; compare against their published fixed version)
-
Verify authenticated access to Broker VM managementConfirm that the Broker VM management interface or API is accessible. Check if user authentication is enabled and review the list of users with Broker VM administrative or operator privileges.Affected if The management interface is exposed and user accounts exist with permission to execute Broker VM commands
-
Inspect for anomalous command executionReview system audit logs, Broker VM logs, and host-level process accounting for unexpected commands spawned from the Broker VM process. Look for commands running as root from the broker-vm service account that were not initiated by expected administrative tasks.Affected if Root-level commands appear in logs that were not initiated by legitimate administrative actions or scheduled tasks
A user is affected if Cortex XDR Broker VM is installed and the installed version falls below the vendor's fixed version, particularly if the management interface is accessible to authenticated users.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
From vendor dataApply the vendor patch when available; in the interim, strictly limit Broker VM access to trusted personnel only, enable enhanced audit logging for administrative actions, and consider network segmentation to reduce the attack surface.
- Consultation4.0 h
- Implementation16.0 h
- Testing8.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $8,960.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-0119 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2025-0119 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data