dbcve.org
Big Ip Access Policy ManagerApplication · F5

CVE-2026-34176

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
When running in Appliance mode, an authenticated remote command injection vulnerability exists in an undisclosed iControl REST endpoint. 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

Authenticated remote command injection vulnerability in undisclosed iControl REST endpoint when F5 products run in Appliance mode. An attacker with valid credentials can inject arbitrary commands through the REST API, potentially achieving code execution and crossing security boundaries.

MitigationApply vendor-provided patches when available; restrict iControl REST API access to trusted admin IPs only; if Appliance mode is not required, consider running in non-appliance mode if supported; monitor for suspicious API activity.

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` on the command line, or log into the BIG-IP Configuration Utility and navigate to System > Software Management > ISO Image to view installed version.
    Affected if The displayed version matches one of the vulnerable ranges: 17.1.0-17.1.3, 17.5.0-17.5.1, 16.1.0-16.1.6, or 21.0.0.
  2. Confirm BIG-IP module installation
    Run `tmsh list sys module` or check the BIG-IP web UI under System > Information to see which modules (APM, AFM, ASM, Analytics, AAM, AVR, Automation Toolchain) are licensed and installed.
    Affected if Any of the listed affected modules (APM, AFM, ASM, Analytics, AAM, AVR, or Automation Toolchain) are installed on the system.
  3. Verify Appliance mode is enabled
    Check the BIG-IP system configuration: run `tmsh list sys db system.appliance` or inspect the system database via the web UI under System > Configuration > Device. Appliance mode restricts administrative access and is typically enabled in certain deployment scenarios.
    Affected if The system database variable `system.appliance` is set to `true` or Appliance mode is explicitly enabled in the device configuration.
  4. Confirm iControl REST API is accessible
    Verify the iControl REST service is running by querying the endpoint (e.g., `curl -k https://localhost/mgmt/shared/authn/login` or checking via `tmsh list sys service restnoded`). The API is enabled by default on BIG-IP management interface.
    Affected if The iControl REST API responds to authentication requests and accepts REST calls, indicating the service is active.

A system is affected if it runs a vulnerable BIG-IP version (17.1.0-17.1.3, 17.5.0-17.5.1, 16.1.0-16.1.6, or 21.0.0) with any affected module installed AND has Appliance mode enabled, with iControl REST API accessible.

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

Apply vendor-provided patches when available; restrict iControl REST API access to trusted admin IPs only; if Appliance mode is not required, consider running in non-appliance mode if supported; monitor for suspicious API activity.

Recommended fix High confidence

Upgrade to 17.1.4+ (if on 17.1.x), 17.5.2+ (if on 17.5.x), or 21.0.1+ (if on 21.0.x). For 16.1.x, migrate to 17.1.4+ as 16.1.x may be at EoTS.

  1. 1. Identify the current BIG-IP version by checking the system information in the management console or running 'tmsh show sys version'
  2. 2. Determine which maintenance stream your current version belongs to (16.1.x, 17.1.x, 17.5.x, or 21.0.x)
  3. 3. For 16.1.x versions: Plan migration path to 17.1.4 or later as 16.1.x may be approaching or at End of Technical Support (EoTS)
  4. 4. For 17.1.0-17.1.3: Upgrade to 17.1.4 or later
  5. 5. For 17.5.0-17.5.1: Upgrade to 17.5.2 or later
  6. 6. For 21.0.0: Upgrade to 21.0.1 or later
  7. 7. Download the appropriate ISO/UGP file from my.f5.com (requires F5 account)
  8. 8. Follow F5 upgrade procedures: backup current configuration using 'tmsh save sys config'
Caveat Review F5 release notes for any configuration or feature changes between versions. Test in non-production environment before deploying to production.

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-2026-34176 — 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-34176 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