dbcve.org
Big Ip Access Policy ManagerApplication · F5

CVE-2026-32673

HIGH · 8.7 CVSS v3.1 Published 2026-05-13
Fix available
A fix is available. Upgrade to after 17.5.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 BIG-IP scripted monitors that may allow an authenticated attacker with the Resource Administrator or Administrator role to execute arbitrary system commands with higher privileges. In appliance mode deployments, 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

A command injection vulnerability exists in BIG-IP scripted monitors where an authenticated attacker with Resource Administrator or Administrator role can execute arbitrary system commands with elevated privileges. In appliance mode deployments, successful exploitation allows crossing security boundaries.

MitigationRestrict administrative access to least privilege principles and apply F5 security patches when available. Monitor and audit administrative actions on 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:>= 17.1.0, <= 17.1.3>= 17.5.0, <= 17.5.1>= 16.1.0, <= 16.1.6= 21.0.0
Big Ip Advanced Firewall ManagerApplication
Affected:>= 17.1.0, <= 17.1.3>= 17.5.0, <= 17.5.1>= 16.1.0, <= 16.1.6= 21.0.0
Big Ip Advanced Web Application FirewallApplication
Affected:>= 17.1.0, <= 17.1.3>= 17.5.0, <= 17.5.1>= 16.1.0, <= 16.1.6= 21.0.0
Big Ip AnalyticsApplication
Affected:>= 17.1.0, <= 17.1.3>= 17.5.0, <= 17.5.1>= 16.1.0, <= 16.1.6= 21.0.0
Big Ip Application Acceleration ManagerApplication
Affected:>= 17.1.0, <= 17.1.3>= 17.5.0, <= 17.5.1>= 16.1.0, <= 16.1.6= 21.0.0
Big Ip Application Security ManagerApplication
Affected:>= 17.1.0, <= 17.1.3>= 17.5.0, <= 17.5.1>= 16.1.0, <= 16.1.6= 21.0.0
Big Ip Application Visibility And ReportingApplication
Affected:>= 17.1.0, <= 17.1.3>= 17.5.0, <= 17.5.1>= 16.1.0, <= 16.1.6= 21.0.0
Big Ip Automation ToolchainApplication
Affected:>= 17.1.0, <= 17.1.3>= 17.5.0, <= 17.5.1>= 16.1.0, <= 16.1.6= 21.0.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
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. Identify BIG-IP version
    Run 'tmsh show sys version' or check the web UI under Dashboard > General Properties to obtain the installed version
    Affected if The version falls within 17.1.0-17.1.3, 17.5.0-17.5.1, 16.1.0-16.1.6, or equals 21.0.0
  2. Determine if scripted monitors exist
    Review monitor configurations via 'tmsh list ltm monitor' or the web UI under Local Traffic > Monitors to identify any monitors of type 'script'
    Affected if Any scripted monitors are configured and enabled on the system
  3. Check for privileged administrative accounts
    Review user roles using 'tmsh list auth user' or via the web UI under User Management > User List to identify accounts with Resource Administrator or Administrator roles
    Affected if Accounts with Resource Administrator or Administrator privileges exist on the system

You are affected if your BIG-IP version matches the affected ranges AND scripted monitors are configured AND privileged administrative accounts exist on the system.

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 a release after 17.5.1
Interim mitigation

Restrict administrative access to least privilege principles and apply F5 security patches when available. Monitor and audit administrative actions on BIG-IP systems.

Recommended fix Moderate confidence

Upgrade to BIG-IP version 17.1.4 or later (17.1.x line), 17.5.2 or later (17.5.x line), 16.1.7 or later (16.1.x line), or the next available stable release beyond 21.0.0 - choose the appropriate branch matching your current deployment

  1. 1. Identify the current BIG-IP version by running 'tmsh show sys version' or checking the web UI (System > Software > Image/List)
  2. 2. Determine which BIG-IP module(s) are affected by checking the installed modules: 'tmsh list sys module'
  3. 3. Download the fixed version from F5 downloads (login required): go to https://my.f5.com/manage/downloads/ and search for the appropriate version >= 17.1.4, >= 17.5.2, >= 16.1.7, or a version beyond 21.0.0
  4. 4. Verify the upgrade does not conflict with existing BIG-IP infrastructure compatibility requirements
  5. 5. Create a backup of the BIG-IP configuration: 'tmsh save sys config'
  6. 6. Upload the ISO image to the BIG-IP via web UI (System > Software > Upload) or SCP
  7. 7. Install the new version: 'tmsh install sys software volume <volume-name> <image-file>'
  8. 8. Reboot into the new volume: 'tmsh reboot volume <volume-name>'
Caveat Review F5 release notes for the target version to check for configuration or behavioral changes; test in a non-production environment before upgrading production systems

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
  • Implementation2.0 h
  • Testing3.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,970
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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