CVE-2026-10025 |
critical
|
9.8 |
0.0065
|
ibm |
qradar_security_information_and_event_manager |
7.5.0
|
|
CVE-2026-10025 |
critical
|
9.8 |
0.0065
|
ibm |
qradar_security_information_and_event_manager |
7.6.0
|
|
CVE-2026-6942 |
critical
|
9.3 |
0.0192
|
radare |
radare2_mcp_server |
< 1.7.0
|
|
CVE-2026-6942 |
critical
|
9.3 |
0.0192
|
radareorg |
radare2-mcp |
0
|
|
CVE-2026-82026 |
high
|
8.7 |
0.0092
|
skyhook-io |
radar |
0
< 1.12.2
|
|
CVE-2026-8695 |
high
|
8.7 |
0.0063
|
radare |
radare2 |
< 6.1.4
|
|
CVE-2026-8696 |
high
|
8.7 |
0.0060
|
radare |
radare2 |
< 6.1.4
|
|
CVE-2026-40527 |
high
|
8.5 |
0.0092
|
radare |
radare2 |
< 6.1.6
|
|
CVE-2026-108387 |
high
|
8.5 |
0.0015
|
radareorg |
radare2 |
< 6.2.2
|
|
CVE-2026-40527 |
high
|
8.5 |
0.0092
|
radareorg |
radare2 |
0
< bc5a89033db3ecb5b1f7bf681fc6ba4dcfc14683
|
|
CVE-2026-40499 |
high
|
8.4 |
0.0120
|
radare |
radare2 |
< 6.1.4
|
|
CVE-2026-40517 |
high
|
8.4 |
0.0105
|
radare |
radare2 |
< 6.1.4
|
|
CVE-2026-40499 |
high
|
8.4 |
0.0120
|
radareorg |
radare2 |
0
< 6.1.4
|
|
CVE-2026-40517 |
high
|
8.4 |
0.0105
|
radareorg |
radare2 |
0
< 6.1.4
|
|
CVE-2026-105467 |
high
|
8.1 |
0.0022
|
IBM |
QRadar |
7.5.0
|
|
CVE-2026-105467 |
high
|
8.1 |
0.0022
|
IBM |
QRadar |
7.6.0.0
|
|
CVE-2026-91869 |
high
|
8.1 |
—
|
IBM |
Security QRadar EDR |
3.12.0
|
|
CVE-2026-6940 |
medium
|
6.9 |
0.0022
|
radare |
radare2 |
< 6.1.4
|
|
CVE-2026-6941 |
medium
|
6.9 |
0.0022
|
radare |
radare2 |
< 6.1.4
|
|
CVE-2026-6940 |
medium
|
6.9 |
0.0022
|
radareorg |
radare2 |
0
< 6.1.4
|
|
CVE-2026-6941 |
medium
|
6.9 |
0.0022
|
radareorg |
radare2 |
0
< 6.1.4
|
|
CVE-2026-91868 |
medium
|
6.5 |
—
|
IBM |
Security QRadar EDR |
3.12.0
|
|
CVE-2025-63745 |
medium
|
5.5 |
0.0016
|
radare |
radare2 |
< 6.0.5
|
|
CVE-2025-60358 |
medium
|
5.5 |
0.0016
|
radare |
radare2 |
< 5.9.8
|
|
CVE-2025-60359 |
medium
|
5.5 |
0.0017
|
radare |
radare2 |
< 5.9.8
|
|
CVE-2025-60360 |
medium
|
5.5 |
0.0017
|
radare |
radare2 |
< 5.9.8
|
|
CVE-2026-13477 |
medium
|
4.7 |
0.0049
|
ibm |
qradar_security_information_and_event_manager |
7.5.0
|
|
CVE-2026-13477 |
medium
|
4.7 |
0.0049
|
ibm |
qradar_security_information_and_event_manager |
7.6.0
|
|
CVE-2026-13477 |
medium
|
4.7 |
0.0049
|
IBM |
QRadar |
7.6.0.0
|
|
CVE-2026-13477 |
medium
|
4.7 |
0.0049
|
IBM |
QRadar |
7.5.0
|
|
CVE-2026-105473 |
medium
|
4.6 |
0.0012
|
IBM |
QRadar |
7.5.0
|
|
CVE-2026-105473 |
medium
|
4.6 |
0.0012
|
IBM |
QRadar |
7.6.0.0
|
|
CVE-2025-63744 |
medium
|
4.3 |
0.0031
|
radare |
radare2 |
< 6.0.5
|
|
CVE-2025-60361 |
low
|
3.3 |
0.0017
|
radare |
radare2 |
< 5.9.8
|
|
CVE-2026-14757 |
low
|
1.9 |
0.0021
|
radare |
radare2 |
< 6.1.8
|
|
CVE-2026-14758 |
low
|
1.9 |
0.0019
|
radare |
radare2 |
< 6.1.8
|
|
CVE-2026-14759 |
low
|
1.9 |
0.0022
|
radare |
radare2 |
< 6.1.8
|
|
CVE-2026-14760 |
low
|
1.9 |
0.0020
|
radare |
radare2 |
< 6.1.8
|
|
CVE-2026-14761 |
low
|
1.9 |
0.0019
|
radare |
radare2 |
< 6.1.8
|
|
CVE-2026-14786 |
low
|
1.9 |
0.0019
|
radare |
radare2 |
< 6.1.8
|
|
CVE-2026-14787 |
low
|
1.9 |
0.0021
|
radare |
radare2 |
< 6.1.6
|
|
CVE-2026-14788 |
low
|
1.9 |
0.0020
|
radare |
radare2 |
< 6.1.6
|
|
CVE-2026-14789 |
low
|
1.9 |
0.0022
|
radare |
radare2 |
< 6.1.6
|
|