Back to Intelligence

VMware vCenter CVSS 9.8 Authentication Bypass: Patch, Lock Down Management Access, and Hunt for Rogue Sessions

SA
Security Arsenal Team
November 19, 2026
10 min read

Broadcom has disclosed a critical VMware vCenter vulnerability, rated CVSS 9.8, that allows an attacker with network access to bypass authentication and gain unauthorized access to the platform. Fixed releases are available for all supported branches, and Broadcom states there is no workaround. The source summary does not include a CVE identifier or exact fixed build numbers, so defenders should pull those directly from the Broadcom advisory rather than relying on reposts.

This is a crown-jewel exposure. vCenter is the control plane for ESXi hosts and virtual machines. Unauthorized access there can become datastore encryption at scale, VM snapshot theft, covert persistence through virtual hardware or guest tools, tampering with backups, and rapid lateral movement across the environment. Treat internet-reachable or broadly reachable vCenter interfaces as compromised until proven otherwise.

Why This Is Urgent

A CVSS 9.8 network authentication bypass against vCenter is close to a worst-case virtualization scenario because exploitation prerequisites are low and impact is centralized. If an attacker reaches vCenter over TCP 443 or auxiliary management ports such as TCP 5480 or legacy TCP 9443, they may not need valid credentials, endpoint malware, or user interaction.

Your immediate objectives are: remove network exposure, apply the fixed build for every supported branch in inventory, rotate credentials that could be replayed after unauthenticated access, and hunt for evidence that sessions, permissions, users, VM operations, or host changes occurred outside approved change windows.

Technical Analysis

Affected Products and Platforms

The affected product is VMware vCenter Server, including the vCenter Server Appliance used in most current deployments. vCenter centrally manages ESXi hosts, clusters, datastores, virtual networks, templates, snapshots, and VM lifecycle operations. Because supported branches are listed as having fixed versions, assume multiple vCenter release trains are affected and inventory every instance, including lab, DMZ, VDI, ROBO, cloud-adjacent, and outsourced environments.

Do not assume a vCenter behind a firewall is safe. Many environments expose vCenter to broad server VLANs, jump hosts, backup networks, HCI management fabrics, or third-party monitoring systems. An attacker only needs network access from a reachable segment.

CVE and Severity

The news item reports CVSS 9.8 and Critical severity, but no CVE identifier is provided in the summary. Do not invent one. Use the Broadcom advisory as the source of truth for the CVE, affected build ranges, fixed build numbers, release dates, and whether additional components such as integrated update or identity services are impacted.

How the Vulnerability Works, Defensively

At a defender level, the condition is an authentication bypass reachable over the network against vCenter services. That means requests to the vCenter management plane may be accepted as authenticated without presenting valid credentials. The practical risk is unauthorized use of the vSphere UI, API, SDK, PowerCLI/govc automation paths, or management endpoints after the bypass.

The likely post-bypass sequence is: access vCenter, establish a session or token, enumerate inventory and permissions, create or elevate a user, then execute privileged VM or host actions. High-impact actions include powering off security tooling VMs, deleting snapshots, exporting or downloading VM disks, changing networks to move laterally, adding SSH keys or local users to ESXi, enabling shell access, modifying DRS or HA to hide disruption, and touching backup or replication jobs.

Exploitation Status

The provided summary confirms vendor disclosure and fixes but does not state confirmed in-the-wild exploitation, public PoC, or CISA KEV inclusion. Treat status as urgent and potentially exploitable rather than theoretical. Check CISA KEV and Broadcom advisory updates continuously; if added to KEV, follow the federal remediation deadline as a minimum bar for all organizations.

Detection and Response

Prioritize high-fidelity signals: new vCenter sessions from non-management sources, creation or modification of users and roles, VAMI or legacy port exposure, and VM/host operations outside change control. Avoid broad rules such as any HTTPS to vCenter; they will be disabled by Friday.

Sigma Rules

