Skip to content
eastbaycyber

Cybersecurity Threat Digest November 20, 2026: vCenter Zero-Day

Threat digests 9 min read
EC
East Bay Cyber Editorial Team Updated
Week of 20 NOV 2026

TL;DR - A critical VMware vCenter authentication bypass was reportedly exploited in attacks since September. - Patch vCenter, F5 BIG-IP, and PHP; investigate exposed management systems and service dependencies. - Treat virtualization and internet-facing infrastructure as urgent priorities today.

Top Stories#

VMware vCenter zero-day reportedly exploited

Broadcom released updates for CVE-2026-123890, a critical authentication-bypass vulnerability in VMware vCenter Server’s VMware Directory Service. The issue carries a CVSS score of 9.8 and was reportedly exploited in zero-day attacks beginning in September 2026.

Prioritize vCenter systems that expose management interfaces to the internet, contain sensitive virtual infrastructure, or provide access to high-value administrative networks. See our CVE-2026-13019 vulnerability coverage for related vulnerability-response guidance.

F5 issues emergency BIG-IP updates

F5 released emergency patches for five critical BIG-IP vulnerabilities that may allow denial of service or remote code execution, according to reporting from BleepingComputer.

Patch affected appliances promptly and restrict BIG-IP management interfaces to trusted administrative networks. Internet exposure, weak administrative controls, and unmonitored management access can increase the impact of appliance vulnerabilities.

N-able breach caused a major service outage

N-able said attackers breached a server and caused a major outage affecting Mail Assure and SpamExperts Hosted Cloud services worldwide.

Managed service providers and organizations using these platforms should validate mail-flow continuity, review provider communications, and confirm whether backup routing or alternate filtering is available. The incident also shows the concentration risk created when critical security and messaging functions depend on a single external provider.

USDA outage follows reported cybersecurity incident

The U.S. Department of Agriculture experienced an outage following a reported cybersecurity incident. Available reporting does not establish the full scope or technical cause, so service disruption alone does not confirm data theft.

The incident raises operational-resilience concerns across government and other critical services. Agencies and regulated organizations should review continuity plans for prolonged identity, application, network, and external-service outages.

SBC Medical Group reports exposure affecting 1.6 million people

SBC Medical Group reported that two cybersecurity incidents exposed sensitive information involving approximately 1.6 million customers and employees.

The organization should be treated as a significant breach-response case for affected individuals and partners. Other healthcare organizations should review identity stores, third-party access, data retention, and monitoring for unusual bulk access to customer and employee records.

Transport for London discloses Oyster data exposure

Transport for London said approximately 265,000 Oyster photocard customers may have had account details exposed.

Transportation providers should review the protection of customer portals, identity data, application programming interfaces, and third-party integrations. Customers should be notified through trusted channels and advised to be cautious about targeted phishing using transit-account information.

Microsoft begins automatic Windows 11 26H2 upgrades

Microsoft began automatically upgrading eligible unmanaged devices to Windows 11 26H2. Automatic upgrades can improve security currency, but they can also affect application compatibility, support workflows, and maintenance windows.

IT teams should identify unmanaged or personally administered systems that access organizational data, confirm backup and recovery coverage, and test business-critical applications against the new release.

Analyst’s Take: Start with the systems that combine reported exploitation and administrative reach: VMware vCenter, followed by exposed F5 BIG-IP appliances. The outage and breach reports also argue for parallel recovery work, especially where mail, identity, or other critical functions rely on an external provider.

Critical Vulnerabilities#

CVE-2026-123890: VMware vCenter authentication bypass

  • Product: VMware vCenter Server and VMware Directory Service
  • Severity: Critical
  • CVSS: 9.8
  • Reported exploitation: Zero-day attacks since September 2026
  • Status: Not listed as added to the supplied CISA KEV data
  • Affected versions: vCenter 9.1.x before 9.1.1.0200, 9.0.x before 9.0.2.0200, 8.0 before U3m, and 5.x before 5.2.5; affected Telco Cloud products are also identified in the advisory

This is the highest-priority vulnerability in today’s digest because it combines a critical severity rating with reported exploitation. Apply Broadcom’s fixes immediately and investigate historical access to affected systems.

Reference: Broadcom security advisory.

PHP session and PHP-FPM vulnerabilities

The PHP project disclosed several high-severity vulnerabilities affecting session handling, PHP-FPM, and specific PHP runtime configurations.

CVE-2026-115560

A session serializer mismatch can lead to remote code execution when session upload progress is enabled and applications use different session serializers.

Reference: PHP security advisory.

CVE-2026-126714

PHP file-based session handling can leave partially overwritten session files. Under suitable conditions, attacker-controlled objects may be unserialized, potentially enabling remote code execution when an appropriate gadget chain exists.

References:

CVE-2026-129182

A use-after-free involving fatal-error backtrace state can cause memory corruption and worker crashes, with potential remote code execution under specific PHP 8.5 configuration conditions.

Reference: PHP security advisory.

CVE-2026-129289

PHP-FPM request smuggling through an unread HTTP request body may allow an unauthenticated attacker to forge a backend FastCGI request and potentially execute attacker-controlled PHP code under connection-reuse configurations.

