VEX records
Browse vendor VEX statements available in this Vulnerability-Lookup instance and pivot to the related vulnerability.
292260 VEX records
API response| Vulnerability | Source | Title | Product status | Imported | Links |
|---|---|---|---|---|---|
| CVE-2024-39291 | suse_vex | SUSE CVE CVE-2024-39291 | known affected: 421 known not affected: 300 recommended: 358 | 2026-07-25T01:46:21+00:00 | Vulnerability · Source |
| CVE-2024-39293 | suse_vex | SUSE CVE CVE-2024-39293 | known not affected: 318 | 2026-07-25T01:46:19+00:00 | Vulnerability · Source |
| CVE-2024-39298 | suse_vex | SUSE CVE CVE-2024-39298 | known affected: 398 known not affected: 358 recommended: 92 | 2026-07-25T01:46:17+00:00 | Vulnerability · Source |
| CVE-2024-39362 | suse_vex | SUSE CVE CVE-2024-39362 | known affected: 394 known not affected: 37 recommended: 358 | 2026-07-25T01:46:15+00:00 | Vulnerability · Source |
| CVE-2024-39462 | suse_vex | SUSE CVE CVE-2024-39462 | known not affected: 318 recommended: 59 | 2026-07-25T01:46:10+00:00 | Vulnerability · Source |
| CVE-2024-39466 | suse_vex | SUSE CVE CVE-2024-39466 | known affected: 394 known not affected: 285 recommended: 358 | 2026-07-25T01:46:08+00:00 | Vulnerability · Source |
| CVE-2024-39480 | suse_vex | SUSE CVE CVE-2024-39480 | known affected: 559 recommended: 310 | 2026-07-25T01:46:00+00:00 | Vulnerability · Source |
| CVE-2024-39484 | suse_vex | SUSE CVE CVE-2024-39484 | known affected: 394 known not affected: 391 recommended: 360 | 2026-07-25T01:45:58+00:00 | Vulnerability · Source |
| CVE-2024-39492 | suse_vex | SUSE CVE CVE-2024-39492 | known not affected: 318 | 2026-07-25T01:45:56+00:00 | Vulnerability · Source |
| CVE-2024-39503 | suse_vex | SUSE CVE CVE-2024-39503 | known not affected: 318 recommended: 20 | 2026-07-25T01:45:54+00:00 | Vulnerability · Source |
| CVE-2024-40782 | suse_vex | SUSE CVE CVE-2024-40782 | known affected: 79 recommended: 643 | 2026-07-25T01:45:44+00:00 | Vulnerability · Source |
| CVE-2024-40857 | suse_vex | SUSE CVE CVE-2024-40857 | known not affected: 196 | 2026-07-25T01:45:43+00:00 | Vulnerability · Source |
| CVE-2024-40866 | suse_vex | SUSE CVE CVE-2024-40866 | known affected: 97 recommended: 767 | 2026-07-25T01:45:41+00:00 | Vulnerability · Source |
| CVE-2024-40903 | suse_vex | SUSE CVE CVE-2024-40903 | known affected: 330 known not affected: 196 recommended: 658 | 2026-07-25T01:45:34+00:00 | Vulnerability · Source |
| CVE-2024-40904 | suse_vex | SUSE CVE CVE-2024-40904 | known affected: 530 known not affected: 12 recommended: 791 | 2026-07-25T01:45:32+00:00 | Vulnerability · Source |
| CVE-2024-40905 | suse_vex | SUSE CVE CVE-2024-40905 | known affected: 581 known not affected: 42 recommended: 677 | 2026-07-25T01:45:29+00:00 | Vulnerability · Source |
| CVE-2024-40913 | suse_vex | SUSE CVE CVE-2024-40913 | known affected: 394 known not affected: 258 recommended: 360 | 2026-07-25T01:45:27+00:00 | Vulnerability · Source |
| CVE-2024-40914 | suse_vex | SUSE CVE CVE-2024-40914 | known affected: 398 known not affected: 359 recommended: 339 | 2026-07-25T01:45:25+00:00 | Vulnerability · Source |
| CVE-2024-40941 | suse_vex | SUSE CVE CVE-2024-40941 | known affected: 514 known not affected: 10 recommended: 777 | 2026-07-25T01:45:13+00:00 | Vulnerability · Source |
| CVE-2024-40943 | suse_vex | SUSE CVE CVE-2024-40943 | known affected: 450 known not affected: 6 recommended: 742 | 2026-07-25T01:45:11+00:00 | Vulnerability · Source |
| CVE-2024-40949 | suse_vex | SUSE CVE CVE-2024-40949 | known not affected: 318 | 2026-07-25T01:45:08+00:00 | Vulnerability · Source |
| CVE-2024-40955 | suse_vex | SUSE CVE CVE-2024-40955 | known not affected: 318 | 2026-07-25T01:45:06+00:00 | Vulnerability · Source |
| CVE-2024-40963 | suse_vex | SUSE CVE CVE-2024-40963 | known not affected: 523 | 2026-07-25T01:44:59+00:00 | Vulnerability · Source |
| CVE-2024-40975 | suse_vex | SUSE CVE CVE-2024-40975 | known affected: 394 known not affected: 299 recommended: 358 | 2026-07-25T01:44:55+00:00 | Vulnerability · Source |
| CVE-2024-40980 | suse_vex | SUSE CVE CVE-2024-40980 | known affected: 539 known not affected: 135 recommended: 544 | 2026-07-25T01:44:50+00:00 | Vulnerability · Source |
| CVE-2024-41003 | suse_vex | SUSE CVE CVE-2024-41003 | known not affected: 318 | 2026-07-25T01:44:40+00:00 | Vulnerability · Source |
| CVE-2024-41005 | suse_vex | SUSE CVE CVE-2024-41005 | known affected: 712 recommended: 431 | 2026-07-25T01:44:38+00:00 | Vulnerability · Source |
| CVE-2024-41021 | suse_vex | SUSE CVE CVE-2024-41021 | known not affected: 324 | 2026-07-25T01:44:36+00:00 | Vulnerability · Source |
| CVE-2024-41027 | suse_vex | SUSE CVE CVE-2024-41027 | known affected: 155 known not affected: 192 | 2026-07-25T01:44:31+00:00 | Vulnerability · Source |
| CVE-2024-41034 | suse_vex | SUSE CVE CVE-2024-41034 | known not affected: 217 | 2026-07-25T01:44:27+00:00 | Vulnerability · Source |
| CVE-2024-41043 | suse_vex | SUSE CVE CVE-2024-41043 | known not affected: 324 | 2026-07-25T01:44:24+00:00 | Vulnerability · Source |
| CVE-2024-41046 | suse_vex | SUSE CVE CVE-2024-41046 | known not affected: 324 | 2026-07-25T01:44:21+00:00 | Vulnerability · Source |
| CVE-2024-41050 | suse_vex | SUSE CVE CVE-2024-41050 | known affected: 471 known not affected: 237 recommended: 360 | 2026-07-25T01:44:16+00:00 | Vulnerability · Source |
| CVE-2024-41055 | suse_vex | SUSE CVE CVE-2024-41055 | known affected: 394 known not affected: 258 recommended: 359 | 2026-07-25T01:44:14+00:00 | Vulnerability · Source |
| CVE-2024-41063 | suse_vex | SUSE CVE CVE-2024-41063 | known affected: 450 known not affected: 6 recommended: 742 | 2026-07-25T01:44:09+00:00 | Vulnerability · Source |
| CVE-2024-41066 | suse_vex | SUSE CVE CVE-2024-41066 | known affected: 453 known not affected: 6 recommended: 762 | 2026-07-25T01:44:06+00:00 | Vulnerability · Source |
| CVE-2024-41067 | suse_vex | SUSE CVE CVE-2024-41067 | known not affected: 324 | 2026-07-25T01:44:04+00:00 | Vulnerability · Source |
| CVE-2024-41077 | suse_vex | SUSE CVE CVE-2024-41077 | known affected: 394 known not affected: 46 recommended: 309 | 2026-07-25T01:43:59+00:00 | Vulnerability · Source |
| CVE-2024-41081 | suse_vex | SUSE CVE CVE-2024-41081 | known affected: 514 known not affected: 10 recommended: 728 | 2026-07-25T01:43:54+00:00 | Vulnerability · Source |
| CVE-2024-41085 | suse_vex | SUSE CVE CVE-2024-41085 | known affected: 404 known not affected: 550 recommended: 111 | 2026-07-25T01:43:50+00:00 | Vulnerability · Source |
| CVE-2024-41087 | suse_vex | SUSE CVE CVE-2024-41087 | known affected: 353 known not affected: 30 recommended: 988 | 2026-07-25T01:43:47+00:00 | Vulnerability · Source |
| CVE-2024-41817 | suse_vex | SUSE CVE CVE-2024-41817 | known not affected: 393 | 2026-07-25T01:43:38+00:00 | Vulnerability · Source |
| CVE-2024-41957 | suse_vex | SUSE CVE CVE-2024-41957 | known not affected: 251 | 2026-07-25T01:43:36+00:00 | Vulnerability · Source |
| CVE-2024-42065 | suse_vex | SUSE CVE CVE-2024-42065 | known not affected: 324 recommended: 59 | 2026-07-25T01:43:31+00:00 | Vulnerability · Source |
| CVE-2024-42071 | suse_vex | SUSE CVE CVE-2024-42071 | known not affected: 324 recommended: 59 | 2026-07-25T01:43:27+00:00 | Vulnerability · Source |
| CVE-2024-42093 | suse_vex | SUSE CVE CVE-2024-42093 | known affected: 365 known not affected: 65 recommended: 856 | 2026-07-25T01:43:23+00:00 | Vulnerability · Source |
| CVE-2024-42096 | suse_vex | SUSE CVE CVE-2024-42096 | known affected: 524 recommended: 791 | 2026-07-25T01:43:21+00:00 | Vulnerability · Source |
| CVE-2024-42100 | suse_vex | SUSE CVE CVE-2024-42100 | known not affected: 324 | 2026-07-25T01:43:17+00:00 | Vulnerability · Source |
| CVE-2024-42103 | suse_vex | SUSE CVE CVE-2024-42103 | known affected: 394 known not affected: 301 recommended: 230 | 2026-07-25T01:43:13+00:00 | Vulnerability · Source |
| CVE-2024-42114 | suse_vex | SUSE CVE CVE-2024-42114 | known affected: 524 known not affected: 58 recommended: 694 | 2026-07-25T01:43:08+00:00 | Vulnerability · Source |