VEX records
Browse vendor VEX statements available in this Vulnerability-Lookup instance and pivot to the related vulnerability.
292263 VEX records
API response| Vulnerability | Source | Title | Product status | Imported | Links |
|---|---|---|---|---|---|
| CVE-2024-46802 | suse_vex | SUSE CVE CVE-2024-46802 | known affected: 548 known not affected: 49 recommended: 661 | 2026-07-25T01:38:03+00:00 | Vulnerability · Source |
| CVE-2024-46803 | suse_vex | SUSE CVE CVE-2024-46803 | known affected: 394 known not affected: 263 recommended: 366 | 2026-07-25T01:38:02+00:00 | Vulnerability · Source |
| CVE-2024-46813 | suse_vex | SUSE CVE CVE-2024-46813 | known affected: 394 known not affected: 90 recommended: 915 | 2026-07-25T01:37:48+00:00 | Vulnerability · Source |
| CVE-2024-46820 | suse_vex | SUSE CVE CVE-2024-46820 | known not affected: 325 recommended: 102 | 2026-07-25T01:37:40+00:00 | Vulnerability · Source |
| CVE-2024-46826 | suse_vex | SUSE CVE CVE-2024-46826 | known affected: 586 known not affected: 36 recommended: 741 | 2026-07-25T01:37:35+00:00 | Vulnerability · Source |
| CVE-2024-46831 | suse_vex | SUSE CVE CVE-2024-46831 | known affected: 394 known not affected: 291 recommended: 366 | 2026-07-25T01:37:28+00:00 | Vulnerability · Source |
| CVE-2024-46832 | suse_vex | SUSE CVE CVE-2024-46832 | known not affected: 325 | 2026-07-25T01:37:27+00:00 | Vulnerability · Source |
| CVE-2024-46834 | suse_vex | SUSE CVE CVE-2024-46834 | known affected: 354 known not affected: 195 recommended: 677 | 2026-07-25T01:37:25+00:00 | Vulnerability · Source |
| CVE-2024-46839 | suse_vex | SUSE CVE CVE-2024-46839 | known not affected: 324 recommended: 43 | 2026-07-25T01:37:22+00:00 | Vulnerability · Source |
| CVE-2024-46840 | suse_vex | SUSE CVE CVE-2024-46840 | known affected: 586 known not affected: 36 recommended: 677 | 2026-07-25T01:37:21+00:00 | Vulnerability · Source |
| CVE-2024-46845 | suse_vex | SUSE CVE CVE-2024-46845 | known affected: 394 known not affected: 263 recommended: 310 | 2026-07-25T01:37:15+00:00 | Vulnerability · Source |
| CVE-2024-46847 | suse_vex | SUSE CVE CVE-2024-46847 | known not affected: 325 | 2026-07-25T01:37:12+00:00 | Vulnerability · Source |
| CVE-2024-46856 | suse_vex | SUSE CVE CVE-2024-46856 | known not affected: 325 | 2026-07-25T01:36:59+00:00 | Vulnerability · Source |
| CVE-2024-46858 | suse_vex | SUSE CVE CVE-2024-46858 | known affected: 496 known not affected: 213 recommended: 461 | 2026-07-25T01:36:54+00:00 | Vulnerability · Source |
| CVE-2024-46864 | suse_vex | SUSE CVE CVE-2024-46864 | known affected: 354 known not affected: 200 recommended: 678 | 2026-07-25T01:36:47+00:00 | Vulnerability · Source |
| CVE-2024-46865 | suse_vex | SUSE CVE CVE-2024-46865 | known not affected: 241 recommended: 461 | 2026-07-25T01:36:46+00:00 | Vulnerability · Source |
| CVE-2024-46896 | suse_vex | SUSE CVE CVE-2024-46896 | known affected: 394 known not affected: 274 recommended: 363 | 2026-07-25T01:36:39+00:00 | Vulnerability · Source |
| CVE-2024-47530 | suse_vex | SUSE CVE CVE-2024-47530 | known not affected: 74 recommended: 20 | 2026-07-25T01:36:30+00:00 | Vulnerability · Source |
| CVE-2024-47660 | suse_vex | SUSE CVE CVE-2024-47660 | known affected: 589 known not affected: 36 recommended: 706 | 2026-07-25T01:36:24+00:00 | Vulnerability · Source |
| CVE-2024-47664 | suse_vex | SUSE CVE CVE-2024-47664 | known affected: 365 known not affected: 290 recommended: 637 | 2026-07-25T01:36:15+00:00 | Vulnerability · Source |
| CVE-2024-47666 | suse_vex | SUSE CVE CVE-2024-47666 | known affected: 650 known not affected: 45 recommended: 460 | 2026-07-25T01:36:11+00:00 | Vulnerability · Source |
| CVE-2024-47672 | suse_vex | SUSE CVE CVE-2024-47672 | known affected: 565 known not affected: 60 recommended: 663 | 2026-07-25T01:36:03+00:00 | Vulnerability · Source |
| CVE-2024-47676 | suse_vex | SUSE CVE CVE-2024-47676 | known not affected: 379 recommended: 6 | 2026-07-25T01:35:54+00:00 | Vulnerability · Source |
| CVE-2024-47678 | suse_vex | SUSE CVE CVE-2024-47678 | known affected: 594 known not affected: 80 recommended: 499 | 2026-07-25T01:35:52+00:00 | Vulnerability · Source |
| CVE-2024-47687 | suse_vex | SUSE CVE CVE-2024-47687 | known affected: 398 known not affected: 373 recommended: 415 | 2026-07-25T01:35:36+00:00 | Vulnerability · Source |
| CVE-2024-47691 | suse_vex | SUSE CVE CVE-2024-47691 | known not affected: 402 recommended: 6 | 2026-07-25T01:35:33+00:00 | Vulnerability · Source |
| CVE-2024-47694 | suse_vex | SUSE CVE CVE-2024-47694 | known not affected: 379 recommended: 65 | 2026-07-25T01:35:28+00:00 | Vulnerability · Source |
| CVE-2024-47703 | suse_vex | SUSE CVE CVE-2024-47703 | known affected: 394 known not affected: 178 recommended: 412 | 2026-07-25T01:35:11+00:00 | Vulnerability · Source |
| CVE-2024-47710 | suse_vex | SUSE CVE CVE-2024-47710 | known affected: 459 known not affected: 210 recommended: 686 | 2026-07-25T01:35:03+00:00 | Vulnerability · Source |
| CVE-2024-47716 | suse_vex | SUSE CVE CVE-2024-47716 | known not affected: 402 recommended: 6 | 2026-07-25T01:34:53+00:00 | Vulnerability · Source |
| CVE-2024-47725 | suse_vex | SUSE CVE CVE-2024-47725 | known not affected: 402 | 2026-07-25T01:34:44+00:00 | Vulnerability · Source |
| CVE-2024-47726 | suse_vex | SUSE CVE CVE-2024-47726 | known not affected: 474 recommended: 6 | 2026-07-25T01:34:43+00:00 | Vulnerability · Source |
| CVE-2024-47731 | suse_vex | SUSE CVE CVE-2024-47731 | known affected: 398 known not affected: 392 recommended: 372 | 2026-07-25T01:34:34+00:00 | Vulnerability · Source |
| CVE-2024-47733 | suse_vex | SUSE CVE CVE-2024-47733 | known not affected: 402 recommended: 6 | 2026-07-25T01:34:31+00:00 | Vulnerability · Source |
| CVE-2024-47734 | suse_vex | SUSE CVE CVE-2024-47734 | known not affected: 292 recommended: 65 | 2026-07-25T01:34:29+00:00 | Vulnerability · Source |
| CVE-2024-47737 | suse_vex | SUSE CVE CVE-2024-47737 | known affected: 484 known not affected: 42 recommended: 724 | 2026-07-25T01:34:25+00:00 | Vulnerability · Source |
| CVE-2024-47776 | suse_vex | SUSE CVE CVE-2024-47776 | known affected: 35 recommended: 99 | 2026-07-25T01:34:02+00:00 | Vulnerability · Source |
| CVE-2024-47778 | suse_vex | SUSE CVE CVE-2024-47778 | known affected: 35 recommended: 99 | 2026-07-25T01:34:01+00:00 | Vulnerability · Source |
| CVE-2024-47866 | suse_vex | SUSE CVE CVE-2024-47866 | known affected: 782 | 2026-07-25T01:33:54+00:00 | Vulnerability · Source |
| CVE-2024-48615 | suse_vex | SUSE CVE CVE-2024-48615 | known not affected: 175 | 2026-07-25T01:33:53+00:00 | Vulnerability · Source |
| CVE-2024-48916 | suse_vex | SUSE CVE CVE-2024-48916 | known affected: 875 | 2026-07-25T01:33:49+00:00 | Vulnerability · Source |
| CVE-2024-48958 | suse_vex | SUSE CVE CVE-2024-48958 | known affected: 394 known not affected: 180 recommended: 37 | 2026-07-25T01:33:47+00:00 | Vulnerability · Source |
| CVE-2024-49195 | suse_vex | SUSE CVE CVE-2024-49195 | known not affected: 1198 recommended: 22 | 2026-07-25T01:33:45+00:00 | Vulnerability · Source |
| CVE-2024-49395 | suse_vex | SUSE CVE CVE-2024-49395 | known affected: 1 | 2026-07-25T01:33:44+00:00 | Vulnerability · Source |
| CVE-2024-49854 | suse_vex | SUSE CVE CVE-2024-49854 | known affected: 394 known not affected: 340 recommended: 316 | 2026-07-25T01:33:29+00:00 | Vulnerability · Source |
| CVE-2024-49858 | suse_vex | SUSE CVE CVE-2024-49858 | known affected: 388 known not affected: 114 recommended: 683 | 2026-07-25T01:33:26+00:00 | Vulnerability · Source |
| CVE-2024-49863 | suse_vex | SUSE CVE CVE-2024-49863 | known affected: 471 known not affected: 138 recommended: 641 | 2026-07-25T01:33:18+00:00 | Vulnerability · Source |
| CVE-2024-49866 | suse_vex | SUSE CVE CVE-2024-49866 | known affected: 426 known not affected: 233 recommended: 642 | 2026-07-25T01:33:16+00:00 | Vulnerability · Source |
| CVE-2024-49872 | suse_vex | SUSE CVE CVE-2024-49872 | known not affected: 379 recommended: 6 | 2026-07-25T01:33:08+00:00 | Vulnerability · Source |
| CVE-2024-49873 | suse_vex | SUSE CVE CVE-2024-49873 | known not affected: 379 recommended: 6 | 2026-07-25T01:33:06+00:00 | Vulnerability · Source |