Cyber Resilience

CVE-2025-61955

F5Os-A 1.5.1 – 1.5.4

Published
15 October 2025
Modified
21 October 2025
Patch / advisory
View advisory
CVSS Score v4 8.5
Click a component to see what it means
Raw vectorCVSS:4.0/AV:L/AC:L/AT:N/PR:L/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X
EPSS Score 0.0023 14th percentile
Risk Priority 32 floored blend · peak EPSS

Summary

CVE-2025-61955 is a high-severity Eval Injection (CWE-95) vulnerability in F5 F5Os-A. Its CVSS base score is 8.5 (High).

Operationally, exploitation aligns with the MITRE ATT&CK technique JavaScript (T1059.007); ranked at the 14th percentile by exploit likelihood (below the median); it is not currently listed in the CISA KEV catalog.

The strongest mitigations our analysis identified map to SA-11 (Developer Testing and Evaluation) and SI-10 (Information Input Validation) — see the control section below for these in your framework.

OWASP Top 10 for Web (2025)

A05:2025 Injection

EU & UK References

Vulnerability Data

A vulnerability exists in F5OS-A and F5OS-C systems 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…

more

of Technical Support (EoTS) are not evaluated.

CWE(s)
CWE-95

Related Threats

MITRE ATT&CK Enterprise Techniques

T1059.007 JavaScript Execution
Adversaries may abuse various implementations of JavaScript for execution.
attack.mitre.org →
T1059 Command and Scripting Interpreter Execution
Adversaries may abuse command and script interpreters to execute commands, scripts, or binaries.
attack.mitre.org →
T1059.001 PowerShell Execution
Adversaries may abuse PowerShell commands and scripts for execution.
attack.mitre.org →
T1059.004 Unix Shell Execution
Adversaries may abuse Unix shell commands and scripts for execution.
attack.mitre.org →
T1059.005 Visual Basic Execution
Adversaries may abuse Visual Basic (VB) for execution.
attack.mitre.org →
T1059.006 Python Execution
Adversaries may abuse Python commands and scripts for execution.
attack.mitre.org →
Derived from this CVE’s CWE(s) via the direct CWE→ATT&CK cross-walk.

CVEs Like This One

CVE-2023-22657Same product: F5 F5Os-A
CVE-2025-57780Same product: F5 F5Os-A
CVE-2025-60015Same product: F5 F5Os-A
CVE-2025-46265Same product: F5 F5Os-A
CVE-2024-23607Same product: F5 F5Os-A
CVE-2025-47150Same product: F5 F5Os-A
CVE-2025-36546Same product: F5 F5Os-A
CVE-2024-24966Same product: F5 F5Os-A
CVE-2025-60013Same product: F5 F5Os-A
CVE-2023-36494Same product: F5 F5Os-A

Affected Assets

f5
f5os-a
1.8.0 · 1.5.1 — 1.5.4
f5
f5os-c
1.6.0 — 1.6.2 · 1.8.0 — 1.8.2

Mitigating Controls

Control response

Prevent
Stop it (NIST 800-53)

—

Detect
Catch it (NIST detect / respond)

—

Harden
Shrink the surface (DISA STIG)

—

Validate
Prove the fix (OWASP ASVS)
  • V1.3.2

Mitigating Controls (NIST 800-53 r5) AI

SA-11 Developer Testing and Evaluation good match

Developer testing and code analysis can discover eval-injection flaws but does not stop their introduction.

SI-10 Information Input Validation good match

Input validation explicitly requires neutralizing untrusted data before it reaches dynamic evaluation constructs such as eval.

SA-15 Development Process, Standards, and Tools partial match

Secure-development standards and tools can mandate safe coding patterns that avoid unsafe dynamic evaluation.

Mitigating Controls (NIST CSF 2.0) AI

Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→CSF cross-walk (authority under review) — links open the control.

PR.PS-06 mostly match
prevents

Secure SDLC practices directly require input neutralization and avoidance of unsafe dynamic evaluation.

Mitigating Controls (ISO/IEC 27001:2022 Annex A) AI

Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→ISO cross-walk (authority under review) — links open the control.

A.8.29 Security testing in development and acceptance mostly match
finds

Security testing in development can detect eval injection vulnerabilities before deployment.

A.8.25 Secure development life cycle partial match
prevents

Secure development life cycle mandates input validation and safe coding practices that directly prevent eval injection.

A.8.26 Application security requirements partial match
prevents

Application security requirements include rules against dynamic code execution of untrusted input.

A.8.27 Secure system architecture and engineering principles partial match
prevents

Secure architecture principles discourage unsafe dynamic evaluation constructs.

A.8.28 Secure coding partial match
prevents

Secure coding explicitly requires neutralization of input before dynamic evaluation, directly mitigating eval injection.

A.8.31 Separation of development, test and production environments none match
none

Separation of environments limits the blast radius if eval injection occurs in non-production.

References