CompaniesLinode (Akamai)Incidents
Linode (Akamai): Customer Security Advisory: Critical F5/NGINX Out-of-Band Vulnerabilities
CVEs mentioned
- CVE-2026-15176NGINX ngx_http_core_module vulnerabilityCVSS 8.1 highnames this CVE
- CVE-2026-93479NGINX map directive and regex matching vulnerabilityCVSS 8.1 highnames this CVE
- CVE-2026-97205NGINX ngx_http_core_module vulnerabilityCVSS 8.1 highnames this CVE
Only CVEs the vendor’s text names by id, or that its notice says it is not affected by. A mention is not a statement that the vulnerability caused this incident.
Timeline of updates
- investigating
Akamai is aware of the recently published F5/NGINX vulnerabilities (CVE-2026-15176, CVE-2026-97205, and CVE-2026-93479), and our teams are actively investigating their potential impact across our platform and infrastructure.
F5 has released out-of-band security patches addressing three critical severity vulnerabilities in NGINX Open Source and NGINX Plus. These vulnerabilities may allow unauthenticated attackers to trigger heap buffer overflows, which could cause a denial of service or potential remote code execution if ASLR is bypassed.
If you are running a vulnerable version of NGINX Open Source or NGINX Plus on a Linode instance, we recommend following guidance from F5/NGINX and applying available patches.
We will provide updates as additional information becomes available.
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 this record existed by then and has not been changed since, by anyone, Rewindex included.
How the archive is checked, and what it cannot prove.
First version captured
In the 2026-10-22 checkpoint, timestamped by FreeTSA and DigiCert on . Record hash
9bde52fb2ddb878b…
Impact, status and times are the vendor’s own, as last archived. View on status.linode.com (opens in new tab).
Linode (Akamai) profileRecent Linode (Akamai) incidentsMarkdownJSON