VEX records
Browse vendor VEX statements available in this Vulnerability-Lookup instance and pivot to the related vulnerability.
291704 VEX records
API response| Vulnerability | Source | Title | Product status | Imported | Links |
|---|---|---|---|---|---|
| CVE-2023-31724 | suse_vex | SUSE CVE CVE-2023-31724 | known not affected: 3 | 2026-08-14T01:12:31+00:00 | Vulnerability · Source |
| CVE-2023-32700 | suse_vex | SUSE CVE CVE-2023-32700 | known not affected: 9209 recommended: 9119 | 2026-08-14T01:12:24+00:00 | Vulnerability · Source |
| CVE-2023-35824 | suse_vex | SUSE CVE CVE-2023-35824 | known affected: 409 known not affected: 114 recommended: 451 | 2026-08-14T01:12:19+00:00 | Vulnerability · Source |
| CVE-2023-37788 | suse_vex | SUSE CVE CVE-2023-37788 | known not affected: 177 | 2026-08-14T01:12:14+00:00 | Vulnerability · Source |
| CVE-2023-38428 | suse_vex | SUSE CVE CVE-2023-38428 | known not affected: 361 | 2026-08-14T01:12:07+00:00 | Vulnerability · Source |
| CVE-2023-39129 | suse_vex | SUSE CVE CVE-2023-39129 | known not affected: 108 | 2026-08-14T01:12:02+00:00 | Vulnerability · Source |
| CVE-2023-39321 | suse_vex | SUSE CVE CVE-2023-39321 | known affected: 3 known not affected: 152 recommended: 200 | 2026-08-14T01:11:59+00:00 | Vulnerability · Source |
| CVE-2023-39351 | suse_vex | SUSE CVE CVE-2023-39351 | recommended: 156 | 2026-08-14T01:11:57+00:00 | Vulnerability · Source |
| CVE-2023-39810 | suse_vex | SUSE CVE CVE-2023-39810 | recommended: 4 | 2026-08-14T01:11:55+00:00 | Vulnerability · Source |
| CVE-2023-40745 | suse_vex | SUSE CVE CVE-2023-40745 | known affected: 394 known not affected: 174 recommended: 69 | 2026-08-14T01:11:53+00:00 | Vulnerability · Source |
| CVE-2023-41359 | suse_vex | SUSE CVE CVE-2023-41359 | known not affected: 537 recommended: 2 | 2026-08-14T01:11:48+00:00 | Vulnerability · Source |
| CVE-2023-42754 | suse_vex | SUSE CVE CVE-2023-42754 | known affected: 199 known not affected: 38 recommended: 1336 | 2026-08-14T01:11:44+00:00 | Vulnerability · Source |
| CVE-2023-45960 | suse_vex | SUSE CVE CVE-2023-45960 | known not affected: 26 | 2026-08-14T01:11:32+00:00 | Vulnerability · Source |
| CVE-2023-46407 | suse_vex | SUSE CVE CVE-2023-46407 | known not affected: 641 | 2026-08-14T01:11:28+00:00 | Vulnerability · Source |
| CVE-2023-46836 | suse_vex | SUSE CVE CVE-2023-46836 | known affected: 259 recommended: 426 | 2026-08-14T01:11:26+00:00 | Vulnerability · Source |
| CVE-2023-47233 | suse_vex | SUSE CVE CVE-2023-47233 | known affected: 255 known not affected: 6 recommended: 984 | 2026-08-14T01:11:22+00:00 | Vulnerability · Source |
| CVE-2023-47470 | suse_vex | SUSE CVE CVE-2023-47470 | known not affected: 641 | 2026-08-14T01:11:21+00:00 | Vulnerability · Source |
| CVE-2023-49463 | suse_vex | SUSE CVE CVE-2023-49463 | known not affected: 29 recommended: 35 | 2026-08-14T01:11:18+00:00 | Vulnerability · Source |
| CVE-2023-49501 | suse_vex | SUSE CVE CVE-2023-49501 | known not affected: 564 recommended: 25 | 2026-08-14T01:11:16+00:00 | Vulnerability · Source |
| CVE-2023-49528 | suse_vex | SUSE CVE CVE-2023-49528 | known not affected: 519 recommended: 51 | 2026-08-14T01:11:15+00:00 | Vulnerability · Source |
| CVE-2023-51042 | suse_vex | SUSE CVE CVE-2023-51042 | known affected: 287 known not affected: 88 recommended: 945 | 2026-08-14T01:11:06+00:00 | Vulnerability · Source |
| CVE-2023-51384 | suse_vex | SUSE CVE CVE-2023-51384 | known not affected: 254 | 2026-08-14T01:11:04+00:00 | Vulnerability · Source |
| CVE-2023-51441 | suse_vex | SUSE CVE CVE-2023-51441 | known affected: 45 recommended: 26 | 2026-08-14T01:11:02+00:00 | Vulnerability · Source |
| CVE-2023-52449 | suse_vex | SUSE CVE CVE-2023-52449 | known affected: 341 known not affected: 60 recommended: 947 | 2026-08-14T01:10:59+00:00 | Vulnerability · Source |
| CVE-2023-52614 | suse_vex | SUSE CVE CVE-2023-52614 | known affected: 542 known not affected: 76 recommended: 608 | 2026-08-14T01:10:51+00:00 | Vulnerability · Source |
| CVE-2023-52854 | suse_vex | SUSE CVE CVE-2023-52854 | known affected: 360 known not affected: 53 recommended: 939 | 2026-08-14T01:10:38+00:00 | Vulnerability · Source |
| CVE-2023-52904 | suse_vex | SUSE CVE CVE-2023-52904 | known affected: 340 known not affected: 435 recommended: 288 | 2026-08-14T01:10:33+00:00 | Vulnerability · Source |
| CVE-2023-52935 | suse_vex | SUSE CVE CVE-2023-52935 | known affected: 414 known not affected: 111 recommended: 330 | 2026-08-14T01:10:31+00:00 | Vulnerability · Source |
| CVE-2023-53005 | suse_vex | SUSE CVE CVE-2023-53005 | known affected: 385 known not affected: 196 recommended: 222 | 2026-08-14T01:10:29+00:00 | Vulnerability · Source |
| CVE-2023-53010 | suse_vex | SUSE CVE CVE-2023-53010 | known affected: 433 known not affected: 117 recommended: 311 | 2026-08-14T01:10:27+00:00 | Vulnerability · Source |
| CVE-2023-53035 | suse_vex | SUSE CVE CVE-2023-53035 | known affected: 339 known not affected: 249 recommended: 214 | 2026-08-14T01:10:26+00:00 | Vulnerability · Source |
| CVE-2023-53056 | suse_vex | SUSE CVE CVE-2023-53056 | known affected: 339 known not affected: 266 recommended: 286 | 2026-08-14T01:10:24+00:00 | Vulnerability · Source |
| CVE-2023-53057 | suse_vex | SUSE CVE CVE-2023-53057 | known not affected: 342 recommended: 96 | 2026-08-14T01:10:22+00:00 | Vulnerability · Source |
| CVE-2023-53073 | suse_vex | SUSE CVE CVE-2023-53073 | known affected: 369 known not affected: 342 recommended: 121 | 2026-08-14T01:10:20+00:00 | Vulnerability · Source |
| CVE-2023-53081 | suse_vex | SUSE CVE CVE-2023-53081 | known affected: 407 known not affected: 198 recommended: 237 | 2026-08-14T01:10:19+00:00 | Vulnerability · Source |
| CVE-2023-53093 | suse_vex | SUSE CVE CVE-2023-53093 | known affected: 390 known not affected: 256 recommended: 214 | 2026-08-14T01:10:17+00:00 | Vulnerability · Source |
| CVE-2023-53111 | suse_vex | SUSE CVE CVE-2023-53111 | known affected: 343 known not affected: 288 recommended: 214 | 2026-08-14T01:10:15+00:00 | Vulnerability · Source |
| CVE-2023-53390 | suse_vex | SUSE CVE CVE-2023-53390 | known affected: 395 known not affected: 253 recommended: 255 | 2026-08-14T01:10:06+00:00 | Vulnerability · Source |
| CVE-2023-53525 | suse_vex | SUSE CVE CVE-2023-53525 | known affected: 381 known not affected: 267 recommended: 255 | 2026-08-14T01:10:02+00:00 | Vulnerability · Source |
| CVE-2023-53667 | suse_vex | SUSE CVE CVE-2023-53667 | known affected: 472 known not affected: 187 recommended: 233 | 2026-08-14T01:09:54+00:00 | Vulnerability · Source |
| CVE-2023-53706 | suse_vex | SUSE CVE CVE-2023-53706 | known not affected: 407 recommended: 29 | 2026-08-14T01:09:52+00:00 | Vulnerability · Source |
| CVE-2023-53710 | suse_vex | SUSE CVE CVE-2023-53710 | known not affected: 407 recommended: 49 | 2026-08-14T01:09:50+00:00 | Vulnerability · Source |
| CVE-2023-53798 | suse_vex | SUSE CVE CVE-2023-53798 | known affected: 112 known not affected: 296 | 2026-08-14T01:09:47+00:00 | Vulnerability · Source |
| CVE-2023-54015 | suse_vex | SUSE CVE CVE-2023-54015 | known affected: 409 known not affected: 286 recommended: 245 | 2026-08-14T01:09:43+00:00 | Vulnerability · Source |
| CVE-2023-54159 | suse_vex | SUSE CVE CVE-2023-54159 | known affected: 409 known not affected: 286 recommended: 196 | 2026-08-14T01:09:38+00:00 | Vulnerability · Source |
| CVE-2024-0074 | suse_vex | SUSE CVE CVE-2024-0074 | recommended: 78 | 2026-08-14T01:09:32+00:00 | Vulnerability · Source |
| CVE-2024-0607 | suse_vex | SUSE CVE CVE-2024-0607 | known affected: 400 known not affected: 90 recommended: 905 | 2026-08-14T01:09:29+00:00 | Vulnerability · Source |
| CVE-2024-8386 | suse_vex | SUSE CVE CVE-2024-8386 | known affected: 30 recommended: 216 | 2026-08-14T01:09:22+00:00 | Vulnerability · Source |
| CVE-2024-21733 | suse_vex | SUSE CVE CVE-2024-21733 | known affected: 46 known not affected: 282 recommended: 45 | 2026-08-14T01:09:16+00:00 | Vulnerability · Source |
| CVE-2024-22019 | suse_vex | SUSE CVE CVE-2024-22019 | known affected: 12 known not affected: 21 recommended: 307 | 2026-08-14T01:09:14+00:00 | Vulnerability · Source |