VEX records
Browse vendor VEX statements available in this Vulnerability-Lookup instance and pivot to the related vulnerability.
292098 VEX records
API response| Vulnerability | Source | Title | Product status | Imported | Links |
|---|---|---|---|---|---|
| CVE-2024-29510 | suse_vex | SUSE CVE CVE-2024-29510 | known affected: 23 recommended: 133 | 2026-07-25T01:52:19+00:00 | Vulnerability · Source |
| CVE-2024-30203 | suse_vex | SUSE CVE CVE-2024-30203 | known affected: 128 recommended: 179 | 2026-07-25T01:52:16+00:00 | Vulnerability · Source |
| CVE-2024-31142 | suse_vex | SUSE CVE CVE-2024-31142 | known affected: 389 known not affected: 36 recommended: 272 | 2026-07-25T01:52:14+00:00 | Vulnerability · Source |
| CVE-2024-31949 | suse_vex | SUSE CVE CVE-2024-31949 | known not affected: 403 | 2026-07-25T01:52:11+00:00 | Vulnerability · Source |
| CVE-2024-31951 | suse_vex | SUSE CVE CVE-2024-31951 | known not affected: 405 recommended: 175 | 2026-07-25T01:52:09+00:00 | Vulnerability · Source |
| CVE-2024-32004 | suse_vex | SUSE CVE CVE-2024-32004 | known affected: 151 known not affected: 119 recommended: 472 | 2026-07-25T01:52:06+00:00 | Vulnerability · Source |
| CVE-2024-32021 | suse_vex | SUSE CVE CVE-2024-32021 | known affected: 151 known not affected: 119 recommended: 472 | 2026-07-25T01:52:04+00:00 | Vulnerability · Source |
| CVE-2024-32936 | suse_vex | SUSE CVE CVE-2024-32936 | known not affected: 318 | 2026-07-25T01:51:58+00:00 | Vulnerability · Source |
| CVE-2024-33427 | suse_vex | SUSE CVE CVE-2024-33427 | known affected: 418 recommended: 28 | 2026-07-25T01:51:55+00:00 | Vulnerability · Source |
| CVE-2024-35176 | suse_vex | SUSE CVE CVE-2024-35176 | known affected: 428 known not affected: 117 recommended: 202 | 2026-07-25T01:51:38+00:00 | Vulnerability · Source |
| CVE-2024-35367 | suse_vex | SUSE CVE CVE-2024-35367 | known affected: 466 known not affected: 158 | 2026-07-25T01:51:37+00:00 | Vulnerability · Source |
| CVE-2024-35793 | suse_vex | SUSE CVE CVE-2024-35793 | known not affected: 330 | 2026-07-25T01:51:28+00:00 | Vulnerability · Source |
| CVE-2024-35798 | suse_vex | SUSE CVE CVE-2024-35798 | known not affected: 330 | 2026-07-25T01:51:22+00:00 | Vulnerability · Source |
| CVE-2024-35816 | suse_vex | SUSE CVE CVE-2024-35816 | known not affected: 330 | 2026-07-25T01:51:16+00:00 | Vulnerability · Source |
| CVE-2024-35818 | suse_vex | SUSE CVE CVE-2024-35818 | known not affected: 330 | 2026-07-25T01:51:15+00:00 | Vulnerability · Source |
| CVE-2024-35826 | suse_vex | SUSE CVE CVE-2024-35826 | known affected: 394 known not affected: 270 recommended: 309 | 2026-07-25T01:51:13+00:00 | Vulnerability · Source |
| CVE-2024-35859 | suse_vex | SUSE CVE CVE-2024-35859 | known not affected: 330 | 2026-07-25T01:51:03+00:00 | Vulnerability · Source |
| CVE-2024-35866 | suse_vex | SUSE CVE CVE-2024-35866 | known affected: 446 known not affected: 111 recommended: 671 | 2026-07-25T01:50:56+00:00 | Vulnerability · Source |
| CVE-2024-35873 | suse_vex | SUSE CVE CVE-2024-35873 | known not affected: 330 | 2026-07-25T01:50:51+00:00 | Vulnerability · Source |
| CVE-2024-35875 | suse_vex | SUSE CVE CVE-2024-35875 | known affected: 362 known not affected: 157 recommended: 704 | 2026-07-25T01:50:49+00:00 | Vulnerability · Source |
| CVE-2024-35883 | suse_vex | SUSE CVE CVE-2024-35883 | known affected: 394 known not affected: 270 recommended: 362 | 2026-07-25T01:50:44+00:00 | Vulnerability · Source |
| CVE-2024-35893 | suse_vex | SUSE CVE CVE-2024-35893 | known affected: 526 known not affected: 10 recommended: 746 | 2026-07-25T01:50:39+00:00 | Vulnerability · Source |
| CVE-2024-35904 | suse_vex | SUSE CVE CVE-2024-35904 | known affected: 334 known not affected: 98 recommended: 814 | 2026-07-25T01:50:36+00:00 | Vulnerability · Source |
| CVE-2024-35906 | suse_vex | SUSE CVE CVE-2024-35906 | known not affected: 60 | 2026-07-25T01:50:34+00:00 | Vulnerability · Source |
| CVE-2024-35910 | suse_vex | SUSE CVE CVE-2024-35910 | known affected: 714 known not affected: 6 recommended: 402 | 2026-07-25T01:50:31+00:00 | Vulnerability · Source |
| CVE-2024-35912 | suse_vex | SUSE CVE CVE-2024-35912 | known affected: 315 known not affected: 181 recommended: 695 | 2026-07-25T01:50:29+00:00 | Vulnerability · Source |
| CVE-2024-35926 | suse_vex | SUSE CVE CVE-2024-35926 | known affected: 421 known not affected: 312 recommended: 358 | 2026-07-25T01:50:18+00:00 | Vulnerability · Source |
| CVE-2024-35929 | suse_vex | SUSE CVE CVE-2024-35929 | known not affected: 330 | 2026-07-25T01:50:16+00:00 | Vulnerability · Source |
| CVE-2024-35931 | suse_vex | SUSE CVE CVE-2024-35931 | known affected: 532 known not affected: 187 recommended: 358 | 2026-07-25T01:50:13+00:00 | Vulnerability · Source |
| CVE-2024-35945 | suse_vex | SUSE CVE CVE-2024-35945 | known affected: 367 known not affected: 111 recommended: 650 | 2026-07-25T01:49:57+00:00 | Vulnerability · Source |
| CVE-2024-35947 | suse_vex | SUSE CVE CVE-2024-35947 | known affected: 425 known not affected: 6 recommended: 779 | 2026-07-25T01:49:54+00:00 | Vulnerability · Source |
| CVE-2024-35948 | suse_vex | SUSE CVE CVE-2024-35948 | known not affected: 330 | 2026-07-25T01:49:52+00:00 | Vulnerability · Source |
| CVE-2024-35952 | suse_vex | SUSE CVE CVE-2024-35952 | known affected: 362 known not affected: 157 recommended: 724 | 2026-07-25T01:49:46+00:00 | Vulnerability · Source |
| CVE-2024-35970 | suse_vex | SUSE CVE CVE-2024-35970 | known affected: 27 known not affected: 311 recommended: 358 | 2026-07-25T01:49:41+00:00 | Vulnerability · Source |
| CVE-2024-35996 | suse_vex | SUSE CVE CVE-2024-35996 | known not affected: 330 | 2026-07-25T01:49:22+00:00 | Vulnerability · Source |
| CVE-2024-35997 | suse_vex | SUSE CVE CVE-2024-35997 | known affected: 440 known not affected: 6 recommended: 744 | 2026-07-25T01:49:20+00:00 | Vulnerability · Source |
| CVE-2024-36001 | suse_vex | SUSE CVE CVE-2024-36001 | known not affected: 330 | 2026-07-25T01:49:17+00:00 | Vulnerability · Source |
| CVE-2024-36013 | suse_vex | SUSE CVE CVE-2024-36013 | known affected: 546 recommended: 773 | 2026-07-25T01:49:07+00:00 | Vulnerability · Source |
| CVE-2024-36014 | suse_vex | SUSE CVE CVE-2024-36014 | known affected: 477 known not affected: 64 recommended: 745 | 2026-07-25T01:49:05+00:00 | Vulnerability · Source |
| CVE-2024-36019 | suse_vex | SUSE CVE CVE-2024-36019 | known affected: 394 known not affected: 270 recommended: 391 | 2026-07-25T01:49:02+00:00 | Vulnerability · Source |
| CVE-2024-36028 | suse_vex | SUSE CVE CVE-2024-36028 | known affected: 394 known not affected: 381 recommended: 354 | 2026-07-25T01:49:00+00:00 | Vulnerability · Source |
| CVE-2024-36031 | suse_vex | SUSE CVE CVE-2024-36031 | known affected: 394 known not affected: 270 recommended: 310 | 2026-07-25T01:48:57+00:00 | Vulnerability · Source |
| CVE-2024-36387 | suse_vex | SUSE CVE CVE-2024-36387 | known affected: 400 known not affected: 211 recommended: 68 | 2026-07-25T01:48:44+00:00 | Vulnerability · Source |
| CVE-2024-36460 | suse_vex | SUSE CVE CVE-2024-36460 | known not affected: 11 | 2026-07-25T01:48:42+00:00 | Vulnerability · Source |
| CVE-2024-36464 | suse_vex | SUSE CVE CVE-2024-36464 | known not affected: 12 | 2026-07-25T01:48:40+00:00 | Vulnerability · Source |
| CVE-2024-36474 | suse_vex | SUSE CVE CVE-2024-36474 | known affected: 30 recommended: 94 | 2026-07-25T01:48:37+00:00 | Vulnerability · Source |
| CVE-2024-36484 | suse_vex | SUSE CVE CVE-2024-36484 | known affected: 354 known not affected: 196 recommended: 619 | 2026-07-25T01:48:32+00:00 | Vulnerability · Source |
| CVE-2024-36883 | suse_vex | SUSE CVE CVE-2024-36883 | known affected: 612 known not affected: 56 recommended: 668 | 2026-07-25T01:48:25+00:00 | Vulnerability · Source |
| CVE-2024-36890 | suse_vex | SUSE CVE CVE-2024-36890 | known affected: 330 known not affected: 211 recommended: 656 | 2026-07-25T01:48:22+00:00 | Vulnerability · Source |
| CVE-2024-36891 | suse_vex | SUSE CVE CVE-2024-36891 | known affected: 394 known not affected: 270 recommended: 362 | 2026-07-25T01:48:20+00:00 | Vulnerability · Source |