Is CVE-2026-40067 exploited in the wild?

No. Junglewise Threat Intelligence has no report of CVE-2026-40067 being exploited in the wild.

How severe is CVE-2026-40067?

High severity, with a CVSS score of 7.5, published 13 May 2026.

Which products and versions are affected?

F5 BIG-IP APM Undisclosed (EoTS versions excluded); F5 Big-Ip Access Policy Manager 17.5.0 to 17.5.1, 17.1.0 to 17.1.3, 16.1.0 to 16.1.6, 21.0.0.

Is there a fix for CVE-2026-40067?

No fixed version is recorded yet. Check the vendor's advisory in the references below. If you run it, Junglewise drafts a mitigation that fits your setup and applies it once you approve, with senior security engineers behind it.

How is CVE-2026-40067 attacked?

It is attacked over the network, in a network appliance.

Am I affected by CVE-2026-40067?

Check whether you run F5 BIG-IP APM or F5 Big-Ip Access Policy Manager at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

CVE-2026-40067: F5 BIG-IP APM buffer overflow in apmd process

CVE-2026-40067 · Severity: high · CVSS 7.5 · Published 2026-05-13

F5 BIG-IP Access Policy Manager (APM) is a solution used to manage secure remote access to corporate applications. A vulnerability has been identified where specific network traffic can cause the system's policy management process to crash. This results in a denial-of-service, potentially preventing users from logging in or accessing protected resources.

Technologies: F5 BIG-IP APM, F5 Big-Ip Access Policy Manager. Vendors: F5.

Quick answers

Is CVE-2026-40067 exploited in the wild?: No. Junglewise Threat Intelligence has no report of CVE-2026-40067 being exploited in the wild.
How severe is CVE-2026-40067?: High severity, with a CVSS score of 7.5, published 13 May 2026.
Which products and versions are affected?: F5 BIG-IP APM Undisclosed (EoTS versions excluded); F5 Big-Ip Access Policy Manager 17.5.0 to 17.5.1, 17.1.0 to 17.1.3, 16.1.0 to 16.1.6, 21.0.0.
Is there a fix for CVE-2026-40067?: No fixed version is recorded yet. Check the vendor's advisory in the references below. If you run it, Junglewise drafts a mitigation that fits your setup and applies it once you approve, with senior security engineers behind it.
How is CVE-2026-40067 attacked?: It is attacked over the network, in a network appliance.
Am I affected by CVE-2026-40067?: Check whether you run F5 BIG-IP APM or F5 Big-Ip Access Policy Manager at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

Technical details

A classic buffer overflow (CWE-120) exists in the F5 BIG-IP APM 'apmd' process when an access policy is configured on a virtual server. The vulnerability is triggered by 'undisclosed traffic' and does not require authentication or user interaction. An attacker can exploit this to terminate the apmd process, leading to a denial-of-service (DoS) condition for access policy enforcement. F5 has released updates for several branches, including 21.0.0.1, 17.5.1.4, and 17.1.3.1, to address the issue.

Affected products

F5 BIG-IP Access Policy Manager 17.5.0 to 17.5.1, 17.1.0 to 17.1.3, 16.1.0 to 16.1.6, 21.0.0

Timeline

2026-05-13: advisory: Initial advisory published by F5 Networks
2026-05-13: disclosed

References

https://my.f5.com/manage/s/article/K000161056

This page as Markdown. Free to reuse under CC BY 4.0 with a link back.