VEX records
Browse vendor VEX statements available in this Vulnerability-Lookup instance and pivot to the related vulnerability.
291704 VEX records
API response| Vulnerability | Source | Title | Product status | Imported | Links |
|---|---|---|---|---|---|
| CVE-2024-22034 | suse_vex | SUSE CVE CVE-2024-22034 | known affected: 18 recommended: 22 | 2026-08-14T01:09:13+00:00 | Vulnerability · Source |
| CVE-2024-22563 | suse_vex | SUSE CVE CVE-2024-22563 | known affected: 204 known not affected: 105 recommended: 333 | 2026-08-14T01:09:12+00:00 | Vulnerability · Source |
| CVE-2024-23342 | suse_vex | SUSE CVE CVE-2024-23342 | known affected: 37 | 2026-08-14T01:09:09+00:00 | Vulnerability · Source |
| CVE-2024-24787 | suse_vex | SUSE CVE CVE-2024-24787 | known not affected: 150 recommended: 176 | 2026-08-14T01:09:07+00:00 | Vulnerability · Source |
| CVE-2024-24791 | suse_vex | SUSE CVE CVE-2024-24791 | known not affected: 58 recommended: 300 | 2026-08-14T01:09:05+00:00 | Vulnerability · Source |
| CVE-2024-25742 | suse_vex | SUSE CVE CVE-2024-25742 | known affected: 260 known not affected: 253 recommended: 554 | 2026-08-14T01:09:01+00:00 | Vulnerability · Source |
| CVE-2024-26924 | suse_vex | SUSE CVE CVE-2024-26924 | known affected: 422 known not affected: 179 recommended: 707 | 2026-08-14T01:08:43+00:00 | Vulnerability · Source |
| CVE-2024-26998 | suse_vex | SUSE CVE CVE-2024-26998 | known not affected: 330 recommended: 59 | 2026-08-14T01:08:39+00:00 | Vulnerability · Source |
| CVE-2024-27388 | suse_vex | SUSE CVE CVE-2024-27388 | known affected: 515 known not affected: 13 recommended: 804 | 2026-08-14T01:08:34+00:00 | Vulnerability · Source |
| CVE-2024-35907 | suse_vex | SUSE CVE CVE-2024-35907 | known affected: 376 known not affected: 181 recommended: 704 | 2026-08-14T01:08:20+00:00 | Vulnerability · Source |
| CVE-2024-39684 | suse_vex | SUSE CVE CVE-2024-39684 | known not affected: 46 | 2026-08-14T01:08:04+00:00 | Vulnerability · Source |
| CVE-2024-43821 | suse_vex | SUSE CVE CVE-2024-43821 | known affected: 438 known not affected: 120 recommended: 691 | 2026-08-14T01:07:45+00:00 | Vulnerability · Source |
| CVE-2024-43896 | suse_vex | SUSE CVE CVE-2024-43896 | known not affected: 310 recommended: 59 | 2026-08-14T01:07:41+00:00 | Vulnerability · Source |
| CVE-2024-46767 | suse_vex | SUSE CVE CVE-2024-46767 | known affected: 394 known not affected: 269 recommended: 357 | 2026-08-14T01:07:28+00:00 | Vulnerability · Source |
| CVE-2024-46790 | suse_vex | SUSE CVE CVE-2024-46790 | known not affected: 325 | 2026-08-14T01:07:25+00:00 | Vulnerability · Source |
| CVE-2024-47076 | suse_vex | SUSE CVE CVE-2024-47076 | known not affected: 101 recommended: 75 | 2026-08-14T01:07:16+00:00 | Vulnerability · Source |
| CVE-2024-47746 | suse_vex | SUSE CVE CVE-2024-47746 | known not affected: 402 recommended: 6 | 2026-08-14T01:07:12+00:00 | Vulnerability · Source |
| CVE-2024-53086 | suse_vex | SUSE CVE CVE-2024-53086 | known not affected: 372 recommended: 59 | 2026-08-14T01:06:54+00:00 | Vulnerability · Source |
| CVE-2025-1011 | suse_vex | SUSE CVE CVE-2025-1011 | known affected: 37 recommended: 178 | 2026-08-14T01:06:24+00:00 | Vulnerability · Source |
| CVE-2025-2361 | suse_vex | SUSE CVE CVE-2025-2361 | known affected: 6 recommended: 35 | 2026-08-14T01:06:21+00:00 | Vulnerability · Source |
| CVE-2025-4035 | suse_vex | SUSE CVE CVE-2025-4035 | known affected: 379 recommended: 3 | 2026-08-14T01:06:17+00:00 | Vulnerability · Source |
| CVE-2025-5264 | suse_vex | SUSE CVE CVE-2025-5264 | known affected: 37 recommended: 186 | 2026-08-14T01:06:13+00:00 | Vulnerability · Source |
| CVE-2025-9708 | suse_vex | SUSE CVE CVE-2025-9708 | known not affected: 397 | 2026-08-14T01:06:08+00:00 | Vulnerability · Source |
| CVE-2025-11081 | suse_vex | SUSE CVE CVE-2025-11081 | known not affected: 201 | 2026-08-14T01:06:06+00:00 | Vulnerability · Source |
| CVE-2025-11961 | suse_vex | SUSE CVE CVE-2025-11961 | known affected: 456 recommended: 83 | 2026-08-14T01:06:04+00:00 | Vulnerability · Source |
| CVE-2025-13086 | suse_vex | SUSE CVE CVE-2025-13086 | known affected: 15 known not affected: 84 recommended: 57 | 2026-08-14T01:06:02+00:00 | Vulnerability · Source |
| CVE-2025-14331 | suse_vex | SUSE CVE CVE-2025-14331 | known affected: 37 recommended: 187 | 2026-08-14T01:06:00+00:00 | Vulnerability · Source |
| CVE-2025-22101 | suse_vex | SUSE CVE CVE-2025-22101 | known not affected: 384 recommended: 53 | 2026-08-14T01:05:44+00:00 | Vulnerability · Source |
| CVE-2025-27148 | suse_vex | SUSE CVE CVE-2025-27148 | known not affected: 23 | 2026-08-14T01:05:37+00:00 | Vulnerability · Source |
| CVE-2025-27820 | suse_vex | SUSE CVE CVE-2025-27820 | known not affected: 42 | 2026-08-14T01:05:34+00:00 | Vulnerability · Source |
| CVE-2025-31650 | suse_vex | SUSE CVE CVE-2025-31650 | known affected: 408 known not affected: 153 recommended: 349 | 2026-08-14T01:05:30+00:00 | Vulnerability · Source |
| CVE-2025-38076 | suse_vex | SUSE CVE CVE-2025-38076 | known not affected: 401 | 2026-08-14T01:05:19+00:00 | Vulnerability · Source |
| CVE-2025-38156 | suse_vex | SUSE CVE CVE-2025-38156 | first fixed: 2 known not affected: 416 recommended: 154 | 2026-08-14T01:05:16+00:00 | Vulnerability · Source |
| CVE-2025-38308 | suse_vex | SUSE CVE CVE-2025-38308 | known not affected: 416 recommended: 27 | 2026-08-14T01:05:08+00:00 | Vulnerability · Source |
| CVE-2025-38356 | suse_vex | SUSE CVE CVE-2025-38356 | first fixed: 2 known affected: 394 known not affected: 383 recommended: 265 | 2026-08-14T01:05:04+00:00 | Vulnerability · Source |
| CVE-2025-38648 | suse_vex | SUSE CVE CVE-2025-38648 | first fixed: 2 known not affected: 416 recommended: 154 | 2026-08-14T01:04:45+00:00 | Vulnerability · Source |
| CVE-2025-39695 | suse_vex | SUSE CVE CVE-2025-39695 | first fixed: 2 known affected: 394 known not affected: 353 recommended: 265 | 2026-08-14T01:04:36+00:00 | Vulnerability · Source |
| CVE-2025-39796 | suse_vex | SUSE CVE CVE-2025-39796 | known not affected: 416 | 2026-08-14T01:04:30+00:00 | Vulnerability · Source |
| CVE-2025-40226 | suse_vex | SUSE CVE CVE-2025-40226 | first fixed: 2 known affected: 394 known not affected: 405 recommended: 172 | 2026-08-14T01:03:55+00:00 | Vulnerability · Source |
| CVE-2025-40299 | suse_vex | SUSE CVE CVE-2025-40299 | known not affected: 414 | 2026-08-14T01:03:51+00:00 | Vulnerability · Source |
| CVE-2025-43342 | suse_vex | SUSE CVE CVE-2025-43342 | known affected: 132 recommended: 608 | 2026-08-14T01:03:48+00:00 | Vulnerability · Source |
| CVE-2025-43501 | suse_vex | SUSE CVE CVE-2025-43501 | known affected: 133 recommended: 624 | 2026-08-14T01:03:46+00:00 | Vulnerability · Source |
| CVE-2025-61780 | suse_vex | SUSE CVE CVE-2025-61780 | known affected: 413 known not affected: 8 recommended: 7 | 2026-08-14T01:03:36+00:00 | Vulnerability · Source |
| CVE-2025-66287 | suse_vex | SUSE CVE CVE-2025-66287 | known affected: 132 recommended: 632 | 2026-08-14T01:03:34+00:00 | Vulnerability · Source |
| CVE-2025-68118 | suse_vex | SUSE CVE CVE-2025-68118 | known not affected: 166 | 2026-08-14T01:03:32+00:00 | Vulnerability · Source |
| CVE-2025-68769 | suse_vex | SUSE CVE CVE-2025-68769 | known affected: 31 known not affected: 326 | 2026-08-14T01:03:26+00:00 | Vulnerability · Source |
| CVE-2026-2604 | suse_vex | SUSE CVE CVE-2026-2604 | known affected: 6 recommended: 200 | 2026-08-14T01:03:14+00:00 | Vulnerability · Source |
| CVE-2026-8400 | suse_vex | SUSE CVE CVE-2026-8400 | known affected: 24 recommended: 76 | 2026-08-14T01:03:02+00:00 | Vulnerability · Source |
| CVE-2026-9375 | suse_vex | SUSE CVE CVE-2026-9375 | known affected: 394 known not affected: 114 recommended: 18 | 2026-08-14T01:02:57+00:00 | Vulnerability · Source |
| CVE-2026-16243 | suse_vex | SUSE CVE CVE-2026-16243 | known affected: 24 recommended: 76 | 2026-08-14T01:02:39+00:00 | Vulnerability · Source |