rewindex

CompaniesAkamaiIncidents

Akamai: Customer Security Advisory: Node.js Brotli Remote Code Execution Vulnerabilities

No impact listedStatus: identifiededitedStarted Not resolved4 updateswww.akamaistatus.com (opens in new tab)

Affected components: Akamai Customer CommunityCustomer Service, Documentation and Community - Akamai Customer Community

Timeline of updates

  1. investigating

    Akamai is aware of the recently published remote code execution vulnerability: CVE-2026-111497.Our subject matter experts are actively investigating and taking the appropriate mitigation actions, while we continue to monitor our platform in parallel. We will provide updates as additional information becomes available.In the interest of time, we are providing you with the most current information available, which is subject to changes, corrections, and updates.

  2. investigating

    We are continuing to investigate this issue. Customers and partners can find more details on the Akamai Community: https://community.akamai.com/customers/s/feed/0D5a700001apcFhCAIWe (opens in new tab) will provide an update as we progress.

  3. investigating

    We are continuing to investigate this issue to evaluate any possible impact to customers and our platform, so far we don't have evidence of customer impact caused by this vulnerability. The appropriate subject matter experts are engaged. We will continue to provide updates until we have a clearer picture about the evaluation and the mitigation plan. Subsequent updates around mitigation status will be posted as progress is made.

  4. identified

    We will continue to investigate and evaluate any possible impact to customers and our platform over the weekend. So far the investigation has not shown evidence of customer impact caused by this vulnerability. The appropriate subject matter experts are engaged. We will continue to provide updates until we have a clearer picture about the evaluation and the mitigation plan. Subsequent updates around mitigation status will be posted as progress is made.

Changes Rewindex caught on this incident

Archive proof

Rewindex commits each version of an incident it captures to a daily checkpoint, chains it to the day before, and has the checkpoint timestamped by FreeTSA and DigiCert. That proves these records existed by then and have not been changed since, by anyone, Rewindex included.

How the archive is checked, and what it cannot prove.

Rewindex captured a newer version after the last checkpoint; the next run () commits it.

Impact, status and times are the vendor’s own, as last archived. View on www.akamaistatus.com (opens in new tab).

Akamai profileRecent Akamai incidentsMarkdownJSON