Skip to main content

F5 BIG-IP CVE-2026-41956

| EUVDEUVD-2026-29990 HIGH
Stack-based Buffer Overflow (CWE-121)
2026-05-13 f5 GHSA-7vhg-fvrv-7x3q
8.7
CVSS 4.0 · Vendor: f5
View

Attack ChainAIDerived

Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain

  1. Access
    Network access to UDP virtual server
  2. Delivery
    Send crafted UDP payload
  3. Exploit
    Trigger stack overflow in TMM classification engine
  4. Execution
    TMM process termination
  5. Impact
    Service denial

Vulnerability Assessment

Weakness
CWE
ASVS 5.0
V15 - Secure Coding and Architecture Stack buffer bounds checking
MITRE ATT&CK

1 technique across 1 tactic: Execution

The technique list with ATT&CK links and the kill-chain view is part of the Basic plan and up.

Exploitation Conditions

UDP virtual server with classification profile enabled on F5 BIG-IP, BIG-IP Next CNF, or BIG-IP Next for Kubernetes. Classification profiles are advanced traffic analysis features not enabled by default on all virtual servers, requiring deliberate administrator configuration for application identification and policy enforcement. Exploitation requires network access to the UDP virtual server's listening address and port. Standard UDP virtual server deployments without classification profiles are not vulnerable. The specific request patterns that trigger the overflow are undisclosed by F5, limiting attacker knowledge but also defender testing capabilities.

Impact

The CVSS 7.5 (High) rating reflects maximum network exploitability (AV:N/AC:L/PR:N/UI:N) with complete availability impact (A:H). However, real-world risk is constrained by specific deployment requirements: exploitation only affects UDP virtual servers with classification profiles enabled, which is not a universal default configuration. The network-accessible attack vector and low complexity are concerning for internet-facing UDP services (DNS, SIP, RADIUS), but the attack surface is limited to organizations using F5's advanced traffic classification features on UDP protocols. No KEV listing or public exploit code identified, suggesting exploitation has not been observed in the wild. The stack overflow vulnerability class (CWE-121) is well-understood by attackers but typically requires protocol-specific expertise to weaponize. Priority should be elevated for organizations running UDP-based services with classification profiles on internet-facing BIG-IP systems, particularly DNS infrastructure and VoIP gateways. Organizations not using classification profiles on UDP virtual servers face minimal practical risk despite the high CVSS score.

Exploit ScenarioDerived

An unauthenticated remote attacker identifies a BIG-IP virtual server configured to handle UDP traffic with a classification profile enabled, such as a DNS load balancer or SIP gateway. The attacker crafts malicious UDP packets containing payload patterns that trigger the stack buffer overflow in TMM's classification engine, causing immediate TMM process termination and resulting in denial of service for all traffic processed by that TMM instance, disrupting critical services for legitimate users.

This Week Schedule remediation this week. Why: HIGH severity (CVSS 7.0-8.9).
Patch available 0.1% exploitation probability (EPSS)

Get an e-mail when this CVE is exploited, patched or re-scored. Free account.

Alert me

AnalysisAIv1 – May 13, 2026

Remote denial-of-service in F5 BIG-IP allows unauthenticated attackers to crash the Traffic Management Microkernel (TMM) by sending specially crafted UDP requests to virtual servers with classification profiles enabled. The vulnerability affects BIG-IP, BIG-IP Next CNF, and BIG-IP Next for Kubernetes platforms. No public exploit identified at time of analysis, with EPSS data unavailable for this recent CVE. Vendor-released patch available per F5 advisory K000158038.

RemediationAI

