Live / Akamai / Incident
Akamai: Customer Security Advisory: PHP Remote Code Execution Vulnerabilities
Akamai · akamai.comResolved2026-10-29 01:52 UTC
Public — what happened
Summary
Akamai posted a security advisory on October 21, 2026 at 15:03 UTC about two newly published PHP remote code execution vulnerabilities, saying its experts were investigating and had released security updates. It said it found some of its systems and applications might be affected and began patching them, but found no evidence that its products, API calls, or Control Center were impacted. On October 23, Akamai said remediation was completed as of 20:06 UTC and again reported no evidence of impact. It later added a postmortem note pointing customers and partners to an incident summary report.
Affected
Akamai Customer Community
Timeline
- Started — 2026-10-21 15:03 UTC
- Investigating — 2026-10-21 15:03 UTC (2 updates)
- Identified — 2026-10-22 18:15 UTC
- Postmortem — 2026-10-29 01:52 UTC
- Resolved — 2026-10-23 20:18 UTC · 2 days after it started
What SquidGrid measured
SquidGrid measured 228 internet paths into Akamai’s network during this incident. None of them ran meaningfully slower than the same paths the day before.
With SquidGrid — where it starts on the route
Independent path health
The status page is the symptom. SquidGrid measures the paths that reach Akamai against their own baselines — whether the routes carrying your traffic degraded, at which handoff, and who owns that stretch.
🔒 Sign in to seeCustomers get the live Provider Assessment Report for Akamai: paths off baseline right now, where on the route conditions change, and its full incident track record.
Included with any paid plan.
Open the Akamai report →
More from Akamai
Covered in The Squid’s Ink, Week 44, 2026, our weekly internet health report.