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-25081 | suse_vex | SUSE CVE CVE-2024-25081 | recommended: 50 | 2026-10-16T02:19:47+00:00 | Vulnerability · Source |
| CVE-2024-25082 | suse_vex | SUSE CVE CVE-2024-25082 | recommended: 47 | 2026-10-16T02:19:45+00:00 | Vulnerability · Source |
| CVE-2024-25111 | suse_vex | SUSE CVE CVE-2024-25111 | known affected: 403 known not affected: 16 recommended: 36 | 2026-10-16T02:19:43+00:00 | Vulnerability · Source |
| CVE-2024-25133 | suse_vex | SUSE CVE CVE-2024-25133 | recommended: 5 | 2026-10-16T02:19:41+00:00 | Vulnerability · Source |
| CVE-2024-25260 | suse_vex | SUSE CVE CVE-2024-25260 | known affected: 9 known not affected: 781 | 2026-10-16T02:19:39+00:00 | Vulnerability · Source |
| CVE-2024-25581 | suse_vex | SUSE CVE CVE-2024-25581 | known not affected: 33 recommended: 8 | 2026-10-16T02:19:37+00:00 | Vulnerability · Source |
| CVE-2024-25621 | suse_vex | SUSE CVE CVE-2024-25621 | known affected: 378 recommended: 132 | 2026-10-16T02:19:35+00:00 | Vulnerability · Source |
| CVE-2024-25629 | suse_vex | SUSE CVE CVE-2024-25629 | known affected: 326 recommended: 268 | 2026-10-16T02:19:33+00:00 | Vulnerability · Source |
| CVE-2024-25710 | suse_vex | SUSE CVE CVE-2024-25710 | known affected: 395 recommended: 1117 | 2026-10-16T02:19:31+00:00 | Vulnerability · Source |
| CVE-2024-25739 | suse_vex | SUSE CVE CVE-2024-25739 | known affected: 305 known not affected: 273 recommended: 697 | 2026-10-16T02:19:29+00:00 | Vulnerability · Source |
| CVE-2024-25741 | suse_vex | SUSE CVE CVE-2024-25741 | known affected: 370 known not affected: 205 recommended: 651 | 2026-10-16T02:19:27+00:00 | Vulnerability · Source |
| CVE-2024-25742 | suse_vex | SUSE CVE CVE-2024-25742 | known affected: 260 known not affected: 310 recommended: 582 | 2026-10-16T02:19:25+00:00 | Vulnerability · Source |
| CVE-2024-25939 | suse_vex | SUSE CVE CVE-2024-25939 | known affected: 17 recommended: 48 | 2026-10-16T02:19:24+00:00 | Vulnerability · Source |
| CVE-2024-26134 | suse_vex | SUSE CVE CVE-2024-26134 | recommended: 7 | 2026-10-16T02:19:22+00:00 | Vulnerability · Source |
| CVE-2024-26256 | suse_vex | SUSE CVE CVE-2024-26256 | known not affected: 167 recommended: 27 | 2026-10-16T02:19:20+00:00 | Vulnerability · Source |
| CVE-2024-26306 | suse_vex | SUSE CVE CVE-2024-26306 | recommended: 34 | 2026-10-16T02:19:18+00:00 | Vulnerability · Source |
| CVE-2024-26328 | suse_vex | SUSE CVE CVE-2024-26328 | known affected: 394 known not affected: 1316 recommended: 684 | 2026-10-16T02:19:16+00:00 | Vulnerability · Source |
| CVE-2024-26584 | suse_vex | SUSE CVE CVE-2024-26584 | known affected: 312 known not affected: 160 recommended: 1150 | 2026-10-16T02:19:14+00:00 | Vulnerability · Source |
| CVE-2024-26585 | suse_vex | SUSE CVE CVE-2024-26585 | known affected: 249 known not affected: 219 recommended: 1121 | 2026-10-16T02:19:12+00:00 | Vulnerability · Source |
| CVE-2024-26586 | suse_vex | SUSE CVE CVE-2024-26586 | known affected: 249 known not affected: 236 recommended: 932 | 2026-10-16T02:19:10+00:00 | Vulnerability · Source |
| CVE-2024-26588 | suse_vex | SUSE CVE CVE-2024-26588 | known not affected: 312 | 2026-10-16T02:19:08+00:00 | Vulnerability · Source |
| CVE-2024-26589 | suse_vex | SUSE CVE CVE-2024-26589 | known affected: 249 known not affected: 236 recommended: 831 | 2026-10-16T02:19:06+00:00 | Vulnerability · Source |
| CVE-2024-26591 | suse_vex | SUSE CVE CVE-2024-26591 | known affected: 255 known not affected: 270 recommended: 679 | 2026-10-16T02:19:04+00:00 | Vulnerability · Source |
| CVE-2024-26592 | suse_vex | SUSE CVE CVE-2024-26592 | known not affected: 312 | 2026-10-16T02:19:02+00:00 | Vulnerability · Source |
| CVE-2024-26596 | suse_vex | SUSE CVE CVE-2024-26596 | known affected: 394 known not affected: 375 recommended: 280 | 2026-10-16T02:19:00+00:00 | Vulnerability · Source |
| CVE-2024-26599 | suse_vex | SUSE CVE CVE-2024-26599 | known affected: 305 known not affected: 334 recommended: 528 | 2026-10-16T02:18:59+00:00 | Vulnerability · Source |
| CVE-2024-26600 | suse_vex | SUSE CVE CVE-2024-26600 | known affected: 376 known not affected: 59 recommended: 986 | 2026-10-16T02:18:57+00:00 | Vulnerability · Source |
| CVE-2024-26603 | suse_vex | SUSE CVE CVE-2024-26603 | known affected: 255 known not affected: 302 recommended: 699 | 2026-10-16T02:18:55+00:00 | Vulnerability · Source |
| CVE-2024-26608 | suse_vex | SUSE CVE CVE-2024-26608 | known not affected: 436 | 2026-10-16T02:18:53+00:00 | Vulnerability · Source |
| CVE-2024-26609 | suse_vex | SUSE CVE CVE-2024-26609 | known not affected: 436 recommended: 78 | 2026-10-16T02:18:51+00:00 | Vulnerability · Source |
| CVE-2024-26610 | suse_vex | SUSE CVE CVE-2024-26610 | known affected: 259 known not affected: 260 recommended: 885 | 2026-10-16T02:18:49+00:00 | Vulnerability · Source |
| CVE-2024-26611 | suse_vex | SUSE CVE CVE-2024-26611 | known affected: 394 known not affected: 425 recommended: 357 | 2026-10-16T02:18:48+00:00 | Vulnerability · Source |
| CVE-2024-26612 | suse_vex | SUSE CVE CVE-2024-26612 | known affected: 305 known not affected: 321 recommended: 528 | 2026-10-16T02:18:46+00:00 | Vulnerability · Source |
| CVE-2024-26613 | suse_vex | SUSE CVE CVE-2024-26613 | known not affected: 362 | 2026-10-16T02:18:44+00:00 | Vulnerability · Source |
| CVE-2024-26614 | suse_vex | SUSE CVE CVE-2024-26614 | known affected: 393 recommended: 1076 | 2026-10-16T02:18:42+00:00 | Vulnerability · Source |
| CVE-2024-26617 | suse_vex | SUSE CVE CVE-2024-26617 | known not affected: 292 | 2026-10-16T02:18:40+00:00 | Vulnerability · Source |
| CVE-2024-26618 | suse_vex | SUSE CVE CVE-2024-26618 | known not affected: 362 recommended: 202 | 2026-10-16T02:18:38+00:00 | Vulnerability · Source |
| CVE-2024-26620 | suse_vex | SUSE CVE CVE-2024-26620 | known affected: 305 known not affected: 321 recommended: 528 | 2026-10-16T02:18:36+00:00 | Vulnerability · Source |
| CVE-2024-26625 | suse_vex | SUSE CVE CVE-2024-26625 | known affected: 728 recommended: 671 | 2026-10-16T02:18:34+00:00 | Vulnerability · Source |
| CVE-2024-26627 | suse_vex | SUSE CVE CVE-2024-26627 | known affected: 425 known not affected: 223 recommended: 528 | 2026-10-16T02:18:32+00:00 | Vulnerability · Source |
| CVE-2024-26629 | suse_vex | SUSE CVE CVE-2024-26629 | known affected: 343 known not affected: 324 recommended: 586 | 2026-10-16T02:18:30+00:00 | Vulnerability · Source |
| CVE-2024-26632 | suse_vex | SUSE CVE CVE-2024-26632 | known affected: 394 known not affected: 425 recommended: 353 | 2026-10-16T02:18:29+00:00 | Vulnerability · Source |
| CVE-2024-26633 | suse_vex | SUSE CVE CVE-2024-26633 | known affected: 524 recommended: 793 | 2026-10-16T02:18:27+00:00 | Vulnerability · Source |
| CVE-2024-26635 | suse_vex | SUSE CVE CVE-2024-26635 | known affected: 634 known not affected: 6 recommended: 735 | 2026-10-16T02:18:24+00:00 | Vulnerability · Source |
| CVE-2024-26639 | suse_vex | SUSE CVE CVE-2024-26639 | known not affected: 292 | 2026-10-16T02:18:20+00:00 | Vulnerability · Source |
| CVE-2024-26641 | suse_vex | SUSE CVE CVE-2024-26641 | known affected: 625 known not affected: 74 recommended: 721 | 2026-10-16T02:18:18+00:00 | Vulnerability · Source |
| CVE-2024-26643 | suse_vex | SUSE CVE CVE-2024-26643 | known affected: 361 known not affected: 199 recommended: 1002 | 2026-10-16T02:18:14+00:00 | Vulnerability · Source |
| CVE-2024-26644 | suse_vex | SUSE CVE CVE-2024-26644 | known affected: 330 known not affected: 374 recommended: 540 | 2026-10-16T02:18:11+00:00 | Vulnerability · Source |
| CVE-2024-26645 | suse_vex | SUSE CVE CVE-2024-26645 | known affected: 425 known not affected: 223 recommended: 548 | 2026-10-16T02:18:09+00:00 | Vulnerability · Source |
| CVE-2024-26648 | suse_vex | SUSE CVE CVE-2024-26648 | known not affected: 362 recommended: 202 | 2026-10-16T02:18:07+00:00 | Vulnerability · Source |