Live

(PwnEscape) Guest-to-Host KVM Escape [CVE-2026-99999]

We have completed our investigation and response to the “PwnEscape” Guest-to-Host Escape vulnerability (CVE-2026-99999). We have published a documentation article with detailed guidance on available mitigations and recommended actions for affected systems: https://www.akamai.com/cloud/guides/cve-2026-99999-pwnescape-mitigation/ We encourage all customers to review the article and apply the appropriate mitigations to their environments. If you have questions or need assistance, please open a Support ticket, or contact us at 855-454-6633 (+1-609-380-7100 Intl.) / support@linode.com.

The latest update from Akamai Cloud (Linode).

State

Resolved

Started

17 d ago

2026-10-15 17:27 UTC

Lasted

15 days

until 2026-10-30 15:06 UTC

Worst impact

Notice

Timeline

4 updates
Oct 15Oct 19Oct 23Oct 26Oct 30
NoticeUpdate postedDates in UTC

Identified

15 days 100%

Updates

Times in UTC

As posted by Akamai Cloud (Linode)

Resolved2026-10-30 15:06 UTC

We have completed our investigation and response to the “PwnEscape” Guest-to-Host Escape vulnerability (CVE-2026-99999). We have published a documentation article with detailed guidance on available mitigations and recommended actions for affected systems: https://www.akamai.com/cloud/guides/cve-2026-99999-pwnescape-mitigation/ We encourage all customers to review the article and apply the appropriate mitigations to their environments. If you have questions or need assistance, please open a Support ticket, or contact us at 855-454-6633 (+1-609-380-7100 Intl.) / support@linode.com.

Identified2026-10-17 05:07 UTC

Akamai has completed patching Compute hypervisors for the known vulnerabilities related to CVE-2026-99999, also referred to as “PwnEscape”, and we have not identified any exploitation on the Akamai platform. We recommend that customers upgrade Linode guest VMs using kernels from upstream OS vendors as those become available, especially for cases where less trusted workloads are being run within containers or nested virtualization. We are in the process of preparing images containing fixes from upstream vendors.

Identified2026-10-16 08:53 UTC

We have not identified any exploitation on the Akamai platform so far. As of now, our subject matter experts are continuing to work on patching server sets in phases across the Akamai platform. We are actively monitoring our platform while we perform the mitigation actions.

Identified2026-10-15 17:27 UTC

Akamai is aware of the recently published Guest-to-Host KVM Escape (CVE-2026-99999) vulnerability. Our teams have proactively identified its potential impact and are actively applying mitigations across our platform and infrastructure. There is potential for customer workload impact as a part of our platform response to this vulnerability. At this time, we have not observed evidence of this vulnerability being actively exploited on our platform. We will provide updates as additional information becomes available.

Akamai Cloud (Linode) in the last 90 days

Full history
90 days agoToday

Incidents in 90 days

27

Days with an incident

89

Median duration

6 h 29 min

This incident

55× the median

How long each incident lasted, on the day it started. The outlined bar is this incident.

15 days
median 6 h 29 min
90 days agoToday

Other Akamai Cloud (Linode) incidents

All incidents

Follow Akamai Cloud (Linode)

Your coding agent knows when Akamai Cloud (Linode) is down, and tells you when a failure is theirs, not yours. You can also get Akamai Cloud (Linode) incidents in a feed reader or in Slack.

Prompt
Install the outages.live MCP server, so that when something breaks you can tell if the cause is a provider we depend on and not my code. It reads the official status pages of cloud, AI, payment and developer providers and gives you their incidents as MCP tools.

Add it as a remote MCP server named "outages" at https://outages.cc/mcp (Streamable HTTP, no authentication), with your CLI command or your MCP config file.

Then:
1. Make sure it connects and shows the tools get_provider, list_feed and send_feedback.
2. Call get_provider with "linode" and tell me if Akamai Cloud (Linode) has a problem right now.
3. From now on, when a call to a third-party service fails or becomes slow, call get_provider for that service before you change my code.

Paste this into any coding agent. It adds the server with its own MCP setup.

RSS
https://outages.cc/feed.xml?providers=linode
Slack
/feed subscribe https://outages.cc/feed.xml?providers=linode

FAQ

Go from tracking outages to fixing production issues with Polylane.

Try Polylane