Signal is active with 4 mentions in latest observed window
Immediate actions
Track advisory updates for patch or workaround availability
Recommended action window: Monitor and triage in normal cycle
NVD description
Description
When an HTTP profile and an iRule containing the PSC::ip_address command are 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 and may allow the attacker 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.
F5 has disclosed six critical BIG-IP vulnerabilities that could allow unauthenticated attackers to disrupt network traffic and potentially execute code remotely.
All six are stack-based buffer overflows rated 9.8 (CVSS v3.1):
- CVE-2026-123637
- CVE-2026-121805
- CVE-2026-120292
- CVE-2026-120285
- CVE-2026-116953
- CVE-2026-120722
Exploitation requires specific iRule or Access Policy Manager configurations.
There are no documented workarounds and no confirmed active exploitation.
If you run F5 BIG-IP in production, audit your virtual server configurations and prioritize testing and deploying the available engineering hotfixes.
🚨 تحذير أمني خطير من F5 !
كشفت الشركة عن 6 ثغرات حرجة في أنظمة BIG-IP بدرجة خطورة 9.8 من 10 !
الثغرات المكتشفة:
• الثغرة - CVE-2026-116953
• الثغرة - CVE-2026-120285
• الثغرة - CVE-2026-120292
• الثغرة - CVE-2026-120722
• الثغرة - CVE-2026-121805
• الثغرة - CVE-2026-123637
⚠️ ما خطورتها؟
قد تسمح لمهاجم عن بُعد ودون مصادقة بتعطيل عملية TMM المسؤولة عن معالجة حركة الشبكة والتسبب بانقطاع الخدمات مع احتمال تنفيذ تعليمات برمجية عن بُعد (RCE).
الثغرات تتعلق بمكونات iRules وAPM وتتطلب إعدادات معينة لتكون قابلة للاستغلال.
🛡️ أصدرت F5 تصحيحات هندسية طارئة (EHF) وتوصي مسؤولي الأنظمة بمراجعة الإصدارات والإعدادات المتأثرة وتثبيت التصحيح المناسب.
لم يُؤكد حتى الآن استغلال هذه الثغرات الست في هجمات فعلية.
📌 المصدر الرسمي:
https://my.f5.com/s/article/K000164058
#أمن_سيبراني #F5#BIGIP #تقنية
00000
Sam | AI bots that do real work@SamAiPr·
PATCH NOW. 18 Nov 2026: F5 disclosed six critical flaws in BIG-IP.
The CVE IDs are CVE-2026-123637, CVE-2026-121805, CVE-2026-120292, CVE-2026-120285, CVE-2026-116953, and CVE-2026-120722. F5 published the records on 18 November 2026. F5 is the CNA. Each flaw is a stack-based buffer overflow, CWE-121, in the data plane. F5 says an unauthenticated attacker can cause the Traffic Management Microkernel (TMM) to terminate. Traffic is disrupted while TMM restarts. F5 also says the flaws may lead to remote code execution. F5 says there is no control plane exposure. This is a data-plane issue only.
Each flaw needs a specific configuration on a virtual server:
CVE-2026-123637 needs BIG-IP APM provisioned, and a per-request policy that includes the Client Information agent and Endpoint Security agents. This record lists BIG-IP only.
CVE-2026-121805 needs an iRule that processes client traffic using PEM::subscriber. This record lists BIG-IP, BIG-IP Next for Kubernetes, and BIG-IP Next CNF.
CVE-2026-120292 needs an HTTP profile and an iRule that uses MR::message route. This record lists BIG-IP and BIG-IP Next for Kubernetes.
CVE-2026-120285 needs an HTTP profile and an iRule that uses PSC::ip_address. This record lists BIG-IP, BIG-IP Next for Kubernetes, and BIG-IP Next CNF.
CVE-2026-116953 needs an iRule that processes client traffic using GENERICMESSAGE::route. This record lists BIG-IP and BIG-IP Next for Kubernetes.
CVE-2026-120722 needs an iRule that processes client traffic using DNS::scrape. This record lists BIG-IP, BIG-IP Next for Kubernetes, and BIG-IP Next CNF.
What is affected
F5's CVE records list the BIG-IP 21.1, 17.5, and 17.1 branches as affected, starting at 21.1.0, 17.5.0, and 17.1.0, until the listed engineering hotfixes. Where Next for Kubernetes or Next CNF is in a record, F5 lists the 2.4, 2.3, and 2.2 lines, starting at 2.4.0, 2.3.0, and 2.2.0. F5 says versions that have reached End of Technical Support are not evaluated. An older release that is missing from those tables has not been shown to be safe.
The http://my.f5.com K-articles were not readable without a login at the time of this check. The version list above comes from the public F5 CNA records.
How severe
F5 assigned a CVSS 3.1 score of 9.8 (Critical) and a CVSS 4.0 score of 9.3 (Critical) for each of the six flaws. The CVSS 3.1 vector is CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H. The CVSS 4.0 vector is CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N. NVD has received the records and has not yet completed its own assessment.
Exploit status
F5 does not say the flaws are exploited. CISA ADP SSVC marks Exploitation as none on each record. As of 19 November 2026, none of the six IDs is in the CISA Known Exploited Vulnerabilities catalog.
Fix
The fixes listed in the F5 CVE records are engineering hotfixes. F5 lists no workaround. For BIG-IP, the listed fixed builds are BIGIP-21.1.0.4.0.19.3-ENG for the 21.1 branch; BIGIP-17.5.1.11.0.61.12-ENG or BIGIP-17.5.1.10.0.80.35-ENG for the 17.5 branch; and BIGIP-17.1.3.7.0.21.4-ENG or BIGIP-17.1.3.6.0.14.20-ENG for the 17.1 branch. For BIG-IP Next for Kubernetes, and in the CNA records that also list Next CNF, the listed fixed builds are BNK-2.4.2-EHF1, BNK-2.3.4-EHF1, and BNK-2.2.5-EHF1.
What to check
Check whether each virtual server uses one of the listed iRules or the APM per-request policy. If it does, apply the matching engineering hotfix. Then confirm the new build.
Damian the Grey@realdamiangrey·
It's known as 👇
CVE-2026-120285: Big-IP vulnerability
🆕 New CVE: CVE-2026-120285 (CVSS 9.8, Enclave score 4/10)
F5 BIG-IP + 1 more · Information disclosure
Remote, no login needed.
Description When an HTTP profile and an iRule containing the PSC::ip_address command are configured on a virtual server…
https://app.enclave.ai/threat-feed/CVE-2026-120285