YAML
---
title: VMware PowerCLI or vSphere CLI Execution From Unexpected Endpoint
id: 4f0b2c1a-7a4e-4b0a-9d6a-7c9b8f2a6d10
status: experimental
description: Detects interactive or scripted use of VMware administration tooling from endpoints that are not approved virtualization jump hosts. Tune the approved host list before production.
references:
  - https://attack.mitre.org/techniques/T1059/
  - https://attack.mitre.org/techniques/T1021/
author: Security Arsenal
date: 2026/11/06
tags:
  - attack.execution
  - attack.t1059
  - attack.lateral_movement
logsource:
  category: process_creation
  product: windows
detection:
  selection_tools:
    Image|endswith:
      - '\powershell.exe'
      - '\pwsh.exe'
      - '\govc.exe'
      - '\vmware-cmd.exe'
      - '\esxcli.exe'
  selection_cli:
    CommandLine|contains:
      - 'Connect-VIServer'
      - 'Set-PowerCLIConfiguration'
      - 'New-VM'
      - 'Set-VM'
      - 'Remove-VM'
      - 'govc vm.'
      - 'govc datastore.'
      - 'govc host.'
      - 'esxcli system account'
  filter_approved_jump_hosts:
    Computer|contains:
      - 'VIT-JUMP'
      - 'MGMT-VCSA-ADM'
  condition: selection_tools and selection_cli and not filter_approved_jump_hosts
falsepositives:
  - Virtualization administrators using PowerCLI from approved jump hosts
  - Backup or monitoring service accounts with documented automation
level: high
---
title: ESXi or vCenter Account and Shell Change Indicators in Forwarded Syslog
id: 9b6d2a70-4f20-43d0-9a73-6e1a2b4d88c2
status: experimental
description: Detects syslog evidence of account creation, shell enablement, permission changes, or snapshot and datastore operations on VMware infrastructure forwarded from ESXi or vCenter.
references:
  - https://attack.mitre.org/techniques/T1136/
  - https://attack.mitre.org/techniques/T1078/
  - https://attack.mitre.org/techniques/T1490/
author: Security Arsenal
date: 2026/11/06
tags:
  - attack.persistence
  - attack.t1136
  - attack.defense_evasion
logsource:
  product: linux
  service: syslog
detection:
  selection_vendor:
    Message|contains:
      - 'vpxd'
      - 'hostd'
      - 'vmware'
      - 'ESXi'
      - 'vCenter'
  selection_actions:
    Message|contains:
      - 'user added'
      - 'created user'
      - 'account created'
      - 'permission'
      - 'role'
      - 'Administrator'
      - 'shell enabled'
      - 'SSH'
      - 'snapshot'
      - 'delete all snapshots'
      - 'datastore'
      - 'download'
      - 'powered off'
  condition: selection_vendor and selection_actions
falsepositives:
  - Approved maintenance and automation during change windows
  - Backup systems performing snapshot orchestration
level: medium

Microsoft Sentinel KQL

Use this against vCenter, ESXi, firewall, load balancer, and VPN telemetry ingested through CommonSecurityLog or Syslog. Replace the placeholder IPs and approved management networks first.

KQL — Microsoft Sentinel / Defender
let VCenter = dynamic(['10.10.5.20','10.10.6.20']);
let ApprovedMgmtPrefixes = dynamic(['10.20.0.0/16','10.30.8.0/24']);
let ChangeWindowStart = datetime(2026-11-01T00:00:00Z);
let ChangeWindowEnd = datetime(2026-11-01T06:00:00Z);
union isfuzzy=true
  (CommonSecurityLog
   | where DestinationIP in (VCenter) and DestinationPort in (443,5480,9443,7444)
   | extend SourcePrefix = strcat(extract(@'^(\d+\.\d+)', 1, SourceIP), '.0.0/16')
   | extend IsApprovedMgmt = SourceIP has_any ('10.20.','10.30.8.')
   | where IsApprovedMgmt == false
   | project TimeGenerated, SourceIP, DestinationIP, DestinationPort, Protocol, DeviceVendor, DeviceProduct, Activity, Message),
  (Syslog
   | where SyslogMessage has_any ('vpxd','hostd','rhttpproxy','vmware','vCenter','ESXi')
   | where SyslogMessage has_any ('login','session','user added','created user','permission','role','shell','SSH','snapshot','datastore','download','powered off')
   | extend SourceHost = tostring(HostName)
   | project TimeGenerated, SourceHost, ProcessName, SeverityLevel, SyslogMessage)
