Skip to main content
View

Attack ChainAIDerived

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

  1. Access
    Gain network path to BIG-IP
  2. Exploit
    Inject undisclosed crafted traffic
  3. Execution
    Corrupt data in protocol lacking integrity checks
  4. Impact
    Unauthorized data modification

Vulnerability Assessment

Weakness
CWE
Exploitation Conditions

Exploitation requires that the targeted BIG-IP traffic use a protocol WITHOUT message integrity protection, and that the attacker be able to deliver 'undisclosed' crafted traffic into that flow - reflected in the CVSS Attack Requirements PRESENT (AT:P) metric, which gates the otherwise unauthenticated network vector. Limiting factors: impact is confined to LOW integrity (data corruption/unauthorized modification) with no confidentiality or availability loss; software versions at End of Technical Support are explicitly not evaluated; and the attacker needs a suitable position/condition to inject traffic rather than a simple single unauthenticated request. No user interaction and no authentication are required per PR:N/UI:N.

Impact

This is a moderate-severity integrity issue, not an urgent priority. The vendor-supplied CVSS 4.0 score is 6.3 (Medium) with vector AV:N/AC:L/AT:P/PR:N/UI:N and VC:N/VI:L/VA:N - meaning network-reachable, unauthenticated, low complexity, but with Attack Requirements PRESENT (AT:P) and impact limited to LOW integrity only (no confidentiality, no availability). EPSS is low at 0.25% (14th percentile), the CVE is NOT on CISA KEV, and no public exploit code was identified, so all exploitation-likelihood signals align toward low real-world risk. The signals are internally consistent: AT:P indicates the attacker needs a specific condition (e.g., the targeted protocol must lack message integrity protection and the attacker must be positioned to inject 'undisclosed traffic'), which tempers the otherwise network/unauthenticated profile. One conflict worth noting: the input Tags include 'Information Disclosure', but the CVSS vector shows VC:N (no confidentiality impact) and VI:L (integrity impact) and the description describes data corruption/unauthorized modification - so the impact is integrity, not disclosure. Treat this as a defense-in-depth patch item rather than an emergency.

Exploit ScenarioDerived

An attacker positioned on the network path (or able to inject traffic into an in-flight session) sends undisclosed crafted traffic to a BIG-IP module handling a protocol that lacks message integrity protection, causing data corruption or unauthorized modification of the data in transit. No public proof-of-concept exists, and the CVSS AT:P flag indicates the attack only works under specific conditions (vulnerable protocol in use and a suitable injection/positioning opportunity), which is consistent with the low AC:L but gated exploitation.

This Month Plan within 30 days. Why: MEDIUM severity (CVSS 4.0-6.9).
No patch listed yet 0.2% exploitation probability (EPSS)

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

Alert me

AnalysisAIv1 – Oct 08, 2026

Undisclosed crafted network traffic can corrupt or modify data handled by F5 BIG-IP when the affected flow uses a protocol that lacks message integrity protection, allowing an unauthenticated remote party to alter data without any confidentiality or availability impact. The issue affects BIG-IP broadly across the LTM, ASM/Advanced WAF, APM, AFM, GTM/DNS, CGNAT, Container Ingress Services and related module lines, and carries a CVSS 4.0 base score of 6.3 (AV:N/AC:L/AT:P/PR:N/UI:N/VI:L), meaning exploitation is gated by attack prerequisites - the attacker must be able to inject traffic into a suitable integrity-less flow - rather than by authentication. Risk is moderate: EPSS is low at 0.25% (14th percentile), there is no KEV listing and no public exploit identified at time of analysis, so this is a hardening and integrity-assurance item rather than an emergency patch trigger.

RemediationAI

