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

CVE-2025-57780: F5 F5OS – Appliance · CWE-250

Affects F5 F5OS – ApplianceSource CVE Database V5

Not known to be exploited · CVSS 8.8 High.

Data as of 26 Oct 2026, 06:26 UTC

CVSS 3.1 base score

8.8High

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

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

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

Attack Vector: Local
Attack Complexity: Low
Privileges Required: Low
User Interaction: None
Scope: Changed
Confidentiality: High
Integrity: High
Availability: High

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

Attack Vector: Local: The vulnerable component is not bound to the network stack and the attacker’s path is via read/write/execute capabilities. Either: the attacker exploits the vulnerability by accessing the target system locally (e.g., keyboard, console), or remotely (e.g., SSH); or the attacker relies on User Interaction by another person to perform actions required to exploit the vulnerability (e.g., tricking a legitimate user into opening a malicious document).
Attack Complexity: Low: Specialized access conditions or extenuating circumstances do not exist. An attacker can expect repeatable success against the vulnerable component.
Privileges Required: Low: The attacker is authorized with (i.e., requires) privileges that provide basic user capabilities that could normally affect only settings and files owned by a user. Alternatively, an attacker with Low privileges may have the ability to cause an impact only to non-sensitive resources.
User Interaction: None: The vulnerable system can be exploited without any interaction from any user.
Scope: Changed: An exploited vulnerability can affect resources beyond the security scope managed by the security authority of the vulnerable component. In this case, the vulnerable component and the impacted component are different and managed by different security authorities.
Confidentiality: High: There is total loss of confidentiality, resulting in all resources within the impacted component being divulged to the attacker. Alternatively, access to only some restricted information is obtained, but the disclosed information presents a direct, serious impact.
Integrity: High: There is a total loss of integrity, or a complete loss of protection. For example, the attacker is able to modify any/all files protected by the impacted component. Alternatively, only some files can be modified, but malicious modification would present a direct, serious consequence to 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 F5OS - Appliance	Affected =1.8.0 =1.5.0	Fixed in–

AI-suggested

To mitigate CVE-2025-57780, organizations should: 1) Immediately identify and inventory all F5OS-A and F5OS-C appliances running affected versions 1.5.0 and 1.8.0. 2) Restrict local access to these appliances strictly to trusted administrators and use strong authentication mechanisms, including multi-factor authentication where possible. 3) Monitor and audit all local login attempts and privilege escalations on these devices to detect suspicious activity early. 4) Implement network segmentation to limit access to management interfaces of F5 appliances, reducing the risk of unauthorized local access. 5) Stay informed on vendor advisories and apply patches or updates promptly once F5 releases fixes for this vulnerability. 6) Consider deploying compensating controls such as host-based intrusion detection systems (HIDS) on management stations and appliances to detect anomalous behavior. 7) Review and harden appliance configurations to minimize attack surface and ensure least privilege principles are enforced. 8) Conduct regular security assessments and penetration testing focused on appliance management interfaces and local access controls. These steps go beyond generic advice by emphasizing proactive access control, monitoring, and segmentation tailored to the nature of this vulnerability.

Description

A vulnerability exists in F5OS-A and F5OS-C system that may allow an authenticated attacker with local access to escalate their privileges. A successful exploit may allow the attacker to cross a security boundary. Note: Software versions which have reached End of Technical Support (EoTS) are not evaluated.

Impact

The potential impact of CVE-2025-57780 is substantial for organizations worldwide that utilize F5OS-A and F5OS-C appliances, particularly versions 1.5.0 and 1.8.0. An attacker who gains authenticated local access could escalate privileges to gain full control over the appliance, compromising confidentiality, integrity, and availability of the device and potentially the broader network it protects. This could lead to unauthorized access to sensitive data, manipulation or disruption of network traffic, and the ability to bypass security controls enforced by the appliance. Given that F5 appliances are often deployed in critical infrastructure, financial institutions, government networks, and large enterprises, exploitation could result in significant operational disruption, data breaches, and damage to organizational reputation. The requirement for local authenticated access limits the attack surface but does not eliminate risk, especially in environments where insider threats or compromised credentials are possible. The absence of known exploits in the wild suggests the vulnerability is not yet actively weaponized, but the high CVSS score indicates that once exploit code is developed, the impact could be severe.

CWE-250Execution with Unnecessary Privileges (opens in a new tab)
Base weaknessLikelihood of exploit: Medium
The product performs an operation at a privilege level that is higher than the minimum level required, which creates new weaknesses or amplifies the consequences of other weaknesses.
Architecture and Design · Operation · Environment Hardening
Run your code using the lowest privileges that are required to accomplish the necessary tasks. If possible, create isolated accounts with limited privileges that are only used for a single task. That way, a successful attack will not immediately give the attacker access to the rest of the software or its environment.
Architecture and Design · Separation of Privilege
Identify the functionality that requires additional privileges, such as access to privileged operating system resources. Wrap and centralize this functionality if possible, and isolate the privileged code as much as possible from other code.
Architecture and Design · Attack Surface Reduction
Identify the functionality that requires additional privileges, such as access to privileged operating system resources. Wrap and centralize this functionality if possible, and isolate the privileged code as much as possible from other code.
OWASP Cheat Sheets
Docker Security (opens in a new tab)
Vulnerable Dependency Management (opens in a new tab)
OWASP ASVS 4.0.3
V1.14.5 (opens in a new tab)
V1.2.1 (opens in a new tab)
V14.2.6 (opens in a new tab)
Attack patterns
Cross Zone Scripting (opens in a new tab)
Expanding Control over the Operating System from the Database (opens in a new tab)
Target Programs with Elevated Privileges (opens in a new tab)
From MITRE CWE, MITRE CAPEC and OWASP (Top 10, OpenCRE).

References

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

WeaknessesCWE-250

Technical details

References

Community reviews

Related threats