dbcve.org
Big Ip Access Policy ManagerApplication · F5

CVE-2026-40629

HIGH · 7.5 CVSS v3.1 Published 2026-05-13
Fix available
A fix is available. Upgrade to after 17.5.1 or later.
See remediation →
84/100
Remediation priority · High
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
When SSL profiles are configured on a virtual server, undisclosed traffic can cause the virtual server to stop processing new client connections.  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 denial of service vulnerability in F5 BIG-IP virtual servers with SSL profiles configured. Certain undisclosed traffic patterns can cause the virtual server to stop accepting new client connections, resulting in service disruption.

MitigationApply the vendor-supplied patch or upgrade to a supported version. For interim mitigation, consider removing SSL profiles from affected virtual servers if operationally feasible, or implement rate limiting on the virtual server.

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
Big Ip Advanced Firewall ManagerApplication
Affected:>= 17.1.0, <= 17.1.3>= 17.5.0, <= 17.5.1>= 16.1.0, <= 16.1.6
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
Big Ip AnalyticsApplication
Affected:>= 17.1.0, <= 17.1.3>= 17.5.0, <= 17.5.1>= 16.1.0, <= 16.1.6
Big Ip Application Acceleration ManagerApplication
Affected:>= 17.1.0, <= 17.1.3>= 17.5.0, <= 17.5.1>= 16.1.0, <= 16.1.6
Big Ip Application Security ManagerApplication
Affected:>= 17.1.0, <= 17.1.3>= 17.5.0, <= 17.5.1>= 16.1.0, <= 16.1.6
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
Big Ip Automation ToolchainApplication
Affected:>= 17.1.0, <= 17.1.3>= 17.5.0, <= 17.5.1>= 16.1.0, <= 16.1.6

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
None
Integrity
None
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/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. Determine F5 BIG-IP system version
    Run 'tmsh show sys version' or check the BIG-IP GUI under Dashboard > System > Software Version
    Affected if Version falls within 16.1.0-16.1.6, 17.1.0-17.1.3, or 17.5.0-17.5.1
  2. Identify virtual servers with SSL profiles
    Run 'tmsh list ltm virtual one-line' and look for entries containing 'ssl profile' or use the BIG-IP GUI under Local Traffic > Virtual Servers to review SSL profile associations for each virtual server
    Affected if Any virtual server has an SSL profile (client or server) assigned
  3. Verify virtual server is operational
    Run 'tmsh show ltm virtual' and check the 'Status' column, or monitor for symptoms such as virtual server no longer accepting new connections via 'tmsh show ltm virtual <name> stats'
    Affected if Virtual server with SSL profile shows as 'Unavailable' or stops accepting new client connections
  4. Check for connection exhaustion
    Run 'tmsh show sys connections server-side' and review connection counts. Also check 'tmsh show ltm virtual' for high connection counts or connection errors
    Affected if Connection count is abnormally high or connection errors are present on virtual servers with SSL profiles

Your environment is affected if you are running a vulnerable BIG-IP version (16.1.0-16.1.6, 17.1.0-17.1.3, or 17.5.0-17.5.1) AND have virtual servers configured with SSL profiles, as the vulnerability requires both conditions to be present.

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 the vendor-supplied patch or upgrade to a supported version. For interim mitigation, consider removing SSL profiles from affected virtual servers if operationally feasible, or implement rate limiting on the virtual server.

Recommended fix Moderate confidence

For 17.1.x: upgrade to 17.1.4 or later; For 17.5.x: upgrade to 17.5.2 or later; For 16.1.x: upgrade to 16.1.7 or later (or migrate to a supported major version)

  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 (APM, AFM, AWAF, Analytics, AAM, ASM, AVR, or Automation Toolchain)
  3. 3. Identify SSL profiles configured on virtual servers: use 'tmsh list ltm profile client-ssl' and 'tmsh list ltm profile server-ssl'
  4. 4. Access my.f5.com and locate the specific security advisory for CVE-2026-40629 to obtain the exact hotfix or maintenance version number
  5. 5. Download the recommended fixed version from F5 Downloads (https://downloads.f5.com)
  6. 6. Backup current configuration using 'tmsh save sys config'
  7. 7. Install the update via the web UI (Software Management > Image List > Upload) or via tmsh: 'tmsh install sys software volume <volume-name> <image-file>'
  8. 8. Reboot the BIG-IP device into the new volume
Caveat Review F5 release notes before upgrading; ensure compatibility with existing iRules and configurations; some legacy SSL ciphers may be deprecated 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
  • Testing4.0 h
  • Review / QA2.0 h
18.0 hours of engineering $3,200
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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