VEX records
Browse vendor VEX statements available in this Vulnerability-Lookup instance and pivot to the related vulnerability.
288586 VEX records
API response| Vulnerability | Source | Title | Product status | Imported | Links |
|---|---|---|---|---|---|
| CVE-2023-53417 | suse_vex | SUSE CVE CVE-2023-53417 | known affected: 354 known not affected: 298 recommended: 196 | 2026-08-03T23:59:47+00:00 | Vulnerability · Source |
| CVE-2024-25744 | suse_vex | SUSE CVE CVE-2024-25744 | known affected: 300 known not affected: 323 recommended: 586 | 2026-08-03T23:59:29+00:00 | Vulnerability · Source |
| CVE-2024-26736 | suse_vex | SUSE CVE CVE-2024-26736 | known affected: 394 known not affected: 268 recommended: 456 | 2026-08-03T23:59:24+00:00 | Vulnerability · Source |
| CVE-2024-28180 | suse_vex | SUSE CVE CVE-2024-28180 | known affected: 29 known not affected: 672 recommended: 285 | 2026-08-03T23:59:17+00:00 | Vulnerability · Source |
| CVE-2024-50038 | suse_vex | SUSE CVE CVE-2024-50038 | known affected: 623 recommended: 526 | 2026-08-03T23:58:48+00:00 | Vulnerability · Source |
| CVE-2024-56611 | suse_vex | SUSE CVE CVE-2024-56611 | known affected: 733 known not affected: 36 recommended: 406 | 2026-08-03T23:58:33+00:00 | Vulnerability · Source |
| CVE-2025-3029 | suse_vex | SUSE CVE CVE-2025-3029 | known affected: 37 recommended: 142 | 2026-08-03T23:58:14+00:00 | Vulnerability · Source |
| CVE-2025-6176 | suse_vex | SUSE CVE CVE-2025-6176 | known not affected: 58 recommended: 22 | 2026-08-03T23:58:05+00:00 | Vulnerability · Source |
| CVE-2025-23393 | suse_vex | SUSE CVE CVE-2025-23393 | known affected: 394 recommended: 68 | 2026-08-03T23:57:44+00:00 | Vulnerability · Source |
| CVE-2025-68299 | suse_vex | SUSE CVE CVE-2025-68299 | known not affected: 418 | 2026-08-03T23:55:53+00:00 | Vulnerability · Source |
| CVE-2025-68470 | suse_vex | SUSE CVE CVE-2025-68470 | known not affected: 6 | 2026-08-03T23:55:49+00:00 | Vulnerability · Source |
| CVE-2026-0685 | suse_vex | SUSE CVE CVE-2026-0685 | known not affected: 25 | 2026-08-03T23:55:29+00:00 | Vulnerability · Source |
| CVE-2026-1519 | suse_vex | SUSE CVE CVE-2026-1519 | known affected: 464 known not affected: 13 recommended: 308 | 2026-08-03T23:55:23+00:00 | Vulnerability · Source |
| CVE-2026-5160 | suse_vex | SUSE CVE CVE-2026-5160 | first fixed: 2 known affected: 4 recommended: 9 | 2026-08-03T23:55:08+00:00 | Vulnerability · Source |
| CVE-2026-6473 | suse_vex | SUSE CVE CVE-2026-6473 | known affected: 574 known not affected: 266 recommended: 1149 | 2026-08-03T23:54:54+00:00 | Vulnerability · Source |
| CVE-2026-6478 | suse_vex | SUSE CVE CVE-2026-6478 | known affected: 574 known not affected: 266 recommended: 1149 | 2026-08-03T23:54:48+00:00 | Vulnerability · Source |
| CVE-2026-6659 | suse_vex | SUSE CVE CVE-2026-6659 | recommended: 2 | 2026-08-03T23:54:46+00:00 | Vulnerability · Source |
| CVE-2026-6694 | suse_vex | SUSE CVE CVE-2026-6694 | known not affected: 26 | 2026-08-03T23:54:44+00:00 | Vulnerability · Source |
| CVE-2026-6695 | suse_vex | SUSE CVE CVE-2026-6695 | known not affected: 26 | 2026-08-03T23:54:43+00:00 | Vulnerability · Source |
| CVE-2026-8484 | suse_vex | SUSE CVE CVE-2026-8484 | known affected: 39 | 2026-08-03T23:54:36+00:00 | Vulnerability · Source |
| CVE-2026-12290 | suse_vex | SUSE CVE CVE-2026-12290 | first fixed: 8 known affected: 30 recommended: 128 | 2026-08-03T23:54:03+00:00 | Vulnerability · Source |
| CVE-2026-12291 | suse_vex | SUSE CVE CVE-2026-12291 | first fixed: 8 known affected: 30 recommended: 128 | 2026-08-03T23:54:01+00:00 | Vulnerability · Source |
| CVE-2026-12292 | suse_vex | SUSE CVE CVE-2026-12292 | first fixed: 8 known affected: 30 recommended: 128 | 2026-08-03T23:53:59+00:00 | Vulnerability · Source |
| CVE-2026-12294 | suse_vex | SUSE CVE CVE-2026-12294 | first fixed: 8 known affected: 30 recommended: 128 | 2026-08-03T23:53:57+00:00 | Vulnerability · Source |
| CVE-2026-12295 | suse_vex | SUSE CVE CVE-2026-12295 | first fixed: 8 known affected: 30 recommended: 128 | 2026-08-03T23:53:56+00:00 | Vulnerability · Source |
| CVE-2026-12296 | suse_vex | SUSE CVE CVE-2026-12296 | first fixed: 8 known affected: 30 recommended: 128 | 2026-08-03T23:53:54+00:00 | Vulnerability · Source |
| CVE-2026-12297 | suse_vex | SUSE CVE CVE-2026-12297 | first fixed: 8 known affected: 30 recommended: 128 | 2026-08-03T23:53:52+00:00 | Vulnerability · Source |
| CVE-2026-12298 | suse_vex | SUSE CVE CVE-2026-12298 | first fixed: 8 known affected: 30 recommended: 128 | 2026-08-03T23:53:50+00:00 | Vulnerability · Source |
| CVE-2026-12299 | suse_vex | SUSE CVE CVE-2026-12299 | first fixed: 8 known affected: 30 recommended: 128 | 2026-08-03T23:53:48+00:00 | Vulnerability · Source |
| CVE-2026-12302 | suse_vex | SUSE CVE CVE-2026-12302 | first fixed: 8 known affected: 30 recommended: 128 | 2026-08-03T23:53:47+00:00 | Vulnerability · Source |
| CVE-2026-12304 | suse_vex | SUSE CVE CVE-2026-12304 | first fixed: 8 known affected: 30 recommended: 128 | 2026-08-03T23:53:45+00:00 | Vulnerability · Source |
| CVE-2026-12305 | suse_vex | SUSE CVE CVE-2026-12305 | first fixed: 8 known affected: 30 recommended: 128 | 2026-08-03T23:53:43+00:00 | Vulnerability · Source |
| CVE-2026-12306 | suse_vex | SUSE CVE CVE-2026-12306 | first fixed: 8 known affected: 30 recommended: 128 | 2026-08-03T23:53:41+00:00 | Vulnerability · Source |
| CVE-2026-12307 | suse_vex | SUSE CVE CVE-2026-12307 | first fixed: 8 known affected: 30 recommended: 128 | 2026-08-03T23:53:40+00:00 | Vulnerability · Source |
| CVE-2026-12308 | suse_vex | SUSE CVE CVE-2026-12308 | first fixed: 8 known affected: 30 recommended: 128 | 2026-08-03T23:53:38+00:00 | Vulnerability · Source |
| CVE-2026-12309 | suse_vex | SUSE CVE CVE-2026-12309 | first fixed: 8 known affected: 30 recommended: 128 | 2026-08-03T23:53:36+00:00 | Vulnerability · Source |
| CVE-2026-12310 | suse_vex | SUSE CVE CVE-2026-12310 | first fixed: 8 known affected: 30 recommended: 128 | 2026-08-03T23:53:34+00:00 | Vulnerability · Source |
| CVE-2026-12311 | suse_vex | SUSE CVE CVE-2026-12311 | first fixed: 8 known affected: 30 recommended: 128 | 2026-08-03T23:53:33+00:00 | Vulnerability · Source |
| CVE-2026-12312 | suse_vex | SUSE CVE CVE-2026-12312 | first fixed: 8 known affected: 30 recommended: 128 | 2026-08-03T23:53:31+00:00 | Vulnerability · Source |
| CVE-2026-12313 | suse_vex | SUSE CVE CVE-2026-12313 | first fixed: 8 known affected: 30 recommended: 128 | 2026-08-03T23:53:29+00:00 | Vulnerability · Source |
| CVE-2026-12314 | suse_vex | SUSE CVE CVE-2026-12314 | first fixed: 8 known affected: 30 recommended: 128 | 2026-08-03T23:53:27+00:00 | Vulnerability · Source |
| CVE-2026-12315 | suse_vex | SUSE CVE CVE-2026-12315 | first fixed: 8 known affected: 30 recommended: 128 | 2026-08-03T23:53:26+00:00 | Vulnerability · Source |
| CVE-2026-12324 | suse_vex | SUSE CVE CVE-2026-12324 | first fixed: 8 known affected: 30 recommended: 128 | 2026-08-03T23:53:24+00:00 | Vulnerability · Source |
| CVE-2026-12325 | suse_vex | SUSE CVE CVE-2026-12325 | first fixed: 8 known affected: 30 recommended: 128 | 2026-08-03T23:53:23+00:00 | Vulnerability · Source |
| CVE-2026-12327 | suse_vex | SUSE CVE CVE-2026-12327 | first fixed: 8 known affected: 30 recommended: 128 | 2026-08-03T23:53:21+00:00 | Vulnerability · Source |
| CVE-2026-12328 | suse_vex | SUSE CVE CVE-2026-12328 | first fixed: 8 known affected: 30 recommended: 128 | 2026-08-03T23:53:20+00:00 | Vulnerability · Source |
| CVE-2026-12329 | suse_vex | SUSE CVE CVE-2026-12329 | first fixed: 8 known affected: 30 recommended: 123 | 2026-08-03T23:53:18+00:00 | Vulnerability · Source |
| CVE-2026-12330 | suse_vex | SUSE CVE CVE-2026-12330 | first fixed: 8 known affected: 30 recommended: 123 | 2026-08-03T23:53:16+00:00 | Vulnerability · Source |
| CVE-2026-13595 | suse_vex | SUSE CVE CVE-2026-13595 | known affected: 457 recommended: 27 | 2026-08-03T23:52:47+00:00 | Vulnerability · Source |
| CVE-2026-15043 | suse_vex | SUSE CVE CVE-2026-15043 | known affected: 10 recommended: 28 | 2026-08-03T23:52:36+00:00 | Vulnerability · Source |