CVE-2026-20732: F5 BIG-IP · User Interface (UI) Misrepresentation of Critical Information
Affects F5 BIG-IPSource CVE Database V5
Not known to be exploited · CVSS 3.1 Low : upgrade to 17.5.1.4 or 17.1.3.1 when convenient.
Data as of 26 Oct 2026, 08:11 UTC
- EPSS
- 0.1% chance of exploitation in 30 days – higher than 7% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
- Patch
- Available – fixed in 17.5.1.4, 17.1.3.1
CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:U/C:N/I:L/A:NExploitation evidence
Disclosed: evidence found.
CVE published 4 Feb 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 2026-10-26.
What to do
Upgrade F5 BIG-IP to 17.5.1.4 or 17.1.3.1.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| F5BIG-IP | Affected
| Fixed in
|
AI-suggested
1. Monitor administrative interfaces closely for any suspicious or unexpected error messages that could indicate spoofing attempts. 2. Educate network and system administrators to verify error messages through multiple sources before acting on them to avoid misinterpretation. 3. Restrict access to the BIG-IP configuration utility page using network segmentation, VPNs, or IP whitelisting to reduce exposure to unauthenticated attackers. 4. Implement strict input validation and sanitization controls where possible, especially if custom configurations or integrations exist. 5. Regularly check for vendor advisories and apply official patches or updates promptly once released. 6. Employ multi-factor authentication and strong access controls on administrative interfaces to reduce risk of unauthorized access. 7. Use logging and alerting mechanisms to detect unusual UI behavior or repeated error message spoofing attempts. 8. Conduct periodic security assessments and penetration testing focused on UI integrity and administrative interface security. These steps go beyond generic advice by focusing on operational awareness, access restrictions, and proactive detection tailored to this specific UI misrepresentation vulnerability.
Description
A vulnerability exists in an undisclosed BIG-IP Configuration utility page that may allow an attacker to spoof error messages. Note: Software versions which have reached End of Technical Support (EoTS) are not evaluated.