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-36920 | suse_vex | SUSE CVE CVE-2024-36920 | known affected: 394 known not affected: 208 recommended: 330 | 2026-07-25T01:48:04+00:00 | Vulnerability · Source |
| CVE-2024-36921 | suse_vex | SUSE CVE CVE-2024-36921 | known affected: 394 known not affected: 270 recommended: 415 | 2026-07-25T01:48:01+00:00 | Vulnerability · Source |
| CVE-2024-36927 | suse_vex | SUSE CVE CVE-2024-36927 | known affected: 411 known not affected: 393 recommended: 330 | 2026-07-25T01:47:59+00:00 | Vulnerability · Source |
| CVE-2024-36939 | suse_vex | SUSE CVE CVE-2024-36939 | known affected: 330 known not affected: 187 recommended: 762 | 2026-07-25T01:47:51+00:00 | Vulnerability · Source |
| CVE-2024-36948 | suse_vex | SUSE CVE CVE-2024-36948 | known not affected: 330 recommended: 59 | 2026-07-25T01:47:46+00:00 | Vulnerability · Source |
| CVE-2024-36954 | suse_vex | SUSE CVE CVE-2024-36954 | known affected: 426 known not affected: 189 recommended: 693 | 2026-07-25T01:47:41+00:00 | Vulnerability · Source |
| CVE-2024-36963 | suse_vex | SUSE CVE CVE-2024-36963 | known not affected: 330 | 2026-07-25T01:47:40+00:00 | Vulnerability · Source |
| CVE-2024-36965 | suse_vex | SUSE CVE CVE-2024-36965 | known affected: 377 known not affected: 188 recommended: 656 | 2026-07-25T01:47:38+00:00 | Vulnerability · Source |
| CVE-2024-36966 | suse_vex | SUSE CVE CVE-2024-36966 | known not affected: 330 | 2026-07-25T01:47:37+00:00 | Vulnerability · Source |
| CVE-2024-36975 | suse_vex | SUSE CVE CVE-2024-36975 | known affected: 330 known not affected: 172 recommended: 656 | 2026-07-25T01:47:28+00:00 | Vulnerability · Source |
| CVE-2024-37407 | suse_vex | SUSE CVE CVE-2024-37407 | known not affected: 160 | 2026-07-25T01:47:25+00:00 | Vulnerability · Source |
| CVE-2024-38306 | suse_vex | SUSE CVE CVE-2024-38306 | known not affected: 318 | 2026-07-25T01:47:20+00:00 | Vulnerability · Source |
| CVE-2024-38388 | suse_vex | SUSE CVE CVE-2024-38388 | known affected: 330 known not affected: 172 recommended: 656 | 2026-07-25T01:47:17+00:00 | Vulnerability · Source |
| CVE-2024-38554 | suse_vex | SUSE CVE CVE-2024-38554 | known affected: 498 known not affected: 159 recommended: 592 | 2026-07-25T01:47:07+00:00 | Vulnerability · Source |
| CVE-2024-38575 | suse_vex | SUSE CVE CVE-2024-38575 | known affected: 394 known not affected: 285 recommended: 407 | 2026-07-25T01:46:58+00:00 | Vulnerability · Source |
| CVE-2024-38589 | suse_vex | SUSE CVE CVE-2024-38589 | known affected: 627 known not affected: 38 recommended: 619 | 2026-07-25T01:46:50+00:00 | Vulnerability · Source |
| CVE-2024-38612 | suse_vex | SUSE CVE CVE-2024-38612 | known not affected: 473 | 2026-07-25T01:46:45+00:00 | Vulnerability · Source |
| CVE-2024-38619 | suse_vex | SUSE CVE CVE-2024-38619 | known affected: 538 known not affected: 33 recommended: 789 | 2026-07-25T01:46:41+00:00 | Vulnerability · Source |
| CVE-2024-38621 | suse_vex | SUSE CVE CVE-2024-38621 | known affected: 511 known not affected: 27 recommended: 740 | 2026-07-25T01:46:40+00:00 | Vulnerability · Source |
| CVE-2024-38662 | suse_vex | SUSE CVE CVE-2024-38662 | known affected: 471 known not affected: 63 recommended: 718 | 2026-07-25T01:46:34+00:00 | Vulnerability · Source |
| CVE-2024-38664 | suse_vex | SUSE CVE CVE-2024-38664 | known affected: 394 known not affected: 288 recommended: 358 | 2026-07-25T01:46:30+00:00 | Vulnerability · Source |
| CVE-2024-38667 | suse_vex | SUSE CVE CVE-2024-38667 | known not affected: 318 | 2026-07-25T01:46:28+00:00 | Vulnerability · Source |
| CVE-2024-38798 | suse_vex | SUSE CVE CVE-2024-38798 | known affected: 180 | 2026-07-25T01:46:26+00:00 | Vulnerability · Source |
| 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 |