VEX records
Browse vendor VEX statements available in this Vulnerability-Lookup instance and pivot to the related vulnerability.
289914 VEX records
API response| Vulnerability | Source | Title | Product status | Imported | Links |
|---|---|---|---|---|---|
| CVE-2025-15444 | suse_vex | SUSE CVE CVE-2025-15444 | known affected: 486 recommended: 53 | 2026-08-06T01:45:54+00:00 | Vulnerability · Source |
| CVE-2025-21502 | suse_vex | SUSE CVE CVE-2025-21502 | known affected: 458 known not affected: 188 recommended: 574 | 2026-08-06T01:45:52+00:00 | Vulnerability · Source |
| CVE-2025-21971 | suse_vex | SUSE CVE CVE-2025-21971 | known affected: 405 recommended: 805 | 2026-08-06T01:44:53+00:00 | Vulnerability · Source |
| CVE-2025-22004 | suse_vex | SUSE CVE CVE-2025-22004 | known affected: 400 recommended: 181 | 2026-08-06T01:44:48+00:00 | Vulnerability · Source |
| CVE-2025-30749 | suse_vex | SUSE CVE CVE-2025-30749 | known affected: 522 recommended: 880 | 2026-08-06T01:44:17+00:00 | Vulnerability · Source |
| CVE-2025-32990 | suse_vex | SUSE CVE CVE-2025-32990 | known affected: 457 known not affected: 1 recommended: 327 | 2026-08-06T01:44:14+00:00 | Vulnerability · Source |
| CVE-2025-38377 | suse_vex | SUSE CVE CVE-2025-38377 | first fixed: 2 known affected: 455 known not affected: 179 recommended: 508 | 2026-08-06T01:42:40+00:00 | Vulnerability · Source |
| CVE-2025-38498 | suse_vex | SUSE CVE CVE-2025-38498 | known affected: 405 known not affected: 324 recommended: 909 | 2026-08-06T01:42:16+00:00 | Vulnerability · Source |
| CVE-2025-40342 | suse_vex | SUSE CVE CVE-2025-40342 | first fixed: 2 known affected: 663 known not affected: 20 recommended: 439 | 2026-08-06T01:39:42+00:00 | Vulnerability · Source |
| CVE-2025-40775 | suse_vex | SUSE CVE CVE-2025-40775 | known not affected: 325 recommended: 38 | 2026-08-06T01:39:37+00:00 | Vulnerability · Source |
| CVE-2025-40778 | suse_vex | SUSE CVE CVE-2025-40778 | known affected: 479 recommended: 412 | 2026-08-06T01:39:35+00:00 | Vulnerability · Source |
| CVE-2025-43440 | suse_vex | SUSE CVE CVE-2025-43440 | known affected: 124 known not affected: 8 recommended: 632 | 2026-08-06T01:39:33+00:00 | Vulnerability · Source |
| CVE-2025-43480 | suse_vex | SUSE CVE CVE-2025-43480 | known affected: 36 known not affected: 96 recommended: 632 | 2026-08-06T01:39:32+00:00 | Vulnerability · Source |
| CVE-2025-47287 | suse_vex | SUSE CVE CVE-2025-47287 | known affected: 412 known not affected: 24 recommended: 437 | 2026-08-06T01:39:30+00:00 | Vulnerability · Source |
| CVE-2025-47908 | suse_vex | SUSE CVE CVE-2025-47908 | known not affected: 152 recommended: 51 | 2026-08-06T01:39:28+00:00 | Vulnerability · Source |
| CVE-2025-49630 | suse_vex | SUSE CVE CVE-2025-49630 | known affected: 448 known not affected: 25 recommended: 262 | 2026-08-06T01:39:25+00:00 | Vulnerability · Source |
| CVE-2025-50106 | suse_vex | SUSE CVE CVE-2025-50106 | known affected: 522 recommended: 840 | 2026-08-06T01:39:22+00:00 | Vulnerability · Source |
| CVE-2025-53020 | suse_vex | SUSE CVE CVE-2025-53020 | known affected: 472 known not affected: 1 recommended: 263 | 2026-08-06T01:39:21+00:00 | Vulnerability · Source |
| CVE-2025-55752 | suse_vex | SUSE CVE CVE-2025-55752 | known affected: 455 known not affected: 19 recommended: 549 | 2026-08-06T01:39:16+00:00 | Vulnerability · Source |
| CVE-2025-55753 | suse_vex | SUSE CVE CVE-2025-55753 | known affected: 466 known not affected: 25 recommended: 200 | 2026-08-06T01:39:15+00:00 | Vulnerability · Source |
| CVE-2025-56005 | suse_vex | SUSE CVE CVE-2025-56005 | known not affected: 25 recommended: 2 | 2026-08-06T01:39:13+00:00 | Vulnerability · Source |
| CVE-2025-59375 | suse_vex | SUSE CVE CVE-2025-59375 | known affected: 381 recommended: 368 | 2026-08-06T01:39:11+00:00 | Vulnerability · Source |
| CVE-2025-61661 | suse_vex | SUSE CVE CVE-2025-61661 | known affected: 596 recommended: 302 | 2026-08-06T01:39:08+00:00 | Vulnerability · Source |
| CVE-2025-65082 | suse_vex | SUSE CVE CVE-2025-65082 | known affected: 490 known not affected: 1 recommended: 220 | 2026-08-06T01:39:03+00:00 | Vulnerability · Source |
| CVE-2025-69277 | suse_vex | SUSE CVE CVE-2025-69277 | known affected: 507 recommended: 57 | 2026-08-06T01:38:23+00:00 | Vulnerability · Source |
| CVE-2026-3644 | suse_vex | SUSE CVE CVE-2026-3644 | known affected: 450 recommended: 903 | 2026-08-06T01:37:54+00:00 | Vulnerability · Source |
| CVE-2026-4224 | suse_vex | SUSE CVE CVE-2026-4224 | known affected: 450 recommended: 903 | 2026-08-06T01:37:49+00:00 | Vulnerability · Source |
| CVE-2026-5402 | suse_vex | SUSE CVE CVE-2026-5402 | known not affected: 167 recommended: 42 | 2026-08-06T01:37:39+00:00 | Vulnerability · Source |
| CVE-2026-6525 | suse_vex | SUSE CVE CVE-2026-6525 | known not affected: 167 recommended: 42 | 2026-08-06T01:37:29+00:00 | Vulnerability · Source |
| CVE-2026-6536 | suse_vex | SUSE CVE CVE-2026-6536 | known not affected: 167 recommended: 42 | 2026-08-06T01:37:28+00:00 | Vulnerability · Source |
| CVE-2026-6867 | suse_vex | SUSE CVE CVE-2026-6867 | first fixed: 12 known affected: 73 known not affected: 29 recommended: 114 | 2026-08-06T01:37:26+00:00 | Vulnerability · Source |
| CVE-2026-6879 | suse_vex | SUSE CVE CVE-2026-6879 | known affected: 358 | 2026-08-06T01:37:25+00:00 | Vulnerability · Source |
| CVE-2026-7260 | suse_vex | SUSE CVE CVE-2026-7260 | first fixed: 106 known affected: 505 recommended: 1462 | 2026-08-06T01:37:21+00:00 | Vulnerability · Source |
| CVE-2026-7375 | suse_vex | SUSE CVE CVE-2026-7375 | first fixed: 12 known affected: 37 known not affected: 130 recommended: 48 | 2026-08-06T01:37:19+00:00 | Vulnerability · Source |
| CVE-2026-7376 | suse_vex | SUSE CVE CVE-2026-7376 | first fixed: 12 known affected: 169 known not affected: 29 recommended: 48 | 2026-08-06T01:37:18+00:00 | Vulnerability · Source |
| CVE-2026-7378 | suse_vex | SUSE CVE CVE-2026-7378 | first fixed: 12 known affected: 102 recommended: 114 | 2026-08-06T01:37:17+00:00 | Vulnerability · Source |
| CVE-2026-7379 | suse_vex | SUSE CVE CVE-2026-7379 | first fixed: 12 known affected: 99 recommended: 133 | 2026-08-06T01:37:16+00:00 | Vulnerability · Source |
| CVE-2026-9669 | suse_vex | SUSE CVE CVE-2026-9669 | known affected: 146 known not affected: 206 recommended: 7 | 2026-08-06T01:37:08+00:00 | Vulnerability · Source |
| CVE-2026-9759 | suse_vex | SUSE CVE CVE-2026-9759 | first fixed: 12 known affected: 13 known not affected: 148 recommended: 42 | 2026-08-06T01:37:04+00:00 | Vulnerability · Source |
| CVE-2026-10649 | suse_vex | SUSE CVE CVE-2026-10649 | known affected: 402 recommended: 99 | 2026-08-06T01:37:02+00:00 | Vulnerability · Source |
| CVE-2026-12246 | suse_vex | SUSE CVE CVE-2026-12246 | recommended: 3 | 2026-08-06T01:36:53+00:00 | Vulnerability · Source |
| CVE-2026-12259 | suse_vex | SUSE CVE CVE-2026-12259 | No product status | 2026-08-06T01:36:52+00:00 | Vulnerability · Source |
| CVE-2026-12289 | suse_vex | SUSE CVE CVE-2026-12289 | first fixed: 8 known affected: 30 recommended: 128 | 2026-08-06T01:36:50+00:00 | Vulnerability · Source |
| CVE-2026-17543 | suse_vex | SUSE CVE CVE-2026-17543 | first fixed: 106 known affected: 505 recommended: 1462 | 2026-08-06T01:35:05+00:00 | Vulnerability · Source |
| CVE-2026-17544 | suse_vex | SUSE CVE CVE-2026-17544 | first fixed: 106 known affected: 1754 recommended: 101 | 2026-08-06T01:35:04+00:00 | Vulnerability · Source |
| CVE-2026-17650 | suse_vex | SUSE CVE CVE-2026-17650 | recommended: 6 | 2026-08-06T01:35:02+00:00 | Vulnerability · Source |
| CVE-2026-17651 | suse_vex | SUSE CVE CVE-2026-17651 | recommended: 6 | 2026-08-06T01:35:01+00:00 | Vulnerability · Source |
| CVE-2026-17652 | suse_vex | SUSE CVE CVE-2026-17652 | recommended: 6 | 2026-08-06T01:35:00+00:00 | Vulnerability · Source |
| CVE-2026-17653 | suse_vex | SUSE CVE CVE-2026-17653 | recommended: 6 | 2026-08-06T01:34:59+00:00 | Vulnerability · Source |
| CVE-2026-17654 | suse_vex | SUSE CVE CVE-2026-17654 | recommended: 6 | 2026-08-06T01:34:58+00:00 | Vulnerability · Source |