Cyber Resilience

CVE-2026-41225

F5 Big-Ip Access Policy Manager 17.1.0 – 17.1.3

Published
13 May 2026
Modified
24 June 2026
Patch / advisory
CVSS Score v4 8.6
Click a component to see what it means
Raw vectorCVSS:4.0/AV:N/AC:L/AT:N/PR:H/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X
EPSS Score 0.0027 19th percentile
Risk Priority 29 floored blend · peak EPSS

Summary

CVE-2026-41225 is a high-severity Incorrect Use of Privileged APIs (CWE-648) vulnerability in F5 Big-Ip Access Policy Manager. Its CVSS base score is 8.6 (High).

Operationally, exploitation aligns with the MITRE ATT&CK technique Abuse Elevation Control Mechanism (T1548); ranked at the 19th percentile by exploit likelihood (below the median); it is not currently listed in the CISA KEV catalog.

The strongest mitigations our analysis identified map to SA-11 (Developer Testing and Evaluation) and AC-3 (Access Enforcement) — see the control section below for these in your framework.

EU & UK References

Vulnerability Data

A vulnerability exists in iControl REST where a highly privileged, authenticated attacker with at least the Manager role can create configuration objects that allow running arbitrary commands. Note: Software versions which have reached End of Technical Support (EoTS) are not…

more

evaluated.

CWE(s)

Related Threats

MITRE ATT&CK Enterprise Techniques

T1548 Abuse Elevation Control Mechanism Privilege Escalation
Adversaries may circumvent mechanisms designed to control privilege elevation to gain higher-level permissions.
T1548.001 Setuid and Setgid Privilege Escalation
An adversary may abuse configurations where an application has the setuid or setgid bits set in order to get code running in a different (and possibly more privileged) user’s context.
Derived from this CVE’s CWE(s) via the direct CWE→ATT&CK cross-walk.

CVEs Like This One

CVE-2026-35062Same product: F5 Big-Ip Access Policy Manager
CVE-2026-39459Same product: F5 Big-Ip Access Policy Manager
CVE-2025-58153Same product: F5 Big-Ip Access Policy Manager
CVE-2026-42406Same product: F5 Big-Ip Access Policy Manager
CVE-2026-40462Same product: F5 Big-Ip Access Policy Manager
CVE-2026-41217Same product: F5 Big-Ip Access Policy Manager
CVE-2026-42937Same product: F5 Big-Ip Access Policy Manager
CVE-2026-42058Same product: F5 Big-Ip Access Policy Manager
CVE-2026-32673Same product: F5 Big-Ip Access Policy Manager
CVE-2024-41723Same product: F5 Big-Ip Access Policy Manager

Affected Assets

f5
big-ip access policy manager
21.0.0 · 17.1.0 — 17.1.3 · 17.5.0 — 17.5.1 · 16.1.0 — 16.1.6
f5
big-ip advanced firewall manager
21.0.0 · 17.1.0 — 17.1.3 · 17.5.0 — 17.5.1 · 16.1.0 — 16.1.6
f5
big-ip advanced web application firewall
21.0.0 · 17.1.0 — 17.1.3 · 17.5.0 — 17.5.1 · 16.1.0 — 16.1.6
f5
big-ip analytics
21.0.0 · 17.1.0 — 17.1.3 · 17.5.0 — 17.5.1 · 16.1.0 — 16.1.6
f5
big-ip application acceleration manager
21.0.0 · 17.1.0 — 17.1.3 · 17.5.0 — 17.5.1 · 16.1.0 — 16.1.6
f5
big-ip application security manager
21.0.0 · 17.1.0 — 17.1.3 · 17.5.0 — 17.5.1 · 16.1.0 — 16.1.6
f5
big-ip application visibility and reporting
21.0.0 · 17.1.0 — 17.1.3 · 17.5.0 — 17.5.1 · 16.1.0 — 16.1.6
f5
big-ip automation toolchain
21.0.0 · 17.1.0 — 17.1.3 · 17.5.0 — 17.5.1 · 16.1.0 — 16.1.6
f5
big-ip carrier-grade nat
21.0.0 · 17.1.0 — 17.1.3 · 17.5.0 — 17.5.1 · 16.1.0 — 16.1.6
f5
big-ip container ingress services
21.0.0 · 17.1.0 — 17.1.3 · 17.5.0 — 17.5.1 · 16.1.0 — 16.1.6
+11 more product configuration(s) — see NVD for full list

Mitigating Controls

Control response

Prevent
Stop it (NIST 800-53)

Detect
Catch it (NIST detect / respond)

Harden
Shrink the surface (DISA STIG)

Validate
Prove the fix (OWASP ASVS)
  • V3.5.2
  • V6.4.6

Mitigating Controls (NIST 800-53 r5) AI

Developer testing and evaluation can discover incorrect calls to privileged APIs before deployment.

Enforces authorization checks around privileged operations so that an API requiring elevated rights cannot be reached or misused without proper rights.

Least-privilege assignment directly reduces both the availability of privileged APIs and the blast radius when they are invoked incorrectly.

Security engineering principles include correct use of privileged interfaces and safe invocation patterns that stop the weakness from being introduced.

Mitigating Controls (NIST CSF 2.0) AI

Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→CSF cross-walk (authority under review) — links open the control.

PR.PS-06 mostly match
prevents

Secure SDLC practices directly enforce correct usage of privileged APIs during development.

Mitigating Controls (ISO/IEC 27001:2022 Annex A) AI

Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→ISO cross-walk (authority under review) — links open the control.

finds

Security testing can detect incorrect privileged API calls but does not prevent them at design time.

degrades

Restricting privileged utility programs limits the exposure of privileged APIs to misuse.

degrades

Privileged access rights directly govern the correct use of privileged APIs and reduce misuse.

prevents

Secure development lifecycle includes API usage standards that can prevent incorrect privileged calls.

prevents

Application security requirements can specify correct invocation of privileged APIs.

prevents

Secure architecture principles guide proper privilege separation and API usage.

References