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-2024-10463 | suse_vex | SUSE CVE CVE-2024-10463 | known affected: 67 recommended: 219 | 2026-10-16T13:18:20+00:00 | Vulnerability · Source |
| CVE-2024-11695 | suse_vex | SUSE CVE CVE-2024-11695 | known affected: 57 recommended: 238 | 2026-10-16T13:18:16+00:00 | Vulnerability · Source |
| CVE-2024-12797 | suse_vex | SUSE CVE CVE-2024-12797 | known affected: 394 known not affected: 739 recommended: 70 | 2026-10-16T13:18:11+00:00 | Vulnerability · Source |
| CVE-2024-14040 | suse_vex | SUSE CVE CVE-2024-14040 | known affected: 250 known not affected: 127 | 2026-10-16T13:18:07+00:00 | Vulnerability · Source |
| CVE-2024-20952 | suse_vex | SUSE CVE CVE-2024-20952 | known affected: 505 known not affected: 218 recommended: 840 | 2026-10-16T13:18:05+00:00 | Vulnerability · Source |
| CVE-2024-21247 | suse_vex | SUSE CVE CVE-2024-21247 | recommended: 25 | 2026-10-16T13:18:03+00:00 | Vulnerability · Source |
| CVE-2024-21806 | suse_vex | SUSE CVE CVE-2024-21806 | known not affected: 372 | 2026-10-16T13:18:00+00:00 | Vulnerability · Source |
| CVE-2024-21810 | suse_vex | SUSE CVE CVE-2024-21810 | known not affected: 372 | 2026-10-16T13:17:58+00:00 | Vulnerability · Source |
| CVE-2024-22195 | suse_vex | SUSE CVE CVE-2024-22195 | known affected: 448 recommended: 401 | 2026-10-16T13:17:55+00:00 | Vulnerability · Source |
| CVE-2024-23196 | suse_vex | SUSE CVE CVE-2024-23196 | known affected: 37 known not affected: 383 | 2026-10-16T13:17:53+00:00 | Vulnerability · Source |
| CVE-2024-23206 | suse_vex | SUSE CVE CVE-2024-23206 | known affected: 86 known not affected: 66 recommended: 659 | 2026-10-16T13:17:51+00:00 | Vulnerability · Source |
| CVE-2024-24783 | suse_vex | SUSE CVE CVE-2024-24783 | recommended: 251 | 2026-10-16T13:17:49+00:00 | Vulnerability · Source |
| CVE-2024-24785 | suse_vex | SUSE CVE CVE-2024-24785 | recommended: 244 | 2026-10-16T13:17:47+00:00 | Vulnerability · Source |
| CVE-2024-25131 | suse_vex | SUSE CVE CVE-2024-25131 | recommended: 4 | 2026-10-16T13:17:45+00:00 | Vulnerability · Source |
| CVE-2024-25132 | suse_vex | SUSE CVE CVE-2024-25132 | recommended: 5 | 2026-10-16T13:17:44+00:00 | Vulnerability · Source |
| CVE-2024-26464 | suse_vex | SUSE CVE CVE-2024-26464 | known not affected: 330 | 2026-10-16T13:17:41+00:00 | Vulnerability · Source |
| CVE-2024-26583 | suse_vex | SUSE CVE CVE-2024-26583 | known affected: 292 known not affected: 236 recommended: 939 | 2026-10-16T13:17:39+00:00 | Vulnerability · Source |
| CVE-2024-26601 | suse_vex | SUSE CVE CVE-2024-26601 | known affected: 355 known not affected: 300 recommended: 729 | 2026-10-16T13:17:36+00:00 | Vulnerability · Source |
| CVE-2024-26621 | suse_vex | SUSE CVE CVE-2024-26621 | known not affected: 362 | 2026-10-16T13:17:33+00:00 | Vulnerability · Source |
| CVE-2024-26623 | suse_vex | SUSE CVE CVE-2024-26623 | known affected: 394 known not affected: 425 recommended: 353 | 2026-10-16T13:17:31+00:00 | Vulnerability · Source |
| CVE-2024-26628 | suse_vex | SUSE CVE CVE-2024-26628 | known not affected: 41 | 2026-10-16T13:17:29+00:00 | Vulnerability · Source |
| CVE-2024-26630 | suse_vex | SUSE CVE CVE-2024-26630 | known not affected: 362 recommended: 58 | 2026-10-16T13:17:26+00:00 | Vulnerability · Source |
| CVE-2024-26638 | suse_vex | SUSE CVE CVE-2024-26638 | known not affected: 425 recommended: 373 | 2026-10-16T13:17:23+00:00 | Vulnerability · Source |
| 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-26922 | suse_vex | SUSE CVE CVE-2024-26922 | known affected: 569 known not affected: 14 recommended: 740 | 2026-10-16T13:16:29+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 |