CVE-2026-120292: Track the BIG-IP hotfix across HA members
F5 disclosed CVE-2026-120292 on November 18, 2026, at 15:00 UTC. Its CNA record rates it Critical: CVSS 3.1 score 9.8 and CVSS 4.0 score 9.3. This guide covers BIG-IP TMOS.
Treat each member of a high-availability deployment as a separate patch-verification item. Updating one device does not establish the state of its peer.
Prepare the HA change record
Before maintenance, record each member’s active release, complete engineering build and current HA role. Check normal configuration synchronization and service health using the deployment’s existing administrative checks. Confirm the supported upgrade sequence and compatibility requirements for the actual topology; do not assume every HA design uses the same failover procedure.
Select the engineering hotfix
The F5 advisory is part of the November 18 security notification. The CNA record lists affected TMOS lines starting at 17.1.0, 17.5.0 and 21.1.0, with the engineering builds below recorded as unaffected. A base release number alone does not confirm that the fix is installed.
Use F5’s build-selection guidance for the current installation. Build identifiers below omit the product prefix and retain the full release and engineering suffix.
| Current installation within the applicable TMOS branch | F5-selected EHF |
|---|---|
| 17.1.3.6.0.9.20-ENG | 17.1.3.6.0.14.20-ENG |
| 17.1.3.7 base or earlier applicable 17.1 base | 17.1.3.7.0.21.4-ENG |
| 17.5.1.10.0.7.35-ENG or 17.5.1.10.0.37.35-ENG | 17.5.1.10.0.80.35-ENG |
| 17.5.1.11 base or earlier applicable 17.5 base | 17.5.1.11.0.61.12-ENG |
| 21.1.0.4 base or earlier applicable 21.1 base | 21.1.0.4.0.19.3-ENG |
These are branch-specific selection rules, not a general upgrade path from any older release. For a custom engineering hotfix, contact F5 Support for a replacement that retains the required fixes. If the current installation falls outside the listed cases, confirm its supported path with F5 before proceeding.
F5 warns that engineering hotfixes receive less extensive QA than scheduled releases and are supplied without a usability warranty or guarantee. Plan validation and recovery for the deployment, and confirm package prerequisites before installation.
Verify each member before continuing
Use the supported rolling-upgrade procedure for the deployment. After each member returns, confirm its active engineering build and normal health before proceeding to the next planned step. At completion, record the build of every member and confirm the intended HA roles and synchronization state. Keep a partially completed pair marked incomplete.
Acknowledgements
This post was created with assistance from AI.