CVE-2025-58071VulnerabilityPublished 15 Oct 2025Updated 26 Feb 2026

CVE-2025-58071: F5 BIG-IP · Use of Uninitialized Variable

Affects F5 BIG-IPSource CVE Database V5

Not known to be exploited · CVSS 7.5 High.

Data as of 26 Oct 2026, 06:26 UTC

CVSS 3.1 base score

7.5High

How severe the flaw is on the 0–10 CVSS scale.

EPSS: 0.3% chance of exploitation in 30 days – higher than 30% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.

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

Attack Vector: Network
Attack Complexity: Low
Privileges Required: None
User Interaction: None
Scope: Unchanged
Confidentiality: None
Integrity: None
Availability: High

Bold values are the worst case: easiest to exploit or largest impact.

Attack Vector: Network: The vulnerable component is bound to the network stack and the set of possible attackers extends beyond the other options listed, up to and including the entire Internet. Such a vulnerability is often termed 'remotely exploitable' and can be thought of as an attack being exploitable at the protocol level one or more network hops away (e.g., across one or more routers).
Attack Complexity: Low: Specialized access conditions or extenuating circumstances do not exist. An attacker can expect repeatable success against the vulnerable component.
Privileges Required: None: The attacker is unauthorized prior to attack, and therefore does not require any access to settings or files to carry out an attack.
User Interaction: None: The vulnerable system can be exploited without any interaction from any user.
Scope: Unchanged: An exploited vulnerability can only affect resources managed by the same security authority. In this case, the vulnerable component and the impacted component are either the same, or both are managed by the same security authority.
Confidentiality: None: There is no loss of confidentiality within the impacted component.
Integrity: None: There is no loss of integrity within the impacted component.
Availability: High: There is total loss of availability, resulting in the attacker being able to fully deny access to resources in the impacted component; this loss is either sustained (while the attacker continues to deliver the attack) or persistent (the condition persists even after the attack has completed). Alternatively, the attacker has the ability to deny some availability, but the loss of availability presents a direct, serious consequence to the impacted component (e.g., the attacker cannot disrupt existing connections, but can prevent new connections; the attacker can repeatedly exploit a vulnerability that, in each instance of a successful attack, leaks a only small amount of memory, but after repeated exploitation causes a service to become completely unavailable).

Definitions: FIRST CVSS v3.1 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 15 Oct 2025
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 2026-10-26.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponised: Public exploit code exists in Metasploit or Exploit-DB, or CISA SSVC reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

Affected software

Product	Affected	Fixed in
F5 BIG-IP	Affected =17.5.0 =17.1.0 =16.1.0 =15.1.0	Fixed in–

AI-suggested

1. Monitor network traffic for unusual or malformed packets targeting IPsec interfaces on BIG-IP devices to detect potential exploitation attempts. 2. Restrict access to IPsec-configured BIG-IP interfaces using network segmentation and firewall rules to limit exposure to untrusted networks. 3. Implement rate limiting or traffic filtering to reduce the risk of triggering the vulnerability via undisclosed traffic patterns. 4. Maintain up-to-date backups and disaster recovery plans to quickly restore services in case of TMM crashes. 5. Apply vendor patches and updates as soon as they become available; coordinate with F5 support for early access or workarounds. 6. Consider temporarily disabling IPsec configurations if feasible and if the risk outweighs operational needs until a patch is applied. 7. Conduct thorough testing of BIG-IP devices in a controlled environment to understand the impact of the vulnerability and validate mitigation controls. 8. Stay informed through F5 security advisories and trusted threat intelligence sources for updates on exploit availability and mitigation guidance.

Description

When IPsec is configured on the BIG-IP system, undisclosed traffic can cause the Traffic Management Microkernel (TMM) to terminate. Note: Software versions which have reached End of Technical Support (EoTS) are not evaluated.

Impact

The primary impact of CVE-2025-58071 is a denial-of-service condition caused by the termination of the TMM process on BIG-IP devices configured with IPsec. This can lead to network outages, disruption of security services such as VPNs, load balancing, and application delivery, and potential downtime for critical business applications. Organizations that rely heavily on BIG-IP for secure remote access, traffic management, or as a security gateway may experience significant operational impact. The vulnerability can be exploited remotely without authentication or user interaction, increasing the risk of widespread attacks. While confidentiality and integrity are not directly affected, the loss of availability can indirectly impact business continuity and service level agreements. The lack of known exploits in the wild currently reduces immediate risk, but the vulnerability’s characteristics make it a likely target once exploit code becomes available. The impact is especially critical for sectors such as finance, telecommunications, government, and healthcare, where BIG-IP devices are commonly deployed and high availability is essential.

CWE-457Use of Uninitialized Variable (opens in a new tab)
Variant weaknessLikelihood of exploit: High
The code uses a variable that has not been initialized, leading to unpredictable or unintended results.
Implementation · Attack Surface Reduction
Ensure that critical variables are initialized before first use.
Build and Compilation · Compilation or Build Hardening
Most compilers will complain about the use of uninitialized variables if warnings are turned on.
Implementation · Operation
When using a language that does not require explicit declaration of variables, run or compile the software in a mode that reports undeclared or unknown variables. This may indicate the presence of a typographic error in the variable's name.
From MITRE CWE, MITRE CAPEC and OWASP (Top 10, OpenCRE).

References

my.f5.com/manage/s/article/K000156746 (opens in a new tab)

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 27 Feb 2026, 05:38 UTC

WeaknessesCWE-457

Technical details

References

Community reviews

Related threats