Customer Security Advisory: PHP Remote Code Execution Vulnerabilities
Customers and partners can find an incident summary report, here: [https://community.akamai.com/customers/s/feed/0D5a700001aNd78CAC](https://community.akamai.com/customers/s/feed/0D5a700001aNd78CAC)
The latest update from Akamai.
State
Resolved
Started
11 d ago
2026-10-21 15:03 UTC
Lasted
2 days
until 2026-10-23 20:18 UTC
Worst impact
Notice
Timeline
5 updatesInvestigating
27 h 12 min 51%
Identified
26 h 3 min 49%
Updates
Times in UTCAs posted by Akamai
Customers and partners can find an incident summary report, here: [https://community.akamai.com/customers/s/feed/0D5a700001aNd78CAC](https://community.akamai.com/customers/s/feed/0D5a700001aNd78CAC)
We can confirm that remediation efforts for the reported vulnerabilities, CVE-2026-109618 and CVE-2026-109619, were completed as of 20:06 UTC on October 23, 2026.We have found no evidence that these vulnerabilities impacted Akamai products, API calls, or Control Center. Customers and partners can view additional details by logging in to Control Center or contacting Akamai Support.We apologize for any concern this advisory may have caused and thank you for your patience and continued support. We remain committed to improving our systems and reducing the risk of similar issues in the future.
Update - We are continuing to assess the reported vulnerabilities (CVE-2026-109618 and CVE-2026-109619) across our systems and applications. Our initial assessment has identified systems and applications that may be affected, and remediation efforts, including patching, are actively underway.At this time, we have found no evidence indicating that these vulnerabilities have impacted our products, API calls, or Control Center. We will continue to review our systems and applications to assess potential exposure and identify any additional remediation requirements. Mitigation efforts are being prioritized based on the assessment of potential risk and impact. We remain focused on addressing identified vulnerabilities and will provide further updates as additional information becomes available. We will provide further updates as we make progress.
We are continuing to assess the reported vulnerabilities (CVE-2026-109618 and CVE-2026-10961) across our systems and applications. Our initial assessment has identified systems and applications that may be affected, and remediation efforts, including patching, are actively underway.At this time, we have found no evidence indicating that these vulnerabilities have impacted our products, API calls, or Control Center. We will continue to review our systems and applications to assess potential exposure and identify any additional remediation requirements.Mitigation efforts are being prioritized based on the assessment of potential risk and impact. We remain focused on addressing identified vulnerabilities and will provide further updates as additional information becomes available. We will provide further updates as we make progress.
Akamai is aware of the recently published remote code execution vulnerabilities CVE-2026-109618 and CVE-2026-10961). Our subject matter experts are actively investigating and taking the appropriate measures. We have released security updates to address these CVEs and monitor for exploitation attempts. We are actively monitoring our platform while we perform the mitigation actions. If you have questions or are experiencing an impact due to this issue, please use the Support Center on Akamai Community (https://community.akamai.com/customers/s/support), or Akamai Control Center, to contact Akamai Technical Support. Contact information is available at https://www.akamai.com/us/en/support/.
Affected components
1Akamai in the last 90 days
Full historyIncidents in 90 days
32
Days with an incident
58
Median duration
22 h 16 min
This incident
2.4× the median
Other Akamai incidents
All incidentsAkamai·Customer Security Advisory: CVE-2026-98432
Akamai reports an operational issue with the Akamai Customer Community and related Customer Service and Documentation components. Akamai is investigating. More details are on the Akamai Community page.
Akamai·Performance Degradation for Customers in Mumbai and Chennai
Akamai reports performance degradation for customers in Mumbai and Chennai. The affected components are Edge Delivery and Content Delivery - Edge Delivery. Akamai is investigating, and the packet loss has subsided.
Akamai·Enterprise Application Access (EAA) Connector Issues
We can confirm that the issue was mitigated at 08:30 UTC on 27 October 2026, and the service has resumed normal operation. Customers and partners can view additional details about the incident by logging in to: https://community.akamai.com/customers/s/feed/0D5a700001bU4YFCA0 or reaching out to Akamai Support. We apologize for the impact and thank you for your patience and continued support. We are committed to making continuous improvements to make our systems better and prevent a recurrence of this issue.
Akamai·Edge Delivery issues between Indonesia and Singapore
Edge Delivery does not work correctly between Indonesia and Singapore. Content Delivery - Edge Delivery is affected. Akamai reports that the state is monitoring.
Akamai·Customer Security Advisory: Brotli Remote Code Execution Vulnerabilities
Akamai reports that Brotli remote code execution vulnerabilities affect the Akamai Customer Community components. Akamai states that most of its platform is not affected by this CVE. Akamai is investigating the issue and will give an update.
Follow Akamai
Your coding agent knows when Akamai is down, and tells you when a failure is theirs, not yours. You can also get Akamai 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 "akamai" and tell me if Akamai 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=akamai/feed subscribe https://outages.cc/feed.xml?providers=akamaiFAQ
Go from tracking outages to fixing production issues with Polylane.
Try Polylane