Skip to content
CVE-2026-121805: Plan the BIG-IP PEM hotfix maintenance

CVE-2026-121805: Plan the BIG-IP PEM hotfix maintenance

November 19, 2026

F5 disclosed CVE-2026-121805 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 Policy Enforcement Manager (PEM) on TMOS.

Plan the PEM update with the service owner and retain the installed build for every participating device. The engineering-hotfix package must match the starting installation.

Prepare the PEM maintenance window

Use administrative inventory to identify the PEM devices, active boot volumes and complete engineering build identifiers. Record normal service and HA health before maintenance. Preserve configuration backups and the recovery procedure, and confirm the supported installation sequence for the selected package.

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.

Verify service restoration and the active build

After the upgrade and required restart, confirm that each device boots the selected engineering build. Review the deployment’s existing PEM service-health indicators and startup alarms, then verify normal HA roles and peer health where applicable. Have the service owner record whether normal operation has resumed; a successful package installation alone does not complete that assessment.

Acknowledgements

This post was created with assistance from AI.

Last updated on