CVE-2026-7300 |
high
|
8.8 |
0.0025
|
rti |
connext_professional |
< 7.4.0
|
|
CVE-2026-42016 |
high
|
8.8 |
0.0864
|
jfrog |
artifactory |
< 7.133.11
|
KEV
|
CVE-2026-42017 |
high
|
8.8 |
0.0052
|
jfrog |
artifactory |
< 7.133.21
|
|
CVE-2026-65616 |
high
|
8.8 |
0.0037
|
jfrog |
artifactory |
< 7.146.27
|
|
CVE-2026-65617 |
high
|
8.8 |
0.0065
|
jfrog |
artifactory |
< 7.111.18
|
|
CVE-2026-65921 |
high
|
8.8 |
0.0059
|
jfrog |
artifactory |
< 7.111.18
|
|
CVE-2026-66014 |
high
|
8.8 |
0.0064
|
jfrog |
artifactory |
< 7.111.18
|
|
CVE-2026-69106 |
high
|
8.8 |
0.0052
|
jfrog |
artifactory |
< 7.146.28
|
|
CVE-2026-70742 |
high
|
8.8 |
0.0043
|
oracle |
hyperion_financial_reporting |
11.2.25.0.000
|
|
CVE-2026-70787 |
high
|
8.8 |
0.0043
|
oracle |
hyperion_financial_reporting |
11.2.25.0.000
|
|
CVE-2023-54357 |
high
|
8.7 |
0.0066
|
artio |
book_it\! |
2.4.9
|
|
CVE-2026-39455 |
high
|
8.7 |
0.0030
|
f5 |
big-ip_application_visibility_and_reporting |
< 17.1.3
|
|
CVE-2026-39455 |
high
|
8.7 |
0.0030
|
f5 |
big-ip_application_visibility_and_reporting |
21.0.0
|
|
CVE-2026-39458 |
high
|
8.7 |
0.0026
|
f5 |
big-ip_application_visibility_and_reporting |
< 17.1.3
|
|
CVE-2026-39458 |
high
|
8.7 |
0.0026
|
f5 |
big-ip_application_visibility_and_reporting |
21.0.0
|
|
CVE-2026-40423 |
high
|
8.7 |
0.0026
|
f5 |
big-ip_application_visibility_and_reporting |
< 17.1.3
|
|
CVE-2026-40423 |
high
|
8.7 |
0.0026
|
f5 |
big-ip_application_visibility_and_reporting |
21.0.0
|
|
CVE-2026-40618 |
high
|
8.7 |
0.0032
|
f5 |
big-ip_application_visibility_and_reporting |
< 17.1.3
|
|
CVE-2026-40618 |
high
|
8.7 |
0.0032
|
f5 |
big-ip_application_visibility_and_reporting |
21.0.0
|
|
CVE-2026-40629 |
high
|
8.7 |
0.0032
|
f5 |
big-ip_application_visibility_and_reporting |
< 17.1.3
|
|
CVE-2026-41218 |
high
|
8.7 |
0.0026
|
f5 |
big-ip_application_visibility_and_reporting |
< 17.1.3
|
|
CVE-2026-41218 |
high
|
8.7 |
0.0026
|
f5 |
big-ip_application_visibility_and_reporting |
21.0.0
|
|
CVE-2026-41956 |
high
|
8.7 |
0.0026
|
f5 |
big-ip_application_visibility_and_reporting |
< 17.1.3
|
|
CVE-2026-41957 |
high
|
8.7 |
0.0051
|
f5 |
big-ip_application_visibility_and_reporting |
< 17.1.3
|
|
CVE-2026-42409 |
high
|
8.7 |
0.0026
|
f5 |
big-ip_application_visibility_and_reporting |
21.0.0
|
|
CVE-2026-42409 |
high
|
8.7 |
0.0026
|
f5 |
big-ip_application_visibility_and_reporting |
< 16.1.6
|
|
CVE-2026-42920 |
high
|
8.7 |
0.0026
|
f5 |
big-ip_application_visibility_and_reporting |
21.0.0
|
|
CVE-2026-42920 |
high
|
8.7 |
0.0026
|
f5 |
big-ip_application_visibility_and_reporting |
< 17.1.3
|
|
CVE-2026-39459 |
high
|
8.6 |
0.0026
|
f5 |
big-ip_application_visibility_and_reporting |
< 17.1.3
|
|
CVE-2026-39459 |
high
|
8.6 |
0.0026
|
f5 |
big-ip_application_visibility_and_reporting |
21.0.0
|
|
CVE-2026-41225 |
high
|
8.6 |
0.0027
|
f5 |
big-ip_application_visibility_and_reporting |
< 17.1.3
|
|
CVE-2026-41225 |
high
|
8.6 |
0.0027
|
f5 |
big-ip_application_visibility_and_reporting |
21.0.0
|
|
CVE-2026-59835 |
high
|
8.6 |
0.0040
|
fortinet |
fortisandbox |
< 4.4.9
|
|
CVE-2026-32643 |
high
|
8.5 |
0.0016
|
f5 |
big-ip_application_visibility_and_reporting |
< 17.1.3
|
|
CVE-2026-32643 |
high
|
8.5 |
0.0016
|
f5 |
big-ip_application_visibility_and_reporting |
21.0.0
|
|
CVE-2026-32673 |
high
|
8.5 |
0.0024
|
f5 |
big-ip_application_visibility_and_reporting |
< 17.1.3
|
|
CVE-2026-32673 |
high
|
8.5 |
0.0024
|
f5 |
big-ip_application_visibility_and_reporting |
21.0.0
|
|
CVE-2026-34176 |
high
|
8.5 |
0.0069
|
f5 |
big-ip_application_visibility_and_reporting |
< 17.1.3
|
|
CVE-2026-34176 |
high
|
8.5 |
0.0069
|
f5 |
big-ip_application_visibility_and_reporting |
21.0.0
|
|
CVE-2026-40631 |
high
|
8.5 |
0.0025
|
f5 |
big-ip_application_visibility_and_reporting |
< 17.1.3
|
|
CVE-2026-40631 |
high
|
8.5 |
0.0025
|
f5 |
big-ip_application_visibility_and_reporting |
21.0.0
|
|
CVE-2026-40698 |
high
|
8.5 |
0.0024
|
f5 |
big-ip_application_visibility_and_reporting |
< 17.1.3
|
|
CVE-2026-40698 |
high
|
8.5 |
0.0024
|
f5 |
big-ip_application_visibility_and_reporting |
21.0.0
|
|
CVE-2026-41953 |
high
|
8.5 |
0.0025
|
f5 |
big-ip_application_visibility_and_reporting |
< 17.1.3
|
|
CVE-2026-41953 |
high
|
8.5 |
0.0025
|
f5 |
big-ip_application_visibility_and_reporting |
21.0.0
|
|
CVE-2026-42406 |
high
|
8.5 |
0.0015
|
f5 |
big-ip_application_visibility_and_reporting |
< 17.1.3
|
|
CVE-2026-42406 |
high
|
8.5 |
0.0015
|
f5 |
big-ip_application_visibility_and_reporting |
21.0.0
|
|
CVE-2026-42924 |
high
|
8.5 |
0.0025
|
f5 |
big-ip_application_visibility_and_reporting |
21.0.0
|
|
CVE-2026-42924 |
high
|
8.5 |
0.0025
|
f5 |
big-ip_application_visibility_and_reporting |
< 17.1.3
|
|
CVE-2026-42930 |
high
|
8.5 |
0.0048
|
f5 |
big-ip_application_visibility_and_reporting |
21.0.0
|
|