Customer Security Advisory: Remote code execution vulnerability in the Apache HTTP Server's HTTP/2 module
Akamai reports a remote code execution vulnerability in the Apache HTTP Server HTTP/2 module, tracked as CVE-2026-119618. The affected versions are Apache HTTP Server 2.4.55 through 2.4.70 with HTTP/2 enabled. Akamai is investigating the possible impact on the Akamai platform and infrastructure.
State
Investigating
Started
Ongoing for
1 h 36 min
Worst impact
Major outage
Timeline
1 updateInvestigating
1 h 36 min 100%
Updates
Times in UTCAs posted by Akamai
Akamai is aware of the recently published remote code execution (RCE) vulnerability in the Apache HTTP Server's HTTP/2 module (CVE-2026-119618). Our subject matter experts (SMEs) are actively investigating its potential impact across our platform and infrastructure. If the vulnerability is exploited, unauthenticated remote attackers can trigger heap corruption and potentially execute arbitrary code with the privileges of the web server process. The affected versions are Apache HTTP Server versions 2.4.55 through 2.4.70 (only servers with HTTP/2 enabled are affected). We will post more details for customers and partners with a valid Control Center login at https://community.akamai.com/customers/s/feed/0D5a700001ewU8ICAU as additional information becomes available. If you have questions or are experiencing an impact due to this issue, please use the Support Center in the Akamai Community or Akamai Control Center to contact Akamai Technical Support. Contact information is available at htt
Affected components
2Akamai in the last 90 days
Full historyIncidents in 90 days
31
Days with an incident
63
Median duration
22 h 26 min
This incident
93% shorter than the median
Other Akamai incidents
All incidentsAkamai·Email Systems Widespread Outage
Akamai email systems have a degraded service. The Customer Service, Documentation and Community email component is also affected. Akamai reports that the incident is under investigation. Akamai gives a workaround: use the Global Support phone numbers on www.akamai.com or +1-617-444-4699 for assistance.
Akamai·Property Manager Property Activation Errors
We became aware of an issue with Property Manager related to activating properties with errors indicating "cloudlet policy not found or not valid" blocking some property activations. The issue lasted between approximately 15:30 UTC on November 3, 2026 and 17:15 UTC on November 3, 2026. We can confirm that the issue is now resolved, and the service has resumed normal operation. Customers and partners can view additional details about the incident by logging in to: 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·Customer Security Advisory: CVE-2026-98432
The Akamai Customer Community is not available. This affects the Akamai Customer Community component and customer service, documentation, and community services. Akamai reports that the issue is resolved. The outage lasted from 30 October 2026 to 9 November 2026, about 10 days.
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 confirms that the issue is resolved.
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.
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.live/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.live/feed.xml?providers=akamai/feed subscribe https://outages.live/feed.xml?providers=akamaiFAQ
Go from tracking outages to fixing production issues with Polylane.
Try Polylane