CVE-2026-123892: VMware SDDC Manager · OS Command Injection
Affects VMware SDDC ManagerSource CVE Database V5
Not known to be exploited · CVSS 7.2 High · fixed in 9.1.1.0200 : patch VMware SDDC Manager soon.
Data as of 19 Nov 2026, 14:21 UTC
Thin evidence
One scorer or none| CNA (vmware) | CVSS 3.1 | 7.2 |
|---|
- Patch
- Available – fixed in 9.1.1.0200, 9.0.2.0100, 5.2.5
CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:HExploitation evidence
Disclosed: evidence found.
CVE published 19 Nov 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 18 Nov 2026.
What to do
Upgrade VMware SDDC Manager to 9.1.1.0200, 9.0.2.0100 or 5.2.5.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| VMwareSDDC Manager | Affected
| Fixed in
|
| VMwareSDDC Manager | Affected
| Fixed in
|
| VMwareSDDC Manager | Affected
| Fixed in
|
AI-suggested
Apply the official patches provided by VMware by upgrading affected SDDC Manager versions to 5.2.5, 9.0.2.0100, or 9.1.1.0200 or later. No other mitigations are specified. Since this is an authenticated vulnerability, restricting access to trusted users and enforcing strong authentication controls can reduce risk until patching is complete.
Description
CVE-2026-123892 is an authenticated OS command injection vulnerability in VMware SDDC Manager caused by improper sanitization of user-supplied input. It affects versions 5.x, 9.0.x.x, and 9.1.x.x prior to fixed releases. The flaw allows an attacker with authenticated access to execute arbitrary OS commands, potentially leading to full system compromise. VMware has released patches in versions 5.2.5, 9.0.2.0100, and 9.1.1.0200 to address this issue.