dbcve.org
Big Ip Access Policy ManagerApplication · F5

CVE-2025-59268

MEDIUM · 5.3 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 →
62/100
Remediation priority · Elevated
Remotely reachable No privileges 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
On the BIG-IP system, undisclosed endpoints that contain static non-sensitive information are accessible to an unauthenticated remote attacker through the Configuration utility.  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

On F5 BIG-IP systems, unauthenticated remote attackers can access undisclosed endpoints via the Configuration utility that contain static non-sensitive information. This represents an information disclosure vulnerability where the specific affected endpoints are not publicly identified in the advisory.

MitigationRestrict access to the BIG-IP Configuration utility to trusted networks or authorized personnel only. Monitor for unauthorized access attempts and apply F5 security patches when available.

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
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
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
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
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
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
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
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

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
None
User interaction
None
Scope
Unchanged
Confidentiality
Low
Integrity
None
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/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. Identify the BIG-IP version
    Run 'tmsh show sys version' or log into the Configuration utility and check System > Overview > Software Version
    Affected if The installed 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
  2. Confirm the Configuration utility is network-accessible
    Verify whether the BIG-IP management interface or a self IP is accepting HTTP/HTTPS connections for the Configuration utility (typically ports 443 or 80)
    Affected if The Configuration utility is reachable from network segments that are not restricted to trusted personnel
  3. Check if management interface is exposed to untrusted networks
    Review the BIG-IP management network configuration via 'tmsh list sys management-ip' and determine if the management interface is accessible from external or untrusted networks
    Affected if The management interface has an IP address in a range accessible from untrusted or internet-facing networks
  4. Assess self IP exposure for Configuration utility access
    Determine which self IPs allow access to the Configuration utility by reviewing the HTTP profile bindings and network access settings
    Affected if Self IPs used for Configuration utility access are exposed to networks outside the trusted administrative zone

You are affected if your BIG-IP version is within 15.1.0-15.1.10.7, 16.1.0-16.1.6.0, 17.1.0-17.1.2, or 17.5.0-17.5.1 AND the Configuration utility is accessible from untrusted networks.

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

Restrict access to the BIG-IP Configuration utility to trusted networks or authorized personnel only. Monitor for unauthorized access attempts and apply F5 security patches when available.

Recommended fix High confidence

Upgrade to 15.1.10.8+ / 16.1.6.1+ / 17.1.3+ / 17.5.2+ depending on your current version branch

  1. 1. Identify the current BIG-IP version by checking the Configuration utility or running 'tmsh show sys version'
  2. 2. Based on your current major version line, plan upgrade to the following minimum fixed version:
  3. - For 15.1.x lines: upgrade to 15.1.10.8 or later
  4. - For 16.1.x lines: upgrade to 16.1.6.1 or later
  5. - For 17.1.x lines: upgrade to 17.1.3 or later
  6. - For 17.5.x lines: upgrade to 17.5.2 or later
  7. 3. Review F5 BIG-IP upgrade documentation and release notes for your version line before upgrading
  8. 4. Perform the upgrade in a test/staging environment first to validate compatibility with your configurations
Caveat Review F5 release notes for potential configuration or compatibility changes between your current version and the target fixed version before upgrading

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
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing4.0 h
  • Review / QA2.0 h
15.0 hours of engineering $2,640
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-59268 — 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-59268 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