SecBoard
Zurück zur CVE-Übersicht

CVE-2026-121805

CRITICAL(9.8)

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

Risk Signal Score30/100 — MITTEL
  • CVSS 9.8 — Kritisch

Erwähnungen (letzte 60 Tage)

Artikel

EPSS-Score

0.7%

Exploit-Wahrscheinlichkeit (30 Tage)

CVSS Score

9.8

Technische Schwere

Beschreibung

Description: When an iRule that processes client traffic using the PEM::subscriber 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 and may 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.

Erkennung & Indikatoren

Ausnutzung

In den geprüften Quellen nicht genannt

Threat-Hunting-Queries

Sentinel/Defender KQL

let timeframe = 1d;
DeviceNetworkEvents
| where ActionType == "ConnectionAttempt"
| where RemotePort == 443 or RemotePort == 80 // Assuming typical web traffic ports for BIG-IP
| where InitiatingProcessFileName contains "tmm" // Targeting the TMM process
| summarize RequestCount = count() by DeviceName, RemoteIP, RemotePort, InitiatingProcessFileName
| where RequestCount > X // Define a threshold for unusual request volume
| project DeviceName, RemoteIP, RemotePort, InitiatingProcessFileName, RequestCount
| join kind=inner (DeviceProcessEvents
    | where InitiatingProcessFileName contains "tmm"
    | where ActionType == "ProcessTerminated"
    | summarize TerminationCount = count() by DeviceName, InitiatingProcessFileName
    | where TerminationCount > 0
) on DeviceName, InitiatingProcessFileName
| project DeviceName, RemoteIP, RemotePort, RequestCount, TerminationCount, InitiatingProcessFileName
| extend AlertReason = "Potential TMM termination due to unusual request patterns"

Splunk SPL

index=* sourcetype=f5_bigip_logs (tmm OR "Traffic Management Microkernel") (terminate OR restart OR crash) 
| stats count by host, source, _time 
| eval time_diff = _time - relative_time(now(), "-1d") 
| where time_diff < 86400 
| join host [search index=* sourcetype=f5_bigip_logs (PEM::subscriber) 
    | stats count by host, source, _time 
    | eval time_diff = _time - relative_time(now(), "-1d") 
    | where time_diff < 86400 ] 
| table _time, host, source, count 
| rename count as TMM_Termination_Count 
| eval AlertReason = "Potential TMM termination on BIG-IP with PEM::subscriber iRule due to undisclosed requests"

Sigma

title: F5 BIG-IP TMM Termination with PEM::subscriber iRule
id: 00000000-0000-0000-0000-000000000000 # Placeholder, generate a real UUID
status: experimental
description: Detects potential Traffic Management Microkernel (TMM) termination on F5 BIG-IP systems configured with PEM::subscriber iRules, which may indicate exploitation of CVE-2026-121805.
references:
  - https://nvd.nist.gov/vuln/detail/CVE-2026-121805
logsource:
  product: f5
  service: bigip
detection:
  selection_tmm_termination:
    EventID: '*'
    Message|contains:
      - 'TMM terminated'
      - 'Traffic Management Microkernel restarting'
      - 'TMM crash'
  selection_pem_subscriber:
    EventID: '*'
    Message|contains:
      - 'PEM::subscriber'
      - 'iRule'
  condition: selection_tmm_termination and selection_pem_subscriber
fields:
  - host
  - Message
level: high

Elastic ES|QL

from logs
| where host.name : "f5_bigip_logs"
| where message : "TMM terminated" or message : "Traffic Management Microkernel restarting" or message : "TMM crash"
| where message : "PEM::subscriber" or message : "iRule"
| limit 100
| sort @timestamp desc
| project @timestamp, host.name, message
| append { from logs
    | where host.name : "f5_bigip_logs"
    | where process.name : "tmm"
    | where event.action : "process_terminated"
    | limit 100
    | sort @timestamp desc
    | project @timestamp, host.name, process.name, event.action, message
}

SecBoard-generated · behavioral · requires customization — Von SecBoard erzeugt und nicht in einer Zielumgebung validiert. Vor dem Einsatz an die eigene Protokollierung anpassen.

Referenzen