Apply vendor-released patches per F5 Security Advisory K000158038 (https://my.f5.com/manage/s/article/K000158038), which provides specific fixed versions for each affected product line. Patching is the primary remediation and should be prioritized for internet-facing UDP virtual servers with classification profiles. As a temporary mitigation for systems that cannot be immediately patched, administrators can disable classification profiles on UDP virtual servers, though this removes traffic analysis capabilities and may impact application visibility and policy enforcement. Alternatively, restrict UDP virtual server access to trusted networks using firewall rules or BIG-IP AFM policies, trading off service availability for security. For critical UDP services like DNS or SIP, consider moving to non-affected load balancers temporarily or implementing redundant BIG-IP instances with staggered patching schedules to maintain availability during remediation. Review F5 advisory for product-specific upgrade paths and compatibility considerations before applying patches to production systems.

Affected VersionsENISA

BIG-IP 17.1.0 <17.1.3.1
BIG-IP Next for Kubernetes 2.0.0 <2.1.0
BIG-IP Next CNF 2.0.0 <2.0.3
BIG-IP Next CNF 1.4.0 <1.4.1
BIG-IP 16.1.0 <*
BIG-IP 17.5.0 <17.5.1.4

Affected Packages

euvd big_ip fix: 17.1.3.1, 17.5.1.4
euvd big_ip_next_cnf fix: 1.4.1, 2.0.3
euvd big_ip_next_for_kubernetes fix: 2.1.0

Source: OSV (Open Source Vulnerabilities)

Affects your stack

Affects 3 packages in euvd

Checking this CVE against your own stacks and servers is part of the Basic plan and up.

Technical ContextAI · show details

F5 BIG-IP's Traffic Management Microkernel (TMM) is the core data plane component responsible for processing and forwarding network traffic through virtual servers. This vulnerability stems from a stack-based buffer overflow (CWE-121) in TMM's handling of UDP traffic when classification profiles are applied. Classification profiles analyze traffic patterns for application identification and policy enforcement. The flaw occurs during parsing or processing of undisclosed UDP request patterns, causing a write operation to exceed stack boundaries and triggering TMM process termination. Affected products span the traditional BIG-IP appliances (cpe:2.3:a:f5:big-ip), container-native BIG-IP Next CNF (Cloud-Native Function), and BIG-IP Next for Kubernetes deployments, indicating the vulnerable code exists across multiple F5 product architectures.

Know when Big Ip Next For Kubernetes gets its next vulnerability

  • Watch products and get an email when something new is published
  • Check this CVE against your own stack and servers
  • Exploit and PoC references, threat intelligence from 22 sources

No credit card · 7-day full trial

Severity by source

Vendor (f5) PRIMARY 8.7 HIGH
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:N/VA:H/SC:N/SI:N/SA:N

Primary rating from Vendor (f5) · only source for this CVE.

CVSS VectorVendor: f5

Attack Vector
Network
Attack Complexity
Low
Attack Requirements
None
Privileges Required
None
User Interaction
None
Vulnerable system: Confidentiality
None
Vulnerable system: Integrity
None
Vulnerable system: Availability
High
Subsequent system: Confidentiality
None
Subsequent system: Integrity
None
Subsequent system: Availability
None

Lifecycle Timeline

2
CVSS changed
May 13, 2026 - 16:22 NVD
7.5 (HIGH) 8.7 (HIGH)
CVE Published
May 13, 2026 - 14:12 nvd
HIGH 7.5

DescriptionCVE.org

When a classification profile is configured on a UDP virtual server, undisclosed requests can cause the Traffic Management Microkernel (TMM) to terminate.  Note: Software versions which have reached End of Technical Support (EoTS) are not evaluated.

Executive ViewAI

Why It Matters

F5 BIG-IP platforms are vulnerable to unauthenticated remote denial-of-service attacks that can crash the Traffic Management Microkernel, disrupting load balancing and application availability across affected infrastructure. Organizations running BIG-IP, BIG-IP Next CNF, or BIG-IP Next for Kubernetes with classification profiles enabled require immediate patching to prevent service interruptions.

Business Impact: High
Compensating Controls

If immediate patching is not feasible: (1) Restrict UDP traffic to virtual servers with classification profiles enabled using network ACLs or firewall rules; (2) Implement rate limiting on UDP requests to affected virtual servers; (3) Disable classification profiles if not operationally critical; (4) Monitor TMM process health and implement automated restart policies. Apply vendor patch as the primary remediation.

Threat Intelligence Overview

EPSS Score
0.1%
Top 78% exploitable
Data Quality
6 sources
Confidence: High

How this decision was reached

The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.

SignalValue
Severity HIGH
CISA KEV No
Public POC No
EPSS 0.1%
Patch available Yes
Active threat No
Deciding rule
HIGH severity (CVSS 7.0-8.9)
What every action level means
Emergency Immediate action required. Criteria: CRITICAL + in CISA KEV (actively exploited) without patch, OR CRITICAL + EPSS > 30% without patch, OR CRITICAL + active threat signals without patch.
Act Now Prioritize within 24-48h. Criteria: in KEV with patch available, OR CRITICAL + public POC, OR HIGH + EPSS > 10%, OR CRITICAL + active threat, OR any CRITICAL severity.
This Week Schedule remediation this week. Criteria: HIGH severity (CVSS 7.0-8.9). Patch within normal change window.
This Month Plan within 30 days. Criteria: MEDIUM severity (CVSS 4.0-6.9), lower exploitation probability. Include in regular patch cycle.
Monitor Track and reassess. Criteria: LOW severity (CVSS 0.1-3.9), minimal exploitation risk. No immediate action needed.

SSVC AssessmentENISA

SSVC Decision
Scheduled
Exploitation
None
System Exposure· derived
Open
Automatable
Yes
Human Impact
High
Technical Impact
Partial

Priority Score

44
Low Medium High Critical
KEV: 0
EPSS: 0
CVSS: +44
PoC: 0
Weaponized: 0
Threat intel: 0
Gov advisory: 0

Attack Technique

A buffer overflow occurs when a program writes more data to a memory buffer than it was allocated to hold, causing the excess data to spill into adjacent memory regions.

A stack-based buffer overflow occurs when a program writes more data to a buffer located on the stack than it was allocated to hold.

CVE-2025-61974 HIGH
8.7 Oct 15

Uncontrolled memory consumption in F5 BIG-IP Next for Kubernetes, BIG-IP Next Cloud-Native Network Functions and BIG-IP

CVE-2025-58071 HIGH
8.7 Oct 15

Denial of service in F5 BIG-IP allows remote, unauthenticated attackers to terminate the Traffic Management Microkernel

CVE-2025-61990 HIGH
8.7 Oct 15

Denial of service in F5 BIG-IP allows remote, unauthenticated attackers to terminate the Traffic Management Microkernel

CVE-2025-58120 HIGH
8.7 Oct 15

Denial of service in F5 BIG-IP Next deployments with HTTP/2 Ingress enabled allows unauthenticated network attackers to

CVE-2025-54479 HIGH
8.7 Oct 15

A remote, unauthenticated denial-of-service condition exists in F5 BIG-IP Policy Enforcement Manager (and the BIG-IP Nex

CVE-2026-59762 HIGH
8.7 Jul 15

Memory-exhaustion denial of service in F5 BIG-IP affects any virtual server configured with an HTTP/2 profile, where a r

CVE-2026-42409 HIGH
8.7 May 13

Remote unauthenticated attackers can crash F5 BIG-IP and BIG-IP Next Traffic Management Microkernel (TMM) processes via

CVE-2026-40618 HIGH
8.7 May 13

Traffic Management Microkernel (TMM) crashes in F5 BIG-IP Virtual Edition and hardware platforms when SSL profiles are c

CVE-2026-40629 HIGH
8.7 May 13

Denial of service in F5 BIG-IP virtual servers with SSL profiles allows remote unauthenticated attackers to exhaust conn

CVE-2025-55670 HIGH
7.1 Oct 15

Repeated calls to an undisclosed API endpoint can force the Traffic Management Microkernel (TMM) to terminate on F5 BIG-

CVE-2025-54805 MEDIUM
6.0 Oct 15

Memory exhaustion in F5 BIG-IP Next can be induced when iRules configured through the declarative API are repeatedly re-

CVE-2025-54500 MEDIUM
6.9 Aug 13

An HTTP/2 implementation flaw allows a denial-of-service (DoS) that uses malformed HTTP/2 control frames in order to bre

This site uses cookies essential for authentication and security. No tracking or analytics cookies are used. Privacy Policy