runbook / 004 · Tailwind Resource Group · Customer advisory · Disclosed November 18, 2026
Compare your BIG-IP systems with the F5 security notification of November 18, 2026, and install the correct hotfix
On November 18, 2026, F5 announced 12 security issues in BIG-IP. Six are Critical. Install the engineering hotfix for your version. Until then, this page shows you which issues apply to your configuration and what decreases your risk.
- Applies to
- BIG-IP 17.1.x, 17.5.x and 21.1.0
- Fix
- The engineering hotfix for your version
- F5 articles
- 12: 6 Critical, 6 High
- Interim
- 1 check script, 4 F5 mitigations
Summary
On November 18, 2026, F5 published an out-of-band security notification, F5 article K000164058. It has 12 articles for BIG-IP.
- By the CVSS v3.1 scores that F5 gives, 6 are Critical and 6 are High.
- F5 says that 10 of them let a remote attacker stop the Traffic Management Microkernel (TMM). Traffic stops while TMM starts again. For the 6 Critical issues, F5 says that the attacker may also be able to run code.
- 9 of the 12 are corrected only in the engineering hotfixes that F5 released on the same day. F5 corrected the other 3 in earlier releases.
- Each issue needs a specific module, iRule command or setting. A system that does not have it is not affected by that issue.
We tested one of the issues, CVE-2026-125272, in a lab before F5 published. The result agrees with the F5 article. We will add an interim iRule for it after the request is public.
Install the engineering hotfix for your version. This is the only complete correction. Until your change window, the check script in this page shows you which issues apply to your configuration.
Does this apply to you?
F5 lists these BIG-IP versions as vulnerable: 17.1.0 to 17.1.3, 17.5.0 to 17.5.1, and 21.1.0. F5 examines only versions that it supports. For an older version, ask F5 Support.
An issue applies to a system with one of those versions if its condition is true. The conditions are from the F5 articles.
F5 article CVE Condition CVSS v3.1 K000163937 CVE-2026-123637 APM: a per-request policy with the Client Information agent and Endpoint Security agents Critical 9.8 K000163939 CVE-2026-120285 An iRule with the PSC::ip_addresscommand, and an HTTP profileCritical 9.8 K000163940 CVE-2026-120292 An iRule with the MR::message routecommand, and an HTTP profileCritical 9.8 K000163941 CVE-2026-116953 An iRule that uses the GENERICMESSAGE::routecommand on client trafficCritical 9.8 K000163945 CVE-2026-120722 An iRule that uses the DNS::scrapecommand on client trafficCritical 9.8 K000163946 CVE-2026-121805 An iRule that uses the PEM::subscribercommand on client trafficCritical 9.8 K000163936 CVE-2026-125274 All configurations: an iControl SOAP user with the Guest role or higher High 8.8 K000163929 CVE-2026-120718 All configurations: iControl REST tokens High 8.1 K000163938 CVE-2026-125272 APM: a per-request policy with a form-based Logon Page High 7.5 K000163942 CVE-2026-126822 APM: an access profile that is a SAML service provider High 7.5 K000163943 CVE-2026-126336 APM: a SAML service provider with encrypted assertions High 7.5 K000163944 CVE-2026-121812 APM: a per-request policy, and the tmm.access.policytracekey enabledHigh 7.5 CVE-2026-120718 is High by CVSS v3.1 and Critical, 9.2, by CVSS v4.0.
You are not affected by an issue if its condition is false. A BIG-IP system that has none of these modules, commands or settings still has the two iControl issues, unless its version already has those corrections. See "Find the fix for your version" below.
This page is for BIG-IP. Some of the articles also apply to BIG-IQ Centralized Management, BIG-IP SSL Orchestrator and BIG-IP Next for Kubernetes. The notification also has 10 articles for NGINX. This page does not include them. Read F5 article K000164058 for those products.
Recommended actions, in order
- Find the fix for your version. The correct engineering hotfix depends on the version and the hotfix that you have now. See "Find the fix for your version" below.
- Run the check script. It compares your configuration with each condition. It changes nothing. See "Check your configuration" below.
- Schedule the hotfix. Use your first available change window. Do the systems with a Critical result first. Install on the standby unit first.
- Use the F5 mitigations. F5 gives a mitigation for 4 of the 12 issues. See "Mitigations from F5" below.
- Decrease exposure for the other issues. See "Steps that F5 does not list" below. These steps are ours.
- Monitor. See "What to monitor" below.
Find the fix for your version
The 9 issues that the engineering hotfixes correct
These are CVE-2026-123637, CVE-2026-125272, CVE-2026-120285, CVE-2026-120292, CVE-2026-116953, CVE-2026-120722, CVE-2026-121805, CVE-2026-126822 and CVE-2026-121812.
F5 article K000164239 tells you which build to install:
You have now Install The 17.5.1.11 base release, or an earlier base release BIGIP-17.5.1.11.0.61.12-ENGBIGIP-17.5.1.10.0.7.35-ENGorBIGIP-17.5.1.10.0.37.35-ENGBIGIP-17.5.1.10.0.80.35-ENGThe 17.1.3.7 base release, or an earlier base release BIGIP-17.1.3.7.0.21.4-ENGBIGIP-17.1.3.6.0.9.20-ENGBIGIP-17.1.3.6.0.14.20-ENGThe 21.1.0.4 base release, or an earlier base release BIGIP-21.1.0.4.0.19.3-ENGA custom engineering hotfix Contact F5 Support and ask for a new engineering hotfix F5 says that engineering hotfixes do not get the full tests of a scheduled release, and that F5 supplies them with no warranty.
The 3 issues that F5 corrected in earlier releases
If your version is the same as the fixed version or later, you have the correction.
F5 article CVE Fixed in K000163929 CVE-2026-120718 17.1.3.6, 17.5.1.10, 21.1.0.2 K000163936 CVE-2026-125274 17.1.3.6, 17.5.1.10, 21.1.0.3 K000163943 CVE-2026-126336 17.1.3.6, 17.5.1.10, 21.1.0.3 Find your version and build
Run this command in the bash shell of the BIG-IP system. For an engineering hotfix, the
Buildline shows the last three numbers of the file name, for example0.61.12.shell tmsh show sys versionCheck your configuration
The script compares the configuration of one BIG-IP system with the condition in each article. It uses
tmsh listandtmsh showcommands only. It changes nothing. The script is ours, not from F5.Run it on each BIG-IP system. In a device group, one unit is sufficient if all units have the same software.
Run the script
Do these steps on the BIG-IP system.
- Copy the script to the BIG-IP system as
/var/tmp/bigip_k000164058_check.sh. - Log on as
root, or as an administrator with the bash shell. - Run the script:
shell bash /var/tmp/bigip_k000164058_check.shRead the result
The script prints one line for each article.
Result Meaning FOUNDThe configuration agrees with the condition in the article. Use the steps in this page NOT FOUNDThe script did not find the condition FIXEDThe software has the correction for the article ALLThe article applies to all configurations of this version This is an example for a system with the 17.5.1.11 base release, APM, a Logon Page in a per-request policy, and one iRule with the
DNS::scrapecommand:Example result Show all 17 linesHide 17 lines
BIG-IP 17.5.1.11 build 0.0.12 K000163937 CVE-2026-123637 NOT FOUND No Client Information agent in a per-request policy. K000163938 CVE-2026-125272 FOUND Logon Page agent in a per-request policy: agent Common/sr_logon_act_logon_page_ag in Common/sr_logon, with a credentials prefix K000163939 CVE-2026-120285 NOT FOUND No iRule with PSC::ip_address on a virtual server. K000163940 CVE-2026-120292 NOT FOUND No iRule with MR::message route on a virtual server. K000163941 CVE-2026-116953 NOT FOUND No iRule with GENERICMESSAGE::route on a virtual server. K000163945 CVE-2026-120722 FOUND iRule with DNS::scrape on a virtual server: iRule Common/dns_rule on virtual server: Common/vs_dns K000163946 CVE-2026-121805 NOT FOUND No iRule with PEM::subscriber on a virtual server. K000163942 CVE-2026-126822 NOT FOUND No SAML Auth agent. K000163943 CVE-2026-126336 FIXED F5 corrected this in a release that this version includes. K000163944 CVE-2026-121812 NOT FOUND tmm.access.policytrace is disable. K000163929 CVE-2026-120718 FIXED F5 corrected this in a release that this version includes. K000163936 CVE-2026-125274 FIXED F5 corrected this in a release that this version includes. Virtual servers with a per-request policy: Common/vs_apm uses Common/prp_apmLimits of the script
- A
NOT FOUNDline is not a statement that the system is safe. The script examines the configuration that tmsh shows. Install the hotfix in all cases. - For K000163937, the script finds a Client Information agent in a per-request policy. The article also names Endpoint Security agents. The script does not examine them, so a
FOUNDline can be a system that the article does not include. - For the 5 iRule articles, the script finds the command text in an iRule that is on a virtual server. It ignores comment lines. It does not examine the profiles of the virtual server. It finds text in a string, so a
FOUNDline can be an iRule that does not run the command. - We tested the script on BIG-IP 17.5.1.11 only. The test had objects in the
Commonpartition, in a second partition and in a folder.
Script
bigip_k000164058_check.shSave this file on the BIG-IP system in
/var/tmp.bigip_k000164058_check.shDownload Show all 199 linesHide 199 lines
#!/bin/bash # Copyright 2026 Tailwind Resource Group # SPDX-License-Identifier: Apache-2.0 # Provided as is, with no warranty. License: https://everythingsfine.io/license/ # # bigip_k000164058_check.sh # # Purpose: compare the configuration of one BIG-IP system with the conditions # in the BIG-IP articles of F5 article K000164058, Out-of-band Security # Notification (November 18, 2026). # # Run as root in the bash shell of the BIG-IP system. The script reads the # configuration with tmsh. It changes nothing. # # Result: one line for each article. # FOUND the configuration agrees with the condition in the article # NOT FOUND the script did not find the condition # FIXED the software has the correction for the article # ALL the article applies to all configurations of this version # This script is not from F5. A NOT FOUND line is not a statement that the # system is safe. Not tested: BIG-IP 17.1.x and 21.1.x. t() { tmsh -q -c "cd /; $1" 2>/dev/null; } line() { printf '%-11s %-15s %-10s %s\n' "$1" "$2" "$3" "$4"; } ver=$(tmsh -q show sys version 2>/dev/null | awk '$1 == "Version" { print $2; exit }') build=$(tmsh -q show sys version 2>/dev/null | awk '$1 == "Build" { print $2; exit }') echo "BIG-IP $ver build $build" # 1 = this build is one of the engineering hotfixes of November 18, 2026. ehf=0 case "$ver/$build" in 17.5.1.11/0.61.12 | 17.5.1.10/0.80.35 | 17.1.3.7/0.21.4 | 17.1.3.6/0.14.20 | 21.1.0.4/0.19.3) ehf=1 ;; esac # ge A B: true if version A is the same as B or later. ge() { [ "$(printf '%s\n%s\n' "$1" "$2" | sort -V | head -1)" = "$2" ]; } # rel F175 F171 F211: 1 = this version has a correction that F5 put in a # release. The arguments are the first fixed version of each branch. rel() { case "$ver" in 17.5.*) ge "$ver" "$1" && echo 1 || echo 0 ;; 17.1.*) ge "$ver" "$2" && echo 1 || echo 0 ;; 21.1.*) ge "$ver" "$3" && echo 1 || echo 0 ;; *) echo 2 ;; esac } case "$ver" in 17.5.* | 17.1.* | 21.1.*) ;; *) echo "F5 examined BIG-IP 17.1.x, 17.5.x and 21.1.x only. The lines below can be incorrect for this version." ;; esac agents=$(t "list apm policy agent recursive one-line") items=$(t "list apm policy policy-item recursive one-line") policies=$(t "list apm policy access-policy recursive one-line") prp=$(printf '%s\n' "$policies" | grep -E "type (per-rq-policy|subroutine)") virtuals=$(t "list ltm virtual recursive one-line") prp_virtuals=$(printf '%s\n' "$virtuals" | grep "per-flow-request-access-policy" \ | awk '{ for (i = 1; i <= NF; i++) if ($i == "per-flow-request-access-policy") print $3 " uses " $(i + 1) }') # in_prp TYPE: the agents of this type that are in a per-request policy or # in a subroutine. One line for each: "agent policy". in_prp() { local agent item pol for agent in $(printf '%s\n' "$agents" | awk -v ty="$1" '$4 == ty { print $5 }'); do item=$(printf '%s\n' "$items" | grep -F " $agent {" | awk '{ print $4 }' | head -1) [ -n "$item" ] || continue pol=$(printf '%s\n' "$prp" | grep -F " $item {" | awk '{ print $4 }' | head -1) [ -n "$pol" ] || continue echo "$agent $pol" done } # K000163937: Client Information agent in a per-request policy. if [ "$ehf" = 1 ]; then line K000163937 CVE-2026-123637 FIXED "This build is an engineering hotfix of November 18, 2026." else r=$(in_prp client-information) if [ -n "$r" ]; then line K000163937 CVE-2026-123637 FOUND "Client Information agent in a per-request policy:" printf '%s\n' "$r" | awk '{ print " agent " $1 " in " $2 }' echo " The article also names Endpoint Security agents. The script does not examine them." else line K000163937 CVE-2026-123637 "NOT FOUND" "No Client Information agent in a per-request policy." fi fi # K000163938: Logon Page in a per-request policy. if [ "$ehf" = 1 ]; then line K000163938 CVE-2026-125272 FIXED "This build is an engineering hotfix of November 18, 2026." else r=$(in_prp logon-page) if [ -n "$r" ]; then line K000163938 CVE-2026-125272 FOUND "Logon Page agent in a per-request policy:" printf '%s\n' "$r" | while read -r a p; do if printf '%s\n' "$agents" | grep -F " $a {" | grep "publish-credentials-prefix" | grep -qv "publish-credentials-prefix none"; then echo " agent $a in $p, with a credentials prefix" else echo " agent $a in $p, with no credentials prefix" fi done else line K000163938 CVE-2026-125272 "NOT FOUND" "No Logon Page agent in a per-request policy." fi fi # K000163939, K000163940, K000163941, K000163945, K000163946: iRule commands. rules=$(t "list ltm rule recursive" | awk ' /^ltm rule / { name = $3; next } /^[ \t]*#/ { next } /PSC::ip_address/ { print "PSC::ip_address " name } /MR::message[ \t]+route/ { print "MR::message_route " name } /GENERICMESSAGE::route/ { print "GENERICMESSAGE::route " name } /DNS::scrape/ { print "DNS::scrape " name } /PEM::subscriber/ { print "PEM::subscriber " name }' | sort -u) irule() { local article="$1" cve="$2" key="$3" text="$4" names name used any=0 out="" if [ "$ehf" = 1 ]; then line "$article" "$cve" FIXED "This build is an engineering hotfix of November 18, 2026." return fi names=$(printf '%s\n' "$rules" | awk -v k="$key" '$1 == k { print $2 }') for name in $names; do used=$(printf '%s\n' "$virtuals" | awk -v r="$name" '{ on = 0 for (i = 1; i <= NF; i++) { if ($i == "rules" && $(i + 1) == "{") { on = 1; i++; continue } if (on && $i == "}") break if (on && $i == r) { print $3; break } } }' | tr '\n' ' ') if [ -n "$used" ]; then any=1 out="$out iRule $name on virtual server: $used"$'\n' else out="$out iRule $name has the command. It is not on a virtual server."$'\n' fi done if [ "$any" = 1 ]; then line "$article" "$cve" FOUND "iRule with $text on a virtual server:" else line "$article" "$cve" "NOT FOUND" "No iRule with $text on a virtual server." fi printf '%s' "$out" } irule K000163939 CVE-2026-120285 "PSC::ip_address" "PSC::ip_address" irule K000163940 CVE-2026-120292 "MR::message_route" "MR::message route" irule K000163941 CVE-2026-116953 "GENERICMESSAGE::route" "GENERICMESSAGE::route" irule K000163945 CVE-2026-120722 "DNS::scrape" "DNS::scrape" irule K000163946 CVE-2026-121805 "PEM::subscriber" "PEM::subscriber" # K000163942: SAML service provider. saml=$(printf '%s\n' "$agents" | awk '$4 == "aaa-saml" { print $5 }' | tr '\n' ' ') if [ "$ehf" = 1 ]; then line K000163942 CVE-2026-126822 FIXED "This build is an engineering hotfix of November 18, 2026." elif [ -n "$saml" ]; then line K000163942 CVE-2026-126822 FOUND "SAML Auth agent in an access policy: $saml" else line K000163942 CVE-2026-126822 "NOT FOUND" "No SAML Auth agent." fi # K000163943: SAML service provider with encrypted assertions. enc=$(t "list apm aaa saml recursive one-line" | grep "want-assertion-encrypted true" | awk '{ print $4 }' | tr '\n' ' ') case "$(rel 17.5.1.10 17.1.3.6 21.1.0.3)" in 1) line K000163943 CVE-2026-126336 FIXED "F5 corrected this in a release that this version includes." ;; *) if [ -n "$enc" ]; then line K000163943 CVE-2026-126336 FOUND "SAML service provider with encrypted assertions: $enc" else line K000163943 CVE-2026-126336 "NOT FOUND" "No SAML service provider with encrypted assertions." fi ;; esac # K000163944: per-request policy and the tmm.access.policytrace key. trace=$(tmsh -q list sys db tmm.access.policytrace value 2>/dev/null | awk '$1 == "value" { gsub(/"/, "", $2); print $2 }') if [ "$ehf" = 1 ]; then line K000163944 CVE-2026-121812 FIXED "This build is an engineering hotfix of November 18, 2026." elif [ "$trace" = enable ] && [ -n "$prp_virtuals" ]; then line K000163944 CVE-2026-121812 FOUND "tmm.access.policytrace is enable, and a virtual server has a per-request policy." else line K000163944 CVE-2026-121812 "NOT FOUND" "tmm.access.policytrace is ${trace:-not known}." fi # K000163929 and K000163936: iControl. No configuration condition. case "$(rel 17.5.1.10 17.1.3.6 21.1.0.2)" in 1) line K000163929 CVE-2026-120718 FIXED "F5 corrected this in a release that this version includes." ;; *) line K000163929 CVE-2026-120718 ALL "iControl REST. See the article for the mitigation." ;; esac case "$(rel 17.5.1.10 17.1.3.6 21.1.0.3)" in 1) line K000163936 CVE-2026-125274 FIXED "F5 corrected this in a release that this version includes." ;; *) line K000163936 CVE-2026-125274 ALL "iControl SOAP. See the article for the mitigation." ;; esac if [ -n "$prp_virtuals" ]; then echo "Virtual servers with a per-request policy:" printf '%s\n' "$prp_virtuals" | sed 's/^/ /' fi- Copy the script to the BIG-IP system as
Mitigations from F5
F5 gives a mitigation for 4 of the 12 issues. For the other 8, the F5 articles say "None". Each F5 article has the full steps and the related F5 articles. Read it before you make a change.
F5 article Mitigation that F5 gives K000163942 If you do not need the SAML service provider, remove the SAML Auth agent from the access policy. Permit access to the virtual server only from trusted client networks K000163943 Configure high availability (HA) to decrease the effect of a TMM restart K000163936 Remove iControl SOAP access for users that you do not fully trust. Block iControl SOAP access through the self IP addresses and the management interface K000163929 Change the scripts that make iControl REST tokens. Make each script delete its token when the work is done Steps that F5 does not list
These steps come from the conditions in the F5 articles. They are our estimate. F5 does not list them as mitigations, and we did not test them against an attack. Use them only if they do not change a function that you need.
- iRule commands. Each of the 5 iRule issues needs the iRule on a virtual server. If the check script finds an iRule that you do not use, remove it from the virtual server.
- The policy trace key. CVE-2026-121812 needs the
tmm.access.policytracekey enabled. F5 says that the key is disabled by default. If the check script showsenableand you do not need the trace, disable the key with the command below. - Network access. Permit connections to the affected virtual servers only from the networks that your users connect from. This does not stop an attacker on a permitted network.
Command to disable the policy trace key
Run these commands in the bash shell of the active unit.
shell tmsh modify sys db tmm.access.policytrace value disable tmsh save sys configWhat to monitor
For 10 of the 12 issues, F5 says that the result is a TMM restart. These are the signs of one. We saw each of them in our lab.
- TMM restarts. The command
bigstart status tmmshows the number of restarts and how long TMM has run. A TMM that started a short time ago, with no known cause, is a sign. - Core files. Look in
/var/corefor files with names that start withtmm. In our lab, each stop made one file of approximately 90 MB. - The TMM log. Look in
/var/log/tmmand/var/log/tmm1forSIGSEGV. - The failover log. Look in
/var/log/ltmfor the entry in the example below. An unexpected failover can be the result of a TMM restart.
If you see these signs, keep the logs and the core files. Contact F5 Support and Tailwind Resource Group before you make changes.
Failover log entry
This is the entry in
/var/log/ltmfrom our lab when TMM stopped./var/log/ltm sod[7670]: 01140029:4: HA daemon_heartbeat tmm fails action is go offline down links and restart.- TMM restarts. The command
References
- F5 article K000164058 (opens in a new tab): the out-of-band security notification of November 18, 2026, and the list of articles.
- F5 article K000164239 (opens in a new tab): the engineering hotfix build for each version.
- F5 article K000163937 (opens in a new tab): CVE-2026-123637, F5 ID 2567577. The condition, the scores, the vulnerable versions and the fixes.
- F5 article K000163938 (opens in a new tab): CVE-2026-125272, F5 IDs 2719261 and 2535485. The condition, the scores, the vulnerable versions and the fixes.
- F5 article K000163939 (opens in a new tab): CVE-2026-120285, F5 ID 2719389. The condition, the scores, the vulnerable versions and the fixes.
- F5 article K000163940 (opens in a new tab): CVE-2026-120292, F5 ID 2719437. The condition, the scores, the vulnerable versions and the fixes.
- F5 article K000163941 (opens in a new tab): CVE-2026-116953, F5 ID 2719457. The condition, the scores, the vulnerable versions and the fixes.
- F5 article K000163945 (opens in a new tab): CVE-2026-120722, F5 ID 2535409. The condition, the scores, the vulnerable versions and the fixes.
- F5 article K000163946 (opens in a new tab): CVE-2026-121805, F5 ID 2734381. The condition, the scores, the vulnerable versions and the fixes.
- F5 article K000163942 (opens in a new tab): CVE-2026-126822, F5 ID 2732661. The condition, the scores, the fixes and the mitigation.
- F5 article K000163943 (opens in a new tab): CVE-2026-126336, F5 ID 2719349. The condition, the scores, the fixed versions and the mitigation.
- F5 article K000163944 (opens in a new tab): CVE-2026-121812, F5 ID 2727661. The condition, the scores, the vulnerable versions and the fixes.
- F5 article K000163936 (opens in a new tab): CVE-2026-125274, F5 ID 2431789. The condition, the scores, the fixed versions and the mitigation.
- F5 article K000163929 (opens in a new tab): CVE-2026-120718, F5 ID 2377801. The condition, the scores, the fixed versions and the mitigation.
About this advisory
The conditions, the scores, the versions and the fixes in this page are from the F5 articles in "References". The check script, the lab results and "Steps that F5 does not list" are ours. They are not statements from F5, and F5 did not examine them. The check script is licensed under the Apache License 2.0 and is supplied as it is, with no warranty. You are responsible for tests in your environment. We will update this page when F5 changes its articles, or when our tests give new results.