⚠ Reference material — not professional advice. Test in staging, back up first, verify against your specific version. Use your own judgment for your environment.
● High · CVSS 7.5

How to Fix CVE-2026-42409: Denial of Service in BIG-IP

Other vulnerabilities in the same area that are worth patching alongside this one:

*By Sai Kiran Pandrala*

⚡ At a glance
SeverityCVSS 7.5 - High
Actively exploited?Not currently listed in CISA KEV
Affected21.0.0 < 21.0.0.1, 17.5.0 < 17.5.1.4, 17.1.0 < 17.1.3.1, 16.1.0 < *, 2.0.0 < 2.0.3, 1.7.0 < 1.7.17, and others
Fixed in21.1.0
Type (CWE)CWE-476: NULL Pointer Dereference

What is CVE-2026-42409?

CVE-2026-42409 is a denial of service flaw in BIG-IP. A crafted request triggers a code path that crashes or hangs the service, taking the product offline for legitimate users. Vendor description: When an HTTP/2 profile and an iRule containing the HTTP::redirect or HTTP::respond command are configured on a virtual server, undisclosed requests can cause the Traffic Management Microkernel (TMM) process to terminate. Note: Software versions which have reached End of Technical Support (EoTS) are not evaluated.

Why this CVE matters

Denial-of-service flaws in a network gateway or firewall have an outsize operational impact. A single packet that reboots an inline device takes down everything behind it, which is why even non-RCE bugs on these products warrant priority patching.

For deployments of BIG-IP that have been exposed to the public internet during the disclosure window, the operating assumption should be that scanning has already happened. Even where exploitation has not been publicly observed, scanning for the vulnerable fingerprint is cheap and routine. Patching closes the door; log review and credential rotation close out the rest of the response.

Am I affected?

You are affected if your installation matches any of these version ranges:

Check your installed version against the list above. If you cannot determine the version, treat the system as affected and follow the upgrade path below.

On BIG-IP, run tmsh show sys version from the CLI. The Active Version line is the value to compare against the advisory.

How to fix CVE-2026-42409

  1. Read the vendor advisory in full: https://my.f5.com/manage/s/article/K000159034
  2. Upgrade BIG-IP to 21.1.0 or a later version listed in the vendor advisory.
  3. Back up the configuration (and database, where applicable) before upgrading.
  4. Apply the patch in a maintenance window. For HA pairs, upgrade the standby node first, fail over, then upgrade the former primary.
  5. Restart the affected service so the patched binary loads, then verify the new version (see verification section).

Upgrade f5 big-ip to the patched release


# CVE-2026-42409 affects BIG-IP 21.0.0 < 21.0.0.1. Fixed in 21.0.0.1.
# Vendor advisory: https://my.f5.com/manage/s/article/K000159034

# 1. Confirm the running version.
tmsh show /sys version

# 2. Import and install the patched image.
tmsh install /sys software image BIGIP-21.0.0.1.iso volume HD1.2

# 3. After reboot, verify.
tmsh show /sys version

Verify the fix landed


# CVE-2026-42409 verification checklist.

# 1. Confirm the running version matches 21.0.0.1 (replace the version probe with
#    the platform-specific command shown above).

# 2. Re-scan the host with your vulnerability scanner (Nessus, Qualys, Tenable,
#    OpenVAS, Wazuh). The scanner must no longer flag CVE-2026-42409.

# 3. Inspect recent service and kernel logs for crash-loops or rollback events.
journalctl -u <service-name> --since "10 minutes ago"
dmesg --since "10 minutes ago"

# 4. Cross-check the running build against the vendor advisory:
#    https://my.f5.com/manage/s/article/K000159034

If you cannot patch immediately

Front the service with rate limiting and drop malformed packets at a load balancer or IPS. Patch to remove the underlying crash condition.

How to verify the fix worked

If your installation was internet-reachable during the disclosure window, treat log review as part of the remediation rather than an optional follow-up. Look for repeated service restarts, crash logs from the affected daemon, and core files generated around the time of any anomalous traffic. A memory-corruption flaw used for exploitation often leaves a trail of failed attempts before the successful one.

Frequently asked questions

Is CVE-2026-42409 being exploited in the wild?

Public exploitation has not been confirmed by CISA at the time of writing. Treat the patch as time-sensitive anyway; reports often lag actual abuse.

Will a WAF or IDS rule fully mitigate CVE-2026-42409?

No. Network-layer filters can reduce noise and slow opportunistic scanners, but they will not stop a determined attacker. The vendor patch is the only durable fix.

How long should I plan for the upgrade?

Typical vendor-documented upgrade windows for BIG-IP run from a few minutes to under an hour depending on cluster size. Test in a staging environment first and follow the vendor's documented HA upgrade order.

References

*This guide was assembled from the official vendor advisory, the NVD record, and the CISA KEV catalog entry on 2026-05-25. Always confirm against the vendor advisory before applying changes in production.*