CVE-2026-0231

MEDIUMPre-NVD 5.75.7—
EchelonGraph scoreMEDIUM confidence

This medium-severity CVE scores 5.7 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.2%, top 93% of all CVEs by exploit prediction. GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).

Triggered by: NVD CVSS baseline
Sources: epss, secondary
5.7EG
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 5.7Exploit: None knownExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

An information disclosure vulnerability in Palo Alto Networks Cortex XDR® Broker VM allows an authenticated user to obtain and modify sensitive information by triggering live terminal session via Cortex UI and modifying any configuration setting.  The attacker must have network access to the Broker VM to exploit this issue.

CVSS v3
5.7
EG Score
5.7(medium)
EG Risk
30(Track)
EG Risk 30/100SSVC: Track

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity57% × 45%
Exploitation0% × 40%
Automatability30% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
7%
KEV
Not listed

Published

March 11, 2026

Last Modified

June 17, 2026

Advisory Details (1)

Auto-updated Aug 4, 2026
No patch confirmed yet.
generic

CVE-2026-0231 Cortex XDR Broker VM: Sensitive Information Disclosure Vulnerability

https://security.paloaltonetworks.com/CVE-2026-0231

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 3× in last 7d / 19× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

  1. 2026-09-18 19:27 UTCEPSS rescore
  2. 2026-09-16 05:14 UTCEPSS rescore
  3. 2026-09-13 16:46 UTCEPSS rescore
  4. 2026-09-12 15:00 UTCEPSS rescore
  5. 2026-09-11 09:36 UTCEPSS rescore
  6. 2026-09-10 09:34 UTCEPSS rescore
  7. 2026-09-08 22:00 UTCEPSS rescore
  8. 2026-09-07 16:01 UTCEPSS rescore
  9. 2026-09-06 13:47 UTCEPSS rescore
  10. 2026-09-04 05:06 UTCEPSS rescore
  11. 2026-09-02 14:11 UTCEPSS rescore
  12. 2026-09-01 13:53 UTCEPSS rescore
  13. 2026-08-30 19:17 UTCEPSS rescore
  14. 2026-08-28 21:40 UTCEPSS rescore
  15. 2026-08-27 14:24 UTCEPSS rescore
  16. 2026-08-25 13:48 UTCEPSS rescore
  17. 2026-08-23 00:19 UTCEPSS rescore
  18. 2026-08-21 23:48 UTCEPSS rescore
  19. 2026-08-20 22:55 UTCEPSS rescore
  20. 2026-08-19 17:03 UTCEPSS rescore
  21. 2026-08-18 13:48 UTCEPSS rescore
  22. 2026-08-16 14:56 UTCEPSS rescore
  23. 2026-08-16 11:52 UTCEG score recompute
  24. 2026-08-16 11:52 UTCGHSA enrichment
  25. 2026-08-16 02:14 UTCEPSS rescore
Show 38 more
  1. 2026-08-15 01:30 UTCEPSS rescore
  2. 2026-08-14 07:50 UTCEG score recompute
  3. 2026-08-14 07:50 UTCGHSA enrichment
  4. 2026-08-13 22:00 UTCEPSS rescore
  5. 2026-08-12 23:01 UTCEG score recompute
  6. 2026-08-12 23:01 UTCGHSA enrichment
  7. 2026-08-12 13:50 UTCEPSS rescore
  8. 2026-08-11 21:51 UTCEG score recompute
  9. 2026-08-11 21:51 UTCGHSA enrichment
  10. 2026-08-11 13:42 UTCEPSS rescore
  11. 2026-08-10 23:59 UTCEPSS rescore
  12. 2026-08-10 08:27 UTCEG score recompute
  13. 2026-08-10 08:27 UTCGHSA enrichment
  14. 2026-08-09 13:46 UTCEPSS rescore
  15. 2026-08-09 07:31 UTCEG score recompute
  16. 2026-08-09 07:31 UTCGHSA enrichment
  17. 2026-08-08 16:37 UTCEPSS rescore
  18. 2026-08-07 18:17 UTCEG score recompute
  19. 2026-08-07 18:17 UTCGHSA enrichment
  20. 2026-08-06 13:46 UTCEPSS rescore
  21. 2026-08-06 02:03 UTCEG score recompute
  22. 2026-08-06 02:03 UTCGHSA enrichment
  23. 2026-08-05 19:17 UTCEPSS rescore
  24. 2026-08-04 15:09 UTCEPSS rescore
  25. 2026-08-04 10:38 UTCEPSS rescore
  26. 2026-08-04 01:21 UTCEG score recompute
  27. 2026-08-04 01:21 UTCGHSA enrichment
  28. 2026-08-03 10:35 UTCEPSS rescore
  29. 2026-08-02 17:36 UTCEG score recompute
  30. 2026-08-02 17:36 UTCGHSA enrichment
  31. 2026-08-02 02:26 UTCEPSS rescore
  32. 2026-08-01 04:15 UTCEPSS rescore
  33. 2026-07-30 16:27 UTCEPSS rescore
  34. 2026-07-30 01:30 UTCEPSS rescore
  35. 2026-07-28 15:36 UTCEPSS rescore
  36. 2026-07-27 14:13 UTCEPSS rescore
  37. 2026-07-27 13:42 UTCEG score recompute
  38. 2026-07-27 13:41 UTCGHSA enrichment

Frequently asked(5)

What is CVE-2026-0231?
CVE-2026-0231 is a medium vulnerability published on March 11, 2026. An information disclosure vulnerability in Palo Alto Networks Cortex XDR® Broker VM allows an authenticated user to obtain and modify sensitive information by triggering live terminal session via Cortex UI and modifying any configuration setting. The attacker must have network access to the Broker…
When was CVE-2026-0231 disclosed?
CVE-2026-0231 was first published in the National Vulnerability Database on March 11, 2026, with the most recent update on June 17, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-0231 actively exploited?
CVE-2026-0231 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0% probability of exploitation in the next 30 days, which ranks it in the top 93.2% of all scored CVEs.
What is the CVSS score of CVE-2026-0231?
CVE-2026-0231 has a CVSS v3 base score of 5.7 (NVD).
How do I remediate CVE-2026-0231?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-0231, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2026-0231

Explore →

Is Your Infrastructure Affected by CVE-2026-0231?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Start Free Scan →Browse All CVEs