VulnerabilityPublished 15 Oct 2025Updated 26 Feb 2026

CVE-2025-58424: F5 BIG-IP · Generation of Predictable Numbers or Identifiers

Affects F5 BIG-IPSource CVE Database V5

Not known to be exploited · CVSS 5.3 Medium.

Data as of 26 Oct 2026, 10:12 UTC

CVSS 3.1 base score

5.3Medium

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

EPSS: 0.2% chance of exploitation in 30 days – higher than 15% 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:L/A:N

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

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: Low: Modification of data is possible, but the attacker does not have control over the consequence of a modification, or the amount of modification is limited. The data modification does not have a direct, serious impact on the impacted component.
Availability: None: There is no impact to availability within the impacted component.

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 26 Oct 2026.

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 or the CVSS exploit maturity 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.1.0 =16.1.0 =15.1.0	Fixed in–

AI-suggested

Monitor F5 Networks advisories closely for official patches addressing CVE-2025-58424 and apply them promptly once available.
Implement network segmentation and strict access controls to limit exposure of BIG-IP management and data plane interfaces to untrusted networks.
Employ protocol-level integrity protections where possible, such as enabling cryptographic message authentication codes (MACs) or using secure versions of protocols that inherently provide integrity checks.
Conduct thorough network traffic analysis to detect anomalous or malformed packets that could indicate exploitation attempts targeting predictable identifiers.
Review and harden BIG-IP configurations to minimize reliance on protocols without message integrity protection, replacing or upgrading legacy protocols where feasible.
Use intrusion detection/prevention systems (IDS/IPS) with signatures tuned to detect exploitation patterns related to predictable identifier generation.
Maintain up-to-date asset inventories and vulnerability management processes to ensure timely identification and remediation of affected BIG-IP devices.
Engage with F5 support for guidance on interim mitigations if patches are delayed, including potential workarounds or configuration changes to reduce risk.

Description

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.

Impact

The primary impact of CVE-2025-58424 is on data integrity within affected BIG-IP systems. Attackers can manipulate data in transit or stored by exploiting predictable identifiers, leading to unauthorized data modification and corruption. This can disrupt network traffic management, load balancing, or security functions performed by BIG-IP devices, potentially causing misrouting, incorrect access control decisions, or degraded service quality. Although confidentiality and availability are not directly compromised, the integrity breach can undermine trust in network communications and lead to secondary impacts such as compliance violations or operational disruptions. Organizations relying heavily on BIG-IP for critical infrastructure, including financial services, telecommunications, and government networks, may face increased risk of targeted attacks exploiting this vulnerability. The ease of remote exploitation without authentication increases the threat level, especially in environments where protocols lacking message integrity protection are in use. The absence of known exploits currently limits immediate risk, but the vulnerability remains a significant concern until patched.

CWE-340Generation of Predictable Numbers or Identifiers (opens in a new tab)
Class weaknessOWASP Top 10 A04:2025: Cryptographic Failures (opens in a new tab)
The product uses a scheme that generates numbers or identifiers that are more predictable than required.
OWASP Cheat Sheets
Forgot Password (opens in a new tab)
Transport Layer Protection (opens in a new tab)
User Privacy Protection (opens in a new tab)
Password Storage (opens in a new tab)
Cryptographic Storage (opens in a new tab)
OWASP ASVS 4.0.3
V2.3.1 (opens in a new tab)
V2.6.2 (opens in a new tab)
V2.7.6 (opens in a new tab)
From MITRE CWE, MITRE CAPEC and OWASP (Top 10, OpenCRE).

References

my.f5.com/manage/s/article/K000151297 (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:40 UTC

WeaknessesCWE-340

Technical details

References

Community reviews

Related threats