| where not(TimeGenerated between (ChangeWindowStart .. ChangeWindowEnd))
| summarize FirstSeen=min(TimeGenerated), LastSeen=max(TimeGenerated), Events=count(), Samples=make_set(strcat(tostring(SourceIP), '|', tostring(Activity), '|', substring(tostring(Message),0,120)), 20)
  by SourceIP, DestinationIP, DestinationPort, SourceHost, ProcessName
| order by Events desc;

Velociraptor VQL

Deploy this to management endpoints and jump hosts to find unexpected processes communicating with vCenter management ports.

VQL — Velociraptor
-- Hunt endpoints for unexpected connections to vCenter management services
LET vc_targets = ['10.10.5.20','10.10.6.20']
LET vc_ports = [443,5480,9443,7444]
SELECT Pid,
       Name,
       Exe,
       LocalAddr,
       LocalPort,
       RemoteAddr,
       RemotePort,
       Status
FROM netstat()
WHERE RemoteAddr IN vc_targets
  AND RemotePort IN vc_ports
  AND NOT (Exe =~ 'Approved\\\\JumpHost' OR Name IN ['chrome.exe','msedge.exe','powershell.exe'] AND LocalAddr =~ '10\\.20\\.')

Verification and Exposure Script

Run from a Linux management host. It does not patch the appliance; it verifies reachability, retrieves the appliance version through the authenticated API where possible, and fails closed if management ports are reachable outside approved networks. Set FIXED_BUILD_MAP from the Broadcom advisory before using the version gate.

Bash / Shell
#!/usr/bin/env bash
set -euo pipefail

VCENTER_LIST=${VCENTER_LIST:-/opt/sec/vcenter-servers.txt}
APPROVED_MGMT=${APPROVED_MGMT:-'10.20.0.0/16,10.30.8.0/24'}
VC_USER=${VC_USER:-administrator@vsphere.local}
OUT=${OUT:-vcenter-exposure-$(date +%Y%m%d-%H%M%S).csv}
echo 'vcenter,tcp443,tcp5480,tcp9443,tcp7444,api_version,build,assessment' > "$OUT"

# Populate FIXED_BUILD_MAP from the Broadcom advisory only. Example format: FIXED_BUILD_MAP='8.0U3e:12345678;7.0U3s:23456789'
FIXED_BUILD_MAP=${FIXED_BUILD_MAP:-''}

while IFS= read -r VC; do
  [ -z "$VC" ] && continue
  p443=closed; p5480=closed; p9443=closed; p7444=closed
  timeout 3 bash -c "</dev/tcp/$VC/443" 2>/dev/null && p443=open || true
  timeout 3 bash -c "</dev/tcp/$VC/5480" 2>/dev/null && p5480=open || true
  timeout 3 bash -c "</dev/tcp/$VC/9443" 2>/dev/null && p9443=open || true
  timeout 3 bash -c "</dev/tcp/$VC/7444" 2>/dev/null && p7444=open || true

  version=unknown; build=unknown; assessment='manual-review-required'
  if [ -n "${VC_PASS:-}" ] && [ "$p443" = open ]; then
    token=$(curl -ks -u "$VC_USER:$VC_PASS" -X POST "https://$VC/rest/com/vmware/cis/session" | sed -n 's/.*"value":"\([^"]*\)".*/\1/p' || true)
    if [ -n "$token" ]; then
      resp=$(curl -ks -H "vmware-api-session-id: $token" "https://$VC/rest/appliance/system/version" || true)
      version=$(printf '%s' "$resp" | sed -n 's/.*"version":"\([^"]*\)".*/\1/p' | head -1)
      build=$(printf '%s' "$resp" | sed -n 's/.*"build":"\([^"]*\)".*/\1/p' | head -1)
      [ -z "$version" ] && version=unknown
      [ -z "$build" ] && build=unknown
      curl -ks -X DELETE -H "vmware-api-session-id: $token" "https://$VC/rest/com/vmware/cis/session" >/dev/null 2>&1 || true
    fi
  fi

  if [ "$p5480" = open ] || [ "$p9443" = open ] || [ "$p7444" = open ]; then
    assessment='EXPOSED-AUX-PORTS-RESTRICT-NOW'
  elif [ "$p443" = open ]; then
    assessment='443-REACHABLE-VERIFY-MGMT-ACL-AND-PATCH'
  else
    assessment='NOT-REACHABLE-FROM-THIS-HOST'
  fi

  if [ -n "$FIXED_BUILD_MAP" ] && [ "$build" != unknown ]; then
    printf '%s' "$FIXED_BUILD_MAP" | grep -q ":$build" && assessment="$assessment;BUILD-MATCHES-FIXED-MAP" || assessment="$assessment;BUILD-NOT-IN-FIXED-MAP"
  fi

  printf '%s,%s,%s,%s,%s,%s,%s,%s\n' "$VC" "$p443" "$p5480" "$p9443" "$p7444" "$version" "$build" "$assessment" >> "$OUT"
