dbcve.org
Big Ip Access Policy ManagerApplication · F5

CVE-2022-26517

HIGH · 7.5 CVSS v3.1 Published 2022-05-05
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
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
On F5 BIG-IP 15.1.x versions prior to 15.1.5.1, 14.1.x versions prior to 14.1.4.6, and 13.1.x versions prior to 13.1.5, when the BIG-IP CGNAT Large Scale NAT (LSN) pool is configured on a virtual server and packet filtering is enabled, undisclosed requests can cause the Traffic Management Microkernel (TMM) to terminate. 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 · high confidence

A denial of service vulnerability in F5 BIG-IP's Traffic Management Microkernel (TMM) allows unauthenticated remote attackers to crash TMM when CGNAT Large Scale NAT (LSN) pool is configured on a virtual server AND packet filtering is enabled. The vulnerability affects specific versions across 13.1.x, 14.1.x, and 15.1.x branches prior to the fixed releases.

MitigationUpgrade to BIG-IP 15.1.5.1, 14.1.4.6, or 13.1.5 or later. Alternatively, as a compensating control, disable packet filtering on affected virtual servers or remove LSN pool configurations if upgrade is not immediately feasible.

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:= 13.1.0= 13.1.1= 13.1.3= 13.1.4= 13.1.5= 14.1.0= 14.1.2= 14.1.3= 14.1.4= 15.1.0= 15.1.1= 15.1.2
Big Ip Advanced Firewall ManagerApplication
Affected:= 13.1.0= 13.1.1= 13.1.3= 13.1.4= 13.1.5= 14.1.0= 14.1.2= 14.1.3= 14.1.4= 15.1.0= 15.1.1= 15.1.2
Big Ip AnalyticsApplication
Affected:= 13.1.0= 13.1.1= 13.1.3= 13.1.4= 13.1.5= 14.1.0= 14.1.2= 14.1.3= 14.1.4= 15.1.0= 15.1.1= 15.1.2
Big Ip Application Acceleration ManagerApplication
Affected:= 13.1.0= 13.1.1= 13.1.3= 13.1.4= 13.1.5= 14.1.0= 14.1.2= 14.1.3= 14.1.4= 15.1.0= 15.1.1= 15.1.2
Big Ip Application Security ManagerApplication
Affected:= 13.1.0= 13.1.1= 13.1.3= 13.1.4= 13.1.5= 14.1.0= 14.1.2= 14.1.3= 14.1.4= 15.1.0= 15.1.1= 15.1.2
Big Ip Domain Name SystemApplication
Affected:= 13.1.0= 13.1.1= 13.1.3= 13.1.4= 13.1.5= 14.1.0= 14.1.2= 14.1.3= 14.1.4= 15.1.0= 15.1.1= 15.1.2
Big Ip Fraud Protection ServiceApplication
Affected:= 13.1.0= 13.1.1= 13.1.3= 13.1.4= 13.1.5= 14.1.0= 14.1.2= 14.1.3= 14.1.4= 15.1.0= 15.1.1= 15.1.2
Big Ip Global Traffic ManagerApplication
Affected:= 13.1.0= 13.1.1= 13.1.3= 13.1.4= 13.1.5= 14.1.0= 14.1.2= 14.1.3= 14.1.4= 15.1.0= 15.1.1= 15.1.2

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. Verify BIG-IP version is within affected range
    Run 'tmsh show sys version' or 'bigpipe version' and compare the output to the affected versions: 13.1.0, 13.1.1, 13.1.3, 13.1.4, 13.1.5, 14.1.0, 14.1.2, 14.1.3, 14.1.4, 15.1.0, 15.1.1, 15.1.2
    Affected if The installed version matches any of the listed affected versions
  2. Identify if CGNAT LSN pools are configured
    Run 'tmsh list lsn pool all-properties' to list all Large Scale NAT pools configured on the system
    Affected if Any LSN pool is configured and assigned to a virtual server
  3. Check if packet filtering is enabled
    Run 'tmsh list /net packet-filter' or 'tmsh list lsn pool <pool-name>' to inspect packet filtering settings on virtual servers with LSN pools
    Affected if Packet filtering is enabled on virtual servers that use LSN pools

A system is affected only if it runs an affected version AND has an LSN pool configured on a virtual server AND packet filtering is enabled on that virtual server.

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
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Upgrade to BIG-IP 15.1.5.1, 14.1.4.6, or 13.1.5 or later. Alternatively, as a compensating control, disable packet filtering on affected virtual servers or remove LSN pool configurations if upgrade is not immediately feasible.

Recommended fix High confidence

13.1.5 (or later) for 13.1.x branches; 14.1.4.6 (or later) for 14.1.x branches; 15.1.5.1 (or later) for 15.1.x branches

  1. Identify the BIG-IP module(s) in use from the affected list (APM, AFM, Analytics, AAM, ASM, DNS, FPS, GTM)
  2. Determine the current BIG-IP version by running 'tmsh show sys version' or checking the management console
  3. For BIG-IP 13.1.x: Plan upgrade to version 13.1.5 or later
  4. For BIG-IP 14.1.x: Plan upgrade to version 14.1.4.6 or later
  5. For BIG-IP 15.1.x: Plan upgrade to version 15.1.5.1 or later
  6. Review release notes for the target version for any known issues
  7. Create a backup of the BIG-IP configuration using 'tmsh save sys config'
  8. Test the upgrade in a non-production environment first
Caveat Review F5 release notes for target version - some configuration changes or behavior differences may occur between minor version upgrades

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 / QA2.0 h
20.0 hours of engineering $3,500
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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