CVE-2026-39455 |
high
|
8.7 |
0.0030
|
f5 |
big-ip_advanced_web_application_firewall |
< 17.1.3
|
|
CVE-2026-39455 |
high
|
8.7 |
0.0030
|
f5 |
big-ip_advanced_web_application_firewall |
< 17.5.1
|
|
CVE-2026-39455 |
high
|
8.7 |
0.0030
|
f5 |
big-ip_advanced_web_application_firewall |
< 16.1.6
|
|
CVE-2026-39455 |
high
|
8.7 |
0.0030
|
f5 |
big-ip_advanced_web_application_firewall |
21.0.0
|
|
CVE-2026-39458 |
high
|
8.7 |
0.0026
|
f5 |
big-ip_advanced_web_application_firewall |
< 17.1.3
|
|
CVE-2026-39458 |
high
|
8.7 |
0.0026
|
f5 |
big-ip_advanced_web_application_firewall |
< 17.5.1
|
|
CVE-2026-39458 |
high
|
8.7 |
0.0026
|
f5 |
big-ip_advanced_web_application_firewall |
< 16.1.6
|
|
CVE-2026-39458 |
high
|
8.7 |
0.0026
|
f5 |
big-ip_advanced_web_application_firewall |
21.0.0
|
|
CVE-2026-40060 |
high
|
8.7 |
0.0032
|
f5 |
big-ip_advanced_web_application_firewall |
< 16.1.6
|
|
CVE-2026-40060 |
high
|
8.7 |
0.0032
|
f5 |
big-ip_advanced_web_application_firewall |
< 17.1.3
|
|
CVE-2026-40060 |
high
|
8.7 |
0.0032
|
f5 |
big-ip_advanced_web_application_firewall |
< 17.5.1
|
|
CVE-2026-40060 |
high
|
8.7 |
0.0032
|
f5 |
big-ip_advanced_web_application_firewall |
21.0.0
|
|
CVE-2026-40423 |
high
|
8.7 |
0.0026
|
f5 |
big-ip_advanced_web_application_firewall |
< 17.1.3
|
|
CVE-2026-40423 |
high
|
8.7 |
0.0026
|
f5 |
big-ip_advanced_web_application_firewall |
< 17.5.1
|
|
CVE-2026-40423 |
high
|
8.7 |
0.0026
|
f5 |
big-ip_advanced_web_application_firewall |
< 16.1.6
|
|
CVE-2026-40423 |
high
|
8.7 |
0.0026
|
f5 |
big-ip_advanced_web_application_firewall |
21.0.0
|
|
CVE-2026-40618 |
high
|
8.7 |
0.0032
|
f5 |
big-ip_advanced_web_application_firewall |
< 17.1.3
|
|
CVE-2026-40618 |
high
|
8.7 |
0.0032
|
f5 |
big-ip_advanced_web_application_firewall |
< 17.5.1
|
|
CVE-2026-40618 |
high
|
8.7 |
0.0032
|
f5 |
big-ip_advanced_web_application_firewall |
< 16.1.6
|
|
CVE-2026-40618 |
high
|
8.7 |
0.0032
|
f5 |
big-ip_advanced_web_application_firewall |
21.0.0
|
|
CVE-2026-40629 |
high
|
8.7 |
0.0032
|
f5 |
big-ip_advanced_web_application_firewall |
< 17.1.3
|
|
CVE-2026-40629 |
high
|
8.7 |
0.0032
|
f5 |
big-ip_advanced_web_application_firewall |
< 17.5.1
|
|
CVE-2026-40629 |
high
|
8.7 |
0.0032
|
f5 |
big-ip_advanced_web_application_firewall |
< 16.1.6
|
|
CVE-2026-41218 |
high
|
8.7 |
0.0026
|
f5 |
big-ip_advanced_web_application_firewall |
< 17.1.3
|
|
CVE-2026-41218 |
high
|
8.7 |
0.0026
|
f5 |
big-ip_advanced_web_application_firewall |
< 17.5.1
|
|
CVE-2026-41218 |
high
|
8.7 |
0.0026
|
f5 |
big-ip_advanced_web_application_firewall |
< 16.1.6
|
|
CVE-2026-41218 |
high
|
8.7 |
0.0026
|
f5 |
big-ip_advanced_web_application_firewall |
21.0.0
|
|
CVE-2026-41227 |
high
|
8.7 |
0.0026
|
f5 |
big-ip_advanced_web_application_firewall |
< 17.1.3
|
|
CVE-2026-41227 |
high
|
8.7 |
0.0026
|
f5 |
big-ip_advanced_web_application_firewall |
< 17.5.1
|
|
CVE-2026-41227 |
high
|
8.7 |
0.0026
|
f5 |
big-ip_advanced_web_application_firewall |
< 16.1.6
|
|
CVE-2026-41956 |
high
|
8.7 |
0.0026
|
f5 |
big-ip_advanced_web_application_firewall |
< 17.1.3
|
|
CVE-2026-41956 |
high
|
8.7 |
0.0026
|
f5 |
big-ip_advanced_web_application_firewall |
< 17.5.1
|
|
CVE-2026-41956 |
high
|
8.7 |
0.0026
|
f5 |
big-ip_advanced_web_application_firewall |
< 16.1.6
|
|
CVE-2026-41957 |
high
|
8.7 |
0.0051
|
f5 |
big-ip_advanced_web_application_firewall |
< 17.1.3
|
|
CVE-2026-41957 |
high
|
8.7 |
0.0051
|
f5 |
big-ip_advanced_web_application_firewall |
< 17.5.1
|
|
CVE-2026-41957 |
high
|
8.7 |
0.0051
|
f5 |
big-ip_advanced_web_application_firewall |
< 16.1.6
|
|
CVE-2026-42409 |
high
|
8.7 |
0.0026
|
f5 |
big-ip_advanced_web_application_firewall |
21.0.0
|
|
CVE-2026-42409 |
high
|
8.7 |
0.0026
|
f5 |
big-ip_advanced_web_application_firewall |
< 16.1.6
|
|
CVE-2026-42409 |
high
|
8.7 |
0.0026
|
f5 |
big-ip_advanced_web_application_firewall |
< 17.1.3
|
|
CVE-2026-42409 |
high
|
8.7 |
0.0026
|
f5 |
big-ip_advanced_web_application_firewall |
< 17.5.1
|
|
CVE-2026-42920 |
high
|
8.7 |
0.0026
|
f5 |
big-ip_advanced_web_application_firewall |
21.0.0
|
|
CVE-2026-42920 |
high
|
8.7 |
0.0026
|
f5 |
big-ip_advanced_web_application_firewall |
< 17.1.3
|
|
CVE-2026-42920 |
high
|
8.7 |
0.0026
|
f5 |
big-ip_advanced_web_application_firewall |
< 17.5.1
|
|
CVE-2026-42920 |
high
|
8.7 |
0.0026
|
f5 |
big-ip_advanced_web_application_firewall |
< 16.1.6
|
|
CVE-2026-39459 |
high
|
8.6 |
0.0026
|
f5 |
big-ip_advanced_web_application_firewall |
< 17.1.3
|
|
CVE-2026-39459 |
high
|
8.6 |
0.0026
|
f5 |
big-ip_advanced_web_application_firewall |
< 17.5.1
|
|
CVE-2026-39459 |
high
|
8.6 |
0.0026
|
f5 |
big-ip_advanced_web_application_firewall |
< 16.1.6
|
|
CVE-2026-39459 |
high
|
8.6 |
0.0026
|
f5 |
big-ip_advanced_web_application_firewall |
21.0.0
|
|
CVE-2026-41225 |
high
|
8.6 |
0.0027
|
f5 |
big-ip_advanced_web_application_firewall |
< 17.1.3
|
|
CVE-2026-41225 |
high
|
8.6 |
0.0027
|
f5 |
big-ip_advanced_web_application_firewall |
< 17.5.1
|
|