VEX records
Browse vendor VEX statements available in this Vulnerability-Lookup instance and pivot to the related vulnerability.
291904 VEX records
API response| Vulnerability | Source | Title | Product status | Imported | Links |
|---|---|---|---|---|---|
| CVE-2024-40989 | suse_vex | SUSE CVE CVE-2024-40989 | known affected: 295 known not affected: 169 recommended: 806 | 2026-08-05T00:55:50+00:00 | Vulnerability · Source |
| CVE-2024-40991 | suse_vex | SUSE CVE CVE-2024-40991 | known not affected: 318 | 2026-08-05T00:55:48+00:00 | Vulnerability · Source |
| CVE-2024-41008 | suse_vex | SUSE CVE CVE-2024-41008 | recommended: 79 | 2026-08-05T00:55:46+00:00 | Vulnerability · Source |
| CVE-2024-41018 | suse_vex | SUSE CVE CVE-2024-41018 | known not affected: 324 | 2026-08-05T00:55:38+00:00 | Vulnerability · Source |
| CVE-2024-41038 | suse_vex | SUSE CVE CVE-2024-41038 | known affected: 387 known not affected: 151 recommended: 668 | 2026-08-05T00:55:31+00:00 | Vulnerability · Source |
| CVE-2024-41056 | suse_vex | SUSE CVE CVE-2024-41056 | known affected: 401 known not affected: 181 recommended: 668 | 2026-08-05T00:55:24+00:00 | Vulnerability · Source |
| CVE-2024-41073 | suse_vex | SUSE CVE CVE-2024-41073 | known affected: 534 known not affected: 6 recommended: 781 | 2026-08-05T00:55:18+00:00 | Vulnerability · Source |
| CVE-2024-41075 | suse_vex | SUSE CVE CVE-2024-41075 | known affected: 394 known not affected: 261 recommended: 360 | 2026-08-05T00:55:16+00:00 | Vulnerability · Source |
| CVE-2024-41086 | suse_vex | SUSE CVE CVE-2024-41086 | known not affected: 324 | 2026-08-05T00:55:13+00:00 | Vulnerability · Source |
| CVE-2024-42067 | suse_vex | SUSE CVE CVE-2024-42067 | known not affected: 324 | 2026-08-05T00:55:07+00:00 | Vulnerability · Source |
| CVE-2024-42104 | suse_vex | SUSE CVE CVE-2024-42104 | known affected: 501 known not affected: 31 recommended: 662 | 2026-08-05T00:55:00+00:00 | Vulnerability · Source |
| CVE-2024-42108 | suse_vex | SUSE CVE CVE-2024-42108 | known not affected: 324 | 2026-08-05T00:54:56+00:00 | Vulnerability · Source |
| CVE-2024-42110 | suse_vex | SUSE CVE CVE-2024-42110 | known affected: 528 known not affected: 6 recommended: 761 | 2026-08-05T00:54:54+00:00 | Vulnerability · Source |
| CVE-2024-42111 | suse_vex | SUSE CVE CVE-2024-42111 | known not affected: 324 | 2026-08-05T00:54:52+00:00 | Vulnerability · Source |
| CVE-2024-42120 | suse_vex | SUSE CVE CVE-2024-42120 | known affected: 504 known not affected: 42 recommended: 732 | 2026-08-05T00:54:47+00:00 | Vulnerability · Source |
| CVE-2024-42233 | suse_vex | SUSE CVE CVE-2024-42233 | known not affected: 311 | 2026-08-05T00:54:39+00:00 | Vulnerability · Source |
| CVE-2024-42235 | suse_vex | SUSE CVE CVE-2024-42235 | known not affected: 311 | 2026-08-05T00:54:38+00:00 | Vulnerability · Source |
| CVE-2024-42256 | suse_vex | SUSE CVE CVE-2024-42256 | known not affected: 310 | 2026-08-05T00:54:29+00:00 | Vulnerability · Source |
| CVE-2024-42258 | suse_vex | SUSE CVE CVE-2024-42258 | known not affected: 311 | 2026-08-05T00:54:28+00:00 | Vulnerability · Source |
| 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 |