---
analysis: While a rule can fire on a vulnerability finding, this hunt correlates internet
  exposure, unpatched versions, and behavioral anomalies (like rare source IPs hitting
  SSO paths) to identify active exploitation that static rules may miss if the attacker
  uses legitimate-looking admin credentials.
blind_spots:
- id: vcenter-log-gap
  question: whether the Directory Service component explicitly logged the bypass attempt
  requires: vCenter internal vmdir audit logs
  risk: Attackers may use alternate paths that do not generate standard HTTP activity
    in the management server logs, leaving only vmdir-specific logs as evidence.
  stage: exploit-vcenter-auth-bypass
- id: tls-inspection-missing
  question: the specific body or headers of the HTTP requests used to bypass authentication
  requires: TLS decryption on management traffic
  risk: Without TLS inspection, only the URL path is visible; the specific CWE-288
    alternate channel payload may be hidden in the encrypted stream.
  stage: exploit-vcenter-auth-bypass
coverage:
- stage: external-vcenter-exposure
  status: covered
  steps:
  - vcenter-exposed-perimeter
- stage: exploit-vcenter-auth-bypass
  status: covered
  steps:
  - vcenter-anomalous-web-traffic
- stage: unauthorized-administrator-access
  status: covered
  steps:
  - vcenter-administrator-logons
- stage: vulnerable-vcenter-inventory
  status: covered
  steps:
  - vcenter-vulnerability-scoping
  - vcenter-internal-inventory
guardrails:
  claims: no_unsupported
  evidence: citation_required
  missing_data: not_benign
  telemetry: untrusted
hunt:
  applicability: campaign-specific
  handoff: keep-as-periodic-hunt
  justification: VMware vCenter is critical infrastructure and the primary management
    plane for virtualized estates. A CVSS 9.8 authentication bypass exploited in the
    wild by state-linked actors (ARMORY CASTLE) requires an emergency hunt to ensure
    environment integrity.
  methodology: model-assisted
  trigger: intel-report
hypothesis: An adversary has exploited a critical authentication bypass in the VMware
  Directory Service (vmdir) to gain unauthorized administrative access to vCenter,
  likely originating from an external or anomalous source IP.
labels:
- hunt
- attack.t1190
- initial access
name: VMware vCenter Authentication Bypass (CVE-2026-123890)
parameters:
  admin_accounts:
    default:
    - Administrator
    - administrator@vsphere.local
    - root
    description: Standard administrative accounts for vCenter management.
    type: list[string]
  cve_id:
    default: CVE-2026-123890
    description: Target CVE identifier.
    from:
      kind: article
      observed: '2026-11-19'
      ref: VMSA-2026-0009
    type: string
  lookback_days:
    default: '14'
    description: Days of history to examine.
    type: number
  scope_hosts:
    default: []
    description: Specific vCenter hostnames to narrow the behavioral hunt; leave empty
      to hunt across all managed hosts.
    type: list[host]
provenance:
  authors:
  - name: Huntbase hunt generation
    org: huntbase.io
  generated:
    by: huntbase-hunt-generation
    from: https://www.rapid7.com/blog/post/etr-cve-2026-123890-critical-authentication-bypass-vmware-vcenter
    gates:
    - dry-run
    - lint
    - critic
    model: hb_google/gemini-3-flash-preview
rationale: Start with any host identified in hb_vulnerability_finding with CVE-2026-123890.
  If scanner coverage is incomplete, use the software inventory query to find vCenter
  installations. Prioritize hosts that also appear in hb_exposed_assets.
references:
- name: "Rapid7 \u2014 CVE-2026-123890: Critical Authentication Bypass in VMware vCenter"
  url: https://www.rapid7.com/blog/post/etr-cve-2026-123890-critical-authentication-bypass-vmware-vcenter
related:
- hunt: vcenter-lateral-movement-to-esxi
  reason: If this hunt confirms vCenter compromise, the next stage is hunting for
    movement from vCenter to managed ESXi hosts.
  relation: follows
