VEX records
Browse vendor VEX statements available in this Vulnerability-Lookup instance and pivot to the related vulnerability.
291935 VEX records
API response| Vulnerability | Source | Title | Product status | Imported | Links |
|---|---|---|---|---|---|
| CVE-2025-11718 | suse_vex | SUSE CVE CVE-2025-11718 | known affected: 70 recommended: 9 | 2026-07-28T17:25:09+00:00 | Vulnerability · Source |
| CVE-2025-13027 | suse_vex | SUSE CVE CVE-2025-13027 | known affected: 14 recommended: 9 | 2026-07-28T17:25:07+00:00 | Vulnerability · Source |
| CVE-2025-14330 | suse_vex | SUSE CVE CVE-2025-14330 | known affected: 37 recommended: 187 | 2026-07-28T17:25:04+00:00 | Vulnerability · Source |
| CVE-2025-14512 | suse_vex | SUSE CVE CVE-2025-14512 | known affected: 550 recommended: 528 | 2026-07-28T17:25:03+00:00 | Vulnerability · Source |
| CVE-2025-15666 | suse_vex | SUSE CVE CVE-2025-15666 | known affected: 841 | 2026-07-28T17:24:59+00:00 | Vulnerability · Source |
| CVE-2025-39696 | suse_vex | SUSE CVE CVE-2025-39696 | known not affected: 416 recommended: 27 | 2026-07-28T17:24:14+00:00 | Vulnerability · Source |
| CVE-2025-40247 | suse_vex | SUSE CVE CVE-2025-40247 | known not affected: 418 | 2026-07-28T17:23:40+00:00 | Vulnerability · Source |
| CVE-2025-40260 | suse_vex | SUSE CVE CVE-2025-40260 | known not affected: 408 | 2026-07-28T17:23:38+00:00 | Vulnerability · Source |
| CVE-2025-47910 | suse_vex | SUSE CVE CVE-2025-47910 | known not affected: 421 recommended: 192 | 2026-07-28T17:23:34+00:00 | Vulnerability · Source |
| CVE-2025-60753 | suse_vex | SUSE CVE CVE-2025-60753 | known affected: 474 recommended: 65 | 2026-07-28T17:23:19+00:00 | Vulnerability · Source |
| CVE-2025-64324 | suse_vex | SUSE CVE CVE-2025-64324 | first fixed: 1 known not affected: 70 recommended: 28 | 2026-07-28T17:23:14+00:00 | Vulnerability · Source |
| CVE-2025-64434 | suse_vex | SUSE CVE CVE-2025-64434 | first fixed: 1 known not affected: 70 recommended: 28 | 2026-07-28T17:23:13+00:00 | Vulnerability · Source |
| CVE-2025-68285 | suse_vex | SUSE CVE CVE-2025-68285 | first fixed: 2 known affected: 536 recommended: 855 | 2026-07-28T17:23:07+00:00 | Vulnerability · Source |
| CVE-2026-4367 | suse_vex | SUSE CVE CVE-2026-4367 | known affected: 394 known not affected: 103 recommended: 17 | 2026-07-28T17:22:48+00:00 | Vulnerability · Source |
| CVE-2026-4800 | suse_vex | SUSE CVE CVE-2026-4800 | recommended: 6 | 2026-07-28T17:22:45+00:00 | Vulnerability · Source |
| CVE-2026-8090 | suse_vex | SUSE CVE CVE-2026-8090 | known affected: 39 recommended: 128 | 2026-07-28T17:22:32+00:00 | Vulnerability · Source |
| CVE-2026-8092 | suse_vex | SUSE CVE CVE-2026-8092 | known affected: 39 recommended: 128 | 2026-07-28T17:22:31+00:00 | Vulnerability · Source |
| CVE-2026-8094 | suse_vex | SUSE CVE CVE-2026-8094 | known affected: 39 recommended: 123 | 2026-07-28T17:22:30+00:00 | Vulnerability · Source |
| CVE-2026-9539 | suse_vex | SUSE CVE CVE-2026-9539 | known affected: 39 recommended: 26 | 2026-07-28T17:22:24+00:00 | Vulnerability · Source |
| CVE-2026-12143 | suse_vex | SUSE CVE CVE-2026-12143 | known affected: 150 known not affected: 226 recommended: 1 | 2026-07-28T17:22:17+00:00 | Vulnerability · Source |
| CVE-2026-12478 | suse_vex | SUSE CVE CVE-2026-12478 | known affected: 228 recommended: 7 | 2026-07-28T17:22:14+00:00 | Vulnerability · Source |
| CVE-2026-13676 | suse_vex | SUSE CVE CVE-2026-13676 | known affected: 8 recommended: 5 | 2026-07-28T17:22:02+00:00 | Vulnerability · Source |
| CVE-2026-15037 | suse_vex | SUSE CVE CVE-2026-15037 | known affected: 1524 | 2026-07-28T17:21:56+00:00 | Vulnerability · Source |
| CVE-2026-16422 | suse_vex | SUSE CVE CVE-2026-16422 | recommended: 6 | 2026-07-28T17:20:34+00:00 | Vulnerability · Source |
| CVE-2026-16423 | suse_vex | SUSE CVE CVE-2026-16423 | recommended: 6 | 2026-07-28T17:20:33+00:00 | Vulnerability · Source |
| CVE-2026-16424 | suse_vex | SUSE CVE CVE-2026-16424 | recommended: 6 | 2026-07-28T17:20:32+00:00 | Vulnerability · Source |
| CVE-2026-16554 | suse_vex | SUSE CVE CVE-2026-16554 | known not affected: 17 | 2026-07-28T17:20:30+00:00 | Vulnerability · Source |
| CVE-2026-16730 | suse_vex | SUSE CVE CVE-2026-16730 | known affected: 15 | 2026-07-28T17:20:29+00:00 | Vulnerability · Source |
| CVE-2026-16743 | suse_vex | SUSE CVE CVE-2026-16743 | known affected: 152 | 2026-07-28T17:20:28+00:00 | Vulnerability · Source |
| CVE-2026-16804 | suse_vex | SUSE CVE CVE-2026-16804 | recommended: 6 | 2026-07-28T17:20:26+00:00 | Vulnerability · Source |
| CVE-2026-16805 | suse_vex | SUSE CVE CVE-2026-16805 | recommended: 6 | 2026-07-28T17:20:24+00:00 | Vulnerability · Source |
| CVE-2026-16806 | suse_vex | SUSE CVE CVE-2026-16806 | recommended: 6 | 2026-07-28T17:20:23+00:00 | Vulnerability · Source |
| CVE-2026-16807 | suse_vex | SUSE CVE CVE-2026-16807 | recommended: 6 | 2026-07-28T17:20:22+00:00 | Vulnerability · Source |
| CVE-2026-17500 | suse_vex | SUSE CVE CVE-2026-17500 | No product status | 2026-07-28T17:20:21+00:00 | Vulnerability · Source |
| CVE-2026-20031 | suse_vex | SUSE CVE CVE-2026-20031 | known not affected: 20 recommended: 203 | 2026-07-28T17:20:13+00:00 | Vulnerability · Source |
| CVE-2026-23231 | suse_vex | SUSE CVE CVE-2026-23231 | first fixed: 2 known affected: 416 known not affected: 204 recommended: 448 | 2026-07-28T17:20:02+00:00 | Vulnerability · Source |
| CVE-2026-23270 | suse_vex | SUSE CVE CVE-2026-23270 | first fixed: 2 known affected: 515 known not affected: 152 recommended: 398 | 2026-07-28T17:19:56+00:00 | Vulnerability · Source |
| CVE-2026-24049 | suse_vex | SUSE CVE CVE-2026-24049 | known affected: 394 known not affected: 286 recommended: 42 | 2026-07-28T17:19:39+00:00 | Vulnerability · Source |
| CVE-2026-27904 | suse_vex | SUSE CVE CVE-2026-27904 | known affected: 531 known not affected: 310 recommended: 170 | 2026-07-28T17:19:33+00:00 | Vulnerability · Source |
| CVE-2026-28780 | suse_vex | SUSE CVE CVE-2026-28780 | known affected: 442 recommended: 202 | 2026-07-28T17:19:31+00:00 | Vulnerability · Source |
| CVE-2026-31402 | suse_vex | SUSE CVE CVE-2026-31402 | first fixed: 2 known affected: 477 recommended: 852 | 2026-07-28T17:19:28+00:00 | Vulnerability · Source |
| CVE-2026-31414 | suse_vex | SUSE CVE CVE-2026-31414 | first fixed: 2 known affected: 648 recommended: 294 | 2026-07-28T17:19:26+00:00 | Vulnerability · Source |
| CVE-2026-31466 | suse_vex | SUSE CVE CVE-2026-31466 | first fixed: 2 known affected: 621 known not affected: 6 recommended: 265 | 2026-07-28T17:19:19+00:00 | Vulnerability · Source |
| CVE-2026-31495 | suse_vex | SUSE CVE CVE-2026-31495 | first fixed: 2 known affected: 649 recommended: 294 | 2026-07-28T17:19:15+00:00 | Vulnerability · Source |
| CVE-2026-31499 | suse_vex | SUSE CVE CVE-2026-31499 | first fixed: 2 known affected: 459 known not affected: 154 recommended: 331 | 2026-07-28T17:19:14+00:00 | Vulnerability · Source |
| CVE-2026-31502 | suse_vex | SUSE CVE CVE-2026-31502 | first fixed: 2 known affected: 613 known not affected: 4 recommended: 329 | 2026-07-28T17:19:12+00:00 | Vulnerability · Source |
| CVE-2026-31555 | suse_vex | SUSE CVE CVE-2026-31555 | first fixed: 2 known affected: 531 known not affected: 98 recommended: 294 | 2026-07-28T17:19:06+00:00 | Vulnerability · Source |
| CVE-2026-31613 | suse_vex | SUSE CVE CVE-2026-31613 | first fixed: 2 known affected: 411 known not affected: 98 recommended: 593 | 2026-07-28T17:19:02+00:00 | Vulnerability · Source |
| CVE-2026-31673 | suse_vex | SUSE CVE CVE-2026-31673 | first fixed: 2 known affected: 608 known not affected: 4 recommended: 331 | 2026-07-28T17:18:58+00:00 | Vulnerability · Source |
| CVE-2026-31674 | suse_vex | SUSE CVE CVE-2026-31674 | first fixed: 2 known affected: 612 recommended: 331 | 2026-07-28T17:18:56+00:00 | Vulnerability · Source |