dbcve.org
Big Ip Access Policy ManagerApplication · F5

CVE-2026-34019

MEDIUM · 5.3 CVSS v3.1 Published 2026-05-13
Fix available
A fix is available. Upgrade to after 17.1.2 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
When Bidirectional Forwarding Detection (BFD) is configured in Static and Dynamic routing protocols, undisclosed traffic can cause the Traffic Management Microkernel (TMM) to stop processing BFD packets and cause the configured routing protocol to fail over.  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

This is a F5 vulnerability affecting the Traffic Management Microkernel (TMM) when Bidirectional Forwarding Detection (BFD) is configured with Static or Dynamic routing protocols. Undisclosed traffic triggers a condition causing TMM to stop processing BFD packets, which forces the routing protocol to fail over to a backup path.

MitigationApply the vendor-supplied F5 software update/patch when available. Until then, consider disabling BFD on affected devices if operationally feasible, or implement additional network monitoring to detect BFD failures.

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.2= 17.5.0>= 16.1.0, <= 16.1.6
Big Ip Advanced Firewall ManagerApplication
Affected:>= 17.1.0, <= 17.1.2= 17.5.0>= 16.1.0, <= 16.1.6
Big Ip Advanced Web Application FirewallApplication
Affected:>= 17.1.0, <= 17.1.2= 17.5.0>= 16.1.0, <= 16.1.6
Big Ip AnalyticsApplication
Affected:>= 17.1.0, <= 17.1.2= 17.5.0>= 16.1.0, <= 16.1.6
Big Ip Application Acceleration ManagerApplication
Affected:>= 17.1.0, <= 17.1.2= 17.5.0>= 16.1.0, <= 16.1.6
Big Ip Application Security ManagerApplication
Affected:>= 17.1.0, <= 17.1.2= 17.5.0>= 16.1.0, <= 16.1.6
Big Ip Application Visibility And ReportingApplication
Affected:>= 17.1.0, <= 17.1.2= 17.5.0>= 16.1.0, <= 16.1.6
Big Ip Automation ToolchainApplication
Affected:>= 17.1.0, <= 17.1.2= 17.5.0>= 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
Low

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

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 installed F5 BIG-IP version
    Run 'tmsh show sys version' or check the BIG-IP GUI under Dashboard > System Information > Version
    Affected if The version listed falls within 17.1.0-17.1.2, 17.5.0, or 16.1.0-16.1.6
  2. Confirm BFD is configured on the device
    Run 'tmsh show /net bfd' or 'tmsh list /net bfd' to list Bidirectional Forwarding Detection configuration
    Affected if BFD configuration exists and is actively running on the device
  3. Verify BFD is used with Static or Dynamic routing
    Run 'tmsh list /net bfd' and 'tmsh list /net routing' to check which routing protocols BFD is paired with
    Affected if BFD is explicitly configured to work with static routes or dynamic routing protocols such as OSPF, BGP, or IS-IS
  4. Monitor TMM BFD packet processing status
    Run 'tmsh show /net bfd stats' and check the 'Packets Processed' or 'Packets Dropped' counters for anomalies
    Affected if BFD packet processing has stopped or shows abnormal drop counts while BFD remains configured

You are affected if your BIG-IP version is within the listed ranges AND BFD is configured with static or dynamic routing protocols, causing potential routing failover.

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.

From vendor data
Upgrade available Upgrade to a release after 17.1.2
Interim mitigation

Apply the vendor-supplied F5 software update/patch when available. Until then, consider disabling BFD on affected devices if operationally feasible, or implement additional network monitoring to detect BFD failures.

Fix this in Big Ip Access Policy Manager Scoped from the published advisory
  • Consultation4.0 h
  • Implementation2.0 h
  • Testing6.0 h
  • Review / QA3.0 h
15.0 hours of engineering $2,600
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,160.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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