VEX records
Browse vendor VEX statements available in this Vulnerability-Lookup instance and pivot to the related vulnerability.
291728 VEX records
API response| Vulnerability | Source | Title | Product status | Imported | Links |
|---|---|---|---|---|---|
| CVE-2023-39593 | suse_vex | SUSE CVE CVE-2023-39593 | known not affected: 348 | 2026-08-13T02:07:21+00:00 | Vulnerability · Source |
| CVE-2023-39929 | suse_vex | SUSE CVE CVE-2023-39929 | known affected: 93 known not affected: 73 recommended: 78 | 2026-08-13T02:07:18+00:00 | Vulnerability · Source |
| CVE-2023-40030 | suse_vex | SUSE CVE CVE-2023-40030 | known not affected: 529 recommended: 70 | 2026-08-13T02:07:13+00:00 | Vulnerability · Source |
| CVE-2023-40589 | suse_vex | SUSE CVE CVE-2023-40589 | recommended: 156 | 2026-08-13T02:07:00+00:00 | Vulnerability · Source |
| CVE-2023-41056 | suse_vex | SUSE CVE CVE-2023-41056 | known not affected: 33 recommended: 4 | 2026-08-13T02:06:56+00:00 | Vulnerability · Source |
| CVE-2023-41900 | suse_vex | SUSE CVE CVE-2023-41900 | known affected: 8 recommended: 357 | 2026-08-13T02:06:52+00:00 | Vulnerability · Source |
| CVE-2023-42503 | suse_vex | SUSE CVE CVE-2023-42503 | known not affected: 26 | 2026-08-13T02:06:50+00:00 | Vulnerability · Source |
| CVE-2023-42818 | suse_vex | SUSE CVE CVE-2023-42818 | recommended: 3 | 2026-08-13T02:06:46+00:00 | Vulnerability · Source |
| CVE-2023-43787 | suse_vex | SUSE CVE CVE-2023-43787 | known affected: 571 recommended: 276 | 2026-08-13T02:06:39+00:00 | Vulnerability · Source |
| CVE-2023-45145 | suse_vex | SUSE CVE CVE-2023-45145 | known affected: 1 recommended: 37 | 2026-08-13T02:06:34+00:00 | Vulnerability · Source |
| CVE-2023-45290 | suse_vex | SUSE CVE CVE-2023-45290 | recommended: 260 | 2026-08-13T02:06:32+00:00 | Vulnerability · Source |
| CVE-2023-46343 | suse_vex | SUSE CVE CVE-2023-46343 | known affected: 508 known not affected: 212 recommended: 280 | 2026-08-13T02:06:21+00:00 | Vulnerability · Source |
| CVE-2023-46840 | suse_vex | SUSE CVE CVE-2023-46840 | known affected: 292 known not affected: 265 recommended: 181 | 2026-08-13T02:06:18+00:00 | Vulnerability · Source |
| CVE-2023-47235 | suse_vex | SUSE CVE CVE-2023-47235 | known affected: 1 recommended: 312 | 2026-08-13T02:06:14+00:00 | Vulnerability · Source |
| CVE-2023-50007 | suse_vex | SUSE CVE CVE-2023-50007 | known not affected: 680 recommended: 51 | 2026-08-13T02:06:03+00:00 | Vulnerability · Source |
| CVE-2023-50009 | suse_vex | SUSE CVE CVE-2023-50009 | known not affected: 680 recommended: 26 | 2026-08-13T02:06:01+00:00 | Vulnerability · Source |
| CVE-2023-50980 | suse_vex | SUSE CVE CVE-2023-50980 | known affected: 81 recommended: 48 | 2026-08-13T02:05:59+00:00 | Vulnerability · Source |
| CVE-2023-51795 | suse_vex | SUSE CVE CVE-2023-51795 | known not affected: 564 | 2026-08-13T02:05:53+00:00 | Vulnerability · Source |
| CVE-2023-51796 | suse_vex | SUSE CVE CVE-2023-51796 | known not affected: 564 recommended: 26 | 2026-08-13T02:05:52+00:00 | Vulnerability · Source |
| CVE-2023-51797 | suse_vex | SUSE CVE CVE-2023-51797 | known not affected: 564 | 2026-08-13T02:05:50+00:00 | Vulnerability · Source |
| CVE-2023-52160 | suse_vex | SUSE CVE CVE-2023-52160 | known affected: 404 known not affected: 7 recommended: 54 | 2026-08-13T02:05:48+00:00 | Vulnerability · Source |
| CVE-2023-52508 | suse_vex | SUSE CVE CVE-2023-52508 | known affected: 254 known not affected: 164 recommended: 768 | 2026-08-13T02:05:25+00:00 | Vulnerability · Source |
| CVE-2023-52529 | suse_vex | SUSE CVE CVE-2023-52529 | known affected: 260 known not affected: 200 recommended: 706 | 2026-08-13T02:05:17+00:00 | Vulnerability · Source |
| CVE-2023-52570 | suse_vex | SUSE CVE CVE-2023-52570 | known not affected: 292 recommended: 206 | 2026-08-13T02:05:14+00:00 | Vulnerability · Source |
| CVE-2023-52595 | suse_vex | SUSE CVE CVE-2023-52595 | known affected: 503 known not affected: 60 recommended: 636 | 2026-08-13T02:05:05+00:00 | Vulnerability · Source |
| CVE-2023-52616 | suse_vex | SUSE CVE CVE-2023-52616 | known affected: 271 known not affected: 223 recommended: 820 | 2026-08-13T02:04:55+00:00 | Vulnerability · Source |
| CVE-2023-52620 | suse_vex | SUSE CVE CVE-2023-52620 | known affected: 502 known not affected: 66 recommended: 451 | 2026-08-13T02:04:52+00:00 | Vulnerability · Source |
| CVE-2023-52629 | suse_vex | SUSE CVE CVE-2023-52629 | known not affected: 311 | 2026-08-13T02:04:46+00:00 | Vulnerability · Source |
| CVE-2023-52633 | suse_vex | SUSE CVE CVE-2023-52633 | known not affected: 272 | 2026-08-13T02:04:44+00:00 | Vulnerability · Source |
| CVE-2023-52682 | suse_vex | SUSE CVE CVE-2023-52682 | known not affected: 330 | 2026-08-13T02:04:32+00:00 | Vulnerability · Source |
| CVE-2023-52686 | suse_vex | SUSE CVE CVE-2023-52686 | known affected: 334 known not affected: 12 recommended: 1045 | 2026-08-13T02:04:30+00:00 | Vulnerability · Source |
| CVE-2023-52701 | suse_vex | SUSE CVE CVE-2023-52701 | known not affected: 330 | 2026-08-13T02:04:21+00:00 | Vulnerability · Source |
| CVE-2023-52702 | suse_vex | SUSE CVE CVE-2023-52702 | known affected: 275 known not affected: 217 recommended: 452 | 2026-08-13T02:04:19+00:00 | Vulnerability · Source |
| CVE-2023-52734 | suse_vex | SUSE CVE CVE-2023-52734 | known not affected: 60 recommended: 49 | 2026-08-13T02:04:16+00:00 | Vulnerability · Source |
| CVE-2023-52737 | suse_vex | SUSE CVE CVE-2023-52737 | known affected: 330 known not affected: 261 recommended: 382 | 2026-08-13T02:04:14+00:00 | Vulnerability · Source |
| CVE-2023-52738 | suse_vex | SUSE CVE CVE-2023-52738 | known affected: 275 known not affected: 217 recommended: 452 | 2026-08-13T02:04:12+00:00 | Vulnerability · Source |
| CVE-2023-52743 | suse_vex | SUSE CVE CVE-2023-52743 | known affected: 364 known not affected: 103 recommended: 522 | 2026-08-13T02:04:09+00:00 | Vulnerability · Source |
| CVE-2023-52756 | suse_vex | SUSE CVE CVE-2023-52756 | known affected: 275 recommended: 514 | 2026-08-13T02:04:01+00:00 | Vulnerability · Source |
| CVE-2023-52770 | suse_vex | SUSE CVE CVE-2023-52770 | known not affected: 330 | 2026-08-13T02:03:57+00:00 | Vulnerability · Source |
| CVE-2023-52774 | suse_vex | SUSE CVE CVE-2023-52774 | known affected: 399 known not affected: 36 recommended: 880 | 2026-08-13T02:03:54+00:00 | Vulnerability · Source |
| CVE-2023-52781 | suse_vex | SUSE CVE CVE-2023-52781 | known affected: 340 known not affected: 39 recommended: 900 | 2026-08-13T02:03:50+00:00 | Vulnerability · Source |
| CVE-2023-52785 | suse_vex | SUSE CVE CVE-2023-52785 | known not affected: 330 | 2026-08-13T02:03:48+00:00 | Vulnerability · Source |
| CVE-2023-52792 | suse_vex | SUSE CVE CVE-2023-52792 | known affected: 394 known not affected: 297 recommended: 358 | 2026-08-13T02:03:46+00:00 | Vulnerability · Source |
| CVE-2023-52899 | suse_vex | SUSE CVE CVE-2023-52899 | known affected: 465 known not affected: 169 recommended: 288 | 2026-08-13T02:03:20+00:00 | Vulnerability · Source |
| CVE-2023-52908 | suse_vex | SUSE CVE CVE-2023-52908 | known affected: 340 known not affected: 248 recommended: 288 | 2026-08-13T02:03:18+00:00 | Vulnerability · Source |
| CVE-2023-52915 | suse_vex | SUSE CVE CVE-2023-52915 | known affected: 557 known not affected: 18 recommended: 710 | 2026-08-13T02:03:15+00:00 | Vulnerability · Source |
| CVE-2023-52923 | suse_vex | SUSE CVE CVE-2023-52923 | known affected: 394 known not affected: 151 recommended: 612 | 2026-08-13T02:03:13+00:00 | Vulnerability · Source |
| CVE-2023-52924 | suse_vex | SUSE CVE CVE-2023-52924 | known affected: 344 known not affected: 328 recommended: 652 | 2026-08-13T02:03:11+00:00 | Vulnerability · Source |
| CVE-2023-52930 | suse_vex | SUSE CVE CVE-2023-52930 | known affected: 371 known not affected: 210 recommended: 222 | 2026-08-13T02:03:09+00:00 | Vulnerability · Source |
| CVE-2023-52931 | suse_vex | SUSE CVE CVE-2023-52931 | known affected: 369 known not affected: 293 recommended: 144 | 2026-08-13T02:03:08+00:00 | Vulnerability · Source |