OFFSEC · Offensive Security

A 2.7-rated ESXi logging flaw reaches KEV, and it is worth more to intruders than its score

CVE-2026-41709 grants no access. CrowdStrike says a China-nexus actor used it as a zero-day to keep its activity out of ESX logs, and patching does not recover what was never recorded.

A vulnerability scored 2.7 out of 10 has just joined the US Known Exploited Vulnerabilities catalogue, and it deserves more attention than its score suggests. CVE-2026-41709 lets an administrator on VMware ESX perform certain operations without them being logged [2]. CrowdStrike reported on 28 October that WARP PANDA, which it tracks as a China-nexus adversary, exploited it as a zero-day in intrusions that ran as late as early 2026 [1]. CISA added it to KEV the same day, with a federal deadline of 11 November [3][4]. The flaw grants no access. It removes the record of what an intruder did after gaining access, which is the evidence incident responders depend on.

What the data says

Broadcom fixed the flaw in VMSA-2026-0006, issued on 29 July 2026 and revised on 3 and 19 August [2]. Cyber Press and GBHackers give 30 July, the CVE record date, as the disclosure date [4][5]. The advisory scores it 2.7 with a vector requiring high privileges and affecting integrity only [2]. It credits Ian Barton of CrowdStrike, lists no workaround, and says the issues were privately reported; it does not state that any were exploited [2]. Broadcom has not said which operations go unlogged, and no public source describes the mechanism [3][6].

Fixed builds are ESXi80U3j-25429389 for 8.0, ESXi-9.0.2.0100-25595025 for 9.0 and ESXi-9.1.0.0-25370933 for 9.1, with VMware Cloud Foundation 5.2.4 and a separate knowledge base article for Telco Cloud Platform [2]. ESX 7.0 does not appear in the matrix for this CVE, and Broadcom has not said whether it is affected [2][3]. The KEV entry lists ransomware use as unknown [4][5].

CrowdStrike’s public account is brief. Its report states that WARP PANDA deployed several malware families in victims’ vCenter environments at US entities, including legal-sector targets, and exploited the ESXi command logging bypass as a zero-day [1]. Rescana found no other public exploitation account and no published indicators [3]. SQ Magazine lists aliases and additional malware families for the group; those details could not be traced to a primary source here and are not relied on [7].

The flaw fits a documented pattern. CrowdStrike’s December 2025 profile describes WARP PANDA clearing logs, timestomping files, creating virtual machines not registered in vCenter, and moving laterally over SSH with the privileged vpxuser account [8]. Google’s threat intelligence group put average BRICKSTORM dwell time at 393 days, often beyond log retention, and observed temporary local administrator accounts created and then deleted [9]. The joint CISA, NSA and Canadian Cyber Centre report records one victim where access lasted from at least April 2024 to at least September 2025 [10]. Google attributes BRICKSTORM activity to UNC5221 and related clusters, and CrowdStrike notes other China-nexus actors may use it; the two vendors’ cluster boundaries are not identical [8][9].

The same advisory also fixed CVE-2026-59310, a 9.8-rated directory traversal in the vCenter syslog service [2]. QUIRSO observed compromised systems contacting attacker infrastructure from 3 August, five days after disclosure, and counted 361 victim IP addresses in 47 countries by 7 August [12][13]. QUIRSO assessed an APT actor was responsible but, according to BleepingComputer, published no supporting evidence [13]. Nothing public links that campaign to WARP PANDA.

What it means

CVSS measures the direct impact of a flaw, not its operational value. A logging bypass is worthless for entry and valuable for tenure. For an actor whose model is long, quiet residence on hypervisors, removing audit evidence is the point [8][9]. Triage that filters on severity would have deferred this patch for three months while it was, by CrowdStrike’s account, already in use [1][2].

Local hypervisor logs were already fragile before this flaw. CrowdStrike showed in August that ESX shell logs record commands before expansion, so an obfuscated command is logged in its encoded form while it runs normally; it catalogued 21 such methods [11]. CVE-2026-41709 goes further, removing certain operations from the record altogether [2]. Together they mean an ESX host’s own logs are weak evidence of its integrity.

Patching restores logging from the point of the update. It does not restore records an attacker suppressed earlier. Hosts that ran unpatched builds while exposed to compromised administrator credentials should be treated as having an incomplete audit trail [3].

