VEX records
Browse vendor VEX statements available in this Vulnerability-Lookup instance and pivot to the related vulnerability.
104719 VEX records
API response| Vulnerability | Source | Title | Product status | Imported | Links |
|---|---|---|---|---|---|
| CVE-2024-26655 | suse_vex | SUSE CVE CVE-2024-26655 | known not affected: 334 | 2026-10-16T13:17:20+00:00 | Vulnerability · Source |
| CVE-2024-26661 | suse_vex | SUSE CVE CVE-2024-26661 | known affected: 345 known not affected: 187 recommended: 759 | 2026-10-16T13:17:18+00:00 | Vulnerability · Source |
| CVE-2024-26687 | suse_vex | SUSE CVE CVE-2024-26687 | known affected: 431 known not affected: 57 recommended: 748 | 2026-10-16T13:17:15+00:00 | Vulnerability · Source |
| CVE-2024-26694 | suse_vex | SUSE CVE CVE-2024-26694 | known not affected: 362 recommended: 222 | 2026-10-16T13:17:13+00:00 | Vulnerability · Source |
| CVE-2024-26697 | suse_vex | SUSE CVE CVE-2024-26697 | known affected: 394 known not affected: 325 recommended: 452 | 2026-10-16T13:17:11+00:00 | Vulnerability · Source |
| CVE-2024-26707 | suse_vex | SUSE CVE CVE-2024-26707 | known affected: 154 known not affected: 308 | 2026-10-16T13:17:10+00:00 | Vulnerability · Source |
| CVE-2024-26725 | suse_vex | SUSE CVE CVE-2024-26725 | known not affected: 362 recommended: 202 | 2026-10-16T13:17:07+00:00 | Vulnerability · Source |
| CVE-2024-26733 | suse_vex | SUSE CVE CVE-2024-26733 | known affected: 372 recommended: 1088 | 2026-10-16T13:17:05+00:00 | Vulnerability · Source |
| CVE-2024-26743 | suse_vex | SUSE CVE CVE-2024-26743 | known affected: 621 known not affected: 67 recommended: 540 | 2026-10-16T13:17:01+00:00 | Vulnerability · Source |
| CVE-2024-26746 | suse_vex | SUSE CVE CVE-2024-26746 | known not affected: 364 recommended: 202 | 2026-10-16T13:16:59+00:00 | Vulnerability · Source |
| CVE-2024-26763 | suse_vex | SUSE CVE CVE-2024-26763 | known affected: 676 known not affected: 77 recommended: 520 | 2026-10-16T13:16:56+00:00 | Vulnerability · Source |
| CVE-2024-26774 | suse_vex | SUSE CVE CVE-2024-26774 | known not affected: 284 recommended: 351 | 2026-10-16T13:16:54+00:00 | Vulnerability · Source |
| CVE-2024-26780 | suse_vex | SUSE CVE CVE-2024-26780 | known not affected: 334 recommended: 353 | 2026-10-16T13:16:52+00:00 | Vulnerability · Source |
| CVE-2024-26793 | suse_vex | SUSE CVE CVE-2024-26793 | known affected: 620 known not affected: 14 recommended: 655 | 2026-10-16T13:16:50+00:00 | Vulnerability · Source |
| CVE-2024-26796 | suse_vex | SUSE CVE CVE-2024-26796 | known not affected: 356 | 2026-10-16T13:16:49+00:00 | Vulnerability · Source |
| CVE-2024-26803 | suse_vex | SUSE CVE CVE-2024-26803 | known affected: 77 known not affected: 324 recommended: 202 | 2026-10-16T13:16:47+00:00 | Vulnerability · Source |
| CVE-2024-26806 | suse_vex | SUSE CVE CVE-2024-26806 | known not affected: 356 | 2026-10-16T13:16:45+00:00 | Vulnerability · Source |
| CVE-2024-26814 | suse_vex | SUSE CVE CVE-2024-26814 | known affected: 317 known not affected: 254 recommended: 779 | 2026-10-16T13:16:43+00:00 | Vulnerability · Source |
| CVE-2024-26827 | suse_vex | SUSE CVE CVE-2024-26827 | known not affected: 366 | 2026-10-16T13:16:41+00:00 | Vulnerability · Source |
| CVE-2024-26838 | suse_vex | SUSE CVE CVE-2024-26838 | known affected: 382 known not affected: 316 recommended: 515 | 2026-10-16T13:16:39+00:00 | Vulnerability · Source |
| CVE-2024-26841 | suse_vex | SUSE CVE CVE-2024-26841 | known not affected: 366 | 2026-10-16T13:16:38+00:00 | Vulnerability · Source |
| CVE-2024-26869 | suse_vex | SUSE CVE CVE-2024-26869 | known not affected: 366 | 2026-10-16T13:16:35+00:00 | Vulnerability · Source |
| CVE-2024-26873 | suse_vex | SUSE CVE CVE-2024-26873 | known affected: 394 known not affected: 272 recommended: 309 | 2026-10-16T13:16:33+00:00 | Vulnerability · Source |
| CVE-2024-26927 | suse_vex | SUSE CVE CVE-2024-26927 | known affected: 310 known not affected: 323 recommended: 522 | 2026-10-16T13:16:27+00:00 | Vulnerability · Source |
| CVE-2024-26931 | suse_vex | SUSE CVE CVE-2024-26931 | known affected: 487 known not affected: 68 recommended: 680 | 2026-10-16T13:16:26+00:00 | Vulnerability · Source |
| CVE-2024-26971 | suse_vex | SUSE CVE CVE-2024-26971 | known not affected: 385 | 2026-10-16T13:16:23+00:00 | Vulnerability · Source |
| CVE-2024-27030 | suse_vex | SUSE CVE CVE-2024-27030 | known affected: 310 known not affected: 102 recommended: 733 | 2026-10-16T13:16:18+00:00 | Vulnerability · Source |
| CVE-2024-27043 | suse_vex | SUSE CVE CVE-2024-27043 | known affected: 362 known not affected: 58 recommended: 1127 | 2026-10-16T13:16:15+00:00 | Vulnerability · Source |
| CVE-2024-27049 | suse_vex | SUSE CVE CVE-2024-27049 | known affected: 394 known not affected: 332 recommended: 413 | 2026-10-16T13:16:12+00:00 | Vulnerability · Source |
| CVE-2024-27398 | suse_vex | SUSE CVE CVE-2024-27398 | known affected: 449 known not affected: 44 recommended: 1116 | 2026-10-16T13:16:09+00:00 | Vulnerability · Source |
| CVE-2024-27402 | suse_vex | SUSE CVE CVE-2024-27402 | known affected: 482 known not affected: 38 recommended: 651 | 2026-10-16T13:16:07+00:00 | Vulnerability · Source |
| CVE-2024-27415 | suse_vex | SUSE CVE CVE-2024-27415 | known affected: 690 known not affected: 155 recommended: 362 | 2026-10-16T13:16:05+00:00 | Vulnerability · Source |
| CVE-2024-27416 | suse_vex | SUSE CVE CVE-2024-27416 | known affected: 368 known not affected: 217 recommended: 670 | 2026-10-16T13:16:03+00:00 | Vulnerability · Source |
| CVE-2024-27430 | suse_vex | SUSE CVE CVE-2024-27430 | No product status | 2026-10-16T13:16:00+00:00 | Vulnerability · Source |
| CVE-2024-27830 | suse_vex | SUSE CVE CVE-2024-27830 | known not affected: 286 | 2026-10-16T13:15:59+00:00 | Vulnerability · Source |
| CVE-2024-28103 | suse_vex | SUSE CVE CVE-2024-28103 | known affected: 16 known not affected: 20 recommended: 98 | 2026-10-16T13:15:57+00:00 | Vulnerability · Source |
| CVE-2024-29131 | suse_vex | SUSE CVE CVE-2024-29131 | known affected: 21 recommended: 47 | 2026-10-16T13:15:55+00:00 | Vulnerability · Source |
| CVE-2024-29510 | suse_vex | SUSE CVE CVE-2024-29510 | known affected: 38 recommended: 130 | 2026-10-16T13:15:54+00:00 | Vulnerability · Source |
| CVE-2024-31068 | suse_vex | SUSE CVE CVE-2024-31068 | known affected: 21 recommended: 44 | 2026-10-16T13:15:52+00:00 | Vulnerability · Source |
| CVE-2024-31080 | suse_vex | SUSE CVE CVE-2024-31080 | known affected: 440 known not affected: 36 recommended: 263 | 2026-10-16T13:15:50+00:00 | Vulnerability · Source |
| CVE-2024-31081 | suse_vex | SUSE CVE CVE-2024-31081 | known affected: 440 known not affected: 36 recommended: 263 | 2026-10-16T13:15:48+00:00 | Vulnerability · Source |
| CVE-2024-32230 | suse_vex | SUSE CVE CVE-2024-32230 | known affected: 481 recommended: 607 | 2026-10-16T13:15:46+00:00 | Vulnerability · Source |
| CVE-2024-32462 | suse_vex | SUSE CVE CVE-2024-32462 | known affected: 38 known not affected: 59 recommended: 392 | 2026-10-16T13:15:44+00:00 | Vulnerability · Source |
| CVE-2024-32487 | suse_vex | SUSE CVE CVE-2024-32487 | known affected: 274 recommended: 190 | 2026-10-16T13:15:42+00:00 | Vulnerability · Source |
| CVE-2024-32658 | suse_vex | SUSE CVE CVE-2024-32658 | recommended: 204 | 2026-10-16T13:15:40+00:00 | Vulnerability · Source |
| CVE-2024-32659 | suse_vex | SUSE CVE CVE-2024-32659 | recommended: 204 | 2026-10-16T13:15:38+00:00 | Vulnerability · Source |
| CVE-2024-33427 | suse_vex | SUSE CVE CVE-2024-33427 | known affected: 427 recommended: 27 | 2026-10-16T13:15:36+00:00 | Vulnerability · Source |
| CVE-2024-33870 | suse_vex | SUSE CVE CVE-2024-33870 | known affected: 37 known not affected: 1 recommended: 138 | 2026-10-16T13:15:33+00:00 | Vulnerability · Source |
| CVE-2024-34064 | suse_vex | SUSE CVE CVE-2024-34064 | known affected: 392 recommended: 269 | 2026-10-16T13:15:31+00:00 | Vulnerability · Source |
| CVE-2024-35365 | suse_vex | SUSE CVE CVE-2024-35365 | known affected: 0 known not affected: 435 recommended: 355 | 2026-10-16T13:15:29+00:00 | Vulnerability · Source |