CVE-2026-120722: Verify the BIG-IP DNS engineering hotfix
F5 disclosed CVE-2026-120722 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 DNS on TMOS.
Keep the BIG-IP DNS device inventory with the patch record so that a completed change on another appliance does not close the DNS rollout prematurely.
Scope the DNS maintenance
List the BIG-IP DNS instances in the deployment and record each one’s active release and complete engineering build. Use the existing administrative inventory and ownership records. A product label or a package download alone does not establish the installed fix, and the presence of the product alone does not establish exposure in every configuration.
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.
Check normal DNS service health
After the approved installation and restart, verify the active build on each DNS instance. Use existing administrative service-health and monitoring results to confirm the deployment returned to its normal state. For HA deployments, verify the intended roles and peer health as well. Record any device awaiting maintenance separately from completed instances.
Acknowledgements
This post was created with assistance from AI.