BIG-IP: Least Privilege Violation
CVE-2026-39459 is a high-severity least privilege violation vulnerability in BIG-IP from F5, with a CVSS 3.1 base score of 7.2 out of 10. It can be exploited remotely over the network by an attacker with administrator privileges, without any action from a user. The record lists versions 21.0.0.2, 17.5.1.6, 17.1.3.2 as the first without the flaw, so updating BIG-IP to one of those releases or later removes the exposure. There is no confirmed exploitation so far. EPSS estimates a 0.26% chance of exploitation within 30 days, which is low compared with other CVEs.
High severity with no evidence of exploitation so far.
What to do
- Update BIG-IP to 21.0.0.2 or 17.5.1.6 or 17.1.3.2, whichever matches your release line, or a later version.
- Read the advisory on my.f5.com for workarounds and exact fixed builds.
Affected products and versions
| Vendor | Product | Affected versions | Fixed in |
|---|---|---|---|
| F5 | BIG-IP | 21.0.0 up to, but not including, 21.0.0.2; 17.5.0 up to, but not including, 17.5.1.6; 17.1.0 up to, but not including, 17.1.3.2; 16.1.0 and later | 21.0.0.2, 17.5.1.6, 17.1.3.2 |
| F5 | Big-ip Access Policy Manager | 17.1.0 through 17.1.3; 17.5.0 through 17.5.1; 16.1.0 through 16.1.6; 21.0.0 | Not stated |
| F5 | Big-ip Advanced Firewall Manager | 17.1.0 through 17.1.3; 17.5.0 through 17.5.1; 16.1.0 through 16.1.6; 21.0.0 | Not stated |
| F5 | Big-ip Advanced Web Application Firewall | 17.1.0 through 17.1.3; 17.5.0 through 17.5.1; 16.1.0 through 16.1.6; 21.0.0 | Not stated |
| F5 | Big-ip Analytics | 17.1.0 through 17.1.3; 17.5.0 through 17.5.1; 16.1.0 through 16.1.6; 21.0.0 | Not stated |
| F5 | Big-ip Application Acceleration Manager | 17.1.0 through 17.1.3; 17.5.0 through 17.5.1; 16.1.0 through 16.1.6; 21.0.0 | Not stated |
| F5 | Big-ip Application Security Manager | 17.1.0 through 17.1.3; 17.5.0 through 17.5.1; 16.1.0 through 16.1.6; 21.0.0 | Not stated |
| F5 | Big-ip Application Visibility And Reporting | 17.1.0 through 17.1.3; 17.5.0 through 17.5.1; 16.1.0 through 16.1.6; 21.0.0 | Not stated |
| F5 | Big-ip Automation Toolchain | 17.1.0 through 17.1.3; 17.5.0 through 17.5.1; 16.1.0 through 16.1.6; 21.0.0 | Not stated |
| F5 | Big-ip Carrier-grade Nat | 17.1.0 through 17.1.3; 17.5.0 through 17.5.1; 16.1.0 through 16.1.6; 21.0.0 | Not stated |
| F5 | Big-ip Container Ingress Services | 17.1.0 through 17.1.3; 17.5.0 through 17.5.1; 16.1.0 through 16.1.6; 21.0.0 | Not stated |
| F5 | Big-ip Ddos Hybrid Defender | 17.1.0 through 17.1.3; 17.5.0 through 17.5.1; 16.1.0 through 16.1.6; 21.0.0 | Not stated |
| F5 | Big-ip Domain Name System | 17.1.0 through 17.1.3; 17.5.0 through 17.5.1; 16.1.0 through 16.1.6; 21.0.0 | Not stated |
| F5 | Big-ip Edge Gateway | 17.1.0 through 17.1.3; 17.5.0 through 17.5.1; 16.1.0 through 16.1.6; 21.0.0 | Not stated |
| F5 | Big-ip Fraud Protection Service | 17.1.0 through 17.1.3; 17.5.0 through 17.5.1; 16.1.0 through 16.1.6; 21.0.0 | Not stated |
| F5 | Big-ip Global Traffic Manager | 17.1.0 through 17.1.3; 17.5.0 through 17.5.1; 16.1.0 through 16.1.6; 21.0.0 | Not stated |
| F5 | Big-ip Link Controller | 17.1.0 through 17.1.3; 17.5.0 through 17.5.1; 16.1.0 through 16.1.6; 21.0.0 | Not stated |
| F5 | Big-ip Local Traffic Manager | 17.1.0 through 17.1.3; 17.5.0 through 17.5.1; 16.1.0 through 16.1.6; 21.0.0 | Not stated |
| F5 | Big-ip Policy Enforcement Manager | 17.1.0 through 17.1.3; 17.5.0 through 17.5.1; 16.1.0 through 16.1.6; 21.0.0 | Not stated |
| F5 | Big-ip SSL Orchestrator | 17.1.0 through 17.1.3; 17.5.0 through 17.5.1; 16.1.0 through 16.1.6; 21.0.0 | Not stated |
| F5 | Big-ip Webaccelerator | 17.1.0 through 17.1.3; 17.5.0 through 17.5.1; 16.1.0 through 16.1.6; 21.0.0 | Not stated |
| F5 | Big-ip Websafe | 17.1.0 through 17.1.3; 17.5.0 through 17.5.1; 16.1.0 through 16.1.6; 21.0.0 | Not stated |
Version data comes from the organisation that assigned the CVE. Confirm against the vendor advisory before deciding you are unaffected.
How the severity score breaks down
- Attack vector
- NetworkCan be exploited remotely over a network, including the internet.
- Attack complexity
- LowNo special conditions are needed; the attack works reliably.
- Privileges required
- HighAdministrator-level access is required first.
- User interaction
- NoneNo action by a victim is required.
- Scope
- UnchangedImpact stays within the vulnerable component.
- Confidentiality
- HighAll data handled by the component can be read.
- Integrity
- HighData or code can be modified at will.
- Availability
- HighThe component can be taken down completely.
Vector: CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H. Scored by CNA (f5.com).
| Scoring system | Score | Severity | Scored by |
|---|---|---|---|
| CVSS 4.0 | 8.6 | High | CNA (f5.com) |
| CVSS 3.1 | 7.2 | High | CNA (f5.com) |
Official description
A vulnerability exists in iControl REST and the TMOS Shell (tmsh) 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 evaluated.
Source: the CVE record as published by its numbering authority, via NVD and CVE.org.
The underlying weakness: Least Privilege Violation
The elevated privilege level required to perform operations such as chroot() should be dropped immediately after the operation is performed.
How developers prevent this class of flaw
- Very carefully manage the setting, management, and handling of privileges. Explicitly manage trust zones in the software.
- Follow the principle of least privilege when assigning access rights to entities in a software system.
- Compartmentalize the system to have safe areas where trust boundaries can be unambiguously drawn. Do not allow sensitive data to go outside of the trust boundary and always be careful when interfacing with a compartment outside of the safe area. Ensure that appropriate compartmentalization is built into the system design, and the compartmentalization allows for and reinforces privilege separation functionality. Architects and designers should rely on the principle of least privilege to decide the appropriate time to use privileges and the time to drop privileges.
Timeline
- CVE record published.
- CISA published its SSVC assessment (exploitation: none, automatable: no, technical impact: total).
- Record last changed materially (score, affected products, status or references).
References
Advisories
- my.f5.com/manage/s/article/K000160863Mitigation
Other vulnerabilities in BIG-IP
- 9.8 Critical severity
F5 BIG-IP APM Heap-based Buffer Overflow Exploited
- 8.8 High severity
- 7.5 High severity
- 8.7 High severity
- 8.7 High severity
- 7.5 High severity
Recent Least Privilege Violation vulnerabilities
- 7.8 High severity
- 7.8 High severity
- 8.8 High severity
- 8.8 High severity
- 7.0 High severity
- 7.3 High severity
Spotted an error? Tell us.