VEX records
Browse vendor VEX statements available in this Vulnerability-Lookup instance and pivot to the related vulnerability.
97904 VEX records
API response| Vulnerability | Source | Title | Product status | Imported | Links |
|---|---|---|---|---|---|
| CVE-2023-52748 | suse_vex | SUSE CVE CVE-2023-52748 | known not affected: 385 | 2026-10-16T13:26:08+00:00 | Vulnerability · Source |
| CVE-2023-52749 | suse_vex | SUSE CVE CVE-2023-52749 | known affected: 394 known not affected: 407 recommended: 353 | 2026-10-16T13:26:07+00:00 | Vulnerability · Source |
| CVE-2023-52752 | suse_vex | SUSE CVE CVE-2023-52752 | known affected: 312 known not affected: 123 recommended: 1170 | 2026-10-16T13:26:03+00:00 | Vulnerability · Source |
| CVE-2023-52753 | suse_vex | SUSE CVE CVE-2023-52753 | known affected: 391 known not affected: 108 recommended: 875 | 2026-10-16T13:26:02+00:00 | Vulnerability · Source |
| CVE-2023-52755 | suse_vex | SUSE CVE CVE-2023-52755 | known not affected: 628 | 2026-10-16T13:26:00+00:00 | Vulnerability · Source |
| CVE-2023-52757 | suse_vex | SUSE CVE CVE-2023-52757 | known affected: 402 known not affected: 103 recommended: 736 | 2026-10-16T13:25:58+00:00 | Vulnerability · Source |
| CVE-2023-52758 | suse_vex | SUSE CVE CVE-2023-52758 | No product status | 2026-10-16T13:25:56+00:00 | Vulnerability · Source |
| CVE-2023-52771 | suse_vex | SUSE CVE CVE-2023-52771 | known affected: 394 known not affected: 374 recommended: 411 | 2026-10-16T13:25:54+00:00 | Vulnerability · Source |
| CVE-2023-52774 | suse_vex | SUSE CVE CVE-2023-52774 | known affected: 455 known not affected: 31 recommended: 875 | 2026-10-16T13:25:53+00:00 | Vulnerability · Source |
| CVE-2023-52802 | suse_vex | SUSE CVE CVE-2023-52802 | known not affected: 379 recommended: 42 | 2026-10-16T13:25:50+00:00 | Vulnerability · Source |
| CVE-2023-52809 | suse_vex | SUSE CVE CVE-2023-52809 | known affected: 467 known not affected: 38 recommended: 828 | 2026-10-16T13:25:48+00:00 | Vulnerability · Source |
| CVE-2023-52811 | suse_vex | SUSE CVE CVE-2023-52811 | known affected: 447 known not affected: 36 recommended: 909 | 2026-10-16T13:25:46+00:00 | Vulnerability · Source |
| CVE-2023-52812 | suse_vex | SUSE CVE CVE-2023-52812 | known affected: 330 known not affected: 294 recommended: 651 | 2026-10-16T13:25:44+00:00 | Vulnerability · Source |
| CVE-2023-52820 | suse_vex | SUSE CVE CVE-2023-52820 | No product status | 2026-10-16T13:25:43+00:00 | Vulnerability · Source |
| CVE-2023-52824 | suse_vex | SUSE CVE CVE-2023-52824 | No product status | 2026-10-16T13:25:40+00:00 | Vulnerability · Source |
| CVE-2023-52832 | suse_vex | SUSE CVE CVE-2023-52832 | known affected: 477 known not affected: 22 recommended: 967 | 2026-10-16T13:25:37+00:00 | Vulnerability · Source |
| CVE-2023-52843 | suse_vex | SUSE CVE CVE-2023-52843 | known affected: 626 recommended: 735 | 2026-10-16T13:25:35+00:00 | Vulnerability · Source |
| CVE-2023-52848 | suse_vex | SUSE CVE CVE-2023-52848 | known not affected: 385 | 2026-10-16T13:25:33+00:00 | Vulnerability · Source |
| CVE-2023-52850 | suse_vex | SUSE CVE CVE-2023-52850 | known affected: 394 known not affected: 354 recommended: 353 | 2026-10-16T13:25:31+00:00 | Vulnerability · Source |
| CVE-2023-52858 | suse_vex | SUSE CVE CVE-2023-52858 | known affected: 342 known not affected: 164 recommended: 805 | 2026-10-16T13:25:29+00:00 | Vulnerability · Source |
| CVE-2023-52869 | suse_vex | SUSE CVE CVE-2023-52869 | known affected: 330 known not affected: 210 recommended: 651 | 2026-10-16T13:25:27+00:00 | Vulnerability · Source |
| CVE-2023-52870 | suse_vex | SUSE CVE CVE-2023-52870 | known affected: 275 known not affected: 184 recommended: 835 | 2026-10-16T13:25:25+00:00 | Vulnerability · Source |
| CVE-2023-52876 | suse_vex | SUSE CVE CVE-2023-52876 | known affected: 342 known not affected: 164 recommended: 805 | 2026-10-16T13:25:23+00:00 | Vulnerability · Source |
| CVE-2023-52877 | suse_vex | SUSE CVE CVE-2023-52877 | known affected: 275 known not affected: 235 recommended: 825 | 2026-10-16T13:25:21+00:00 | Vulnerability · Source |
| CVE-2023-52878 | suse_vex | SUSE CVE CVE-2023-52878 | known affected: 463 known not affected: 23 recommended: 848 | 2026-10-16T13:25:19+00:00 | Vulnerability · Source |
| CVE-2023-52899 | suse_vex | SUSE CVE CVE-2023-52899 | known affected: 483 known not affected: 212 recommended: 288 | 2026-10-16T13:25:16+00:00 | Vulnerability · Source |
| CVE-2023-52912 | suse_vex | SUSE CVE CVE-2023-52912 | known affected: 340 known not affected: 310 recommended: 288 | 2026-10-16T13:25:13+00:00 | Vulnerability · Source |
| CVE-2023-52920 | suse_vex | SUSE CVE CVE-2023-52920 | known affected: 520 known not affected: 327 recommended: 390 | 2026-10-16T13:25:10+00:00 | Vulnerability · Source |
| CVE-2023-52923 | suse_vex | SUSE CVE CVE-2023-52923 | known affected: 426 known not affected: 213 recommended: 582 | 2026-10-16T13:25:09+00:00 | Vulnerability · Source |
| CVE-2023-52924 | suse_vex | SUSE CVE CVE-2023-52924 | known affected: 344 known not affected: 435 recommended: 655 | 2026-10-16T13:25:07+00:00 | Vulnerability · Source |
| CVE-2023-52973 | suse_vex | SUSE CVE CVE-2023-52973 | known affected: 60 known not affected: 186 recommended: 376 | 2026-10-16T13:25:05+00:00 | Vulnerability · Source |
| CVE-2023-52981 | suse_vex | SUSE CVE CVE-2023-52981 | known affected: 430 known not affected: 331 recommended: 173 | 2026-10-16T13:25:02+00:00 | Vulnerability · Source |
| CVE-2023-53009 | suse_vex | SUSE CVE CVE-2023-53009 | known affected: 430 known not affected: 335 recommended: 173 | 2026-10-16T13:24:59+00:00 | Vulnerability · Source |
| CVE-2023-53022 | suse_vex | SUSE CVE CVE-2023-53022 | known affected: 61 known not affected: 395 | 2026-10-16T13:24:57+00:00 | Vulnerability · Source |
| CVE-2023-53039 | suse_vex | SUSE CVE CVE-2023-53039 | known affected: 403 known not affected: 227 recommended: 394 | 2026-10-16T13:24:55+00:00 | Vulnerability · Source |
| CVE-2023-53040 | suse_vex | SUSE CVE CVE-2023-53040 | known affected: 382 known not affected: 340 recommended: 214 | 2026-10-16T13:24:54+00:00 | Vulnerability · Source |
| CVE-2023-53064 | suse_vex | SUSE CVE CVE-2023-53064 | known affected: 339 known not affected: 381 recommended: 288 | 2026-10-16T13:24:52+00:00 | Vulnerability · Source |
| CVE-2023-53065 | suse_vex | SUSE CVE CVE-2023-53065 | known affected: 339 known not affected: 381 recommended: 272 | 2026-10-16T13:24:50+00:00 | Vulnerability · Source |
| CVE-2023-53072 | suse_vex | SUSE CVE CVE-2023-53072 | known affected: 61 known not affected: 441 recommended: 78 | 2026-10-16T13:24:48+00:00 | Vulnerability · Source |
| CVE-2023-53080 | suse_vex | SUSE CVE CVE-2023-53080 | known affected: 558 known not affected: 281 recommended: 23 | 2026-10-16T13:24:47+00:00 | Vulnerability · Source |
| CVE-2023-53082 | suse_vex | SUSE CVE CVE-2023-53082 | known affected: 369 known not affected: 438 recommended: 92 | 2026-10-16T13:24:45+00:00 | Vulnerability · Source |
| CVE-2023-53086 | suse_vex | SUSE CVE CVE-2023-53086 | known affected: 0 known not affected: 502 recommended: 78 | 2026-10-16T13:24:43+00:00 | Vulnerability · Source |
| CVE-2023-53087 | suse_vex | SUSE CVE CVE-2023-53087 | known affected: 382 known not affected: 338 recommended: 292 | 2026-10-16T13:24:41+00:00 | Vulnerability · Source |
| CVE-2023-53088 | suse_vex | SUSE CVE CVE-2023-53088 | known affected: 0 known not affected: 502 recommended: 78 | 2026-10-16T13:24:39+00:00 | Vulnerability · Source |
| CVE-2023-53090 | suse_vex | SUSE CVE CVE-2023-53090 | known affected: 533 known not affected: 146 recommended: 329 | 2026-10-16T13:24:38+00:00 | Vulnerability · Source |
| CVE-2023-53100 | suse_vex | SUSE CVE CVE-2023-53100 | known affected: 535 known not affected: 144 recommended: 309 | 2026-10-16T13:24:36+00:00 | Vulnerability · Source |
| CVE-2023-53102 | suse_vex | SUSE CVE CVE-2023-53102 | known affected: 499 known not affected: 308 recommended: 170 | 2026-10-16T13:24:34+00:00 | Vulnerability · Source |
| CVE-2023-53107 | suse_vex | SUSE CVE CVE-2023-53107 | known affected: 0 known not affected: 502 recommended: 58 | 2026-10-16T13:24:32+00:00 | Vulnerability · Source |
| CVE-2023-53111 | suse_vex | SUSE CVE CVE-2023-53111 | known affected: 343 known not affected: 377 recommended: 214 | 2026-10-16T13:24:30+00:00 | Vulnerability · Source |
| CVE-2023-53113 | suse_vex | SUSE CVE CVE-2023-53113 | known affected: 0 known not affected: 502 recommended: 78 | 2026-10-16T13:24:28+00:00 | Vulnerability · Source |