Live / Akamai / Incident
Akamai: Customer Security Advisory: CVE-2026-98432
Akamai · akamai.comResolved2026-11-09 21:14 UTC
Public — what happened
Summary
Akamai said on 2026-10-30 that it was looking into a newly published security vulnerability, CVE-2026-98432, which allows remote code execution, and that it was taking protective steps while monitoring its platform. Over the following days it repeated that the investigation was continuing and pointed customers and partners to its community site for details. On 2026-11-09 Akamai marked the matter resolved, saying most of its platform is not exposed to the attack method involved and that fixes for other exposed, vulnerable systems were finished.
Affected
Customer Security Advisory
Timeline
- Started — 2026-10-30 18:03 UTC
- Investigating — 2026-10-30 18:03 UTC (4 updates)
- Resolved — 2026-11-09 21:14 UTC · 10 days after it started
What SquidGrid measured
SquidGrid measured 235 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 45, 2026, our weekly internet health report.