Dev.to Security 🔐 Cybersecurity 👁 0 📖 1 min read

F5 iRule Commands Put the BIG-IP Data Plane on the Critical Patch Path

F5 iRule Commands Put the BIG-IP Data Plane on the Critical Patch Path F5 BIG-IP appliances often terminate TLS, balance production traffic, and enforce network policy. Two current iRule issues matter because exploitat

F5 iRule Commands Put the BIG-IP Data Plane on the Critical Patch Path

F5 BIG-IP appliances often terminate TLS, balance production traffic, and enforce network policy. Two current iRule issues matter because exploitation occurs on that data plane, not in an optional reporting page.

Affected paths

CVE-2026-116953 affects virtual servers whose iRules process client traffic with GENERICMESSAGE::route. CVE-2026-121805 affects virtual servers using PEM::subscriber. F5 says undisclosed requests can terminate the Traffic Management Microkernel and may lead to remote code execution. The vendor describes a remote, unauthenticated data-plane attack with no control-plane exposure.

That description still depends on configuration. The presence of BIG-IP is not proof that either vulnerable command is used. Defenders need both the appliance version and the virtual-server iRule inventory.

Prioritize correctly

First identify internet-facing virtual servers and those that carry authentication, payment, or administrative traffic. Search iRule configurations for the affected commands. Apply the fixed release listed in each F5 advisory and follow the vendor's installation guidance.

Where immediate maintenance is impossible, reduce exposure through tightly scoped virtual servers, source restrictions, or disabling unused commands. These controls do not replace the vendor fix, and they may not stop every request path.

After patching, verify the running software version on every cluster member. Check standby devices and synchronization status. A patch list for one appliance does not prove that the traffic group is protected.

Detection and hardening

Review TMM restarts, unexpected traffic disruption, crash evidence, and process behavior around the time of alerts. Preserve iRule versions and deployment history. Determine whether an unfamiliar iRule appeared or an existing one gained a vulnerable command.

Restrict management access separately from data-plane access. Use source-controlled iRule deployment with approval and drift detection. Remove unused iRules and keep a tested emergency procedure for disabling a virtual server without losing all visibility.

References

📰 Read the original article on Dev.to Security

Originally published by Dev.to Security. Aggregated on AIWithGhost for educational purposes — full credit and traffic to the original publisher.