VEX records
Browse vendor VEX statements available in this Vulnerability-Lookup instance and pivot to the related vulnerability.
291925 VEX records
API response| Vulnerability | Source | Title | Product status | Imported | Links |
|---|---|---|---|---|---|
| CVE-2024-42264 | suse_vex | SUSE CVE CVE-2024-42264 | known not affected: 310 recommended: 59 | 2026-08-05T00:54:25+00:00 | Vulnerability · Source |
| CVE-2024-42272 | suse_vex | SUSE CVE CVE-2024-42272 | known not affected: 311 recommended: 29 | 2026-08-05T00:54:23+00:00 | Vulnerability · Source |
| CVE-2024-42288 | suse_vex | SUSE CVE CVE-2024-42288 | known affected: 420 known not affected: 30 recommended: 718 | 2026-08-05T00:54:14+00:00 | Vulnerability · Source |
| CVE-2024-42296 | suse_vex | SUSE CVE CVE-2024-42296 | known not affected: 514 | 2026-08-05T00:54:13+00:00 | Vulnerability · Source |
| CVE-2024-42300 | suse_vex | SUSE CVE CVE-2024-42300 | known not affected: 310 | 2026-08-05T00:54:11+00:00 | Vulnerability · Source |
| CVE-2024-42313 | suse_vex | SUSE CVE CVE-2024-42313 | known affected: 389 known not affected: 86 recommended: 648 | 2026-08-05T00:54:06+00:00 | Vulnerability · Source |
| CVE-2024-43848 | suse_vex | SUSE CVE CVE-2024-43848 | known not affected: 310 recommended: 59 | 2026-08-05T00:53:56+00:00 | Vulnerability · Source |
| CVE-2024-43881 | suse_vex | SUSE CVE CVE-2024-43881 | known affected: 394 known not affected: 254 recommended: 360 | 2026-08-05T00:53:48+00:00 | Vulnerability · Source |
| CVE-2024-43891 | suse_vex | SUSE CVE CVE-2024-43891 | known not affected: 311 | 2026-08-05T00:53:45+00:00 | Vulnerability · Source |
| CVE-2024-44933 | suse_vex | SUSE CVE CVE-2024-44933 | known not affected: 310 recommended: 59 | 2026-08-05T00:53:41+00:00 | Vulnerability · Source |
| CVE-2024-44966 | suse_vex | SUSE CVE CVE-2024-44966 | known not affected: 324 | 2026-08-05T00:53:32+00:00 | Vulnerability · Source |
| CVE-2024-45030 | suse_vex | SUSE CVE CVE-2024-45030 | known affected: 394 known not affected: 353 recommended: 357 | 2026-08-05T00:53:09+00:00 | Vulnerability · Source |
| CVE-2024-46705 | suse_vex | SUSE CVE CVE-2024-46705 | known not affected: 325 recommended: 59 | 2026-08-05T00:52:58+00:00 | Vulnerability · Source |
| CVE-2024-46709 | suse_vex | SUSE CVE CVE-2024-46709 | known affected: 394 known not affected: 354 recommended: 357 | 2026-08-05T00:52:56+00:00 | Vulnerability · Source |
| CVE-2024-46737 | suse_vex | SUSE CVE CVE-2024-46737 | known affected: 489 known not affected: 86 recommended: 715 | 2026-08-05T00:52:49+00:00 | Vulnerability · Source |
| CVE-2024-46751 | suse_vex | SUSE CVE CVE-2024-46751 | known affected: 588 known not affected: 32 recommended: 682 | 2026-08-05T00:52:41+00:00 | Vulnerability · Source |
| CVE-2024-46762 | suse_vex | SUSE CVE CVE-2024-46762 | known not affected: 325 | 2026-08-05T00:52:38+00:00 | Vulnerability · Source |
| CVE-2024-46799 | suse_vex | SUSE CVE CVE-2024-46799 | known not affected: 325 | 2026-08-05T00:52:31+00:00 | Vulnerability · Source |
| CVE-2024-46844 | suse_vex | SUSE CVE CVE-2024-46844 | known not affected: 518 | 2026-08-05T00:52:22+00:00 | Vulnerability · Source |
| CVE-2024-46850 | suse_vex | SUSE CVE CVE-2024-46850 | known not affected: 325 recommended: 59 | 2026-08-05T00:52:20+00:00 | Vulnerability · Source |
| CVE-2024-46862 | suse_vex | SUSE CVE CVE-2024-46862 | known not affected: 324 recommended: 59 | 2026-08-05T00:52:17+00:00 | Vulnerability · Source |
| CVE-2024-46869 | suse_vex | SUSE CVE CVE-2024-46869 | known not affected: 325 recommended: 65 | 2026-08-05T00:52:15+00:00 | Vulnerability · Source |
| CVE-2024-47659 | suse_vex | SUSE CVE CVE-2024-47659 | known not affected: 381 | 2026-08-05T00:52:12+00:00 | Vulnerability · Source |
| CVE-2024-47690 | suse_vex | SUSE CVE CVE-2024-47690 | known not affected: 402 recommended: 6 | 2026-08-05T00:52:07+00:00 | Vulnerability · Source |
| CVE-2024-47711 | suse_vex | SUSE CVE CVE-2024-47711 | known not affected: 402 recommended: 6 | 2026-08-05T00:52:02+00:00 | Vulnerability · Source |
| CVE-2024-47740 | suse_vex | SUSE CVE CVE-2024-47740 | known not affected: 402 recommended: 6 | 2026-08-05T00:51:57+00:00 | Vulnerability · Source |
| CVE-2024-49859 | suse_vex | SUSE CVE CVE-2024-49859 | known not affected: 379 recommended: 6 | 2026-08-05T00:51:49+00:00 | Vulnerability · Source |
| CVE-2024-49956 | suse_vex | SUSE CVE CVE-2024-49956 | known not affected: 379 recommended: 6 | 2026-08-05T00:51:37+00:00 | Vulnerability · Source |
| CVE-2024-49999 | suse_vex | SUSE CVE CVE-2024-49999 | known not affected: 379 recommended: 49 | 2026-08-05T00:51:30+00:00 | Vulnerability · Source |
| CVE-2024-50043 | suse_vex | SUSE CVE CVE-2024-50043 | known not affected: 379 recommended: 6 | 2026-08-05T00:51:24+00:00 | Vulnerability · Source |
| CVE-2024-50066 | suse_vex | SUSE CVE CVE-2024-50066 | known not affected: 399 recommended: 6 | 2026-08-05T00:51:19+00:00 | Vulnerability · Source |
| CVE-2024-50086 | suse_vex | SUSE CVE CVE-2024-50086 | known not affected: 402 recommended: 6 | 2026-08-05T00:51:14+00:00 | Vulnerability · Source |
| CVE-2024-50106 | suse_vex | SUSE CVE CVE-2024-50106 | known affected: 744 known not affected: 36 recommended: 455 | 2026-08-05T00:51:09+00:00 | Vulnerability · Source |
| CVE-2024-50149 | suse_vex | SUSE CVE CVE-2024-50149 | known not affected: 378 recommended: 65 | 2026-08-05T00:51:01+00:00 | Vulnerability · Source |
| CVE-2024-50161 | suse_vex | SUSE CVE CVE-2024-50161 | known not affected: 378 recommended: 6 | 2026-08-05T00:50:58+00:00 | Vulnerability · Source |
| CVE-2024-50165 | suse_vex | SUSE CVE CVE-2024-50165 | known not affected: 378 recommended: 6 | 2026-08-05T00:50:56+00:00 | Vulnerability · Source |
| CVE-2024-50174 | suse_vex | SUSE CVE CVE-2024-50174 | known not affected: 378 recommended: 65 | 2026-08-05T00:50:54+00:00 | Vulnerability · Source |
| CVE-2024-50207 | suse_vex | SUSE CVE CVE-2024-50207 | known not affected: 378 recommended: 6 | 2026-08-05T00:50:48+00:00 | Vulnerability · Source |
| CVE-2024-50297 | suse_vex | SUSE CVE CVE-2024-50297 | known not affected: 372 | 2026-08-05T00:50:33+00:00 | Vulnerability · Source |
| CVE-2024-51729 | suse_vex | SUSE CVE CVE-2024-51729 | known not affected: 346 recommended: 53 | 2026-08-05T00:50:30+00:00 | Vulnerability · Source |
| CVE-2024-53080 | suse_vex | SUSE CVE CVE-2024-53080 | known not affected: 372 recommended: 59 | 2026-08-05T00:50:23+00:00 | Vulnerability · Source |
| CVE-2024-53090 | suse_vex | SUSE CVE CVE-2024-53090 | known affected: 620 known not affected: 76 recommended: 461 | 2026-08-05T00:50:21+00:00 | Vulnerability · Source |
| CVE-2024-53093 | suse_vex | SUSE CVE CVE-2024-53093 | known affected: 621 known not affected: 51 recommended: 512 | 2026-08-05T00:50:18+00:00 | Vulnerability · Source |
| CVE-2024-53127 | suse_vex | SUSE CVE CVE-2024-53127 | known affected: 364 known not affected: 285 recommended: 411 | 2026-08-05T00:50:09+00:00 | Vulnerability · Source |
| CVE-2024-53128 | suse_vex | SUSE CVE CVE-2024-53128 | known not affected: 438 | 2026-08-05T00:50:07+00:00 | Vulnerability · Source |
| CVE-2024-53147 | suse_vex | SUSE CVE CVE-2024-53147 | known affected: 678 known not affected: 95 recommended: 405 | 2026-08-05T00:50:02+00:00 | Vulnerability · Source |
| CVE-2024-53220 | suse_vex | SUSE CVE CVE-2024-53220 | known affected: 133 known not affected: 304 | 2026-08-05T00:49:42+00:00 | Vulnerability · Source |
| CVE-2024-56554 | suse_vex | SUSE CVE CVE-2024-56554 | known not affected: 438 | 2026-08-05T00:49:30+00:00 | Vulnerability · Source |
| CVE-2024-56556 | suse_vex | SUSE CVE CVE-2024-56556 | known not affected: 438 | 2026-08-05T00:49:29+00:00 | Vulnerability · Source |
| CVE-2024-56692 | suse_vex | SUSE CVE CVE-2024-56692 | known not affected: 425 | 2026-08-05T00:48:58+00:00 | Vulnerability · Source |