done < "$VCENTER_LIST"

echo "Wrote $OUT. Approved management networks: $APPROVED_MGMT. Confirm firewall ACLs match these prefixes only."

Remediation

  1. Patch immediately. Upgrade every vCenter instance to the fixed build listed by Broadcom for its exact supported branch. Because the source summary does not list build numbers, copy the affected and fixed build matrix directly from the Broadcom advisory and attach it to the change record. Do not patch by major version alone; validate the exact build after reboot.

  2. Remove network paths now. Until patches are verified, restrict TCP 443 to named jump hosts and SOC/Vulnerability scanners. Block TCP 5480, TCP 9443, and TCP 7444 from everything except a tiny break-glass management subnet. vCenter must never be internet-facing. Confirm with external scanning and internal port validation, not only firewall policy review.

  3. Snapshot and back up before change, but protect the backups. Take an offline or immutable backup of vCenter and the PSC topology where applicable. Ensure backup credentials are not readable from vCenter and backup repositories are not writable from ESXi hosts.

  4. Rotate credentials after patching. Prioritize administrator@vsphere.local or equivalent SSO admins, AD/LDAP bind accounts, service accounts used by backup/monitoring/automation, API tokens, PowerCLI stored credentials, govc sessions, and any secrets embedded in orchestration tools. If unauthenticated access was possible before patching, assume session tokens and cached credentials may have been exposed.

  5. Review identity state. Enumerate SSO users and groups, local appliance users, global permissions, roles, licenses, trusted identity providers, SAML/OIDC configuration, and solution user certificates. Look for new administrators, broadened permissions, changed role assignments, or unfamiliar identity sources.

  6. Review control-plane actions. Audit VM power operations, snapshot deletion, datastore browser downloads, OVF exports, VMDK attach/detach, vMotion and Storage vMotion spikes, ESXi shell/SSH enablement, host account creation, lockdown mode changes, syslog target changes, and alarm suppression. Compare against change tickets.

  7. Validate compensating controls. Ensure vCenter and ESXi logs are forwarded to the SIEM with reliable time sync, VAMI is disabled or restricted where not required, MFA is enforced for administrative access through your identity layer, and EDR coverage exists on jump hosts and management servers.

  8. If exposure was broad or unauthenticated sessions are unexplained, open an IR case. Preserve vCenter logs, ESXi hostd/vpxd/syslog, firewall and VPN logs, identity provider events, and forensic images of management endpoints before aggressive cleanup. Rebuild credentials from known-good secret stores rather than rotating in place if compromise is suspected.

  9. Track regulatory drivers. Monitor CISA KEV for addition and apply the KEV deadline if published. For PCI-DSS, HIPAA, and NIST CSF programs, document exposure windows, affected assets, evidence of patching, credential rotation, and follow-up hunts because vCenter is usually in scope for critical-system and audit-log requirements.

Related Resources

Security Arsenal Penetration Testing Services AlertMonitor Platform Book a SOC Assessment vulnerability-management Intel Hub

Is your security operations ready?

Get a free SOC assessment or see how AlertMonitor cuts through alert noise with automated triage.