CVE-2026-40699 — BIG-IP Configuration utility vulnerability
A vulnerability exists in the undisclosed pages in the Configuration utility that may allow a low-privileged authenticated attacker to access to undisclosed sensitive information. Note: Software versions which have reached End of Technical Support (EoTS) are not evaluated.
Who exploits it and how urgent it is
A 0–100 score combining confirmed exploitation, ransomware and APT use, public exploits, EPSS and severity.
How the score was calculated
- EPSS 0.4% (30-day exploitation probability)+5
- Technical severity (medium)+3
The score orders the patch queue; it does not replace your asset context (internet exposure, criticality, compensating controls).
Triage
Is it exploited, how likely is exploitation, what does it touch, and how severe do the sources call it.
CISA SSVC assessment CISA
Three decision points CISA publishes for the CVEs it assesses (SSVC 2.0.3). A stakeholder decision, not a severity score.
Remediation
Fixes and mitigations documented by the sources — linked to the original advisory.
- Documented mitigation — my.f5.com (NIST National Vulnerability Database)
First 24 hours
Ordered from the record’s own fields — exposure first, because you cannot patch what you have not found. A rule-generated starting point.
- Identify exposed assets running the affected vendor/product/version combinations (F5 BIG-IP, F5 Big-ip Access Policy Manager, F5 Big-ip Advanced Firewall Manager…).
- Apply the documented mitigations until a definitive fix is available.
- Search available logs for exploit probes, errors and authentication anomalies.
Affected scope
Vendor, product and versions as the sources word them.
| Vendor | Product | Versions | Status | Source |
|---|---|---|---|---|
| F5 | BIG-IP | ≥ 16.1.0≥ 17.1.0 and < 17.1.3.1≥ 17.5.0 and < 17.5.1.4≥ 21.0.0 and < 21.0.0.1 | Vulnerable | CVE Program (cve.org) e CISA ADP |
| F5 | Big-ip Access Policy Manager | ≥ 17.5.0 and ≤ 17.5.1≥ 16.1.0 and ≤ 16.1.6≥ 17.1.0 and ≤ 17.1.3 | Vulnerable | NIST National Vulnerability Database |
| F5 | Big-ip Advanced Firewall Manager | ≥ 17.1.0 and ≤ 17.1.3≥ 17.5.0 and ≤ 17.5.1≥ 16.1.0 and ≤ 16.1.6 | Vulnerable | NIST National Vulnerability Database |
| F5 | Big-ip Advanced Web Application Firewall | ≥ 17.1.0 and ≤ 17.1.3≥ 17.5.0 and ≤ 17.5.1≥ 16.1.0 and ≤ 16.1.6 | Vulnerable | NIST National Vulnerability Database |
| F5 | Big-ip Analytics | ≥ 16.1.0 and ≤ 16.1.6≥ 17.5.0 and ≤ 17.5.1≥ 17.1.0 and ≤ 17.1.3 | Vulnerable | NIST National Vulnerability Database |
| F5 | Big-ip Application Acceleration Manager | ≥ 17.1.0 and ≤ 17.1.3≥ 17.5.0 and ≤ 17.5.1≥ 16.1.0 and ≤ 16.1.6 | Vulnerable | NIST National Vulnerability Database |
| F5 | Big-ip Application Security Manager | ≥ 16.1.0 and ≤ 16.1.6≥ 17.5.0 and ≤ 17.5.1≥ 17.1.0 and ≤ 17.1.3 | Vulnerable | NIST National Vulnerability Database |
| F5 | Big-ip Application Visibility And Reporting | ≥ 16.1.0 and ≤ 16.1.6≥ 17.5.0 and ≤ 17.5.1≥ 17.1.0 and ≤ 17.1.3 | Vulnerable | NIST National Vulnerability Database |
| F5 | Big-ip Automation Toolchain | ≥ 16.1.0 and ≤ 16.1.6≥ 17.1.0 and ≤ 17.1.3≥ 17.5.0 and ≤ 17.5.1 | Vulnerable | NIST National Vulnerability Database |
| F5 | Big-ip Carrier-grade Nat | ≥ 16.1.0 and ≤ 16.1.6≥ 17.5.0 and ≤ 17.5.1≥ 17.1.0 and ≤ 17.1.3 | Vulnerable | NIST National Vulnerability Database |
| F5 | Big-ip Container Ingress Services | ≥ 16.1.0 and ≤ 16.1.6≥ 17.1.0 and ≤ 17.1.3≥ 17.5.0 and ≤ 17.5.1 | Vulnerable | NIST National Vulnerability Database |
| F5 | Big-ip Ddos Hybrid Defender | ≥ 16.1.0 and ≤ 16.1.6≥ 17.5.0 and ≤ 17.5.1≥ 17.1.0 and ≤ 17.1.3 | Vulnerable | NIST National Vulnerability Database |
| F5 | Big-ip Domain Name System | ≥ 16.1.0 and ≤ 16.1.6≥ 17.5.0 and ≤ 17.5.1≥ 17.1.0 and ≤ 17.1.3 | Vulnerable | NIST National Vulnerability Database |
| F5 | Big-ip Edge Gateway | ≥ 17.1.0 and ≤ 17.1.3≥ 17.5.0 and ≤ 17.5.1≥ 16.1.0 and ≤ 16.1.6 | Vulnerable | NIST National Vulnerability Database |
| F5 | Big-ip Fraud Protection Service | ≥ 16.1.0 and ≤ 16.1.6≥ 17.5.0 and ≤ 17.5.1≥ 17.1.0 and ≤ 17.1.3 | Vulnerable | NIST National Vulnerability Database |
| F5 | Big-ip Global Traffic Manager | ≥ 16.1.0 and ≤ 16.1.6≥ 17.5.0 and ≤ 17.5.1≥ 17.1.0 and ≤ 17.1.3 | Vulnerable | NIST National Vulnerability Database |
| F5 | Big-ip Link Controller | ≥ 17.1.0 and ≤ 17.1.3≥ 17.5.0 and ≤ 17.5.1≥ 16.1.0 and ≤ 16.1.6 | Vulnerable | NIST National Vulnerability Database |
| F5 | Big-ip Local Traffic Manager | ≥ 16.1.0 and ≤ 16.1.6≥ 17.5.0 and ≤ 17.5.1≥ 17.1.0 and ≤ 17.1.3 | Vulnerable | NIST National Vulnerability Database |
| F5 | Big-ip Policy Enforcement Manager | ≥ 16.1.0 and ≤ 16.1.6≥ 17.5.0 and ≤ 17.5.1≥ 17.1.0 and ≤ 17.1.3 | Vulnerable | NIST National Vulnerability Database |
| F5 | Big-ip Ssl Orchestrator | ≥ 17.1.0 and ≤ 17.1.3≥ 16.1.0 and ≤ 16.1.6≥ 17.5.0 and ≤ 17.5.1 | Vulnerable | NIST National Vulnerability Database |
| F5 | Big-ip Webaccelerator | ≥ 16.1.0 and ≤ 16.1.6≥ 17.5.0 and ≤ 17.5.1≥ 17.1.0 and ≤ 17.1.3 | Vulnerable | NIST National Vulnerability Database |
| F5 | Big-ip Websafe | ≥ 16.1.0 and ≤ 16.1.6≥ 17.5.0 and ≤ 17.5.1≥ 17.1.0 and ≤ 17.1.3 | Vulnerable | NIST National Vulnerability Database |
Attack characteristics
The CVSS vector, decoded. It describes the attack, not your exposure to it.
Every base score collected
Sources score independently and may disagree; each row says who scored it and under which version.
| Score | Version | Severity | Expl. | Impact | Scored by |
|---|---|---|---|---|---|
| 7.1 | CVSS 4.0 | High | — | — | f5sirt@f5.com via NIST National Vulnerability Database |
| 7.1 | CVSS 4.0 | High | — | — | f5 via CVE Program (cve.org) e CISA ADP |
| 6.5 | CVSS 3.1 | Medium | 2.8 | 3.6 | f5sirt@f5.com via NIST National Vulnerability Database |
| 6.5 | CVSS 3.1 | Medium | — | — | f5 via CVE Program (cve.org) e CISA ADP |
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N (score shown at the top: f5sirt@f5.com) Weakness MITRE
Weakness class according to MITRE’s CWE catalog.
EPSS over time FIRST
Oct 13, 2026 → Oct 14, 2026 · 2 reading(s) · max 0.38%
Detection
Read off the CVSS vector and the weakness class. Starting points, not tested rules.
- Prioritize edge telemetry for the network-reachable component (proxy, WAF, IDS/IPS).
Timeline
What happened to this CVE, newest first.
- 2026
- Affected products added · f5/big-ip
- SSVC assessment updated
- Record published
- Fix documented
- CVSS changed · 6.5
- Source status changed · → Analyzed
- Record created in this database
- CVE published
Source activity
Repeated readings are counted rather than listed.
- 1× Official description updated · Oct 13, 2026 – Oct 13, 2026
References
1 on the record
Elsewhere on this site
Related CVEs (same products)
- Critical CVE-2026-94127 F5 BIG-IP APM Heap-based Buffer Overflow Vulnerability KEV 23d
- Low CVE-2026-63020 A vulnerability exists in an undisclosed BIG-IP Configuration utility page that may… Sep 2, 2026
- High CVE-2026-59762 BIG-IP HTTP/2 vulnerability Jul 15, 2026
- Medium CVE-2026-42937 iControl REST and tmsh vulnerability May 13, 2026
- High CVE-2026-42920 BIG-IP DTLS Vulnerability May 13, 2026
- Medium CVE-2026-42919 F5 BIG-IP Appliance Mode Vulnerability May 13, 2026
Not in any source we poll
Listed rather than left blank: an empty field and an unmeasured one look identical on screen, and only one is a reason to look elsewhere.
- No confirmed IOCs, IP addresses, domains, file hashes, or malware artifacts supplied.
- No organization-specific asset inventory, compensating-control status, or patch deployment evidence supplied.
- No exploit packet captures, log samples, or incident case IDs supplied.
Answered from this record
Text assembled only from the fields above — no additional claims.
What should defenders know first?
CVE-2026-40699 is "BIG-IP Configuration utility vulnerability", rated Medium. It affects BIG-IP (F5); versions are in the scope table. It is not in CISA KEV, which does not rule out exploitation. CVSS 6.5 describes technical severity. EPSS 0.38% estimates the probability of exploitation in 30 days; neither replaces your asset context. First verify whether exposed or business-critical assets run the affected versions, apply vendor fixes or mitigations, and preserve logs for review.
Comments
Moderated technical discussion. Read the community guidelines.
No comments yet.
Sign in or create an account to comment and suggest corrections.