Skip to main content
Akamai

Customer Security Advisory: Critical F5/NGINX Out-of-Band Vulnerabilities

Degraded Lasted 1d 1h · started · Akamai's page

Level
confirmed
Worst impact
Degraded
Regions
us
Down Index
37of 100

What to do

  • Check whether you use Akamai in us. Check your stack

    Paste a package.json, lockfile, Terraform or a list of domains at down.guide/stack to see every provider you depend on.
  • Confirm your retries, queues and scheduled jobs caught up after the 1d 1h it lasted.

    Anything that failed between 2026-10-22 20:17 UTC and 2026-10-23 21:55 UTC may need a replay.
  • Subscribe to Akamai's feed to hear about the next one first. RSS feed

    https://down.guide/feed?provider=akamai works in Slack (/feed subscribe), Discord feed bots and any RSS reader.

Updates from Akamai 4

  1. 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 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, we recommend following guidance from F5/NGINX and applying available patches.We will post more details for customers and partners with a valid Control Center login at https://community.akamai.com/customers/s/group/0F90f000000DFgx/service-incident-notifications as additional information becomes available. If you have questions or are experiencing an impact due to this issue, please use the Support Center on Akamai Community, or Akamai Control Center, to contact Akamai Technical Support. Contact information is available at https://www.akamai.com/us/en/support/.

    provider

  2. identified

    Akamai continues to investigate the potential impact of the recently published F5/NGINX vulnerabilities (CVE-2026-15176, CVE-2026-97205, and CVE-2026-93479) across our platform and infrastructure. Our teams are taking action where necessary and will provide additional updates as more information becomes available.Customers and partners with a valid Control Center login can find more details at https://community.akamai.com/customers/s/group/0F90f000000DFgx/service-incident-notifications.If you have questions or are experiencing impact related to this issue, please use the Support Center on Akamai Community or Akamai Control Center to contact Akamai Technical Support. Contact information is available at https://www.akamai.com/us/en/support/.

    provider

  3. monitoring

    Akamai continues to investigate the potential impact of the recently published F5/NGINX vulnerabilities (CVE-2026-15176, CVE-2026-97205, and CVE-2026-93479) across our platform and infrastructure.As part of our initial assessment, we included EAA, MFA, and SIA in the affected component selection. Based on our investigation to date, we have determined that these offerings are not vulnerable to these CVEs and have updated the affected component selection accordingly. We apologize for any concern this may have caused.Our teams continue to monitor the situation closely and respond where necessary. We will update the affected components as our investigation progresses.Customers and partners with a valid Control Center login can find more details at https://community.akamai.com/customers/s/group/0F90f000000DFgx/service-incident-notifications.If you have questions or are experiencing impact related to this issue, please use the Support Center on Akamai Community or Akamai Control Center to contact Akamai Technical Support. Contact information is available at https://www.akamai.com/us/en/support/.

    provider

  4. monitoring

    Akamai continues to investigate the potential impact of the recently published F5/NGINX vulnerabilities (CVE-2026-15176, CVE-2026-97205, and CVE-2026-93479) across our platform and infrastructure. Customers and partners with a valid Control Center login can find more details at https://community.akamai.com/customers/s/group/0F90f000000DFgx/service-incident-notifications. If you have questions or are experiencing impact related to this issue, please use the Support Center on Akamai Community or Akamai Control Center to contact Akamai Technical Support. Contact information is available at https://www.akamai.com/us/en/support/.

    provider

Reports count in aggregate; nothing about you is shown.

Corrections

None so far.

Something wrong on this page? Report an error or send us a note. Every fix is listed here.

Questions about DWN-974d88899d

Is Akamai still down?

No, this incident was resolved 2026-10-23 21:55 UTC. For Akamai's live state, see https://down.guide/akamai.

How long did it last?

1d 1h, from 2026-10-22 20:17 UTC to 2026-10-23 21:55 UTC, by the times Akamai posted.

What was affected?

Akamai named in us.

What caused it?

Akamai hasn't published a root cause. If it does, it shows here.

Where does this come from?

Akamai's official status page, https://www.akamaistatus.com, quoted verbatim. down.guide's own probes, reports and social counts are labeled as ours.