Skip to content
A detailed explainer is available in Japanese. Read the Japanese explainer
Critical 9.8

BIG-IPに脆弱性6件、TMM停止とRCEの恐れ・修正版あり

CVE-2026-120722 First seen on SecPulse

Summary

BIG-IPの通信処理を担うTMMが外部からの要求で停止し、コード実行に至るおそれもある脆弱性が6件公表されました。BIG-IPやBIG-IP Next for Kubernetesを運用する組織は、版と該当設定を確認して修正版へ更新してください。

AI summary

Produced by SecPulse using an external AI model; it may contain mistakes. Check the original description and references below before acting on it.

BIG-IPの通信処理を担うTMMが外部からの要求で停止し、コード実行に至るおそれもある脆弱性が6件公表されました。BIG-IPやBIG-IP Next for Kubernetesを運用する組織は、版と該当設定を確認して修正版へ更新してください。

Affected packages

PackageAffected → Fixed
F5BIG-IP
≥ 21.1.0 (no fix yet)→ Not listed
≥ 17.5.0 (no fix yet)→ Not listed
≥ 17.1.0 (no fix yet)→ Not listed
F5BIG-IP Next for Kubernetes
≥ 2.4.0 (no fix yet)→ Not listed
≥ 2.3.0 (no fix yet)→ Not listed
≥ 2.2.0 (no fix yet)→ Not listed
F5BIG-IP Next CNF
≥ 2.4.0 (no fix yet)→ Not listed
≥ 2.3.0 (no fix yet)→ Not listed
≥ 2.2.0 (no fix yet)→ Not listed

This record does not list fixed versions. Check the article or the vendor advisory in the references for whether and where it is fixed.

Original description The description as published by the source.

Description:

When an iRule that processes client traffic using the DNS::scrape command is configured on a virtual server, undisclosed requests can cause the Traffic Management Microkernel (TMM) to terminate and may lead to remote code execution (RCE). 

Impact:

Traffic is disrupted while the TMM process restarts. This vulnerability allows a remote, unauthenticated attacker to cause a denial-of-service (DoS) on the BIG-IP system. In addition, the attacker may be able to perform RCE. There is no control plane exposure; this is a data plane issue only.

Note: Software versions which have reached End of Technical Support (EoTS) are not evaluated.

Source: CVE.org (CVE Program・cvelistV5) NVD

References

We use cookies for analytics and ad measurement. This setting applies to all Game co., Ltd. sites. Details