Patching at Fleet Scale, Twice: How DigitalOcean Closed Januscape and the AMD Safe RET Issue Without Customer Impact

DigitalOcean describes its responses to two serious cloud infrastructure vulnerabilities in July and August 2026: Januscape, a KVM nested-virtualization flaw that could enable guest-to-host escapes, and an AMD Safe RET issue involving speculative-execution protections that could permit information disclosure across privilege boundaries. For Januscape, the company developed and deployed live patches across most of its hypervisor fleet, while handling several hundred older-kernel hosts through workload evacuation, host upgrades, capacity reallocation, and a separately hardened custom patch, reaching full coverage eight days after disclosure. For the AMD issue, which could not be livepatched and required reboots on roughly 1,600 hypervisors in 12 regions, DigitalOcean used coordinated disclosure time to test kernels, stage updates, migrate workloads, reboot hosts, and complete remediation before the vulnerability became public. The company attributes zero confirmed customer-facing impact to cross-team coordination among kernel, security, capacity, operations, support, and fleet-management teams, along with staged rollouts, continuous monitoring, detection engineering, and reusable automation. It concludes that increasingly rapid exploit development requires even faster fleet-wide remediation capabilities and says it is reviewing both incidents to reduce response times further.

No tracked trend matches for this post yet.

Use this post, company, and trend context to find content marketing opportunities, perform competitive analysis, or address product feature gaps via the Plushcap MCP server or the Plushcap API.