VEX records
Browse vendor VEX statements available in this Vulnerability-Lookup instance and pivot to the related vulnerability.
294119 VEX records
API response| Vulnerability | Source | Title | Product status | Imported | Links |
|---|---|---|---|---|---|
| CVE-2018-8787 | suse_vex | SUSE CVE CVE-2018-8787 | recommended: 219 | 2026-07-19T18:28:56+00:00 | Vulnerability · Source |
| CVE-2018-11712 | suse_vex | SUSE CVE CVE-2018-11712 | known affected: 93 known not affected: 100 recommended: 1271 | 2026-07-19T18:28:27+00:00 | Vulnerability · Source |
| CVE-2018-12367 | suse_vex | SUSE CVE CVE-2018-12367 | known affected: 21 recommended: 105 | 2026-07-19T18:28:16+00:00 | Vulnerability · Source |
| CVE-2018-12371 | suse_vex | SUSE CVE CVE-2018-12371 | known affected: 21 recommended: 105 | 2026-07-19T18:28:15+00:00 | Vulnerability · Source |
| CVE-2018-16984 | suse_vex | SUSE CVE CVE-2018-16984 | recommended: 17 | 2026-07-19T18:27:15+00:00 | Vulnerability · Source |
| CVE-2018-19567 | suse_vex | SUSE CVE CVE-2018-19567 | known not affected: 85 recommended: 24 | 2026-07-19T18:26:47+00:00 | Vulnerability · Source |
| CVE-2018-19655 | suse_vex | SUSE CVE CVE-2018-19655 | known not affected: 85 recommended: 29 | 2026-07-19T18:26:43+00:00 | Vulnerability · Source |
| CVE-2018-19935 | suse_vex | SUSE CVE CVE-2018-19935 | known affected: 1080 known not affected: 1493 recommended: 2503 | 2026-07-19T18:26:38+00:00 | Vulnerability · Source |
| CVE-2018-20721 | suse_vex | SUSE CVE CVE-2018-20721 | recommended: 58 | 2026-07-19T18:26:18+00:00 | Vulnerability · Source |
| CVE-2019-3688 | suse_vex | SUSE CVE CVE-2019-3688 | known affected: 344 known not affected: 85 recommended: 264 | 2026-07-19T18:25:49+00:00 | Vulnerability · Source |
| CVE-2019-3883 | suse_vex | SUSE CVE CVE-2019-3883 | recommended: 152 | 2026-07-19T18:25:33+00:00 | Vulnerability · Source |
| CVE-2019-9803 | suse_vex | SUSE CVE CVE-2019-9803 | known affected: 20 known not affected: 76 recommended: 9 | 2026-07-19T18:24:21+00:00 | Vulnerability · Source |
| CVE-2019-10130 | suse_vex | SUSE CVE CVE-2019-10130 | known affected: 153 known not affected: 205 recommended: 504 | 2026-07-19T18:24:09+00:00 | Vulnerability · Source |
| CVE-2019-10217 | suse_vex | SUSE CVE CVE-2019-10217 | known affected: 1 known not affected: 4 recommended: 248 | 2026-07-19T18:24:04+00:00 | Vulnerability · Source |
| CVE-2019-12308 | suse_vex | SUSE CVE CVE-2019-12308 | known not affected: 3 recommended: 26 | 2026-07-19T18:23:29+00:00 | Vulnerability · Source |
| CVE-2019-14232 | suse_vex | SUSE CVE CVE-2019-14232 | known not affected: 4 recommended: 25 | 2026-07-19T18:23:00+00:00 | Vulnerability · Source |
| CVE-2019-14383 | suse_vex | SUSE CVE CVE-2019-14383 | recommended: 328 | 2026-07-19T18:22:54+00:00 | Vulnerability · Source |
| CVE-2019-15945 | suse_vex | SUSE CVE CVE-2019-15945 | known affected: 2 known not affected: 8 recommended: 72 | 2026-07-19T18:22:30+00:00 | Vulnerability · Source |
| CVE-2019-18904 | suse_vex | SUSE CVE CVE-2019-18904 | known affected: 11 known not affected: 25 recommended: 135 | 2026-07-19T18:22:09+00:00 | Vulnerability · Source |
| CVE-2020-8165 | suse_vex | SUSE CVE CVE-2020-8165 | known affected: 405 recommended: 155 | 2026-07-19T18:21:07+00:00 | Vulnerability · Source |
| CVE-2020-13396 | suse_vex | SUSE CVE CVE-2020-13396 | recommended: 182 | 2026-07-19T18:20:08+00:00 | Vulnerability · Source |
| CVE-2020-13398 | suse_vex | SUSE CVE CVE-2020-13398 | recommended: 181 | 2026-07-19T18:20:06+00:00 | Vulnerability · Source |
| CVE-2020-24584 | suse_vex | SUSE CVE CVE-2020-24584 | known not affected: 8 recommended: 17 | 2026-07-19T18:19:08+00:00 | Vulnerability · Source |
| CVE-2021-33571 | suse_vex | SUSE CVE CVE-2021-33571 | recommended: 276 | 2026-07-19T18:15:33+00:00 | Vulnerability · Source |
| CVE-2021-34552 | suse_vex | SUSE CVE CVE-2021-34552 | known not affected: 48 recommended: 46 | 2026-07-19T18:15:30+00:00 | Vulnerability · Source |
| CVE-2021-38191 | suse_vex | SUSE CVE CVE-2021-38191 | recommended: 18 | 2026-07-19T18:15:16+00:00 | Vulnerability · Source |
| CVE-2022-0544 | suse_vex | SUSE CVE CVE-2022-0544 | recommended: 16 | 2026-07-19T18:14:23+00:00 | Vulnerability · Source |
| CVE-2022-0546 | suse_vex | SUSE CVE CVE-2022-0546 | recommended: 16 | 2026-07-19T18:14:22+00:00 | Vulnerability · Source |
| CVE-2022-28347 | suse_vex | SUSE CVE CVE-2022-28347 | known not affected: 5 recommended: 17 | 2026-07-19T18:11:50+00:00 | Vulnerability · Source |
| CVE-2022-34265 | suse_vex | SUSE CVE CVE-2022-34265 | recommended: 106 | 2026-07-19T18:11:11+00:00 | Vulnerability · Source |
| CVE-2023-5871 | suse_vex | SUSE CVE CVE-2023-5871 | recommended: 46 | 2026-07-19T18:08:13+00:00 | Vulnerability · Source |
| CVE-2023-25744 | suse_vex | SUSE CVE CVE-2023-25744 | known affected: 1 recommended: 233 | 2026-07-19T18:07:27+00:00 | Vulnerability · Source |
| CVE-2024-32040 | suse_vex | SUSE CVE CVE-2024-32040 | known not affected: 48 recommended: 150 | 2026-07-19T18:01:00+00:00 | Vulnerability · Source |
| CVE-2024-32041 | suse_vex | SUSE CVE CVE-2024-32041 | known not affected: 48 recommended: 150 | 2026-07-19T18:00:59+00:00 | Vulnerability · Source |
| CVE-2024-32458 | suse_vex | SUSE CVE CVE-2024-32458 | known not affected: 48 recommended: 150 | 2026-07-19T18:00:56+00:00 | Vulnerability · Source |
| CVE-2025-2151 | suse_vex | SUSE CVE CVE-2025-2151 | recommended: 11 | 2026-07-19T17:52:49+00:00 | Vulnerability · Source |
| CVE-2025-43970 | suse_vex | SUSE CVE CVE-2025-43970 | recommended: 3 | 2026-07-19T17:45:56+00:00 | Vulnerability · Source |
| CVE-2025-47871 | suse_vex | SUSE CVE CVE-2025-47871 | recommended: 3 | 2026-07-19T17:45:51+00:00 | Vulnerability · Source |
| CVE-2025-58218 | suse_vex | SUSE CVE CVE-2025-58218 | No product status | 2026-07-19T17:45:29+00:00 | Vulnerability · Source |
| CVE-2025-58266 | suse_vex | SUSE CVE CVE-2025-58266 | recommended: 14 | 2026-07-19T17:45:28+00:00 | Vulnerability · Source |
| CVE-2026-13713 | suse_vex | SUSE CVE CVE-2026-13713 | recommended: 1 | 2026-07-19T17:43:55+00:00 | Vulnerability · Source |
| CVE-2026-23103 | suse_vex | SUSE CVE CVE-2026-23103 | first fixed: 2 known affected: 439 known not affected: 20 recommended: 556 | 2026-07-19T17:43:40+00:00 | Vulnerability · Source |
| CVE-2026-23120 | suse_vex | SUSE CVE CVE-2026-23120 | first fixed: 2 known affected: 617 known not affected: 20 recommended: 318 | 2026-07-19T17:43:37+00:00 | Vulnerability · Source |
| CVE-2026-23262 | suse_vex | SUSE CVE CVE-2026-23262 | first fixed: 2 known affected: 603 known not affected: 34 recommended: 318 | 2026-07-19T17:43:15+00:00 | Vulnerability · Source |
| CVE-2026-23272 | suse_vex | SUSE CVE CVE-2026-23272 | first fixed: 2 known affected: 435 known not affected: 20 recommended: 556 | 2026-07-19T17:43:09+00:00 | Vulnerability · Source |
| CVE-2026-23292 | suse_vex | SUSE CVE CVE-2026-23292 | first fixed: 2 known affected: 631 known not affected: 6 recommended: 318 | 2026-07-19T17:43:03+00:00 | Vulnerability · Source |
| CVE-2026-23340 | suse_vex | SUSE CVE CVE-2026-23340 | first fixed: 2 known affected: 209 known not affected: 34 recommended: 318 | 2026-07-19T17:42:53+00:00 | Vulnerability · Source |
| CVE-2026-23378 | suse_vex | SUSE CVE CVE-2026-23378 | first fixed: 2 known affected: 209 known not affected: 34 recommended: 318 | 2026-07-19T17:42:44+00:00 | Vulnerability · Source |
| CVE-2026-23386 | suse_vex | SUSE CVE CVE-2026-23386 | first fixed: 2 known affected: 555 known not affected: 82 recommended: 318 | 2026-07-19T17:42:38+00:00 | Vulnerability · Source |
| CVE-2026-23391 | suse_vex | SUSE CVE CVE-2026-23391 | first fixed: 2 known affected: 239 known not affected: 4 recommended: 318 | 2026-07-19T17:42:37+00:00 | Vulnerability · Source |