Cyber Resilience

CVE-2025-58153

F5 Big-Ip Access Policy Manager 15.1.0 – 15.1.10.8

Published
15 October 2025
Modified
04 February 2026
Patch / advisory
CVSS Score v4 8.2
Click a component to see what it means
Raw vectorCVSS:4.0/AV:N/AC:H/AT:N/PR:N/UI:N/VC:N/VI:N/VA:H/SC:N/SI:N/SA:L/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.0022 12th percentile
Risk Priority 33 floored blend · peak EPSS

Summary

CVE-2025-58153 is a high-severity Improper Locking (CWE-667) vulnerability in F5 Big-Ip Access Policy Manager. Its CVSS base score is 8.2 (High).

Operationally, exploitation aligns with the MITRE ATT&CK technique Endpoint Denial of Service (T1499); ranked at the 12th percentile by exploit likelihood (below the median); it is not currently listed in the CISA KEV catalog.

EU & UK References

Vulnerability Data

Under undisclosed traffic conditions along with conditions beyond the attacker's control, hardware systems with a High-Speed Bridge (HSB) may experience a lockup of the HSB.  Note: Software versions which have reached End of Technical Support (EoTS) are not evaluated.

CWE(s)

Related Threats

MITRE ATT&CK Enterprise Techniques

T1499 Endpoint Denial of Service Impact
Adversaries may perform Endpoint Denial of Service (DoS) attacks to degrade or block the availability of services to users.
T1499.004 Application or System Exploitation Impact
Adversaries may exploit software vulnerabilities that can cause an application or system to crash and deny availability to users.
T1068 Exploitation for Privilege Escalation Privilege Escalation
Adversaries may exploit software vulnerabilities in an attempt to elevate privileges.
T1548 Abuse Elevation Control Mechanism Privilege Escalation
Adversaries may circumvent mechanisms designed to control privilege elevation to gain higher-level permissions.
Derived from this CVE’s CWE(s) via the direct CWE→ATT&CK cross-walk.

CVEs Like This One

CVE-2025-52585Same product: F5 Big-Ip Access Policy Manager
CVE-2025-41433Same product: F5 Big-Ip Access Policy Manager
CVE-2026-42920Same product: F5 Big-Ip Access Policy Manager
CVE-2026-42781Same product: F5 Big-Ip Access Policy Manager
CVE-2026-39459Same product: F5 Big-Ip Access Policy Manager
CVE-2025-20045Same product: F5 Big-Ip Access Policy Manager
CVE-2024-25560Same product: F5 Big-Ip Access Policy Manager
CVE-2025-41414Same product: F5 Big-Ip Access Policy Manager
CVE-2026-42409Same product: F5 Big-Ip Access Policy Manager
CVE-2024-41164Same product: F5 Big-Ip Access Policy Manager

Affected Assets

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

Mitigating Controls

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 include code reviews, static analysis, and concurrency standards that prevent improper locking.

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 race conditions and locking errors before release.

prevents

Secure development lifecycle includes concurrency and locking requirements that reduce improper locking defects.

prevents

Application security requirements can mandate proper lock acquisition/release patterns.

prevents

Secure architecture principles address thread-safety and resource synchronization.

prevents

Secure coding standards directly prohibit missing or incorrect lock usage.

prevents

Change management may catch locking issues introduced by modifications but does not prevent the weakness itself.

References