VEX records
Browse vendor VEX statements available in this Vulnerability-Lookup instance and pivot to the related vulnerability.
291348 VEX records
API response| Vulnerability | Source | Title | Product status | Imported | Links |
|---|---|---|---|---|---|
| CVE-2020-35728 | suse_vex | SUSE CVE CVE-2020-35728 | recommended: 54 | 2026-08-07T00:26:16+00:00 | Vulnerability · Source |
| CVE-2021-3483 | suse_vex | SUSE CVE CVE-2021-3483 | known affected: 322 known not affected: 17 recommended: 1520 | 2026-08-07T00:26:09+00:00 | Vulnerability · Source |
| CVE-2021-3487 | suse_vex | SUSE CVE CVE-2021-3487 | known affected: 396 recommended: 542 | 2026-08-07T00:26:07+00:00 | Vulnerability · Source |
| CVE-2021-4186 | suse_vex | SUSE CVE CVE-2021-4186 | known affected: 75 known not affected: 82 recommended: 228 | 2026-08-07T00:25:55+00:00 | Vulnerability · Source |
| CVE-2021-21341 | suse_vex | SUSE CVE CVE-2021-21341 | known affected: 394 recommended: 67 | 2026-08-07T00:25:48+00:00 | Vulnerability · Source |
| CVE-2021-21345 | suse_vex | SUSE CVE CVE-2021-21345 | known affected: 394 recommended: 69 | 2026-08-07T00:25:46+00:00 | Vulnerability · Source |
| CVE-2021-28146 | suse_vex | SUSE CVE CVE-2021-28146 | known affected: 1 known not affected: 9 recommended: 242 | 2026-08-07T00:25:34+00:00 | Vulnerability · Source |
| CVE-2021-28148 | suse_vex | SUSE CVE CVE-2021-28148 | known not affected: 12 recommended: 242 | 2026-08-07T00:25:33+00:00 | Vulnerability · Source |
| CVE-2021-39144 | suse_vex | SUSE CVE CVE-2021-39144 | known affected: 394 recommended: 71 | 2026-08-07T00:25:20+00:00 | Vulnerability · Source |
| CVE-2021-39153 | suse_vex | SUSE CVE CVE-2021-39153 | known affected: 394 recommended: 71 | 2026-08-07T00:25:18+00:00 | Vulnerability · Source |
| CVE-2021-47402 | suse_vex | SUSE CVE CVE-2021-47402 | known affected: 269 known not affected: 174 recommended: 650 | 2026-08-07T00:24:49+00:00 | Vulnerability · Source |
| CVE-2022-1048 | suse_vex | SUSE CVE CVE-2022-1048 | known affected: 180 known not affected: 9 recommended: 2080 | 2026-08-07T00:24:39+00:00 | Vulnerability · Source |
| CVE-2022-2255 | suse_vex | SUSE CVE CVE-2022-2255 | known affected: 405 recommended: 94 | 2026-08-07T00:24:33+00:00 | Vulnerability · Source |
| CVE-2022-2795 | suse_vex | SUSE CVE CVE-2022-2795 | known affected: 253 known not affected: 171 recommended: 1090 | 2026-08-07T00:24:30+00:00 | Vulnerability · Source |
| CVE-2018-5407 | microsoft_vex | Simultaneous Multi-threading (SMT) in processors can enable local users to exploit software vulnerable to timing attacks via a side-channel timing attack on 'port contention'. | known affected: 4 under investigation: 4 | 2026-08-07T00:24:28+00:00 | Vulnerability · Source |
| CVE-2022-2953 | suse_vex | SUSE CVE CVE-2022-2953 | known not affected: 184 recommended: 6 | 2026-08-07T00:24:28+00:00 | Vulnerability · Source |
| CVE-2022-2991 | suse_vex | SUSE CVE CVE-2022-2991 | known affected: 394 known not affected: 59 recommended: 266 | 2026-08-07T00:24:23+00:00 | Vulnerability · Source |
| CVE-2022-31197 | suse_vex | SUSE CVE CVE-2022-31197 | known affected: 395 known not affected: 23 recommended: 60 | 2026-08-07T00:24:01+00:00 | Vulnerability · Source |
| CVE-2022-38023 | suse_vex | SUSE CVE CVE-2022-38023 | known affected: 272 known not affected: 106 recommended: 2471 | 2026-08-07T00:23:53+00:00 | Vulnerability · Source |
| CVE-2022-42011 | suse_vex | SUSE CVE CVE-2022-42011 | known affected: 254 known not affected: 1 recommended: 529 | 2026-08-07T00:23:43+00:00 | Vulnerability · Source |
| CVE-2022-45153 | suse_vex | SUSE CVE CVE-2022-45153 | known affected: 394 recommended: 20 | 2026-08-07T00:23:37+00:00 | Vulnerability · Source |
| CVE-2022-48727 | suse_vex | SUSE CVE CVE-2022-48727 | known affected: 330 known not affected: 205 recommended: 391 | 2026-08-07T00:23:32+00:00 | Vulnerability · Source |
| CVE-2022-48797 | suse_vex | SUSE CVE CVE-2022-48797 | known affected: 295 known not affected: 205 recommended: 426 | 2026-08-07T00:23:27+00:00 | Vulnerability · Source |
| CVE-2022-48803 | suse_vex | SUSE CVE CVE-2022-48803 | known affected: 295 known not affected: 205 recommended: 426 | 2026-08-07T00:23:25+00:00 | Vulnerability · Source |
| CVE-2022-48810 | suse_vex | SUSE CVE CVE-2022-48810 | known affected: 518 known not affected: 82 recommended: 382 | 2026-08-07T00:23:21+00:00 | Vulnerability · Source |
| CVE-2022-48830 | suse_vex | SUSE CVE CVE-2022-48830 | known affected: 295 known not affected: 205 recommended: 467 | 2026-08-07T00:23:19+00:00 | Vulnerability · Source |
| CVE-2022-48884 | suse_vex | SUSE CVE CVE-2022-48884 | known affected: 340 known not affected: 249 recommended: 335 | 2026-08-07T00:23:16+00:00 | Vulnerability · Source |
| CVE-2022-49374 | suse_vex | SUSE CVE CVE-2022-49374 | known affected: 106 known not affected: 246 recommended: 42 | 2026-08-07T00:22:58+00:00 | Vulnerability · Source |
| CVE-2022-49552 | suse_vex | SUSE CVE CVE-2022-49552 | known affected: 419 known not affected: 247 recommended: 127 | 2026-08-07T00:22:54+00:00 | Vulnerability · Source |
| CVE-2022-49594 | suse_vex | SUSE CVE CVE-2022-49594 | known affected: 55 known not affected: 297 recommended: 27 | 2026-08-07T00:22:52+00:00 | Vulnerability · Source |
| CVE-2022-50771 | suse_vex | SUSE CVE CVE-2022-50771 | known affected: 214 known not affected: 179 recommended: 29 | 2026-08-07T00:22:27+00:00 | Vulnerability · Source |
| CVE-2023-2183 | suse_vex | SUSE CVE CVE-2023-2183 | known not affected: 5 recommended: 64 | 2026-08-07T00:22:21+00:00 | Vulnerability · Source |
| CVE-2023-3128 | suse_vex | SUSE CVE CVE-2023-3128 | known affected: 394 known not affected: 5 recommended: 17 | 2026-08-07T00:22:18+00:00 | Vulnerability · Source |
| CVE-2023-34462 | suse_vex | SUSE CVE CVE-2023-34462 | known not affected: 50 recommended: 47 | 2026-08-07T00:21:52+00:00 | Vulnerability · Source |
| CVE-2023-53126 | suse_vex | SUSE CVE CVE-2023-53126 | known not affected: 397 recommended: 49 | 2026-08-07T00:21:17+00:00 | Vulnerability · Source |
| CVE-2023-53282 | suse_vex | SUSE CVE CVE-2023-53282 | known affected: 422 known not affected: 181 recommended: 333 | 2026-08-07T00:21:13+00:00 | Vulnerability · Source |
| CVE-2024-1313 | suse_vex | SUSE CVE CVE-2024-1313 | recommended: 104 | 2026-08-07T00:20:55+00:00 | Vulnerability · Source |
| CVE-2024-8118 | suse_vex | SUSE CVE CVE-2024-8118 | known affected: 2 known not affected: 2 recommended: 71 | 2026-08-07T00:20:44+00:00 | Vulnerability · Source |
| CVE-2024-20697 | suse_vex | SUSE CVE CVE-2024-20697 | known affected: 394 known not affected: 200 recommended: 37 | 2026-08-07T00:20:36+00:00 | Vulnerability · Source |
| CVE-2016-2568 | microsoft_vex | pkexec, when used with --user nonpriv, allows local users to escape to the parent session | fixed: 4 known affected: 4 under investigation: 1 | 2026-08-07T00:20:17+00:00 | Vulnerability · Source |
| CVE-2024-36350 | suse_vex | SUSE CVE CVE-2024-36350 | known affected: 343 recommended: 818 | 2026-08-07T00:20:04+00:00 | Vulnerability · Source |
| CVE-2024-42516 | suse_vex | SUSE CVE CVE-2024-42516 | known affected: 472 recommended: 283 | 2026-08-07T00:19:46+00:00 | Vulnerability · Source |
| CVE-2007-3205 | microsoft_vex | The parse_str function in (1) PHP, (2) Hardened-PHP, and (3) Suhosin, when called without a second parameter, might allow remote attackers to overwrite arbitrary variables by specifying variable names and values in the string to be parsed. NOTE: it is not clear whether this is a design limitation of the function or a bug in PHP, although it is likely to be regarded as a bug in Hardened-PHP and Suhosin. | fixed: 2 known affected: 2 under investigation: 1 | 2026-08-07T00:19:25+00:00 | Vulnerability · Source |
| CVE-2024-53131 | suse_vex | SUSE CVE CVE-2024-53131 | known affected: 620 known not affected: 76 recommended: 420 | 2026-08-07T00:19:18+00:00 | Vulnerability · Source |
| CVE-2024-58067 | suse_vex | SUSE CVE CVE-2024-58067 | known not affected: 352 | 2026-08-07T00:18:52+00:00 | Vulnerability · Source |
| CVE-2025-9900 | suse_vex | SUSE CVE CVE-2025-9900 | known affected: 431 known not affected: 466 recommended: 160 | 2026-08-07T00:18:29+00:00 | Vulnerability · Source |
| CVE-2025-11839 | suse_vex | SUSE CVE CVE-2025-11839 | known affected: 191 | 2026-08-07T00:18:23+00:00 | Vulnerability · Source |
| CVE-2025-11840 | suse_vex | SUSE CVE CVE-2025-11840 | known affected: 191 | 2026-08-07T00:18:21+00:00 | Vulnerability · Source |
| CVE-2025-12818 | suse_vex | SUSE CVE CVE-2025-12818 | known affected: 484 known not affected: 490 recommended: 1967 | 2026-08-07T00:18:18+00:00 | Vulnerability · Source |
| CVE-2025-38013 | suse_vex | SUSE CVE CVE-2025-38013 | known affected: 394 known not affected: 308 recommended: 490 | 2026-08-07T00:17:41+00:00 | Vulnerability · Source |