A decade-old patch bundle on a hypervisor that Broadcom stopped supporting in 2020
Plugin 81085 flags any ESXi 5.5 host at a build below 2352327 (January 2015 patch level) as vulnerable to a bundle of seven CVEs, dominated by POODLE (CVE-2014-3566), a handful of OpenSSL companion bugs (CVE-2014-3513, -3567, -3568), a libxml2 entity-expansion DoS (CVE-2014-3660), and a vmware-authd DoS (CVE-2014-8370). The most notable is CVE-2015-1044, an information-disclosure flaw in the ESXi authentication handling. Fix is patch bundles ESXi550-201403102-SG and ESXi550-201501101-SG, which by 2026 are ancient.
Tenable calls this HIGH (CVSSv2 8.1). Vendor listing you were shown as MEDIUM undersells reality: the underlying CVEs are individually medium-grade (mostly SSL/TLS MitM and DoS), but the *host* still failing this check in 2026 is running ESXi 5.5, which reached General Support end-of-life on 19 Sep 2018 and Technical Guidance EOL on 19 Sep 2020. There are no more patches, no more advisories, and every VMSA published since — including the 2024–2025 hypervisor escape wave — is unaddressable. MEDIUM is wrong. HIGH is right, and the reason isn't POODLE.
4 steps from start to impact.
Locate the aging hypervisor
http-vmware-path-vuln and Nessus's own banner grab identify the 5.5 build immediately. Shodan and Censys still list a small residual population of internet-exposed 5.5 hosts primarily in SMB and lab environments.- Network reachability to ESXi management interface
- TCP/443 or TCP/902 open
- Well-run shops isolate the ESXi management VLAN
- vCenter typically fronts host management
Downgrade TLS to SSL 3.0 (POODLE)
openssl s_client and Thomas Pornin's original POODLE POC force renegotiation to SSL 3.0 CBC and decrypt one byte per ~256 requests. Practical only against long-lived cookies or basic-auth headers.- Active MitM position on ESXi mgmt traffic
- Client that still speaks SSLv3
- Victim initiates many requests
- Modern browsers dropped SSLv3 in 2014-2015
- vSphere Client and PowerCLI negotiate TLS 1.2+
- Requires attacker-controlled JavaScript or long-lived session
Trigger DoS via libxml2 / vmware-authd
CVE-2014-3660 (billion laughs / entity expansion) and CVE-2014-8370 (input validation in vmware-authd) let an authenticated or network-adjacent attacker knock the management daemon offline. Both are DoS, not code execution — the guest VMs keep running but the admin loses control plane access.- Reachable vmware-authd (TCP/902)
- Ability to send crafted XML/auth payload
- No lateral movement value — DoS only
- Watchdog restarts most daemons
hostd uptime catches it.Pivot to the real problem — every VMSA since 2020
CVE-2021-21974 — the ESXiArgs ransomware vector), the OpenSLP RCE chain, and everything Broadcom shipped through VMSA-2025-0010 including CVE-2025-41238. None of these have patches for 5.5. Any RCE on ESXi is a fleet-defining event: one host = every VM on it, and lateral movement to vCenter = the datacenter.- Continued operation of ESXi 5.5
- Any network path to the host
- None — this is unfixable on 5.5
The supporting signals.
| In-the-wild status | POODLE actively exploited in downgrade research since 2014. CVE-2021-21974 (an unpatchable follow-on for these hosts) exploited by ESXiArgs ransomware from Feb 2023. |
|---|---|
| KEV status | The specific 2014 CVEs are not in CISA KEV. However, downstream ESXi CVEs the host is now defenseless against — including CVE-2023-20867, CVE-2023-34048 — are KEV-listed. |
| PoC availability | POODLE PoC public since 2014 (Bodo Möller/Thomas Duong/Krzysztof Kotowicz, Google). openssl s_client reproduces trivially. |
| EPSS | CVE-2014-3566 (POODLE): ~0.94 (94th percentile). CVE-2015-1044: ~0.05. |
| CVSS | Tenable aggregate 8.1 (CVSSv2 AV:N/AC:M/Au:N/C:C/I:P/A:N). Vendor MEDIUM label understates. |
| Affected versions | ESXi 5.5 at any build below 2352327 (2015-01-27). |
| Fixed version | Patch bundles ESXi550-201403102-SG + ESXi550-201501101-SG. These are the last relevant patches — 5.5 is EOL. |
| Exposure data | Shodan product:"VMware ESXi" version:5.5: residual internet-facing population in the low four-digits globally as of 2026, concentrated in edu/lab/legacy hosting. |
| Disclosure | Original CVEs disclosed Oct 2014 – Jan 2015. VMware advisories VMSA-2014-0012 and VMSA-2015-0001. |
| Support status | ESXi 5.5 General Support ended 2018-09-19; Technical Guidance ended 2020-09-19. No patches issued since. |
noisgate verdict.
The single decisive factor is role multiplier: the affected component is a Type-1 hypervisor, and every ESXi host by definition carries fleet-scale blast radius. The specific 2014 CVEs are pedestrian, but any host failing 81085 in 2026 is EOL and cannot be patched against six years of subsequent RCE and hypervisor-escape advisories.
Why this verdict
- Role multiplier — hypervisor: Any successful chain on ESXi ends in *every VM on that host* being compromised, and pivoting to vCenter turns it into a datacenter event. Per the noisgate hard rule, a canonical hypervisor deployment floors the verdict at HIGH minimum.
- EOL amplifier: ESXi 5.5 lost Technical Guidance in Sep 2020. A host still failing this 2015 check has missed every VMSA since — including
CVE-2021-21974(ESXiArgs),CVE-2023-20867,CVE-2023-34048, and the 2025 hypervisor-escape wave. Plugin 81085 is a proxy for *systemic* unpatchability, not just POODLE. - Friction on the individual 2014 CVEs pulls DOWN: POODLE requires an active MitM plus an SSLv3-speaking client, which basically doesn't exist in 2026. libxml2 and vmware-authd bugs are DoS-only. If this were a supported version, MEDIUM would be defensible.
- Net: floor of HIGH from hypervisor role + EOL exposure, not lifted to CRITICAL because the *named CVEs in the plugin* are not directly RCE and the exploit population that reaches the mgmt VLAN is bounded.
Why not higher?
The seven CVEs specifically flagged by plugin 81085 are POODLE-class MitM and DoS bugs — not remote unauthenticated RCE. CRITICAL requires a directly weaponizable chain on the flagged CVEs; the CRITICAL story here belongs to downstream VMSAs the host is separately vulnerable to, and those have their own plugins.
Why not lower?
MEDIUM assumes the host will be patched. It cannot be — 5.5 has been out of support since 2020. Any hypervisor that has drifted this far behind is a fleet-scale risk regardless of which single CVE lights up the scanner, and treating it as MEDIUM lets it sit in the 365-day backlog when it should be on a decommission plan measured in weeks.
What to do — in priority order.
- Decommission or migrate every ESXi 5.5 host within 30 days — There is no supported patch path. Migrate VMs to ESXi 7.0 U3 or 8.0 U3 (or a KVM/Proxmox target if licensing forces it). Per the noisgate HIGH mitigation SLA, this is the only real remediation.
- Isolate ESXi mgmt interfaces to a dedicated VLAN, ACL-restricted to jump hosts — Blocks the network reachability precondition for every step in the chain — POODLE, DoS, and the downstream VMSAs the host is now defenseless against. Deploy today; the noisgate mitigation SLA of 30 days for HIGH assumes this is the interim control.
- Disable SSLv3 on any remaining ESXi 5.5 hosts — Set
UserVars.ESXiVPsDisabledProtocolsto includesslv3in/etc/vmware/rhttpproxy/config.xmland restartrhttpproxy. Kills the POODLE path specifically. - Verify no internet exposure via external attack-surface tooling — Query Censys / Shodan / your ASM tool for
vmware+443on your ASN ranges. Any 5.5 host reachable from the internet is a P0 — pull it offline within 24 hours. - Snapshot and export every VM on the affected hosts — Assume compromise possibility during the migration window. Full offline backup before you kick off vMotion or a cold migration.
- Applying
ESXi550-201501101-SGin 2026 — it only closes the 2014 CVEs and leaves you exposed to every VMSA from 2015 onward. - Web-server-only TLS hardening (nginx, F5) — doesn't touch
hostdorvmware-authdon TCP/902. - EDR on the guest VMs — irrelevant; the hypervisor is below the guest kernel.
- vCenter upgrades alone — vCenter 7/8 will manage 5.5 hosts to a limited extent, but the host itself remains unpatchable.
Crowdsourced verification payload.
Run on an auditor workstation with SSH or esxcli reachability to the target ESXi host. Invoke as ./check_esxi_81085.sh <esxi-host>; needs an ESXi account with Host.Config.Settings or root SSH. Reports VULNERABLE if build < 2352327 OR the host is any 5.5 release (which is EOL).
#!/usr/bin/env bash
# noisgate verification — tenable:81085
# Detects ESXi 5.5 hosts below build 2352327 AND flags any 5.5 host as EOL.
set -u
HOST="${1:-}"
if [[ -z "$HOST" ]]; then
echo "Usage: $0 <esxi-host-or-ip>"; exit 2
fi
THRESHOLD=2352327
# Try SSH (esxcli) first; fall back to remote banner grab over HTTPS.
get_via_ssh() {
ssh -o BatchMode=yes -o ConnectTimeout=5 root@"$HOST" \
'vmware -v; echo ---; esxcli system version get' 2>/dev/null
}
get_via_https() {
# ESXi exposes build info in the /sdk endpoint response headers and
# the /client/clients.xml file on many builds.
curl -sk --max-time 8 "https://$HOST/sdk" -X POST \
-H 'Content-Type: text/xml' \
--data '<?xml version="1.0"?><soap:Envelope xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/"><soap:Body><RetrieveServiceContent xmlns="urn:vim25"><_this type="ServiceInstance">ServiceInstance</_this></RetrieveServiceContent></soap:Body></soap:Envelope>'
}
OUT="$(get_via_ssh)"
if [[ -z "$OUT" ]]; then
OUT="$(get_via_https)"
fi
if [[ -z "$OUT" ]]; then
echo "UNKNOWN: could not reach $HOST via SSH or HTTPS"; exit 3
fi
VERSION="$(echo "$OUT" | grep -oE 'VMware ESXi [0-9]+\.[0-9]+\.[0-9]+' | head -1)"
BUILD="$(echo "$OUT" | grep -oE 'build[- ]?[0-9]+' | grep -oE '[0-9]+' | head -1)"
if [[ -z "$VERSION" || -z "$BUILD" ]]; then
echo "UNKNOWN: could not parse version/build from response"; exit 3
fi
echo "Detected: $VERSION build $BUILD"
# Anything 5.5 is EOL — always VULNERABLE per noisgate reassessment.
if echo "$VERSION" | grep -q 'ESXi 5\.5'; then
if [[ "$BUILD" -lt "$THRESHOLD" ]]; then
echo "VULNERABLE: ESXi 5.5 build $BUILD < $THRESHOLD (plugin 81085) AND version is EOL"
else
echo "VULNERABLE: ESXi 5.5 is EOL since 2020-09-19 — no patches available for downstream VMSAs"
fi
exit 1
fi
echo "PATCHED: host is not ESXi 5.5"
exit 0
If you remember one thing.
Sources
What defenders are saying.
Crowdsourced verification outputs.
Results submitted by users who ran the verification payload against their environment.