dbcve.org
Big Ip Access Policy ManagerApplication · F5

CVE-2025-61958

HIGH · 8.7 CVSS v3.1 Published 2025-10-15
Fix available
A fix is available. Upgrade to 15.1.10.8 / 16.1.6.1 or later.
See remediation →
93/100
Remediation priority · Urgent
Remotely reachable Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
A vulnerability exists in the iHealth command that may allow an authenticated attacker with at least a resource administrator role to bypass tmsh restrictions and gain access to a bash shell.  For BIG-IP systems running in Appliance mode, a successful exploit can allow the attacker to cross a security boundary.  Note: Software versions which have reached End of Technical Support (EoTS) are not evaluated.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · moderate confidence

The iHealth diagnostic command in F5 BIG-IP contains a vulnerability allowing authenticated users with at least resource administrator role to escape tmsh (Traffic Management Shell) restrictions and obtain an unrestricted bash shell. On BIG-IP systems running in Appliance mode, this bypasses the security boundary that normally limits administrative access.

MitigationApply the F5 security patch for this vulnerability. Restrict iHealth command access to only necessary personnel and ensure resource administrator accounts follow least-privilege principles.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Big Ip Access Policy ManagerApplication
Affected:>= 15.1.0, < 15.1.10.8>= 16.1.0, < 16.1.6.1>= 17.1.0, < 17.1.3>= 17.5.0, < 17.5.1.1
Big Ip Advanced Firewall ManagerApplication
Affected:>= 15.1.0, < 15.1.10.8>= 16.1.0, < 16.1.6.1>= 17.1.0, < 17.1.3>= 17.5.0, < 17.5.1.1
Big Ip Advanced Web Application FirewallApplication
Affected:>= 15.1.0, < 15.1.10.8>= 16.1.0, < 16.1.6.1>= 17.1.0, < 17.1.3>= 17.5.0, < 17.5.1.1
Big Ip AnalyticsApplication
Affected:>= 15.1.0, < 15.1.10.8>= 16.1.0, < 16.1.6.1>= 17.1.0, < 17.1.3>= 17.5.0, < 17.5.1.1
Big Ip Application Acceleration ManagerApplication
Affected:>= 15.1.0, < 15.1.10.8>= 16.1.0, < 16.1.6.1>= 17.1.0, < 17.1.3>= 17.5.0, < 17.5.1.1
Big Ip Application Security ManagerApplication
Affected:>= 15.1.0, < 15.1.10.8>= 16.1.0, < 16.1.6.1>= 17.1.0, < 17.1.3>= 17.5.0, < 17.5.1.1
Big Ip Application Visibility And ReportingApplication
Affected:>= 15.1.0, < 15.1.10.8>= 16.1.0, < 16.1.6.1>= 17.1.0, < 17.1.3>= 17.5.0, < 17.5.1.1
Big Ip Automation ToolchainApplication
Affected:>= 15.1.0, < 15.1.10.8>= 16.1.0, < 16.1.6.1>= 17.1.0, < 17.1.3>= 17.5.0, < 17.5.1.1

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
High
User interaction
None
Scope
Changed
Confidentiality
High
Integrity
High
Availability
None

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

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Check BIG-IP version
    Run 'tmsh show sys version' from the command line or query the BIG-IP version via the management interface
    Affected if The version falls within any of these ranges: 15.1.0 to 15.1.10.7, 16.1.0 to 16.1.6.0, 17.1.0 to 17.1.2, or 17.5.0 to 17.5.1.0
  2. Confirm iHealth is accessible
    Verify the iHealth diagnostic command interface is available on the system
    Affected if iHealth is enabled and accessible to authenticated users
  3. Identify users with resource administrator role
    Review user accounts and their assigned roles using 'tmsh list auth user' or the management GUI user management section
    Affected if Any user account has the resource administrator role or higher privileges assigned
  4. Check if Appliance mode is enabled
    Run 'tmsh show sys hardware' or review system security settings to determine if Appliance mode is active
    Affected if The system is running in Appliance mode, which creates the security boundary that this vulnerability bypasses

You are affected if your BIG-IP version is within the affected ranges and you have users with resource administrator role who can access the iHealth diagnostic command, especially on Appliance mode systems.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to 15.1.10.8 / 16.1.6.1 / 17.1.3 or later
Fixed in 15.1.10.816.1.6.117.1.3
Interim mitigation

Apply the F5 security patch for this vulnerability. Restrict iHealth command access to only necessary personnel and ensure resource administrator accounts follow least-privilege principles.

Recommended fix High confidence

Upgrade to 15.1.10.8 (or later 15.1.x), 16.1.6.1 (or later 16.1.x), 17.1.3 (or later 17.1.x), or 17.5.1.1 (or later 17.5.x) depending on your current major version branch

  1. 1. Identify the currently installed BIG-IP version using 'tmsh show sys version' or the web management interface.
  2. 2. Determine which module(s) are affected (APM, AFM, ASM, Analytics, AAM, AVR, or Automation Toolchain).
  3. 3. Plan for a maintenance window as the upgrade will require a system reboot.
  4. 4. Backup the current BIG-IP configuration using 'tmsh save sys config' and verify the backup is stored securely.
  5. 5. Download the appropriate hotfix from F5 Networks my.f5.com based on your current major version (15.1.x, 16.1.x, 17.1.x, or 17.5.x).
  6. 6. Upload the hotfix to the BIG-IP system via the web management interface (System > Software Management > Image List) or via tmsh.
  7. 7. Install the hotfix using the software management interface or via tmsh: 'tmsh install sys software volume <volume-name> <image-name>'.
  8. 8. Verify the installation completed successfully.
Caveat Review F5 release notes for breaking changes before upgrading; note that software hotfixes may require additional license provisioning and some features may behave differently in newer versions

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Big Ip Access Policy Manager Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA4.0 h
22.0 hours of engineering $3,860
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,176.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-61958 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2025-61958 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data