The authoritative fix guidance is F5 security advisory K000151297 (https://my.f5.com/manage/s/article/K000151297), which lists the fixed BIG-IP releases for each affected branch and module; apply the vendor's recommended upgrade for the branch you run, and note that no exact fixed version is established by the intelligence supplied here, so do not assume a specific build is patched without checking the advisory. Because EoTS branches are explicitly excluded from evaluation, plan to migrate off any end-of-support release rather than waiting for a backport. Where an immediate upgrade is not feasible, the effective compensating control is to remove the dependency on protocols that lack message integrity protection for any traffic crossing an untrusted path: terminate affected flows inside TLS/DTLS, IPsec or an equivalent integrity-protected tunnel, or enable per-protocol authentication mechanisms (for example TCP-MD5-style peer authentication, DNSSEC where applicable, or application-layer message signing). The trade-off is real - adding cryptographic integrity typically incurs CPU and latency overhead on the BIG-IP data plane, may not be supported by legacy peers that only speak the unprotected variant, and in some deployments requires re-issuing certificates or renegotiating peering. A blunter alternative is to restrict who can reach the affected virtual servers at all, tightening firewall and self-IP/management-access rules so that only trusted networks can deliver traffic into integrity-less flows; this reduces exposure but will break any legitimate client that must reach those services from outside the allow-list. Where neither is possible, enable logging and anomaly detection around the affected listener so unexpected data mutations are at least visible, accepting that detection does not prevent the modification.

Affects your stack

Find out whether the stacks and servers you run are on an affected version.

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

Technical ContextAI · show details

BIG-IP is F5's traffic-management, proxy and security platform, and the affected surface is its handling of network protocol payloads rather than a memory-safety flaw. The assigned root-cause class is CWE-340 (Generation of Predictable Numbers or Identifiers), which in this context describes weak or predictable values that an attacker positioned on the path can anticipate and supply, so that injected data is accepted as legitimate by a protocol that performs no message integrity or authenticity check on the payload. When a protocol does not provide a MAC, signature or equivalent end-to-end integrity guarantee, any party who can inject packets into the flow can alter in-transit data with the BIG-IP appliance unable to detect the change. The CVSS 4.0 vector reflects this precisely: Attack Requirements are PRESENT (AT:P) because a suitable injection position and an integrity-less protocol must both exist, while PR:N and UI:N confirm no credentials or victim interaction are needed once those conditions hold; VC/VA and all subsequent-system impact metrics are None, with only VI:L, so the outcome is bounded to low-severity integrity loss on the targeted system. F5 restrict the scope by stating that software versions past End of Technical Support are not evaluated, and the exact nature of the crafted 'undisclosed' traffic is deliberately withheld in the advisory.

Know when Big Ip Advanced Web Application Firewall 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 6.3 MEDIUM
CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:N/VI:L/VA:N/SC:N/SI:N/SA:N
vuln.today AI 3.7 LOW

Network-reachable and unauthenticated (AV:N/PR:N), but AT:P maps to AC:H given the required vulnerable-protocol and injection conditions; impact is low integrity only, so C:N/A:N.

3.1 AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:L/A:N
4.0 AV:N/AC:L/AT:P/PR:N/UI:N/VC:N/VI:L/VA:N/SC:N/SI:N/SA:N

Primary rating from Vendor (f5).

CVSS VectorVendor: f5

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

DescriptionCVE.org

On BIG-IP systems, undisclosed traffic can cause data corruption and unauthorized data modification in protocols which do not have message integrity protection.  Note: Software versions which have reached End of Technical Support (EoTS) are not evaluated.

Threat Intelligence Overview

EPSS Score
0.2%
Top 86% exploitable
Prevalence
High
F5 BIG-IP is widely deployed enterprise ADC/security appliance across many large networks
Data Quality
3 sources
Confidence: Low

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 MEDIUM
CISA KEV No
Public POC No
EPSS 0.2%
Patch available No
Active threat No
Deciding rule
MEDIUM severity (CVSS 4.0-6.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· derived
Scheduled
Exploitation· derived
None
System Exposure· derived
Open
Automatable· derived
Yes
Human Impact· derived
Medium

Priority Score

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

Attack Technique

Information disclosure occurs when an application unintentionally exposes sensitive data that aids attackers in reconnaissance or directly compromises security.

Affected Products (CPE)CVE.org

cpe:2.3:a:f5:big-ip_access_policy_manager:*:*:*:*:*:*:*:*
cpe:2.3:a:f5:big-ip_advanced_firewall_manager:*:*:*:*:*:*:*:*
cpe:2.3:a:f5:big-ip_advanced_web_application_firewall:*:*:*:*:*:*:*:*
cpe:2.3:a:f5:big-ip_analytics:*:*:*:*:*:*:*:*
cpe:2.3:a:f5:big-ip_application_acceleration_manager:*:*:*:*:*:*:*:*
cpe:2.3:a:f5:big-ip_application_security_manager:*:*:*:*:*:*:*:*
cpe:2.3:a:f5:big-ip_application_visibility_and_reporting:*:*:*:*:*:*:*:*
cpe:2.3:a:f5:big-ip_automation_toolchain:*:*:*:*:*:*:*:*
cpe:2.3:a:f5:big-ip_carrier-grade_nat:*:*:*:*:*:*:*:*
cpe:2.3:a:f5:big-ip_container_ingress_services:*:*:*:*:*:*:*:*
cpe:2.3:a:f5:big-ip_ddos_hybrid_defender:*:*:*:*:*:*:*:*
cpe:2.3:a:f5:big-ip_domain_name_system:*:*:*:*:*:*:*:*
cpe:2.3:a:f5:big-ip_edge_gateway:*:*:*:*:*:*:*:*
cpe:2.3:a:f5:big-ip_fraud_protection_service:*:*:*:*:*:*:*:*
cpe:2.3:a:f5:big-ip_global_traffic_manager:*:*:*:*:*:*:*:*
cpe:2.3:a:f5:big-ip_link_controller:*:*:*:*:*:*:*:*
cpe:2.3:a:f5:big-ip_local_traffic_manager:*:*:*:*:*:*:*:*
cpe:2.3:a:f5:big-ip_policy_enforcement_manager:*:*:*:*:*:*:*:*
cpe:2.3:a:f5:big-ip_ssl_orchestrator:*:*:*:*:*:*:*:*
cpe:2.3:a:f5:big-ip_webaccelerator:*:*:*:*:*:*:*:*
+ 43 more
CVE-2023-44487 HIGH POC
7.5 Oct 10

Denial of service against HTTP/2 server implementations allows remote unauthenticated attackers to exhaust server resour

CVE-2025-53521 CRITICAL POC
9.3 Oct 15

F5 BIG-IP APM (Access Policy Manager) contains a remote code execution vulnerability triggered by specific malicious tra

CVE-2025-20029 HIGH
8.7 Feb 05

F5 BIG-IP contains an authenticated command injection in the iControl REST API and TMOS Shell (tmsh) save command. Authe

CVE-2023-46747 CRITICAL POC
9.8 Oct 26

Undisclosed requests may bypass configuration utility authentication, allowing an attacker with network access to the BI

CVE-2021-22986 CRITICAL POC
9.8 Mar 31

On BIG-IP versions 16.0.x before 16.0.1.1, 15.1.x before 15.1.2.1, 14.1.x before 14.1.4, 13.1.x before 13.1.3.6, and 12.

CVE-2023-46748 HIGH POC
8.8 Oct 26

An authenticated SQL injection vulnerability exists in the BIG-IP Configuration utility which may allow an authenticated

CVE-2024-45844 HIGH POC
8.6 Oct 16

BIG-IP monitor functionality may allow an attacker to bypass access control restrictions, regardless of the port lockdow

CVE-2023-41373 CRITICAL
9.9 Oct 10

A directory traversal vulnerability exists in the BIG-IP Configuration Utility that may allow an authenticated attacker

CVE-2021-23031 CRITICAL
9.9 Sep 14

On version 16.0.x before 16.0.1.2, 15.1.x before 15.1.3, 14.1.x before 14.1.4.1, 13.1.x before 13.1.4, 12.1.x before 12.

CVE-2021-22987 CRITICAL
9.9 Mar 31

On BIG-IP versions 16.0.x before 16.0.1.1, 15.1.x before 15.1.2.1, 14.1.x before 14.1.4, 13.1.x before 13.1.3.6, 12.1.x

CVE-2021-22991 CRITICAL
9.8 Mar 31

On BIG-IP versions 16.0.x before 16.0.1.1, 15.1.x before 15.1.2.1, 14.1.x before 14.1.4, 13.1.x before 13.1.3.6, and 12.

CVE-2021-22992 CRITICAL
9.8 Mar 31

On BIG-IP versions 16.0.x before 16.0.1.1, 15.1.x before 15.1.2.1, 14.1.x before 14.1.4, 13.1.x before 13.1.3.6, 12.1.x

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