VEX records
Browse vendor VEX statements available in this Vulnerability-Lookup instance and pivot to the related vulnerability.
306786 VEX records
API response| Vulnerability | Source | Title | Product status | Imported | Links |
|---|---|---|---|---|---|
| CVE-2024-27049 | suse_vex | SUSE CVE CVE-2024-27049 | known affected: 394 known not affected: 332 recommended: 413 | 2026-10-11T00:34:44+00:00 | Vulnerability · Source |
| CVE-2024-27054 | suse_vex | SUSE CVE CVE-2024-27054 | known affected: 540 known not affected: 69 recommended: 617 | 2026-10-11T00:34:41+00:00 | Vulnerability · Source |
| CVE-2024-27056 | suse_vex | SUSE CVE CVE-2024-27056 | known affected: 530 known not affected: 54 recommended: 691 | 2026-10-11T00:34:39+00:00 | Vulnerability · Source |
| CVE-2024-27057 | suse_vex | SUSE CVE CVE-2024-27057 | known affected: 394 known not affected: 332 recommended: 357 | 2026-10-11T00:34:37+00:00 | Vulnerability · Source |
| CVE-2024-27068 | suse_vex | SUSE CVE CVE-2024-27068 | known affected: 394 known not affected: 385 recommended: 209 | 2026-10-11T00:34:35+00:00 | Vulnerability · Source |
| CVE-2024-27071 | suse_vex | SUSE CVE CVE-2024-27071 | known affected: 394 known not affected: 385 recommended: 209 | 2026-10-11T00:34:32+00:00 | Vulnerability · Source |
| CVE-2024-27073 | suse_vex | SUSE CVE CVE-2024-27073 | known affected: 503 known not affected: 53 recommended: 606 | 2026-10-11T00:34:30+00:00 | Vulnerability · Source |
| CVE-2024-27080 | suse_vex | SUSE CVE CVE-2024-27080 | known affected: 394 known not affected: 332 recommended: 357 | 2026-10-11T00:34:28+00:00 | Vulnerability · Source |
| CVE-2024-27267 | suse_vex | SUSE CVE CVE-2024-27267 | known affected: 443 known not affected: 579 recommended: 125 | 2026-10-11T00:34:25+00:00 | Vulnerability · Source |
| CVE-2024-27306 | suse_vex | SUSE CVE CVE-2024-27306 | known affected: 406 recommended: 76 | 2026-10-11T00:34:23+00:00 | Vulnerability · Source |
| CVE-2024-27389 | suse_vex | SUSE CVE CVE-2024-27389 | known affected: 271 known not affected: 200 recommended: 819 | 2026-10-11T00:34:21+00:00 | Vulnerability · Source |
| CVE-2024-27393 | suse_vex | SUSE CVE CVE-2024-27393 | known affected: 569 known not affected: 37 recommended: 645 | 2026-10-11T00:34:19+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-11T00:34:17+00:00 | Vulnerability · Source |
| CVE-2024-27403 | suse_vex | SUSE CVE CVE-2024-27403 | known affected: 521 known not affected: 123 recommended: 701 | 2026-10-11T00:34:15+00:00 | Vulnerability · Source |
| CVE-2024-27407 | suse_vex | SUSE CVE CVE-2024-27407 | known affected: 394 known not affected: 374 recommended: 280 | 2026-10-11T00:34:14+00:00 | Vulnerability · Source |
| CVE-2024-27408 | suse_vex | SUSE CVE CVE-2024-27408 | known affected: 394 known not affected: 374 recommended: 353 | 2026-10-11T00:34:12+00:00 | Vulnerability · Source |
| CVE-2024-27412 | suse_vex | SUSE CVE CVE-2024-27412 | known affected: 315 known not affected: 213 recommended: 670 | 2026-10-11T00:34:09+00:00 | Vulnerability · Source |
| CVE-2024-27417 | suse_vex | SUSE CVE CVE-2024-27417 | known affected: 315 known not affected: 155 recommended: 724 | 2026-10-11T00:34:08+00:00 | Vulnerability · Source |
| CVE-2024-27419 | suse_vex | SUSE CVE CVE-2024-27419 | known affected: 315 recommended: 669 | 2026-10-11T00:34:06+00:00 | Vulnerability · Source |
| CVE-2024-27433 | suse_vex | SUSE CVE CVE-2024-27433 | known affected: 394 known not affected: 373 recommended: 355 | 2026-10-11T00:34:02+00:00 | Vulnerability · Source |
| CVE-2024-27437 | suse_vex | SUSE CVE CVE-2024-27437 | known affected: 476 known not affected: 6 recommended: 737 | 2026-10-11T00:34:00+00:00 | Vulnerability · Source |
| CVE-2024-27454 | suse_vex | SUSE CVE CVE-2024-27454 | recommended: 15 | 2026-10-11T00:33:58+00:00 | Vulnerability · Source |
| CVE-2024-28102 | suse_vex | SUSE CVE CVE-2024-28102 | recommended: 14 | 2026-10-11T00:33:55+00:00 | Vulnerability · Source |
| CVE-2024-28180 | suse_vex | SUSE CVE CVE-2024-28180 | known affected: 47 known not affected: 706 recommended: 284 | 2026-10-11T00:33:53+00:00 | Vulnerability · Source |
| CVE-2024-28397 | suse_vex | SUSE CVE CVE-2024-28397 | recommended: 12 | 2026-10-11T00:33:51+00:00 | Vulnerability · Source |
| CVE-2024-28834 | suse_vex | SUSE CVE CVE-2024-28834 | known affected: 260 known not affected: 266 recommended: 364 | 2026-10-11T00:33:48+00:00 | Vulnerability · Source |
| CVE-2024-28863 | suse_vex | SUSE CVE CVE-2024-28863 | recommended: 24 | 2026-10-11T00:33:46+00:00 | Vulnerability · Source |
| CVE-2024-28882 | suse_vex | SUSE CVE CVE-2024-28882 | known affected: 71 recommended: 63 | 2026-10-11T00:33:44+00:00 | Vulnerability · Source |
| CVE-2024-28892 | suse_vex | SUSE CVE CVE-2024-28892 | recommended: 4 | 2026-10-11T00:33:42+00:00 | Vulnerability · Source |
| CVE-2024-28956 | suse_vex | SUSE CVE CVE-2024-28956 | known affected: 630 recommended: 952 | 2026-10-11T00:33:40+00:00 | Vulnerability · Source |
| CVE-2024-29039 | suse_vex | SUSE CVE CVE-2024-29039 | known affected: 347 known not affected: 9 recommended: 125 | 2026-10-11T00:33:38+00:00 | Vulnerability · Source |
| CVE-2024-29508 | suse_vex | SUSE CVE CVE-2024-29508 | known affected: 111 recommended: 66 | 2026-10-11T00:33:34+00:00 | Vulnerability · Source |
| CVE-2024-29511 | suse_vex | SUSE CVE CVE-2024-29511 | known not affected: 144 | 2026-10-11T00:33:32+00:00 | Vulnerability · Source |
| CVE-2024-29857 | suse_vex | SUSE CVE CVE-2024-29857 | known not affected: 121 recommended: 50 | 2026-10-11T00:33:30+00:00 | Vulnerability · Source |
| CVE-2024-30045 | suse_vex | SUSE CVE CVE-2024-30045 | recommended: 70 | 2026-10-11T00:33:29+00:00 | Vulnerability · Source |
| CVE-2024-30105 | suse_vex | SUSE CVE CVE-2024-30105 | recommended: 43 | 2026-10-11T00:33:27+00:00 | Vulnerability · Source |
| CVE-2024-30171 | suse_vex | SUSE CVE CVE-2024-30171 | recommended: 152 | 2026-10-11T00:33:24+00:00 | Vulnerability · Source |
| CVE-2024-30203 | suse_vex | SUSE CVE CVE-2024-30203 | known affected: 142 recommended: 172 | 2026-10-11T00:33:23+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-11T00:33:21+00:00 | Vulnerability · Source |
| CVE-2024-32040 | suse_vex | SUSE CVE CVE-2024-32040 | known not affected: 48 recommended: 155 | 2026-10-11T00:33:19+00:00 | Vulnerability · Source |
| CVE-2024-32460 | suse_vex | SUSE CVE CVE-2024-32460 | known not affected: 48 recommended: 155 | 2026-10-11T00:33:17+00:00 | Vulnerability · Source |
| CVE-2024-32487 | suse_vex | SUSE CVE CVE-2024-32487 | known affected: 274 recommended: 190 | 2026-10-11T00:33:15+00:00 | Vulnerability · Source |
| CVE-2024-32659 | suse_vex | SUSE CVE CVE-2024-32659 | recommended: 204 | 2026-10-11T00:33:13+00:00 | Vulnerability · Source |
| CVE-2024-32662 | suse_vex | SUSE CVE CVE-2024-32662 | known not affected: 116 recommended: 10 | 2026-10-11T00:33:12+00:00 | Vulnerability · Source |
| CVE-2024-33427 | suse_vex | SUSE CVE CVE-2024-33427 | known affected: 427 recommended: 27 | 2026-10-11T00:33:09+00:00 | Vulnerability · Source |
| CVE-2024-33599 | suse_vex | SUSE CVE CVE-2024-33599 | known affected: 264 known not affected: 252 recommended: 1404 | 2026-10-11T00:33:07+00:00 | Vulnerability · Source |
| CVE-2024-33601 | suse_vex | SUSE CVE CVE-2024-33601 | known affected: 337 known not affected: 75 recommended: 1404 | 2026-10-11T00:33:05+00:00 | Vulnerability · Source |
| CVE-2024-33602 | suse_vex | SUSE CVE CVE-2024-33602 | known affected: 441 known not affected: 75 recommended: 1404 | 2026-10-11T00:33:03+00:00 | Vulnerability · Source |
| CVE-2024-33662 | suse_vex | SUSE CVE CVE-2024-33662 | recommended: 4 | 2026-10-11T00:33:01+00:00 | Vulnerability · Source |
| CVE-2024-33847 | suse_vex | SUSE CVE CVE-2024-33847 | known not affected: 568 | 2026-10-11T00:32:59+00:00 | Vulnerability · Source |