scenario:
  stages:
  - name: External vCenter Exposure
    observables:
    - VMware vCenter Server instances exposed to the internet
    - Open ports 443, 636, or 389 on vCenter infrastructure
    slug: external-vcenter-exposure
    tactic: initial-access
    techniques:
    - T1190
  - name: vCenter Authentication Bypass Exploitation
    observables:
    - CVE-2026-123890
    - Requests to VMware Directory Service (vmdir) component
    - Anomalous HTTP requests to vCenter management interfaces
    slug: exploit-vcenter-auth-bypass
    tactic: initial-access
    techniques:
    - T1190
  - name: Unauthorized Administrator Access
    observables:
    - Administrator login events without corresponding authentication steps
    - Logins for 'Administrator' from unusual or external source IPs
    - Anomalous session creation in vCenter
    slug: unauthorized-administrator-access
    tactic: initial-access
    techniques:
    - T1190
  - name: Vulnerable vCenter Inventory
    observables:
    - vCenter Server version < 8.0 U3m
    - vCenter Server version < 9.0.2.0200
    - vCenter Server version 7.0
    - CVE-2026-123890 vulnerability findings
    slug: vulnerable-vcenter-inventory
    tactic: initial-access
    techniques:
    - T1190
  summary: Chinese state-linked actor ARMORY CASTLE has been exploiting a critical
    authentication bypass in the VMware Directory Service (CVE-2026-123890) to gain
    unauthorized Administrator access to vCenter Server. The vulnerability allows
    attackers with network access to bypass authentication via an alternate path or
    channel, bypassing existing security controls.
severity: critical
targets:
  analyst:
    name: Tier-2 analyst
    role: analyst
  endpoint:
    category: endpoint
    name: Endpoint telemetry (hb_ surfaces)
    telemetry:
    - endpoint
  hunter:
    agent: true
    name: Hunt agent
  identity:
    category: identity
    name: Identity / sign-in telemetry
    telemetry:
    - identity
  web:
    category: siem
    name: Web server / proxy logs
    telemetry:
    - network
tlp: clear
type: investigation
---


# VMware vCenter Authentication Bypass (CVE-2026-123890)

This hunt identifies VMware vCenter instances vulnerable to CVE-2026-123890, confirms their internet exposure, and searches for evidence of exploitation through anomalous HTTP requests and unauthorized Administrator logins. The phased flow correlates inventory risk with behavioral signals to identify compromised management planes before lateral movement into the virtualized estate occurs.

## vcenter-vulnerability-scoping
<!-- Identify hosts with reported CVE findings -->
Find resources already identified as vulnerable to CVE-2026-123890 by security scanners.

```sqlite target=endpoint role=scoping params=(cve_id=cve_id)
~~~yaml
expected: Rows identify specific vCenter resources known to be vulnerable. Silence
  means no scanner has reported this CVE yet, but the software inventory step may
  still find vulnerable versions.
reads:
- device_uid
- resource_uid
- cve_uid
- severity
- first_seen
silence: not_evidence_of_absence
source: hb_vulnerability_finding
verified: dry-run
verified_at: '2026-11-20'
~~~
SELECT device_uid, resource_uid, cve_uid, severity, first_seen FROM hb_vulnerability_finding WHERE cve_uid = '{{cve_id}}' AND status != 'suppressed'
```

## parallel-identify-exposure
<!-- Identify exposure and inventory -->
parallel:
- → vcenter-exposed-perimeter
- → vcenter-internal-inventory
join: → early-stage-assessment

## vcenter-exposed-perimeter
<!-- Internet-exposed vCenter instances -->
Find vCenter management interfaces reachable from the internet, which are at highest risk of exploitation.

```sqlite target=endpoint role=baseline
~~~yaml
expected: Identifies the external perimeter exposure. Any row represents a high-priority
  target for the ARMORY CASTLE threat actor.
reads:
- domain_or_ip
- port
- product
- version
- provider
- discovered_at
silence: not_evidence_of_absence
source: hb_exposed_assets
verified: dry-run
verified_at: '2026-11-20'
~~~
SELECT domain_or_ip, port, product, version, provider, discovered_at FROM hb_exposed_assets WHERE LOWER(product) LIKE '%vcenter%'
```

## vcenter-internal-inventory
<!-- Confirm unpatched vCenter versions -->
Verify specific vCenter version strings to identify unpatched systems that scanners might have missed.

```sqlite target=endpoint role=baseline params=(scope_hosts=scope_hosts)
~~~yaml
expected: A list of hosts and their versions. Analyst must compare versions (e.g.,
  < 8.0 U3m) against the advisory to confirm vulnerability.
reads:
- device_hostname
- package_name
- package_version
- install_path
silence: evidence_of_absence
source: hb_software_inventory
verified: dry-run
verified_at: '2026-11-20'
~~~
SELECT device_hostname, package_name, package_version, install_path FROM hb_software_inventory WHERE LOWER(package_name) LIKE '%vcenter%' AND ('{{scope_hosts}}' = '' OR instr(',' || '{{scope_hosts}}' || ',', ',' || device_hostname || ',') > 0)
```

## early-stage-assessment
<!-- Risk and priority assessment -->
```agent target=hunter
cite: required
context:
- vcenter-vulnerability-scoping
- vcenter-exposed-perimeter
- vcenter-internal-inventory
max_iterations: 3
objective: Determine which hosts are vulnerable to CVE-2026-123890 and identify those
  reachable from the internet.
success_criteria: A per-host risk assessment citing unpatched versions and exposure
  status.
tools:
- endpoint
- identity
- web
```