What to do

  • Patch every ESX host to the fixed build for its line, and confirm the running build on each host rather than in the cluster image [2][4].
  • For ESX 7.0 estates, ask Broadcom directly whether CVE-2026-41709 applies; the advisory is silent [2][3].
  • Patch vCenter for CVE-2026-59310 and CVE-2026-59309 in the same window if not already done [2][12].
  • Forward ESXi syslog and audit records to a collector that ESX administrators cannot alter, using an encrypted transport, and set retention on that collector, since ESXi cannot control it [15][16].
  • Monitor the forwarding path itself: Broadcom notes forwarding stops after a lost connection until the syslog service restarts [15].
  • Cross-check host logs against vCenter events, external syslog and network data for unexpected administrator activity, SSH sessions as root or vpxuser, unregistered virtual machines and unexpected clones [3][8][9].
  • Apply the published hardening: restrict ESXi and vCenter outbound access, disable or restrict SSH, enable execInstalledOnly, and require MFA for vCenter through an identity provider [8][9][14].
  • Hunt for obfuscated shell commands in existing ESX telemetry, after baselining normal administrative activity [11].
  • Use the CISA, NSA and Cyber Centre detection rules for BRICKSTORM, and check boot configuration files on vCenter and ESXi for unauthorised changes [10][14].

The offensive security view

Red teams have long treated defence evasion on hypervisors as a matter of tradecraft: clear logs, timestomp, use legitimate tools. CVE-2026-41709 shows a capable actor turning that tradecraft into a product flaw, and using it as a zero-day [1][8]. Assessments of virtualisation estates should therefore test whether administrative actions on ESX hosts are captured somewhere the host cannot reach, not only whether the hosts are patched. The public evidence for exploitation rests on a single vendor, CrowdStrike, with KEV listing as corroboration [1][4]. Broadcom and CrowdStrike have not described which operations escape logging, which limits precise detection. Defenders should assume the gap existed on every unpatched host and build evidence collection that does not depend on it.

Sources

Every R3KONX article cites its primary material. 16 sources, in order of first citation. Links open the original publication.

  1. CrowdStrike 2026 Legal Threat Landscape Report CrowdStrike · 2026-10-28
  2. VMSA-2026-0006: VMware ESX, vCenter Server, Workstation and Fusion updates address multiple vulnerabilities Broadcom · 2026-07-29
  3. VMware ESX CVE-2026-41709: Low-Rated Logging Flaw Now in CISA KEV After Zero-Day Use Rescana · 2026-10-29
  4. CISA Adds Actively Exploited VMware ESXi Logging Flaw to KEV Catalog GBHackers · 2026-10-29
  5. CISA Warns of Actively Exploited VMware ESXi Flaw That Lets Admins Hide Malicious Activity Cyber Press · 2026-10-29
  6. VMware ESX logging bypass let attackers run ESXi commands that never reached the logs (CVE-2026-41709) HOL Guard · accessed 2026-10-30
  7. Warp Panda Exploited ESXi Logging Flaw CVE-2026-41709 SQ Magazine · 2026-10-29
  8. Unveiling WARP PANDA: a new sophisticated China-nexus adversary CrowdStrike · 2025-12-04
  9. Another BRICKSTORM: stealthy backdoor enabling espionage into tech and legal sectors Google Threat Intelligence Group · 2025-09-24
  10. Malware Analysis Report: BRICKSTORM backdoor CISA, NSA and Canadian Centre for Cyber Security · 2025-12-04
  11. CrowdStrike threat hunts for shell command obfuscation on VMware ESX CrowdStrike · 2026-08-07
  12. vCenter flaw exploited just five days after disclosure Infosecurity Magazine · 2026-08-13
  13. Critical VMware vCenter RCE flaw exploited for reverse SSH access BleepingComputer · 2026-08-13
  14. BRICKSTORM backdoor to vSphere (KB 427833) Broadcom Knowledge Base · accessed 2026-10-30
  15. Configuring syslog on ESXi (KB 318939) Broadcom Knowledge Base · accessed 2026-10-30
  16. Enable the transmission of audit records to a remote host with ESXCLI VMware vSphere 8.0 documentation · accessed 2026-10-30

Researched and written by the R3KONX analysis desk from the cited primary material. Evidence of exploitation comes from a single vendor, CrowdStrike, whose public account is brief and names no indicators; it has not been independently replicated. The CISA alert and KEV catalogue entry could not be retrieved; the KEV date, deadline and ransomware field are taken from reports that quote them. Sources give 29 July (Broadcom advisory) and 30 July (CVE record) as the disclosure date; both are reported. Corrections to event@r3konx.asia.

R3KONX 2027

Work in this domain? So does the programme

4–6 May 2027, World Trade Centre Kuala Lumpur. Curated talks, hands-on training and The BattleGrid.