Live  /  Akamai  /  Incident

Akamai: Customer Security Advisory: Brotli Remote Code Execution Vulnerabilities [CVE-2026-111497]

Akamai · akamai.comResolved2026-11-03 17:13 UTC
Public — what happened

Summary

Akamai said it began looking into a newly published remote code execution vulnerability in Brotli (CVE-2026-111497) on October 23, 2026, and that its experts were working on mitigation while monitoring its platform. It said it found no evidence of customer impact, and on October 26 it noted the issue's scope had widened beyond node.js to any outside data handled by the Brotli decoder. By October 28 Akamai said most of its platform was not affected, though it was still checking remaining products. On November 3 it marked the matter resolved, saying it finished hardening its platform around 23:00 UTC on November 2 and detected no unauthorized access or impact to customer environments.

Affected

Akamai Customer Community

As listed on Akamai’s status page.

Timeline

Source of record: provider status page. Summary written by SquidGrid from the provider’s published updates; times in UTC.

What SquidGrid measured

SquidGrid measured 237 internet paths into Akamai’s network during this incident. None of them ran meaningfully slower than the same paths the day before.

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 see
Customers 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.

The full archive is on the Akamai status & history page.

Related: Akamai status & history. SquidGrid is not affiliated with Akamai.