Customer Security Advisory: PHP Remote Code Execution Vulnerabilities
On October 10, 2026, Akamai became aware of two zero-day remote code execution \(RCE\) vulnerabilities affecting the PHP core engine, tracked as CVE-2026-109618 and CVE-2026-109619. Akamai began a platform-wide investigation, and deployed global Web Application Firewall \(WAF\) mitigation rules on October 21, 2026, and carried out remediation protocols across potentially impacted infrastructure. At this time, Akamai has observed no evidence that these vulnerabilities impacted core Akamai products, API calls, or the Akamai Control Center \(ACC\). The potential scope included PHP Core, Linode Speed Test Services, and Quick Deploy Marketplace applications. As a precaution, Akamai temporarily disabled Cloud Infrastructure Speed Tests while teams isolated and rebuilt related systems. Akamai deployed protective WAF rules across the Akamai edge platform to inspect and mitigate potential exploitation attempts. Marketplace application templates were also updated so new Linode Compute Marketplac
The latest update from Akamai Cloud (Linode).
State
Resolved
Started
11 d ago
2026-10-21 14:44 UTC
Lasted
2 days
until 2026-10-23 20:37 UTC
Worst impact
Notice
Timeline
5 updatesInvestigating
2 h 57 min 5%
Identified
2 days 95%
Updates
Times in UTCAs posted by Akamai Cloud (Linode)
On October 10, 2026, Akamai became aware of two zero-day remote code execution \(RCE\) vulnerabilities affecting the PHP core engine, tracked as CVE-2026-109618 and CVE-2026-109619. Akamai began a platform-wide investigation, and deployed global Web Application Firewall \(WAF\) mitigation rules on October 21, 2026, and carried out remediation protocols across potentially impacted infrastructure. At this time, Akamai has observed no evidence that these vulnerabilities impacted core Akamai products, API calls, or the Akamai Control Center \(ACC\). The potential scope included PHP Core, Linode Speed Test Services, and Quick Deploy Marketplace applications. As a precaution, Akamai temporarily disabled Cloud Infrastructure Speed Tests while teams isolated and rebuilt related systems. Akamai deployed protective WAF rules across the Akamai edge platform to inspect and mitigate potential exploitation attempts. Marketplace application templates were also updated so new Linode Compute Marketplac
Akamai has completed its assessment of the recently published PHP remote code execution vulnerabilities (CVE-2026-109618 and CVE-2026-109619) across our platform and infrastructure, and mitigation efforts are complete. Cloud Infrastructure Speed Tests will remain offline in the near term. We plan to bring them back online in the near future. If you are running a vulnerable version of PHP on a Linode instance, we recommend following guidance from the upstream vendor (PHP) and applying upstream patches as they become available. We appreciate your patience while our teams completed this work.
Akamai is aware of the recently published (CVE-2026-109618 and CVE-2026-109619) vulnerabilities and our teams are actively investigating its potential impact across our platform and infrastructure. As a part of ongoing mitigation efforts, our Cloud Infrastructure Speed Tests will be unavailable. If you are running a vulnerable version of PHP on a Linode instance, we recommend following guidance from the upstream vendor (PHP) and applying upstream patches as they become available. We will provide updates as additional information becomes available.
Updated Guidance after assessment: Akamai is aware of the recently published (CVE-2026-109618 and CVE-2026-109619) vulnerabilities and our teams are actively investigating its potential impact across our platform and infrastructure. As a part of ongoing mitigation efforts, our Cloud Infrastructure Speed Tests will be unavailable. If you are running a vulnerable version of PHP on a Linode instance, we recommend following guidance from the upstream vendor (PHP) and applying upstream patches as they become available. We will provide updates as additional information becomes available.
Akamai is aware of the recently published (CVE-2026-109618 and CVE-2026-109619) vulnerabilities and our teams are actively investigating its potential impact across our platform and infrastructure. As a part of ongoing mitigation efforts, some Quick Deploy Apps, speed test pages, and parts of the website may be unavailable. If you are running a vulnerable version of PHP on a Linode instance, we recommend following guidance from the upstream vendor (PHP) and applying upstream patches as they become available. We will provide updates as additional information becomes available.
Akamai Cloud (Linode) in the last 90 days
Full historyIncidents in 90 days
27
Days with an incident
89
Median duration
6 h 29 min
This incident
8.3× the median
Other Akamai Cloud (Linode) incidents
All incidentsAkamai Cloud (Linode)·Service Issue - US-Southeast (Atlanta)
A service issue affects US-Southeast (Atlanta). Akamai Cloud (Linode) reports that the region has degraded performance. Akamai Cloud (Linode) is still investigating the issue.
Akamai Cloud (Linode)·Customer Security Advisory: CVE-2026-98432
Akamai Cloud (Linode) reports a security advisory for CVE-2026-98432. Akamai states that it is investigating and is deploying mitigations for the known attack vector. Akamai advises customers to apply OS updates from their upstream provider when those updates become available.
Akamai Cloud (Linode)·Service Issue - Block Storage (BR-GRU)
Block Storage does not work in the BR-GRU (São Paulo) region. Akamai Cloud reports that a fix is in place and the state is monitoring.
Akamai Cloud (Linode)·Connectivity Issue between ID-CGK (Jakarta) and SG-SIN-2 (Singapore 2)
Akamai Cloud reports a connectivity problem between ID-CGK (Jakarta) and SG-SIN-2 (Singapore 2). The service is degraded in these two regions. Akamai Cloud moved the incident to monitoring and continues to monitor the impact.
Akamai Cloud (Linode)·Connectivity Issue - Dallas Data Center (IPv6 Traffic to Google)
This issue is considered resolved.
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.
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.
https://outages.cc/feed.xml?providers=linode/feed subscribe https://outages.cc/feed.xml?providers=linodeFAQ
Go from tracking outages to fixing production issues with Polylane.
Try Polylane