References:

Required PHP versions

The supplied advisories identify these versions as affected:

  • PHP versions before 8.2.36
  • PHP 8.3.x before 8.3.37
  • PHP 8.4.x before 8.4.28
  • PHP 8.5.x before 8.5.13

Upgrade to the appropriate fixed release for the deployed branch. Restart PHP-FPM workers after patching so vulnerable processes are no longer serving requests.

What Defenders Should Do Today#

  1. Patch VMware vCenter immediately. Start with internet-accessible management interfaces, systems supporting sensitive workloads, and environments with broad administrative trust.
  2. Investigate vCenter activity since September 2026. Review authentication logs, directory-service events, administrator creation, privilege changes, unusual API access, and unexpected connections from management hosts.
  3. Patch F5 BIG-IP appliances. Restrict management access to trusted administration networks while remediation is in progress.
  4. Inventory PHP and PHP-FPM versions. Include production servers, containers, development environments, appliances, and unmanaged application hosts.
  5. Review PHP configuration. Pay particular attention to session upload progress, session serializers, file-based sessions, object deserialization, reverse-proxy behavior, and HTTP connection reuse.
  6. Upgrade PHP and restart PHP-FPM. Confirm that package repositories, container images, and runtime processes all use fixed versions.
  7. Validate N-able service dependencies. Check Mail Assure and SpamExperts Hosted Cloud status, mail routing, quarantine access, continuity plans, and alternate delivery paths.
  8. Review breach exposure in critical-service sectors. Healthcare, transportation, government, and managed-service providers should check for relevant customer or partner notifications.
  9. Harden privileged infrastructure. Require MFA, perform privileged-access reviews, segment management networks, and monitor administrative interfaces.
  10. Test recovery procedures. Confirm that virtualization, network appliances, identity systems, mail services, and customer-facing platforms can be restored during a provider or ransomware-style outage.
  11. Track primary advisories. Monitor Broadcom, F5, and the PHP project for revised affected-version information, indicators of compromise, and additional mitigations.

Technical Notes#

vCenter investigation checklist

Preserve relevant logs before rotating or rebuilding systems. Correlate authentication and directory activity with network telemetry and hypervisor administration events.

Review:
- Successful and failed administrator authentication
- New or modified vCenter and directory accounts
- Unexpected privilege assignments
- Unusual API calls or session creation
- Access from unfamiliar source addresses
- Changes to hosts, datastores, virtual machines, or distributed switches
- Connections to vCenter management services from unapproved networks

Example searches should be adapted to the organization’s logging platform:

event_source = "vcenter"
AND (
  action IN ("user_created", "user_modified", "privilege_changed")
  OR service IN ("directory", "authentication", "api")
)
AND timestamp >= "2026-09-01"

This is a hunting pattern, not a vendor-provided indicator. Validate field names and event semantics against the deployed vCenter and SIEM versions.

PHP and PHP-FPM inventory

Example commands for Linux hosts:

php -v
php --ini
php -i | grep -E 'session.serialize_handler|session.upload_progress|session.save_handler'
php-fpm8.3 -v 2>/dev/null || php-fpm -v

For containerized deployments:

docker ps --format '{{.ID}}\t{{.Image}}\t{{.Names}}'
docker exec <container> php -v
docker image inspect <image> --format '{{.RepoTags}}'

Package inventory should be combined with application-level checks because the binary version in production may differ from the host package version.

PHP-FPM and reverse-proxy review

Review whether reverse proxies or load balancers reuse backend connections and whether request bodies can remain unread or be forwarded inconsistently. Validate the complete request path:

Client -> CDN/WAF -> Reverse proxy -> Web server -> PHP-FPM -> Application

Check for:

  • Backend connection reuse and pooling
  • HTTP protocol translation
  • Request-body buffering
  • FastCGI parameter handling
  • Conflicting timeout and body-size settings
  • Multiple PHP-FPM pools with inconsistent versions
  • Applications that unserialize attacker-controlled data
  • Session files stored on shared or writable locations

Post-patch validation

After applying updates:

php -v
systemctl status php*-fpm --no-pager
systemctl restart php8.3-fpm 2>/dev/null || systemctl restart php-fpm

Use the service name appropriate to the installed PHP branch. Confirm that the running worker processes have restarted and that the application remains functional after the change.

Bottom Line#

Remediate VMware vCenter first and investigate possible compromise because the vulnerability was reportedly exploited before disclosure. Patch F5 BIG-IP appliances and affected PHP/PHP-FPM deployments next. Then validate continuity plans for N-able-dependent mail services and other critical providers, with recovery testing covering virtualization, identity, network, and customer-facing systems.

Organizations should treat the reported outages and data exposures as operational signals: preventing compromise is only half the response when a provider or critical service becomes unavailable.

This article may contain affiliate links. We earn a commission on qualifying purchases at no extra cost to you.

CISA KEV additions this week#

CISA added 9 vulnerabilities to the Known Exploited Vulnerabilities catalog in the seven days to this digest. Source: CISA KEV catalog.

All KEV additions by date

Last verified: 2026-11-20

Disclaimer: This article may contain affiliate links. We earn a commission on qualifying purchases at no extra cost to you.