Critical BIG-IP Flaws With Hotfixes Only and No Workaround: A Step-by-Step Guide to Checking Whether Your F5 Setup Is Exposed
F5 has issued emergency engineering hotfixes for a set of critical BIG-IP flaws that let an unauthenticated attacker crash traffic processing and possibly run code, but only on systems with specific iRule or access-policy settings. This walkthrough explains how to work out whether yours qualifies and what to do next.
F5’s BIG-IP appliances sit in front of websites, VPNs and business applications at a lot of mid-size organizations, often managed by an outside provider. This week the company published a batch of critical fixes that come with an unusual catch: they are engineering hotfixes rather than regular releases, and there is no workaround in the meantime. The good news is that each flaw needs a specific configuration to be reachable. The steps below are based on The Hacker News’ detailed rundown of F5’s advisories, with exposure figures from BleepingComputer.
The short version
The flaws are stack-based buffer overflows in BIG-IP’s data plane, the part that handles customer traffic. An attacker who does not need to log in can crash the Traffic Management Microkernel (TMM), interrupting traffic until it restarts, and F5 says code execution may also be possible. The Hacker News counts six critical flaws, each scored 9.8 under CVSS v3.1; BleepingComputer’s report focuses on five. F5 says the management side is not exposed, and none of its advisories reports exploitation so far. A watchTowr researcher reported four of the flaws and F5 found the rest itself.
Walking through it
- Find every BIG-IP you depend on. Include appliances in your own racks, virtual editions in the cloud, and any your managed service provider or hosting company runs on your behalf. Shadowserver, cited by BleepingComputer, tracks more than 177,000 BIG-IP instances visible on the internet, including over 14,600 addresses showing signs of the Access Policy Manager (APM) module.
- Check the iRules attached to your virtual servers. Five of the critical flaws depend on an iRule, BIG-IP’s traffic scripting feature, using a particular command: PEM::subscriber (CVE-2026-121805), MR::message route with an HTTP profile (CVE-2026-120292), PSC::ip_address with an HTTP profile (CVE-2026-120285), GENERICMESSAGE::route (CVE-2026-116953) or DNS::scrape (CVE-2026-120722). If none of your iRules use those commands, those particular bugs are not reachable.
- Check APM access policies. The sixth, CVE-2026-123637, needs an APM per-request policy that includes both the Client Information agent and Endpoint Security agents. Several lower-rated APM flaws fixed in the same hotfixes involve form-based logon pages and SAML service provider setups, so note those too.
- Don’t forget the cloud-native editions. Some of the flaws also affect BIG-IP Next for Kubernetes and BIG-IP CNF. For those, F5 lists fixes such as BNK-2.4.2-EHF1 and CNF-2.4.2-EHF1, with matching hotfixes for the 2.3 and 2.2 branches.
- Get the right hotfix, and understand what it is. No scheduled software release is listed as a fix. Engineering hotfixes are builds F5 issues between normal releases, and the company warns they do not go through the same extensive testing. If a system already runs a custom hotfix, it needs a new one from F5 support. Schedule the change in a maintenance window, take a configuration backup first, and test failover if you run a high-availability pair.
- Look at the rest of the batch. F5 also fixed lower-rated flaws in management interfaces, including an iControl SOAP issue that could let a user with as little as the Guest role run system commands, fixed in BIG-IP 21.1.0.3, 17.5.1.10 and 17.1.3.6. Keep management interfaces reachable only from trusted networks.
- Check support status. F5 only evaluates versions still within technical support, so an older release missing from its tables has not been shown to be safe. If you are on one, plan an upgrade.
Why not wait for the regular release?
Attackers have a long history with F5 gear. BleepingComputer notes that CISA has listed seven F5 vulnerabilities as actively exploited since November 2021, four of them used by ransomware gangs, and a separate critical APM flaw patched in September was exploited as a zero-day. Because these new flaws need no login, a system with an affected configuration is worth treating as urgent.
What this means for your company
If you do not know whether you run BIG-IP, that is the first answer to find; ask whoever manages your firewall, VPN, website hosting or remote access. The bigger lesson applies to any network appliance at the edge: these devices handle all your traffic, are often forgotten once installed, and are a favorite target because one flaw can open the door to everything behind them. Keep an inventory of edge devices with their software versions and support dates, know who is responsible for patching each one, and agree in advance how fast critical fixes will be applied. If an outside provider manages them, ask for written confirmation when a critical patch has been checked or installed.
If you are not sure which edge devices sit in front of your business or when they were last patched, we can help you build that list and keep it current. Reach out to Layer 7 Data Solutions to discuss how we’ve helped companies similar to yours.
