Customer Security Advisory: CVE-2026-98432

What to do

• Check whether you use Akamai Cloud (Linode) Customer Security Advisory in us. Check your stack

  Paste a package.json, lockfile, Terraform or a list of domains at down.guide/stack to see every provider you depend on.

• Confirm your retries, queues and scheduled jobs caught up after the 10d 3h it lasted.

  Anything that failed between 2026-10-30 18:10 UTC and 2026-11-09 21:23 UTC may need a replay.

• Subscribe to Akamai Cloud (Linode)'s feed to hear about the next one first. RSS feed

  https://down.guide/feed?provider=linode works in Slack (/feed subscribe), Discord feed bots and any RSS reader.

Updates from Akamai Cloud (Linode) 5

1. investigatingOct 30, 2026, 6:10 PM UTC

   Akamai is aware of the recently published remote code execution CVE-2026-98432. We are actively investigating and taking the appropriate mitigation actions, while we continue to monitor our platform in parallel. If you have questions or are experiencing an impact due to this issue, please reach out to us in a ticket at https://cloud.linode.com/support.

   provider

2. investigatingOct 30, 2026, 9:18 PM UTC

   We are continuing to investigate this issue. The appropriate subject matter experts are engaged. Subsequent updates around mitigation status will be posted as progress is made.

   provider

3. investigatingOct 31, 2026, 1:55 AM UTC

   We are in the process of deploying mitigations for the underlying known attack vector while we continue to analyze any other possible impact. Customers are strongly advised to apply OS updates from their upstream provider to their workloads as soon as those become available. At this time, we have no evidence of this vulnerability being exploited on the Akamai Compute platform.

   provider

4. investigatingNov 2, 2026, 10:55 AM UTC

   While we continue to deploy kernel patches across our infrastructure, we have also deployed network rules that drop IPv4 packets with optional headers on public and VPC interfaces. This eliminates the immediate remote attack vector and protects our infrastructure as well as customer workloads without impacting performance or functionality, and notably is not limited to only focusing on the MPTCP exploit, but the underlying vulnerability. We continue to track upstream OS provider security releases and will make updated distributions available to customers as they are released. Customers using the Linode provided kernel are likewise advised to deploy the latest version when it becomes available as well.

   provider

5. resolvedNov 9, 2026, 9:23 PM UTC

   We continue to monitor our systems and track upstream OS providers’ security releases; as of November 9, 2026, the majority of upstream vendors have provided updated kernel packages that include fixes for this vulnerability, and we recommend customers apply those updates to their Linodes. Customers using the Linode provided kernel are likewise advised to deploy the latest version as indicated on our kernels page . By applying IPv4 network rules to both public and VPC interfaces, we have already eliminated the immediate remote attack vector, addressing the root vulnerability rather than just the MPTCP exploit. We remain committed to improving our systems and reducing the risk of similar issues in the future.

   provider

Corrections

None so far.

Something wrong on this page? Report an error or send us a note. Every fix is listed here.