## parallel-detect-behavior
<!-- Detect exploitation behaviors -->
parallel:
- → vcenter-anomalous-web-traffic
- → vcenter-administrator-logons
join: → exploitation-triage

## vcenter-anomalous-web-traffic
<!-- Anomalous web traffic to sensitive paths -->
Detect unexpected HTTP traffic to vCenter management endpoints, specifically the vmdir and websso components.

```sqlite target=web role=baseline params=(lookback_days=lookback_days, scope_hosts=scope_hosts)
~~~yaml
baseline:
  compare: first_seen
  window: '{{lookback_days}}d'
expected: A concentration of requests to SSO or Directory Service paths from rare
  source IPs. High volume from an external IP is highly suspicious.
prevalence:
  by: device_hostname
  key:
  - src_endpoint_ip
  rare_below: 3
reads:
- src_endpoint_ip
- device_hostname
- url_path
- time
silence: not_evidence_of_absence
source: hb_http_activity
verified: dry-run
verified_at: '2026-11-20'
~~~
SELECT src_endpoint_ip, COUNT(DISTINCT device_hostname) AS host_count, COUNT(*) AS request_count, MIN(time) AS first_seen, MAX(time) AS last_seen FROM hb_http_activity WHERE (LOWER(url_path) LIKE '/websso/%' OR LOWER(url_path) LIKE '/vca/%' OR LOWER(url_path) LIKE '/vmdir/%') AND ('{{scope_hosts}}' = '' OR instr(',' || '{{scope_hosts}}' || ',', ',' || device_hostname || ',') > 0) AND time >= datetime('now', '-{{lookback_days}} days') GROUP BY src_endpoint_ip HAVING host_count <= 2 ORDER BY request_count DESC
```

## vcenter-administrator-logons
<!-- Anomalous Administrator sign-ins -->
Find successful administrative logons from source IPs that do not match known management workstations.

```sqlite target=identity role=triage params=(lookback_days=lookback_days, admin_accounts=admin_accounts, scope_hosts=scope_hosts)
~~~yaml
expected: Administrator logins from unusual IPs. Silence is not evidence of absence
  if the attacker uses internal proxies or session theft.
reads:
- device_hostname
- actor_user_name
- src_endpoint_ip
- logon_type
- status
- time
silence: not_evidence_of_absence
source: hb_auth_signin
verified: dry-run
verified_at: '2026-11-20'
~~~
SELECT device_hostname, actor_user_name, src_endpoint_ip, logon_type, status, time FROM hb_auth_signin WHERE instr(',' || '{{admin_accounts}}' || ',', ',' || actor_user_name || ',') > 0 AND status_id = 1 AND ('{{scope_hosts}}' = '' OR instr(',' || '{{scope_hosts}}' || ',', ',' || device_hostname || ',') > 0) AND time >= datetime('now', '-{{lookback_days}} days')
```

## exploitation-triage
<!-- Exploitation triage and correlation -->
```agent target=hunter
cite: required
context:
- early-stage-assessment
- vcenter-anomalous-web-traffic
- vcenter-administrator-logons
max_iterations: 5
objective: Decide if the anomalous HTTP traffic and Administrator logins indicate
  successful exploitation of CVE-2026-123890 in the context of vCenter vulnerability
  and exposure.
success_criteria: A per-host verdict of malicious | suspicious | benign, citing both
  the unpatched status and the specific anomalous activity.
tools:
- endpoint
- identity
- web
```

## verdict-decision
<!-- Route on verdict -->
if~: "the exploitation-triage verdict is malicious or suspicious for at least one host" (confidence: high, judge=hunter)
then: → isolate-compromised-host
indeterminate: → analyst-manual-review
unavailable: → analyst-manual-review (blind_spot: vcenter-log-gap)
else: → remediation-and-closeout

## isolate-compromised-host
<!-- Isolate compromised vCenter -->
```action target=endpoint
~~~yaml
approval: required
~~~
Isolate the compromised vCenter instance from the network immediately. Capture volatile memory and vCenter audit logs before shutdown.
```
→ analyst-manual-review

## analyst-manual-review
<!-- Analyst manual review -->
```manual target=analyst
Review the identified web traffic and login events. Confirm if the source IPs belong to authorized management workstations or jump boxes. If exploitation is confirmed, initiate an Incident Response procedure.
```
→ remediation-and-closeout

## remediation-and-closeout
<!-- Remediation and closeout -->
```manual target=analyst
Ensure all identified vulnerable hosts are scheduled for emergency patching to fixed versions (e.g., 8.0 U3m or 9.0.2.0200). Record what was examined and any remaining blind spots.
```
→ end
