Integrity compromise via unvalidated certificate and key fields
Published May 13, 2026 · Updated May 13, 2026
Improper input validation in Palo Alto Networks Cortex XDR Broker VM before 30.0.24 allows attackers to inject arbitrary field content. The certificate and private-key fields accept arbitrary content without sufficient validation; no more specific code locus is publicly disclosed. Exploitation requires authenticated administrator access and can alter Broker VM or subsequent-system integrity, without confidentiality or availability impact.
Summary
What happened
Improper input validation in Palo Alto Networks Cortex XDR Broker VM before 30.0.24 allows attackers to inject arbitrary field content. The certificate and private-key fields accept arbitrary content without sufficient validation; no more specific code locus is publicly disclosed. Exploitation requires authenticated administrator access and can alter Broker VM or subsequent-system integrity, without confidentiality or availability impact.
The record
- CVE
- CVE-2026-0238
- Published
- May 13, 2026
- Updated
- May 13, 2026
- Vendor
- Palo Alto Networks
- Product
- Cortex XDR Broker VM
- Classifications
- CWE-20, CAPEC-153, T1565.002
- Attack vector
- local
- Privileges
- admin
Timeline
How it unfolded
- May 13, 2026CVE publishedPublication date reported by the CVE source.
- May 13, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=30.0 <30.0.24 changes=[{"at":"30.0.24","status":"unaffected"}]
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo