Skip to main content
株式会社オブライト
株式会社オブライト

VMware vCenter CVE-2026-123890 + 11 more

Vulnerability Digest Nov 20, 2026

Published 2026/11/2012 min read

vCenter auth bypass CVE-2026-123890 (CVSS 9.8) has no workaround and is exploited, per Mandiant. Update now. PHP fixes seven Critical flaws in four releases.

From the information published on November 19-20, we picked the items most relevant to small and midsize business systems. The top priority is the VMware vCenter authentication bypass (CVE-2026-123890). Broadcom rates it CVSS v3.1 9.8 (Critical). An attacker who can reach vCenter over the network may gain administrator access without authenticating, and no workaround is provided. Broadcom does not say it has confirmed exploitation, but Google's Mandiant and GTIG report that a suspected China-linked group (ARMORY CASTLE, formerly UNC5221) had been exploiting the flaw since early September. If you use vCenter, updating to a fixed version (9.1.1.0200, 9.0.2.0200 or 8.0 U3m) is the top priority. Limiting management traffic to a small set of internal machines also helps.

On the same day, PHP released 8.5.13, 8.4.28, 8.3.37 and 8.2.36. They include seven Critical flaws (CVSS v4.0 9.2) that may allow remote code execution through session handling and PHP-FPM. Most require specific settings or a usable gadget chain in the application. The same VMware advisory (VMSA-2026-0009) also covers three SDDC Manager flaws and one VMware Tools for Windows flaw. In this digest, "exploitation confirmed" means a listing in CISA's KEV catalog, or a vendor or primary source that explicitly states exploitation. Today's confirmed exploitation count is one (vCenter, reported by Mandiant and GTIG). As for KEV, the CISA data I could access was current only to the November 18 update, so I could not verify whether vCenter has been listed.

Today's vulnerability list

ProductCVESeverity (CVSS)ExploitationFix (patched version)
VMware vCenter (Directory Service)CVE-2026-1238909.8 (v3.1, Broadcom/NVD)Exploitation confirmed (Mandiant/GTIG report attacks since early September; Broadcom does not state it)9.1.1.0200 / 9.0.2.0200 / 8.0 U3m / VCF 5.2.5. No workaround
VMware SDDC Manager (SQL injection)CVE-2026-1238918.1 (v3.1, Broadcom)No reports9.1.1.0200 / 9.0.2.0100 / 5.2.5
VMware SDDC Manager (command injection)CVE-2026-1238927.2 (v3.1, Broadcom)No reportsSame as above
VMware SDDC Manager (privilege escalation)CVE-2026-1238936.7 (v3.1, Broadcom)No reportsSame as above
VMware Tools for WindowsCVE-2026-1238946.7 (v3.1, Broadcom)No reports13.1.5.0 (13.x) / 12.5.5 (12.x line)
PHP (session: serializer mismatch)CVE-2026-1155609.2 (v4.0, PHP team)No reports8.5.13 / 8.4.28 / 8.3.37 / 8.2.36
PHP (session: corrupted file)CVE-2026-1267149.2 (v4.0)No reportsSame as above
PHP (timezone cache)CVE-2026-1294969.2 (v4.0)No reportsSame as above
PHP (PHP-FPM request smuggling)CVE-2026-1292899.2 (v4.0)No reportsSame as above
PHP (session shutdown)CVE-2026-1294819.2 (v4.0)No reports8.5.13 / 8.4.28 / 8.3.37 (8.2 not affected)
PHP 8.5 (magic method backtrace)CVE-2026-1294749.2 (v4.0)No reports8.5.13 (8.5 only)
PHP 8.5 (fatal error backtrace)CVE-2026-1291829.2 (v4.0)No reports8.5.13 (8.5 only)

VMware vCenter CVE-2026-123890: administrator access without authentication, exploited as a zero-day

What happens. vCenter is the management server that controls multiple virtual servers (ESXi hosts). Its authentication and directory function (VMware Directory Service) has an authentication bypass, so an attacker with network access may obtain administrator rights. Broadcom says the flaw applies whether or not Enhanced Linked Mode is enabled. In Mandiant's analysis, the attacker obtained an authenticated session as the SSO administrator (administrator@vsphere.local). It is a different flaw from CVE-2026-59309, another authentication bypass disclosed in July.

Severity, affected and fixed versions. Broadcom and NVD rate it CVSS v3.1 9.8 (Critical). According to NVD, vCenter 9.1.x is fixed in 9.1.1.0200, 9.0.x in 9.0.2.0200, 8.0 in 8.0 U3m, and VMware Cloud Foundation (VCF) 5.x in 5.2.5. Telco Cloud Platform and Telco Cloud Infrastructure are also affected; see KB463116. For vCenter 7.0, Broadcom tells customers with an extended support contract to contact Broadcom Support.

Exploitation. Broadcom's advisory does not state that attacks were confirmed. In its November 20 report, however, Google's Mandiant and GTIG say ARMORY CASTLE had used the flaw since early September. The attacker first got in through a BeyondTrust Remote Support zero-day (CVE-2026-102764) and reached vCenter from an internal Linux appliance. Using a custom tool called BONESAW, they reportedly created an SSO administrator, stole the credential database and the SAML signing key, and extracted Active Directory data from virtual machines on ESXi. Mandiant says the intrusion hit a vCenter already patched against the flaw fixed in July (CVE-2026-59309), suggesting the group knew of this flaw in advance.

What to do today. (1) Check your vCenter version and update to a fixed version above. Broadcom says the update does not affect running virtual machines; the vSphere Client and some operations are briefly unavailable. vCenter Quick Patch cannot be used. (2) Limit access to the vCenter management console and management ports (443, 2012, 22, 5480 and others) to internal admin machines only. Mandiant has published the VCSA Hardening & Logging Tool, which helps block these ports by default. (3) Check whether you were already compromised. Updating does not remove administrator accounts that were already created or keys that were already stolen. Ask your contractor to look for suspicious SSO administrator additions, SSH being enabled, and unusual outbound traffic. Mandiant's report includes detection rules and indicators of compromise (IOCs).

Caution. According to Broadcom's Q&A, applying vCenter 8.0 U3m or 9.0.2.0200 blocks upgrades to VCF 9.1.1; Broadcom advises waiting for VCF 9.1.2. If you run VCF, review the advisory before planning.

Four more in the same advisory: three in SDDC Manager, one in VMware Tools for Windows

VMSA-2026-0009 includes four more issues besides vCenter. Broadcom rates them Important or Moderate, and all require an authenticated user or administrator. None of the sources I consulted reports exploitation. If you do not use SDDC Manager, the VMware Cloud Foundation management tool, the three SDDC Manager flaws do not apply.

The three SDDC Manager flaws. CVE-2026-123891 is SQL injection that lets an authenticated attacker read and write the database (CVSS 8.1). CVE-2026-123892 is authenticated command injection that runs arbitrary commands on the appliance (7.2). CVE-2026-123893 is a local privilege escalation in which an administrator can reach root (6.7). Fixed versions are 9.1.1.0200 for 9.1.x, 9.0.2.0100 for 9.0.x, and 5.2.5 for 5.x. 9.1.1.0200 is described as the latest release covering all three.

CVE-2026-123894 in VMware Tools for Windows (CVSS 6.7). A SAML token signature check can be bypassed, so an attacker with a privileged local process in a Windows virtual machine that uses guest alias mapping may escalate privileges. Fixed versions are 13.1.5.0 for 13.x and 12.5.5 for the 12.x line (12.3 to 12.5); 12.4.10 covers 32-bit Windows. Broadcom says disabling guest operations does not protect against it, and stopping or uninstalling VMware Tools is not a workaround because it also disables time sync, guest shutdown and similar functions. You can check guest alias settings by running VGAuthCLI.exe list inside the virtual machine. ESX, NSX, VCF Operations and others are not affected by this advisory. None of these issues allow VM escape to the ESX host.

# Check guest alias settings inside a Windows virtual machine (method described in Broadcom's Q&A)
VGAuthCLI.exe list

PHP 8.5.13 / 8.4.28 / 8.3.37 / 8.2.36: security release with seven Critical fixes

What happens. The PHP team released updates for four release lines on November 19. Seven flaws are rated Critical in the official GitHub security advisories (GHSA), all CVSS v4.0 9.2. Each depends on specific settings or on a usable gadget chain in the application. The conditions are as follows.

- CVE-2026-115560 (session): session upload progress is enabled and the session serializers do not match. If the application has a usable gadget chain, code runs with the PHP worker's privileges.
- CVE-2026-126714 (session): with PHP's default file-based session storage, an interrupted write can leave a file mixing old and new data, which is then loaded. This also requires a gadget chain in the application.
- CVE-2026-129496 (date): on a non-thread-safe PHP build, when a startup error is written to a file-based log, freed memory is accessed. A mistake in date.timezone in php.ini can be a trigger.
- CVE-2026-129289 (PHP-FPM): if a connection is reused without reading the whole request body, attacker data may be treated as a separate FastCGI request, bypassing front-end routing and authentication and executing code.
- CVE-2026-129481 (session, 8.3 and later): after session shutdown is interrupted, the next request in the same worker handles a freed string.
- CVE-2026-129474 (8.5 only): with fatal_error_backtraces=1 and zend.exception_ignore_args=0, a backtrace taken around a magic method (such as __call) accesses freed memory. PHP 8.5 enables the former by default, but php.ini-production sets the latter to 1, which blocks this path.
- CVE-2026-129182 (8.5 only): an incomplete fix from last month; in certain configuration combinations a fatal error backtrace persists and is referenced by the next request after being freed.

Affected and fixed versions. The fixed versions are 8.5.13, 8.4.28, 8.3.37 and 8.2.36. According to the GHSA affected ranges, versions before 8.2 are also affected by many of the flaws above, and several fall within the 8.1 range. 8.1 and earlier are no longer officially supported and will not get fixes, so migrating to 8.2 or later is required. The same release also contains many non-Critical fixes, including a PHP-FPM local privilege escalation (CVE-2026-129291, CVSS v4.0 8.8) and a PHAR signature verification bypass (CVE-2026-128090, 7.7).

Exploitation. The sources I consulted do not describe exploitation in the wild. Still, details of many of the flaws are public, so it is safer not to delay. PHP provided by OS distributions such as Ubuntu, Debian and RHEL, or by rental servers, may be fixed under different version numbers. Check your provider's or distribution's information.

# Check the PHP version
php -v

# Check settings related to CVE-2026-129474 on PHP 8.5
php -i | grep -E 'fatal_error_backtraces|exception_ignore_args'

Checklist for non-IT staff: what to do today

- Ask your IT contact or maintenance vendor whether you have a VMware (vSphere, vCenter) virtualization platform. If not, record "not applicable" and you are done
- If you have vCenter, ask for an update today to 9.1.1.0200, 9.0.2.0200 or 8.0 U3m or later (5.2.5 for VCF 5.x). There is no workaround
- At the same time, ask for the vCenter management console to be restricted to a small set of internal machines, and confirm it is not reachable from the internet
- After the update, ask for a check for prior compromise (suspicious SSO administrator additions, SSH enabled, unusual outbound traffic)
- Ask for version checks on VMware Cloud Foundation's SDDC Manager and on VMware Tools in Windows virtual machines
- Ask your developer whether your website or business systems run on PHP, and whether the version is 8.5.13, 8.4.28, 8.3.37 or 8.2.36 or later
- If you run PHP 8.1 or earlier, no fix will be released, so discuss a migration plan
- If you use a rental server, check your provider's PHP update notice

Related articles

Preparation for vulnerabilities is summarized in Vulnerability assessment costs and how to choose. For the previous day, see the November 19 vulnerability digest (nginx and more).

Sources

- Broadcom VMSA-2026-0009: https://support.broadcom.com/web/ecx/support-content-notification/-/external/content/SecurityAdvisories/0/39495
- Broadcom VMSA-2026-0009 Q&A: https://github.com/vmware/vcf-security-and-compliance-guidelines/blob/main/security-advisories/vmsa-2026-0009/README.md
- NVD CVE-2026-123890: https://nvd.nist.gov/vuln/detail/CVE-2026-123890
- Google Cloud (Mandiant/GTIG) ARMORY CASTLE exploits vSphere: https://cloud.google.com/blog/topics/threat-intelligence/armory-castle-exploits-vsphere
- Broadcom VMSA-2026-0006 (CVE-2026-59309): https://support.broadcom.com/web/ecx/support-content-notification/-/external/content/SecurityAdvisories/0/38017
- PHP 8 ChangeLog: https://www.php.net/ChangeLog-8.php
- PHP GHSA-658j-r8rw-q6mx (CVE-2026-115560): https://github.com/php/php-src/security/advisories/GHSA-658j-r8rw-q6mx
- PHP GHSA-fm2m-fjf5-v3cp (CVE-2026-126714): https://github.com/php/php-src/security/advisories/GHSA-fm2m-fjf5-v3cp
- PHP GHSA-gr4f-wgx5-jpfv (CVE-2026-129496): https://github.com/php/php-src/security/advisories/GHSA-gr4f-wgx5-jpfv
- PHP GHSA-qc49-hpvq-g2w6 (CVE-2026-129289): https://github.com/php/php-src/security/advisories/GHSA-qc49-hpvq-g2w6
- PHP GHSA-g3vh-838c-65v7 (CVE-2026-129481): https://github.com/php/php-src/security/advisories/GHSA-g3vh-838c-65v7
- PHP GHSA-8mjj-2r7p-4hg2 (CVE-2026-129474): https://github.com/php/php-src/security/advisories/GHSA-8mjj-2r7p-4hg2
- PHP GHSA-2fjv-p558-g82m (CVE-2026-129182): https://github.com/php/php-src/security/advisories/GHSA-2fjv-p558-g82m
- CISA KEV catalog: https://www.cisa.gov/known-exploited-vulnerabilities-catalog

FAQ

Can I update vCenter without stopping virtual machines?

Broadcom says a vCenter update does not affect running workloads (virtual machines); the vSphere Client and some encryption operations are briefly unavailable. vCenter Quick Patch is not eligible, so the normal update procedure is required. Schedule it with your contractor or maintenance vendor.

If vCenter is not exposed to the internet, can I wait?

No. The flaw affects attackers who can reach vCenter over the network, and in Mandiant's report an attacker who entered through another appliance (BeyondTrust remote support) used an internal machine as a foothold to reach vCenter. Even if it is not directly visible from outside, compromise of another internal device is enough. With no workaround, it is safest to update and restrict management traffic at the same time.

If I update, am I safe even if I was already compromised?

No. The update stops new attacks, but administrator accounts already created and signing keys or credentials already stolen remain. Mandiant reports that a stolen signing key can be used to forge authentication tokens. After updating, review the history of suspicious account additions and SSH being enabled, and discuss replacing keys and credentials with a specialist if needed.

Are the seven Critical PHP flaws dangerous for every PHP user?

No. Most require conditions such as session upload progress being enabled, a usable gadget chain in the application, a specific error configuration, or PHP-FPM being in use. Because it is hard to check all conditions yourself, updating to 8.5.13, 8.4.28, 8.3.37 or 8.2.36 is the reliable approach.

I run PHP 8.1. What should I do?

8.1 is no longer officially supported and no fixed version was released for it. The GHSA affected ranges include 8.1 for some flaws. Migrating to 8.2 or later is the basic answer. If you cannot migrate right away, ask your developer or hosting provider whether the distribution has shipped its own fixes.

株式会社オブライト

Oflight Inc. is a Tokyo-based IT company providing software development, digital signage, web development, network systems, and IoT/AR/VR technology services.

Feel free to contact us

Contact Us