Skip to content
Fencer Vulns
high 7.5

CVE-2021-22975 json

On BIG-IP version 16.0.x before 16.0.1.1, 15.1.x before 15.1.2.1, and 14.1.x before 14.1.3.1, under some circumstances, Traffic Management…

published 2021-02-12 5 y ago modified 2026-06-17 4 mo ago also EUVD-2021-10093

cvss
7.5
version 3.1, NVD
cisa kev
Not listed
not in CISA's catalog
epss
1.0%
EPSS 1.0% chance of exploitation in 30 days, percentile 62%
public exploits
0
none known

Summary

On BIG-IP version 16.0.x before 16.0.1.1, 15.1.x before 15.1.2.1, and 14.1.x before 14.1.3.1, under some circumstances, Traffic Management Microkernel (TMM) may restart on the BIG-IP system while passing large bursts of traffic. Note: Software versions which have reached End of Software Development (EoSD) are not evaluated.

Patch / fix

  • f5 big-ip_access_policy_manager 14.1.3.1, 15.1.2.1, 16.0.1.1
  • f5 big-ip_advanced_firewall_manager 14.1.3.1, 15.1.2.1, 16.0.1.1
  • f5 big-ip_advanced_web_application_firewall 14.1.3.1, 15.1.2.1, 16.0.1.1
  • f5 big-ip_analytics 14.1.3.1, 15.1.2.1, 16.0.1.1
  • f5 big-ip_application_acceleration_manager 14.1.3.1, 15.1.2.1, 16.0.1.1
  • f5 big-ip_application_security_manager 14.1.3.1, 15.1.2.1, 16.0.1.1
  • f5 big-ip_ddos_hybrid_defender 14.1.3.1, 15.1.2.1, 16.0.1.1
  • f5 big-ip_domain_name_system 14.1.3.1, 15.1.2.1, 16.0.1.1
  • f5 big-ip_fraud_protection_service 14.1.3.1, 15.1.2.1, 16.0.1.1
  • f5 big-ip_global_traffic_manager 14.1.3.1, 15.1.2.1, 16.0.1.1
  • f5 big-ip_link_controller 14.1.3.1, 15.1.2.1, 16.0.1.1
  • f5 big-ip_local_traffic_manager 14.1.3.1, 15.1.2.1, 16.0.1.1
  • f5 big-ip_policy_enforcement_manager 14.1.3.1, 15.1.2.1, 16.0.1.1
  • f5 big-ip_ssl_orchestrator 14.1.3.1, 15.1.2.1, 16.0.1.1

Exploit prediction

0.98% chance of exploitation in the next 30 days, higher than 62% of all scored CVEs (FIRST EPSS, 2026-11-08).

CVSS scores

assigned by version score vector
NVD 3.1 7.5 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
NVD 2.0 4.3 AV:N/AC:M/Au:N/C:N/I:N/A:P

Affected products

  • n/a BIG-IP

References

Sources

Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.