Verified reference description
The following technical description is credited to the CISA KEV dataset (CC0):
Broadcom VMware vCenter contains a path traversal vulnerability which could allow a threat actor with network access to vCenter to execute arbitrary code.
Record and timeline
- Product: Broadcom — VMware vCenter
- Identifier: CVE-2026-59310
- CVE record published: 2026-07-30
- Added to CISA KEV: 2026-08-18
- Reference score: 9.8/10, CVSS 3.1; provider: vmware
- Weakness class: CWE-22
A KEV addition date is not a discovery date. CVSS describes technical severity; actual exposure and asset importance also influence remediation priority.
Defensive next steps
Match the installed Broadcom VMware vCenter version and configuration against the linked technical advisory. Apply the manufacturer-approved fixed release or an explicitly documented mitigation; this profile does not guess a fixed version. Verify the patch and review relevant logs afterward. Plan a supported replacement where the product is end-of-life.
Scope and limitations
This is an awareness and defensive-prioritization profile, not a penetration test or a finding that your network is compromised. KEV membership indicates evidence of real-world exploitation. Mandatory CISA deadlines apply to entities covered by the relevant directive, not universally to every reader.
Reported versions and platforms
The table shows up to ten structured version entries from the official CVE-2026-59310 record. Original field names and values are retained deliberately. This is not an automated exposure verdict or a complete list of every product branch; use the full record and vendor advisory for a deployment decision.
| Product in record | Platform | Version fields — original values | Record status |
|---|---|---|---|
| VMware — Cloud Foundation | — | version=9.1.x.x | affected |
| VMware — Cloud Foundation | — | version=9.0.x.x | affected |
| VMware — Cloud Foundation | — | version=5.x | affected |
| VMware — vSphere Foundation | — | version=9.1.x.x | affected |
| VMware — vSphere Foundation | — | version=9.0.x.x | affected |
| VMware — vCenter | — | version=9.1.x.x; lessThan=9.1.0.0300; versionType=custom | affected |
| VMware — vCenter | — | version=9.0.x.x; lessThan=9.0.2.0100; versionType=custom | affected |
| VMware — vCenter | — | version=8.0; lessThan=8.0 U3k; versionType=custom | affected |
| VMware — Telco Cloud Infrastructure | — | version=3.0 | affected |
| VMware — Telco Cloud Platform | — | version=5.1.x | affected |
Full record and technical references
Turn the record into an operational decision
For Broadcom VMware vCenter, record the asset, effective version, enabled feature and access path. When the reference does not map clearly to your package or branch, retain an explicit unknown status and assign follow-up rather than guessing that the system is safe.
After remediation, record the effective running version, health-check outcome and change time, not merely installation success. Evidence of compromise requires the appropriate incident-response workflow; this page does not diagnose any network as compromised or clean.
Scoring vector and scope
Vector recorded by the reference: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
CVSS is owned by FIRST and used by permission. The reference score is not a substitute for organizational risk assessment. Version data comes from the record retrieved for this review and may change when sources are updated.
