Skip to content
CVE-2026-116953: Inventory the complete BIG-IP engineering build

CVE-2026-116953: Inventory the complete BIG-IP engineering build

November 19, 2026

F5 disclosed CVE-2026-116953 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.

Start the change record with the complete installed build for each appliance. The short release number can hide the difference between a base release and an engineering hotfix.

Record the active installation

Use the BIG-IP administrative software inventory to record the active boot volume, release and full engineering build identifier on each device. Retain the complete suffix rather than shortening the record to 17.1, 17.5 or 21.1. An image uploaded to another volume is not evidence that the active system is patched.

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 branchF5-selected EHF
17.1.3.6.0.9.20-ENG17.1.3.6.0.14.20-ENG
17.1.3.7 base or earlier applicable 17.1 base17.1.3.7.0.21.4-ENG
17.5.1.10.0.7.35-ENG or 17.5.1.10.0.37.35-ENG17.5.1.10.0.80.35-ENG
17.5.1.11 base or earlier applicable 17.5 base17.5.1.11.0.61.12-ENG
21.1.0.4 base or earlier applicable 21.1 base21.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.

Close the change with device-level evidence

After the approved upgrade and restart, reopen the software inventory and compare the active build with the selected EHF. Record the result separately for every HA member, together with its normal HA state and service-health result. Leave any device still running the old volume open in the change record.

Acknowledgements

This post was created with assistance from AI.

Last updated on