VEX records
Browse vendor VEX statements available in this Vulnerability-Lookup instance and pivot to the related vulnerability.
292225 VEX records
API response| Vulnerability | Source | Title | Product status | Imported | Links |
|---|---|---|---|---|---|
| CVE-2024-45231 | suse_vex | SUSE CVE CVE-2024-45231 | recommended: 20 | 2026-07-16T19:07:49+00:00 | Vulnerability · Source |
| CVE-2024-45679 | suse_vex | SUSE CVE CVE-2024-45679 | recommended: 8 | 2026-07-16T19:07:39+00:00 | Vulnerability · Source |
| CVE-2024-46951 | suse_vex | SUSE CVE CVE-2024-46951 | known affected: 30 known not affected: 1 recommended: 134 | 2026-07-16T19:06:27+00:00 | Vulnerability · Source |
| CVE-2024-48872 | suse_vex | SUSE CVE CVE-2024-48872 | recommended: 3 | 2026-07-16T19:05:25+00:00 | Vulnerability · Source |
| CVE-2024-49767 | suse_vex | SUSE CVE CVE-2024-49767 | known not affected: 89 recommended: 23 | 2026-07-16T19:05:17+00:00 | Vulnerability · Source |
| CVE-2024-49769 | suse_vex | SUSE CVE CVE-2024-49769 | known affected: 8 recommended: 84 | 2026-07-16T19:05:15+00:00 | Vulnerability · Source |
| CVE-2024-52281 | suse_vex | SUSE CVE CVE-2024-52281 | recommended: 3 | 2026-07-16T19:03:25+00:00 | Vulnerability · Source |
| CVE-2024-52303 | suse_vex | SUSE CVE CVE-2024-52303 | known not affected: 64 recommended: 6 | 2026-07-16T19:03:23+00:00 | Vulnerability · Source |
| CVE-2024-53861 | suse_vex | SUSE CVE CVE-2024-53861 | known affected: 394 known not affected: 112 recommended: 7 | 2026-07-16T19:02:02+00:00 | Vulnerability · Source |
| CVE-2024-53862 | suse_vex | SUSE CVE CVE-2024-53862 | recommended: 3 | 2026-07-16T19:02:00+00:00 | Vulnerability · Source |
| CVE-2024-53907 | suse_vex | SUSE CVE CVE-2024-53907 | known affected: 2 recommended: 18 | 2026-07-16T19:01:59+00:00 | Vulnerability · Source |
| CVE-2024-54148 | suse_vex | SUSE CVE CVE-2024-54148 | recommended: 3 | 2026-07-16T19:01:57+00:00 | Vulnerability · Source |
| CVE-2024-54534 | suse_vex | SUSE CVE CVE-2024-54534 | known affected: 126 recommended: 596 | 2026-07-16T19:01:53+00:00 | Vulnerability · Source |
| CVE-2024-55196 | suse_vex | SUSE CVE CVE-2024-55196 | recommended: 3 | 2026-07-16T19:01:50+00:00 | Vulnerability · Source |
| CVE-2024-55658 | suse_vex | SUSE CVE CVE-2024-55658 | recommended: 3 | 2026-07-16T19:01:43+00:00 | Vulnerability · Source |
| CVE-2024-55947 | suse_vex | SUSE CVE CVE-2024-55947 | recommended: 3 | 2026-07-16T19:01:40+00:00 | Vulnerability · Source |
| CVE-2024-56201 | suse_vex | SUSE CVE CVE-2024-56201 | known affected: 404 known not affected: 89 recommended: 83 | 2026-07-16T19:01:36+00:00 | Vulnerability · Source |
| CVE-2024-56326 | suse_vex | SUSE CVE CVE-2024-56326 | known affected: 392 recommended: 190 | 2026-07-16T19:01:34+00:00 | Vulnerability · Source |
| CVE-2024-56560 | suse_vex | SUSE CVE CVE-2024-56560 | known not affected: 435 recommended: 53 | 2026-07-16T19:01:09+00:00 | Vulnerability · Source |
| CVE-2024-56606 | suse_vex | SUSE CVE CVE-2024-56606 | known affected: 737 known not affected: 36 recommended: 389 | 2026-07-16T19:00:43+00:00 | Vulnerability · Source |
| CVE-2024-56722 | suse_vex | SUSE CVE CVE-2024-56722 | known affected: 560 known not affected: 119 recommended: 490 | 2026-07-16T18:59:48+00:00 | Vulnerability · Source |
| CVE-2024-56731 | suse_vex | SUSE CVE CVE-2024-56731 | recommended: 3 | 2026-07-16T18:59:41+00:00 | Vulnerability · Source |
| CVE-2024-57884 | suse_vex | SUSE CVE CVE-2024-57884 | known affected: 634 known not affected: 58 recommended: 432 | 2026-07-16T18:58:46+00:00 | Vulnerability · Source |
| CVE-2025-0312 | suse_vex | SUSE CVE CVE-2025-0312 | recommended: 3 | 2026-07-16T18:57:31+00:00 | Vulnerability · Source |
| CVE-2025-0750 | suse_vex | SUSE CVE CVE-2025-0750 | recommended: 3 | 2026-07-16T18:57:22+00:00 | Vulnerability · Source |
| CVE-2025-0928 | suse_vex | SUSE CVE CVE-2025-0928 | recommended: 3 | 2026-07-16T18:57:20+00:00 | Vulnerability · Source |
| CVE-2025-1098 | suse_vex | SUSE CVE CVE-2025-1098 | recommended: 3 | 2026-07-16T18:57:11+00:00 | Vulnerability · Source |
| CVE-2025-1472 | suse_vex | SUSE CVE CVE-2025-1472 | recommended: 3 | 2026-07-16T18:56:58+00:00 | Vulnerability · Source |
| CVE-2025-1937 | suse_vex | SUSE CVE CVE-2025-1937 | known affected: 37 recommended: 167 | 2026-07-16T18:56:47+00:00 | Vulnerability · Source |
| CVE-2025-2487 | suse_vex | SUSE CVE CVE-2025-2487 | known not affected: 129 recommended: 36 | 2026-07-16T18:56:43+00:00 | Vulnerability · Source |
| CVE-2025-3879 | suse_vex | SUSE CVE CVE-2025-3879 | known not affected: 96 recommended: 3 | 2026-07-16T18:56:25+00:00 | Vulnerability · Source |
| CVE-2025-4057 | suse_vex | SUSE CVE CVE-2025-4057 | recommended: 3 | 2026-07-16T18:56:24+00:00 | Vulnerability · Source |
| CVE-2025-4563 | suse_vex | SUSE CVE CVE-2025-4563 | known not affected: 433 recommended: 3 | 2026-07-16T18:56:13+00:00 | Vulnerability · Source |
| CVE-2025-4574 | suse_vex | SUSE CVE CVE-2025-4574 | known affected: 82 known not affected: 1328 recommended: 7 | 2026-07-16T18:56:09+00:00 | Vulnerability · Source |
| CVE-2025-4658 | suse_vex | SUSE CVE CVE-2025-4658 | recommended: 3 | 2026-07-16T18:56:05+00:00 | Vulnerability · Source |
| CVE-2025-4921 | suse_vex | SUSE CVE CVE-2025-4921 | known affected: 45 recommended: 8 | 2026-07-16T18:55:57+00:00 | Vulnerability · Source |
| CVE-2025-5981 | suse_vex | SUSE CVE CVE-2025-5981 | recommended: 3 | 2026-07-16T18:55:44+00:00 | Vulnerability · Source |
| CVE-2025-6004 | suse_vex | SUSE CVE CVE-2025-6004 | recommended: 11 | 2026-07-16T18:55:42+00:00 | Vulnerability · Source |
| CVE-2025-6011 | suse_vex | SUSE CVE CVE-2025-6011 | recommended: 11 | 2026-07-16T18:55:41+00:00 | Vulnerability · Source |
| CVE-2025-7700 | suse_vex | SUSE CVE CVE-2025-7700 | known affected: 138 recommended: 581 | 2026-07-16T18:55:18+00:00 | Vulnerability · Source |
| CVE-2025-8837 | suse_vex | SUSE CVE CVE-2025-8837 | known affected: 485 recommended: 54 | 2026-07-16T18:54:51+00:00 | Vulnerability · Source |
| CVE-2025-9179 | suse_vex | SUSE CVE CVE-2025-9179 | known affected: 37 recommended: 183 | 2026-07-16T18:54:48+00:00 | Vulnerability · Source |
| CVE-2025-10148 | suse_vex | SUSE CVE CVE-2025-10148 | first fixed: 13 known affected: 356 known not affected: 39 recommended: 232 | 2026-07-16T18:54:33+00:00 | Vulnerability · Source |
| CVE-2025-11277 | suse_vex | SUSE CVE CVE-2025-11277 | known affected: 3 recommended: 13 | 2026-07-16T18:54:19+00:00 | Vulnerability · Source |
| CVE-2025-14323 | suse_vex | SUSE CVE CVE-2025-14323 | known affected: 37 recommended: 184 | 2026-07-16T18:53:40+00:00 | Vulnerability · Source |
| CVE-2025-14324 | suse_vex | SUSE CVE CVE-2025-14324 | known affected: 37 recommended: 184 | 2026-07-16T18:53:39+00:00 | Vulnerability · Source |
| CVE-2025-14327 | suse_vex | SUSE CVE CVE-2025-14327 | known affected: 37 recommended: 141 | 2026-07-16T18:53:37+00:00 | Vulnerability · Source |
| CVE-2025-14329 | suse_vex | SUSE CVE CVE-2025-14329 | known affected: 37 recommended: 184 | 2026-07-16T18:53:36+00:00 | Vulnerability · Source |
| CVE-2025-20033 | suse_vex | SUSE CVE CVE-2025-20033 | recommended: 3 | 2026-07-16T18:53:10+00:00 | Vulnerability · Source |
| CVE-2025-21605 | suse_vex | SUSE CVE CVE-2025-21605 | known affected: 2 recommended: 74 | 2026-07-16T18:53:02+00:00 | Vulnerability · Source |