CVE-2026-121805: BIG-IP iRule Vulnerability

Published Nov 18, 2026
·
Updated

Description:

When an iRule that processes client traffic using the PEM::subscriber command is configured on a virtual server, undisclosed requests can cause the Traffic Management Microkernel (TMM) to terminate and may lead to remote code execution (RCE).

Impact:

Traffic is disrupted while the TMM process restarts. This vulnerability allows a remote unauthenticated attacker to cause a denial-of-service (DoS) on the BIG-IP system and may perform RCE. There is no control plane exposure; this is a data plane issue only.

Note: Software versions which have reached End of Technical Support (EoTS) are not evaluated.

Affected Software

4 affected componentsFixes available
F5 BIG-IP
F5 BIG-IP Next for Kubernetes>=2.4.0<=2.4.2, >=2.3.0<=2.3.4, >=2.2.0<=2.2.5
-2.4.2-13-2.3.4-13-2.2.5-13
F5 BIG-IP PEM=21.1.0
-21.1.0.4.0.19.3-3
F5 BIG-IP PEM>=17.5.0<=17.5.1, >=17.1.0<=17.1.3
-17.5.1.11.0.61.12-3-17.5.1.10.0.80.35-3-17.1.3.7.0.21.4-3-17.1.3.6.0.14.20-3

Remediation

Recommended actions to resolve this vulnerability, in priority order.

  1. Upgrade

    Upgrade to a fixed release to a version that resolves this vulnerability.

    Fixed in -2.4.2-Fixed in 1Fixed in 3Fixed in -2.3.4-Fixed in 1Fixed in 3Fixed in -2.2.5-Fixed in 1Fixed in 3
  2. Upgrade

    Upgrade to a fixed release to a version that resolves this vulnerability.

    Fixed in -21.1.0.4.0.19.3-Fixed in 3
  3. Upgrade

    Upgrade to a fixed release to a version that resolves this vulnerability.

    Fixed in -17.5.1.11.0.61.12-Fixed in 3Fixed in -17.5.1.10.0.80.35-Fixed in 3Fixed in -17.1.3.7.0.21.4-Fixed in 3Fixed in -17.1.3.6.0.14.20-Fixed in 3

Event History

Nov 18, 2026
Advisory Published
via F5·02:51 PM
Data Sourced
via F5·02:51 PM
DescriptionSeverityWeaknessAffected Software
CVE Published
via MITRE·03:23 PM
Data Sourced
via MITRE·03:23 PM
DescriptionSeverityWeakness
Data Sourced
via NVD·04:18 PM
DescriptionSeverityWeakness

Frequently Asked Questions

1

Which deployments are exposed to this issue?

Exposure is limited to the data plane. A virtual server must have an iRule configured that processes client traffic with the PEM::subscriber command; there is no control-plane exposure.

2

Does exploitation require authentication or user interaction?

No. The issue can be triggered by a remote unauthenticated attacker through client traffic, with no user interaction described.

3

What operational impact should responders expect?

Undisclosed requests can terminate the Traffic Management Microkernel (TMM), disrupting traffic while the TMM process restarts. The issue may also allow remote code execution.

4

Are end-of-support software versions covered by the evaluation?

No. Software versions that have reached End of Technical Support (EoTS) were not evaluated.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203