Skip to content
CVE-2026-120285: Select a BIG-IP hotfix without losing custom fixes

CVE-2026-120285: Select a BIG-IP hotfix without losing custom fixes

November 19, 2026

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

An existing custom engineering hotfix changes the upgrade decision. Preserve its full identifier and support history before choosing the replacement package.

Identify existing engineering fixes

Record the active release and full build identifier from the administrative software inventory. Check the installation’s change records for custom fixes and their F5 Support cases. A base-version match does not establish that a standard EHF preserves the fixes in a customized build.

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.

Confirm the replacement with Support

If the installed build is custom or does not match the selection rows, give F5 Support its complete identifier and the required CVE remediation. Obtain the replacement build and supported installation path before scheduling the change. After restart, verify the active build on each device and confirm normal HA and application health; retain the support confirmation with the rollout evidence.

Acknowledgements

This post was created with assistance from AI.

Last updated on