127 GB — that was the amount of host RAM a researcher says he could read from a Digital Ocean "Droplet" after exploiting a recently disclosed KVM flaw, adding urgency to a week already crowded with critical VMware advisories and emergency patches.
VMware advisories: VMSA-2026-0009 and VMSA-2026-0010 spell out high-rated exposure
VMware published two security advisories that demand attention. VMSA-2026-0009 centers on CVE-2026-123890, a 9.8-rated vulnerability VMware says allows "a malicious actor with network access to vCenter" to bypass authentication and gain unauthorized access to systems managed by vCenter, the administrative tool used to manage fleets of virtual machines. VMware says the flaw exists in its Cloud Foundation suite; that advisory also details four additional CVEs, some rated high.
VMSA-2026-0010 warns that Cloud Foundation, Aria Operations, and VCF Operations HCX products ship components that use Apache, which contains CVE-2026-119618 — a 9.8-rated remote code execution vulnerability. Both advisories were published as organizations are already juggling emergency patches for other widely used software such as PHP, Java, and PostgreSQL.
KVM bug CVE-2026-99312: who is affected and how severe is it?
The KVM issue, recorded as CVE-2026-99312 and disclosed on November 18, allows a guest virtual machine to inflict denial-of-service or memory-corruption attacks on the host. Unlike a full guest-to-host escape, this bug only affects systems running on AMD processors that enable nested virtualization — the practice of running a hypervisor inside a virtual machine. Because nested virtualization is not commonly used in many enterprises, but is employed by clouds to power things like OS emulators, the flaw received a CVSSv3 score of 5.5.
Security researcher Oren Tomtov of Accomplish.ai says the vulnerability let him access 127 GB of host RAM on a Digital Ocean Droplet, illustrating why even a limited-scope guest-host flaw can be consequential in multi-tenant cloud settings.

The cyber insurance questionnaire just landed. Now what?
SOC 2, HIPAA, insurance renewals - someone has to own security strategy. Nubivance provides fractional CISO leadership without the full-time salary.
Get a security leadOrigins, fixes, and the disclosure timeline
According to the reporting, Tomtov told Digital Ocean and the Linux kernel security team about the flaw in October. Kernel maintainers merged a fix into mainline on November 2, and "full fixes" landed on November 17; the CVE appeared publicly on November 18. Two independent analyses — from Tomtov and from Terra Security — were posted quickly after the disclosure but were removed within hours. The Register reports Digital Ocean asked for the posts to be taken down to give the company more time to update its Linux implementations; Digital Ocean did not respond to multiple requests for comment.
Terra Security's analysis asserts the bug was introduced to KVM in 2022 when developers applied a fix for CVE-2022-3344, and the company calculates that 3.2 percent of CVEs in the Linux kernel were introduced by fixes for other CVEs. Those claims are reported as Terra's analysis rather than independently verified by the vendor or kernel maintainers in the article.
What this means for technologists, cloud providers, and VMware customers
- Technologists and security teams: Prioritize applying VMware's VMSA-2026-0009 and VMSA-2026-0010 patches for Cloud Foundation, Aria Operations, and VCF Operations HCX, and assess exposure where vCenter is reachable on your network. For KVM hosts using AMD CPUs, evaluate whether nested virtualization is enabled and consider temporary mitigations.
- Cloud providers and platform operators (Digital Ocean and peers): The timeline shows the kernel fix was available in mainline on November 2 and fully landed on November 17, but the public analysis and operational mitigations prompted a request to delay public disclosure. Providers will need to coordinate kernel updates across their fleets and manage customer communications; the Register reports Digital Ocean did not respond to multiple requests for comment.
- VMware customers and administrators: The presence of a 9.8-rated authentication bypass to vCenter (CVE-2026-123890) means administrators should treat VMSA-2026-0009 as an immediate priority alongside other critical patches already in progress.
Mitigations, practical steps, and a closing observation
For the KVM issue there is a straightforward operational mitigant: disabling nested virtualization defeats the exploit without an immediate kernel update. For the VMware issues, follow VMSA-2026-0009 and VMSA-2026-0010 guidance and patch affected products that rely on Apache components vulnerable to CVE-2026-119618.
The technical record here is concrete: high-scoring VMware advisories and a medium-scoring KVM flaw with a clear, practical mitigation, accompanied by a rapid patch landing in the kernel tree. The episode also underscores a narrower, specific risk flagged by Terra Security — that some kernel vulnerabilities can be introduced by earlier fixes — and a live operational tension over the timing of public analysis and cloud updates, as evidenced by the removal of public write-ups at Digital Ocean's request. Administrators now have patches and a mechanical workaround; the remaining question the record leaves is how quickly large clouds and on-premises fleets will roll those fixes into production.




