VEX records
Browse vendor VEX statements available in this Vulnerability-Lookup instance and pivot to the related vulnerability.
299358 VEX records
API response| Vulnerability | Source | Title | Product status | Imported | Links |
|---|---|---|---|---|---|
| CVE-2019-11485 | suse_vex | SUSE CVE CVE-2019-11485 | known affected: 1 recommended: 6 | 2026-05-27T06:11:52+00:00 | Vulnerability · Source |
| CVE-2019-13990 | suse_vex | SUSE CVE CVE-2019-13990 | known affected: 374 recommended: 2 | 2026-05-27T06:09:15+00:00 | Vulnerability · Source |
| CVE-2019-19530 | suse_vex | SUSE CVE CVE-2019-19530 | known affected: 100 known not affected: 61 recommended: 750 | 2026-05-27T06:03:36+00:00 | Vulnerability · Source |
| CVE-2019-19807 | suse_vex | SUSE CVE CVE-2019-19807 | known affected: 300 known not affected: 341 recommended: 814 | 2026-05-27T06:03:15+00:00 | Vulnerability · Source |
| CVE-2019-20391 | suse_vex | SUSE CVE CVE-2019-20391 | recommended: 1 | 2026-05-27T06:02:31+00:00 | Vulnerability · Source |
| CVE-2019-20392 | suse_vex | SUSE CVE CVE-2019-20392 | recommended: 1 | 2026-05-27T06:02:30+00:00 | Vulnerability · Source |
| CVE-2019-20393 | suse_vex | SUSE CVE CVE-2019-20393 | recommended: 1 | 2026-05-27T06:02:29+00:00 | Vulnerability · Source |
| CVE-2019-20394 | suse_vex | SUSE CVE CVE-2019-20394 | recommended: 1 | 2026-05-27T06:02:28+00:00 | Vulnerability · Source |
| CVE-2019-20395 | suse_vex | SUSE CVE CVE-2019-20395 | recommended: 1 | 2026-05-27T06:02:27+00:00 | Vulnerability · Source |
| CVE-2019-20397 | suse_vex | SUSE CVE CVE-2019-20397 | recommended: 1 | 2026-05-27T06:02:26+00:00 | Vulnerability · Source |
| CVE-2019-20398 | suse_vex | SUSE CVE CVE-2019-20398 | recommended: 1 | 2026-05-27T06:02:25+00:00 | Vulnerability · Source |
| CVE-2020-6467 | suse_vex | SUSE CVE CVE-2020-6467 | recommended: 17 | 2026-05-27T05:59:07+00:00 | Vulnerability · Source |
| CVE-2020-6472 | suse_vex | SUSE CVE CVE-2020-6472 | recommended: 17 | 2026-05-27T05:59:06+00:00 | Vulnerability · Source |
| CVE-2020-6474 | suse_vex | SUSE CVE CVE-2020-6474 | recommended: 17 | 2026-05-27T05:59:04+00:00 | Vulnerability · Source |
| CVE-2020-6475 | suse_vex | SUSE CVE CVE-2020-6475 | recommended: 17 | 2026-05-27T05:59:03+00:00 | Vulnerability · Source |
| CVE-2020-6481 | suse_vex | SUSE CVE CVE-2020-6481 | recommended: 17 | 2026-05-27T05:59:01+00:00 | Vulnerability · Source |
| CVE-2020-6490 | suse_vex | SUSE CVE CVE-2020-6490 | recommended: 17 | 2026-05-27T05:58:59+00:00 | Vulnerability · Source |
| CVE-2020-7216 | suse_vex | SUSE CVE CVE-2020-7216 | known affected: 332 known not affected: 18 recommended: 241 | 2026-05-27T05:58:17+00:00 | Vulnerability · Source |
| CVE-2020-12693 | suse_vex | SUSE CVE CVE-2020-12693 | known not affected: 194 recommended: 1628 | 2026-05-27T05:54:20+00:00 | Vulnerability · Source |
| CVE-2020-14798 | suse_vex | SUSE CVE CVE-2020-14798 | known affected: 444 recommended: 1129 | 2026-05-27T05:51:49+00:00 | Vulnerability · Source |
| CVE-2020-27821 | suse_vex | SUSE CVE CVE-2020-27821 | known affected: 368 known not affected: 245 recommended: 1555 | 2026-05-27T05:46:34+00:00 | Vulnerability · Source |
| CVE-2020-37011 | suse_vex | SUSE CVE CVE-2020-37011 | No product status | 2026-05-27T05:44:01+00:00 | Vulnerability · Source |
| CVE-2021-28657 | suse_vex | SUSE CVE CVE-2021-28657 | known affected: 374 known not affected: 2 recommended: 94 | 2026-05-27T05:34:04+00:00 | Vulnerability · Source |
| CVE-2021-47952 | suse_vex | SUSE CVE CVE-2021-47952 | No product status | 2026-05-27T05:16:08+00:00 | Vulnerability · Source |
| CVE-2022-0613 | suse_vex | SUSE CVE CVE-2022-0613 | recommended: 9 | 2026-05-27T05:15:01+00:00 | Vulnerability · Source |
| CVE-2022-21592 | suse_vex | SUSE CVE CVE-2022-21592 | recommended: 17 | 2026-05-27T05:07:32+00:00 | Vulnerability · Source |
| CVE-2022-21607 | suse_vex | SUSE CVE CVE-2022-21607 | recommended: 17 | 2026-05-27T05:07:30+00:00 | Vulnerability · Source |
| CVE-2022-21635 | suse_vex | SUSE CVE CVE-2022-21635 | recommended: 17 | 2026-05-27T05:07:21+00:00 | Vulnerability · Source |
| CVE-2022-21638 | suse_vex | SUSE CVE CVE-2022-21638 | recommended: 17 | 2026-05-27T05:07:20+00:00 | Vulnerability · Source |
| CVE-2022-21641 | suse_vex | SUSE CVE CVE-2022-21641 | recommended: 17 | 2026-05-27T05:07:18+00:00 | Vulnerability · Source |
| CVE-2022-23708 | suse_vex | SUSE CVE CVE-2022-23708 | known not affected: 5 | 2026-05-27T05:05:49+00:00 | Vulnerability · Source |
| CVE-2022-33879 | suse_vex | SUSE CVE CVE-2022-33879 | known affected: 374 recommended: 2 | 2026-05-27T05:02:16+00:00 | Vulnerability · Source |
| CVE-2022-36369 | suse_vex | SUSE CVE CVE-2022-36369 | known not affected: 39 recommended: 6 | 2026-05-27T05:01:30+00:00 | Vulnerability · Source |
| CVE-2022-40964 | suse_vex | SUSE CVE CVE-2022-40964 | recommended: 55 | 2026-05-27T05:00:20+00:00 | Vulnerability · Source |
| CVE-2022-43760 | suse_vex | SUSE CVE CVE-2022-43760 | known affected: 374 | 2026-05-27T04:59:13+00:00 | Vulnerability · Source |
| CVE-2023-21866 | suse_vex | SUSE CVE CVE-2023-21866 | recommended: 17 | 2026-05-27T04:20:48+00:00 | Vulnerability · Source |
| CVE-2023-21913 | suse_vex | SUSE CVE CVE-2023-21913 | recommended: 18 | 2026-05-27T04:20:43+00:00 | Vulnerability · Source |
| CVE-2023-21963 | suse_vex | SUSE CVE CVE-2023-21963 | recommended: 18 | 2026-05-27T04:20:38+00:00 | Vulnerability · Source |
| CVE-2023-22026 | suse_vex | SUSE CVE CVE-2023-22026 | recommended: 18 | 2026-05-27T04:20:30+00:00 | Vulnerability · Source |
| CVE-2023-22647 | suse_vex | SUSE CVE CVE-2023-22647 | known affected: 374 | 2026-05-27T04:20:12+00:00 | Vulnerability · Source |
| CVE-2023-29452 | suse_vex | SUSE CVE CVE-2023-29452 | known not affected: 16 | 2026-05-27T04:17:55+00:00 | Vulnerability · Source |
| CVE-2023-41914 | suse_vex | SUSE CVE CVE-2023-41914 | known not affected: 44 recommended: 2593 | 2026-05-27T04:14:16+00:00 | Vulnerability · Source |
| CVE-2023-43632 | suse_vex | SUSE CVE CVE-2023-43632 | No product status | 2026-05-27T04:13:49+00:00 | Vulnerability · Source |
| CVE-2023-46575 | suse_vex | SUSE CVE CVE-2023-46575 | No product status | 2026-05-27T04:13:05+00:00 | Vulnerability · Source |
| CVE-2024-3834 | suse_vex | SUSE CVE CVE-2024-3834 | recommended: 10 | 2026-05-27T03:52:17+00:00 | Vulnerability · Source |
| CVE-2024-5154 | suse_vex | SUSE CVE CVE-2024-5154 | No product status | 2026-05-27T03:51:55+00:00 | Vulnerability · Source |
| CVE-2024-21386 | suse_vex | SUSE CVE CVE-2024-21386 | recommended: 65 | 2026-05-27T03:49:41+00:00 | Vulnerability · Source |
| CVE-2024-29645 | suse_vex | SUSE CVE CVE-2024-29645 | recommended: 19 | 2026-05-27T03:42:39+00:00 | Vulnerability · Source |
| CVE-2024-45614 | suse_vex | SUSE CVE CVE-2024-45614 | known affected: 374 recommended: 13 | 2026-05-27T03:27:11+00:00 | Vulnerability · Source |
| CVE-2024-49369 | suse_vex | SUSE CVE CVE-2024-49369 | recommended: 48 | 2026-05-27T03:23:16+00:00 | Vulnerability · Source |