dbcve.org
Big Ip Access Policy ManagerApplication · F5

CVE-2025-47148

MEDIUM · 6.5 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 →
71/100
Remediation priority · Elevated
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
When the BIG-IP system is configured as both a Security Assertion Markup Language (SAML) service provider (SP) and Identity Provider (IdP), with single logout (SLO) enabled on an access policy, undisclosed requests can cause an increase in memory resource utilization.  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

A memory resource exhaustion vulnerability exists in F5 BIG-IP systems configured simultaneously as both a SAML Service Provider (SP) and Identity Provider (IdP) with Single Logout (SLO) enabled on an access policy. Undisclosed requests trigger excessive memory consumption, potentially leading to denial of service conditions.

MitigationReview and restrict SAML configurations to disable SLO when not required, or upgrade to a patched version once available from F5. Monitor memory utilization on affected BIG-IP systems.

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
Big Ip Ssl OrchestratorApplication
Affected:>= 15.1.0, < 15.1.10.8>= 16.1.0, < 16.1.6.1>= 17.1.0, < 17.1.3= 17.5.0

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

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

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 APM or SSL Orchestrator version
    Run 'tmsh show sys version' or view the version in the BIG-IP web UI under Overview > System > Software. Compare against affected ranges: 15.1.0-15.1.10.7, 16.1.0-16.1.6.0, 17.1.0-17.2.x, or 17.5.0
    Affected if Installed version falls within any of the affected version ranges
  2. Verify SAML Service Provider (SP) configuration exists
    Navigate to Access Policy > SAML > Virtual Server Configuration in the BIG-IP UI, or run 'tmsh list apm saml sp' to list configured SAML Service Providers
    Affected if Any SAML SP configuration exists on the system
  3. Verify SAML Identity Provider (IdP) configuration exists
    Navigate to Access Policy > SAML > Identity Provider Settings in the BIG-IP UI, or run 'tmsh list apm saml idp' to list configured SAML Identity Providers
    Affected if Any SAML IdP configuration exists on the system
  4. Confirm Single Logout (SLO) is enabled on access policy
    Review the access policy associated with the SAML SP or IdP configuration in Access Policy > Access Profiles. Check the SAML SP or IdP object settings for SLO (Single Logout) option enabled, or inspect the access policy XML for SLO elements
    Affected if SLO is enabled on an access policy that uses SAML authentication

System is affected if it runs a vulnerable BIG-IP version AND is configured as both a SAML SP and IdP with SLO enabled on an access policy, causing memory exhaustion under specific undisclosed requests.

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

Review and restrict SAML configurations to disable SLO when not required, or upgrade to a patched version once available from F5. Monitor memory utilization on affected BIG-IP systems.

Recommended fix High confidence

Minimum fixed versions: 15.1.10.8, 16.1.6.1, 17.1.3, or 17.5.1 (or later releases in each respective branch)

  1. 1. Identify the currently deployed BIG-IP APM or SSL Orchestrator version using 'tmsh show sys version' or the web management console.
  2. 2. Determine which version branch your current deployment is on (15.1.x, 16.1.x, 17.1.x, or 17.5.0).
  3. 3. For version 15.1.0-15.1.10.7: Upgrade to version 15.1.10.8 or later.
  4. 4. For version 16.1.0-16.1.6.0: Upgrade to version 16.1.6.1 or later.
  5. 5. For version 17.1.0-17.1.2: Upgrade to version 17.1.3 or later.
  6. 6. For version 17.5.0: Upgrade to version 17.5.1 or later.
  7. 7. Download the appropriate ISO/IMG upgrade image from the F5 Downloads site (my.f5.com).
  8. 8. Upload the upgrade image to the BIG-IP system via web management console or SCP.
Caveat Standard F5 BIG-IP upgrade considerations apply - review release notes for compatibility with other modules, ensure backup of configuration exists, and plan for maintenance window as upgrade may require reboot.

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
  • Implementation6.0 h
  • Testing8.0 h
  • Review / QA4.0 h
22.0 hours of engineering $3,800
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,080.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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