BIG-IP vulnerabilities and CVEs
Known vulnerabilities affecting BIG-IP, with exploit availability attached to each one, so you can tell a flaw someone has written code for from one nobody has.
12 vulnerabilities tracked.
- 9.3 Description: When an iRule that processes client traffic using the PEM::subscriber command is configured on a virtual server, undisclosed…
- 9.3 Description: When an iRule that processes client traffic using the GENERICMESSAGE::route command is configured on a virtual server,…
- 9.3 Description: When an HTTP profile and an iRule using the MR::message route command are configured on a virtual server, undisclosed requests…
- 9.3 Description When an HTTP profile and an iRule containing the PSC::ipaddress command are configured on a virtual server, undisclosed…
- 9.3 When BIG-IP APM is provisioned and a per-request policy that includes the Client Information agent and Endpoint Security agents is applied…
- 9.3 Description: When an iRule that processes client traffic using the DNS::scrape command is configured on a virtual server, undisclosed…
- 9.2 Description: BIG-IP iControl REST tokens may not expire as expected in all scenarios.
- 8.7 Description: When BIG-IP APM is provisioned, an Access Profile is configured as a SAML SP (Service Provider) and is applied to a virtual…
- 8.7 Description: When BIG-IP APM is provisioned, and a virtual server is configured with an APM access profile and a per-request policy, and…
- 8.7 Description: When BIG-IP APM is licensed and provisioned, and a virtual server with the APM access profile is configured with a per-request…
- 8.7 Description: When BIG-IP APM is provisioned and a virtual server is configured with an APM Access profile and a SAML Service Provider (SP)…
- 8.7 An authenticated iControl SOAP user with at least Guest access can inject an unauthorized management request.
What this covers
This feed accumulates forward from the day it started storing records, and a name search that finds nothing here is also looked up against the registers directly — so an older advisory resolves even when it predates the corpus. It is still a reading view, not a substitute for the vendor's own advisory, and absence from this page is not a statement that BIG-IP is free of vulnerabilities.
Query this from an agent over MCP · Check a lockfile by version
Other products tracked here
Linux Windows Server 2025 (Server Core installation) Windows Server 2025 Windows 11 version 26H1 Windows 11 Version 24H2 Windows Server 2022 Windows 11 Version 25H2 Windows Server 2019 (Server Core installation) Windows Server 2019 Windows 10 Version 21H2 Windows 10 Version 22H2 Windows 10 Version 1809 Windows 11 Version 23H2 Windows Server 2016 Windows Server 2016 (Server Core installation) Windows 10 Version 1607 Red Hat Enterprise Linux 9 Red Hat Enterprise Linux 8 Windows Server 2012 R2 Windows Server 2012 R2 (Server Core installation) Chrome Windows Server 2012 Windows Server 2012 (Server Core installation) Windows 11 Version 26H2