VEX records
Browse vendor VEX statements available in this Vulnerability-Lookup instance and pivot to the related vulnerability.
291994 VEX records
API response| Vulnerability | Source | Title | Product status | Imported | Links |
|---|---|---|---|---|---|
| CVE-2022-50753 | suse_vex | SUSE CVE CVE-2022-50753 | known affected: 61 known not affected: 392 | 2026-07-25T17:04:59+00:00 | Vulnerability · Source |
| CVE-2022-50765 | suse_vex | SUSE CVE CVE-2022-50765 | known not affected: 453 | 2026-07-25T17:04:55+00:00 | Vulnerability · Source |
| CVE-2022-50772 | suse_vex | SUSE CVE CVE-2022-50772 | known affected: 167 known not affected: 286 recommended: 29 | 2026-07-25T17:04:54+00:00 | Vulnerability · Source |
| CVE-2022-50780 | suse_vex | SUSE CVE CVE-2022-50780 | known affected: 394 known not affected: 411 recommended: 66 | 2026-07-25T17:04:47+00:00 | Vulnerability · Source |
| CVE-2022-50785 | suse_vex | SUSE CVE CVE-2022-50785 | known not affected: 453 | 2026-07-25T17:04:45+00:00 | Vulnerability · Source |
| CVE-2022-50786 | suse_vex | SUSE CVE CVE-2022-50786 | known affected: 622 known not affected: 193 recommended: 37 | 2026-07-25T17:04:44+00:00 | Vulnerability · Source |
| CVE-2022-50810 | suse_vex | SUSE CVE CVE-2022-50810 | known not affected: 453 | 2026-07-25T17:04:43+00:00 | Vulnerability · Source |
| CVE-2022-50812 | suse_vex | SUSE CVE CVE-2022-50812 | known not affected: 453 | 2026-07-25T17:04:41+00:00 | Vulnerability · Source |
| CVE-2022-50820 | suse_vex | SUSE CVE CVE-2022-50820 | known affected: 112 known not affected: 341 recommended: 29 | 2026-07-25T17:04:39+00:00 | Vulnerability · Source |
| CVE-2022-50841 | suse_vex | SUSE CVE CVE-2022-50841 | known not affected: 453 | 2026-07-25T17:04:27+00:00 | Vulnerability · Source |
| CVE-2022-50857 | suse_vex | SUSE CVE CVE-2022-50857 | known affected: 61 known not affected: 193 | 2026-07-25T17:04:21+00:00 | Vulnerability · Source |
| CVE-2022-50865 | suse_vex | SUSE CVE CVE-2022-50865 | known affected: 608 known not affected: 209 recommended: 72 | 2026-07-25T17:04:17+00:00 | Vulnerability · Source |
| CVE-2022-50879 | suse_vex | SUSE CVE CVE-2022-50879 | known not affected: 423 recommended: 52 | 2026-07-25T17:04:10+00:00 | Vulnerability · Source |
| CVE-2022-50888 | suse_vex | SUSE CVE CVE-2022-50888 | known affected: 354 known not affected: 341 recommended: 196 | 2026-07-25T17:04:07+00:00 | Vulnerability · Source |
| CVE-2023-0051 | suse_vex | SUSE CVE CVE-2023-0051 | known affected: 358 known not affected: 1 recommended: 322 | 2026-07-25T17:04:04+00:00 | Vulnerability · Source |
| CVE-2023-0054 | suse_vex | SUSE CVE CVE-2023-0054 | known affected: 358 known not affected: 1 recommended: 322 | 2026-07-25T17:04:02+00:00 | Vulnerability · Source |
| CVE-2023-0288 | suse_vex | SUSE CVE CVE-2023-0288 | known affected: 358 known not affected: 1 recommended: 322 | 2026-07-25T17:04:01+00:00 | Vulnerability · Source |
| CVE-2023-0801 | suse_vex | SUSE CVE CVE-2023-0801 | known affected: 494 known not affected: 1 recommended: 161 | 2026-07-25T17:03:46+00:00 | Vulnerability · Source |
| CVE-2023-0802 | suse_vex | SUSE CVE CVE-2023-0802 | known affected: 494 known not affected: 1 recommended: 161 | 2026-07-25T17:03:45+00:00 | Vulnerability · Source |
| CVE-2023-1906 | suse_vex | SUSE CVE CVE-2023-1906 | known affected: 46 known not affected: 237 recommended: 319 | 2026-07-25T17:03:32+00:00 | Vulnerability · Source |
| CVE-2023-3180 | suse_vex | SUSE CVE CVE-2023-3180 | known affected: 430 known not affected: 72 recommended: 1648 | 2026-07-25T17:03:25+00:00 | Vulnerability · Source |
| CVE-2023-3355 | suse_vex | SUSE CVE CVE-2023-3355 | known not affected: 361 | 2026-07-25T17:03:23+00:00 | Vulnerability · Source |
| CVE-2023-4573 | suse_vex | SUSE CVE CVE-2023-4573 | known affected: 49 recommended: 115 | 2026-07-25T17:03:11+00:00 | Vulnerability · Source |
| CVE-2023-4576 | suse_vex | SUSE CVE CVE-2023-4576 | known affected: 49 recommended: 285 | 2026-07-25T17:03:10+00:00 | Vulnerability · Source |
| CVE-2023-5088 | suse_vex | SUSE CVE CVE-2023-5088 | known not affected: 1297 recommended: 141 | 2026-07-25T17:03:04+00:00 | Vulnerability · Source |
| CVE-2023-5824 | suse_vex | SUSE CVE CVE-2023-5824 | known affected: 42 known not affected: 20 recommended: 8 | 2026-07-25T17:02:57+00:00 | Vulnerability · Source |
| CVE-2023-5870 | suse_vex | SUSE CVE CVE-2023-5870 | known affected: 551 known not affected: 420 recommended: 1815 | 2026-07-25T17:02:55+00:00 | Vulnerability · Source |
| CVE-2023-6209 | suse_vex | SUSE CVE CVE-2023-6209 | known affected: 38 recommended: 278 | 2026-07-25T17:02:52+00:00 | Vulnerability · Source |
| CVE-2023-7216 | suse_vex | SUSE CVE CVE-2023-7216 | known affected: 3 known not affected: 74 | 2026-07-25T17:02:46+00:00 | Vulnerability · Source |
| CVE-2023-20592 | suse_vex | SUSE CVE CVE-2023-20592 | known affected: 15 recommended: 1436 | 2026-07-25T17:02:42+00:00 | Vulnerability · Source |
| CVE-2023-22049 | suse_vex | SUSE CVE CVE-2023-22049 | known affected: 515 recommended: 894 | 2026-07-25T17:02:40+00:00 | Vulnerability · Source |
| CVE-2023-22652 | suse_vex | SUSE CVE CVE-2023-22652 | recommended: 68 | 2026-07-25T17:02:39+00:00 | Vulnerability · Source |
| CVE-2023-25360 | suse_vex | SUSE CVE CVE-2023-25360 | known not affected: 122 recommended: 851 | 2026-07-25T17:02:35+00:00 | Vulnerability · Source |
| CVE-2023-26607 | suse_vex | SUSE CVE CVE-2023-26607 | known not affected: 519 | 2026-07-25T17:02:30+00:00 | Vulnerability · Source |
| CVE-2023-26767 | suse_vex | SUSE CVE CVE-2023-26767 | known affected: 28 known not affected: 2 recommended: 248 | 2026-07-25T17:02:29+00:00 | Vulnerability · Source |
| CVE-2023-28100 | suse_vex | SUSE CVE CVE-2023-28100 | known affected: 1 known not affected: 35 recommended: 287 | 2026-07-25T17:02:27+00:00 | Vulnerability · Source |
| CVE-2023-28177 | suse_vex | SUSE CVE CVE-2023-28177 | known affected: 1 recommended: 214 | 2026-07-25T17:02:26+00:00 | Vulnerability · Source |
| CVE-2023-28625 | suse_vex | SUSE CVE CVE-2023-28625 | known affected: 5 recommended: 52 | 2026-07-25T17:02:23+00:00 | Vulnerability · Source |
| CVE-2023-29454 | suse_vex | SUSE CVE CVE-2023-29454 | known not affected: 21 recommended: 50 | 2026-07-25T17:02:20+00:00 | Vulnerability · Source |
| CVE-2023-29533 | suse_vex | SUSE CVE CVE-2023-29533 | known affected: 15 recommended: 305 | 2026-07-25T17:02:19+00:00 | Vulnerability · Source |
| CVE-2023-29941 | suse_vex | SUSE CVE CVE-2023-29941 | known not affected: 1268 | 2026-07-25T17:02:17+00:00 | Vulnerability · Source |
| CVE-2023-30630 | suse_vex | SUSE CVE CVE-2023-30630 | known affected: 296 recommended: 170 | 2026-07-25T17:02:16+00:00 | Vulnerability · Source |
| CVE-2023-30774 | suse_vex | SUSE CVE CVE-2023-30774 | known not affected: 175 recommended: 3 | 2026-07-25T17:02:15+00:00 | Vulnerability · Source |
| CVE-2023-31081 | suse_vex | SUSE CVE CVE-2023-31081 | known not affected: 327 | 2026-07-25T17:02:13+00:00 | Vulnerability · Source |
| CVE-2023-31130 | suse_vex | SUSE CVE CVE-2023-31130 | known affected: 295 recommended: 472 | 2026-07-25T17:02:12+00:00 | Vulnerability · Source |
| CVE-2023-31554 | suse_vex | SUSE CVE CVE-2023-31554 | known not affected: 410 | 2026-07-25T17:02:08+00:00 | Vulnerability · Source |
| CVE-2023-32208 | suse_vex | SUSE CVE CVE-2023-32208 | known affected: 65 recommended: 9 | 2026-07-25T17:02:06+00:00 | Vulnerability · Source |
| CVE-2023-32248 | suse_vex | SUSE CVE CVE-2023-32248 | known not affected: 416 | 2026-07-25T17:02:05+00:00 | Vulnerability · Source |
| CVE-2023-32255 | suse_vex | SUSE CVE CVE-2023-32255 | known not affected: 416 | 2026-07-25T17:02:04+00:00 | Vulnerability · Source |
| CVE-2023-32722 | suse_vex | SUSE CVE CVE-2023-32722 | known not affected: 17 recommended: 10 | 2026-07-25T17:02:01+00:00 | Vulnerability · Source |