VEX records
Browse vendor VEX statements available in this Vulnerability-Lookup instance and pivot to the related vulnerability.
291348 VEX records
API response| Vulnerability | Source | Title | Product status | Imported | Links |
|---|---|---|---|---|---|
| CVE-2025-49010 | suse_vex | SUSE CVE CVE-2025-49010 | known affected: 404 recommended: 38 | 2026-08-07T00:15:58+00:00 | Vulnerability · Source |
| CVE-2025-58098 | suse_vex | SUSE CVE CVE-2025-58098 | known affected: 491 recommended: 228 | 2026-08-07T00:15:45+00:00 | Vulnerability · Source |
| CVE-2025-61663 | suse_vex | SUSE CVE CVE-2025-61663 | known affected: 596 recommended: 302 | 2026-08-07T00:15:35+00:00 | Vulnerability · Source |
| CVE-2025-68276 | suse_vex | SUSE CVE CVE-2025-68276 | known affected: 711 recommended: 368 | 2026-08-07T00:15:22+00:00 | Vulnerability · Source |
| CVE-2025-68468 | suse_vex | SUSE CVE CVE-2025-68468 | known affected: 711 recommended: 368 | 2026-08-07T00:15:18+00:00 | Vulnerability · Source |
| CVE-2025-68480 | suse_vex | SUSE CVE CVE-2025-68480 | known affected: 394 recommended: 32 | 2026-08-07T00:15:16+00:00 | Vulnerability · Source |
| CVE-2025-69225 | suse_vex | SUSE CVE CVE-2025-69225 | known affected: 394 recommended: 53 | 2026-08-07T00:15:11+00:00 | Vulnerability · Source |
| CVE-2025-70103 | suse_vex | SUSE CVE CVE-2025-70103 | known affected: 158 recommended: 49 | 2026-08-07T00:15:07+00:00 | Vulnerability · Source |
| CVE-2025-70873 | suse_vex | SUSE CVE CVE-2025-70873 | known affected: 465 known not affected: 98 recommended: 134 | 2026-08-07T00:15:05+00:00 | Vulnerability · Source |
| CVE-2026-0994 | suse_vex | SUSE CVE CVE-2026-0994 | known affected: 456 recommended: 177 | 2026-08-07T00:14:55+00:00 | Vulnerability · Source |
| CVE-2026-4539 | suse_vex | SUSE CVE CVE-2026-4539 | known affected: 466 recommended: 28 | 2026-08-07T00:14:26+00:00 | Vulnerability · Source |
| CVE-2026-6477 | suse_vex | SUSE CVE CVE-2026-6477 | known affected: 574 known not affected: 266 recommended: 1153 | 2026-08-07T00:14:06+00:00 | Vulnerability · Source |
| CVE-2026-6893 | suse_vex | SUSE CVE CVE-2026-6893 | known affected: 414 known not affected: 13 recommended: 134 | 2026-08-07T00:14:00+00:00 | Vulnerability · Source |
| CVE-2026-9323 | suse_vex | SUSE CVE CVE-2026-9323 | known affected: 394 recommended: 37 | 2026-08-07T00:13:37+00:00 | Vulnerability · Source |
| CVE-2026-11979 | suse_vex | SUSE CVE CVE-2026-11979 | known affected: 436 known not affected: 14 recommended: 171 | 2026-08-07T00:13:10+00:00 | Vulnerability · Source |
| CVE-2026-14474 | suse_vex | SUSE CVE CVE-2026-14474 | known affected: 199 recommended: 740 | 2026-08-07T00:12:53+00:00 | Vulnerability · Source |
| CVE-2026-14476 | suse_vex | SUSE CVE CVE-2026-14476 | known affected: 199 recommended: 740 | 2026-08-07T00:12:51+00:00 | Vulnerability · Source |
| CVE-2026-14741 | suse_vex | SUSE CVE CVE-2026-14741 | known affected: 415 recommended: 13 | 2026-08-07T00:12:48+00:00 | Vulnerability · Source |
| CVE-2026-15165 | suse_vex | SUSE CVE CVE-2026-15165 | known affected: 13 known not affected: 136 recommended: 36 | 2026-08-07T00:12:42+00:00 | Vulnerability · Source |
| CVE-2026-15173 | suse_vex | SUSE CVE CVE-2026-15173 | known affected: 13 known not affected: 136 recommended: 36 | 2026-08-07T00:12:37+00:00 | Vulnerability · Source |
| CVE-2026-18839 | suse_vex | SUSE CVE CVE-2026-18839 | known affected: 129 | 2026-08-07T00:10:53+00:00 | Vulnerability · Source |
| CVE-2026-19023 | suse_vex | SUSE CVE CVE-2026-19023 | No product status | 2026-08-07T00:10:51+00:00 | Vulnerability · Source |
| CVE-2026-19024 | suse_vex | SUSE CVE CVE-2026-19024 | No product status | 2026-08-07T00:10:49+00:00 | Vulnerability · Source |
| CVE-2026-19025 | suse_vex | SUSE CVE CVE-2026-19025 | No product status | 2026-08-07T00:10:47+00:00 | Vulnerability · Source |
| CVE-2026-19026 | suse_vex | SUSE CVE CVE-2026-19026 | No product status | 2026-08-07T00:10:45+00:00 | Vulnerability · Source |
| CVE-2026-19027 | suse_vex | SUSE CVE CVE-2026-19027 | No product status | 2026-08-07T00:10:43+00:00 | Vulnerability · Source |
| CVE-2026-19028 | suse_vex | SUSE CVE CVE-2026-19028 | No product status | 2026-08-07T00:10:41+00:00 | Vulnerability · Source |
| CVE-2026-21895 | suse_vex | SUSE CVE CVE-2026-21895 | known affected: 3 known not affected: 107 recommended: 13 | 2026-08-07T00:10:38+00:00 | Vulnerability · Source |
| CVE-2026-23393 | suse_vex | SUSE CVE CVE-2026-23393 | first fixed: 2 known affected: 403 known not affected: 112 recommended: 639 | 2026-08-07T00:10:06+00:00 | Vulnerability · Source |
| CVE-2026-23553 | suse_vex | SUSE CVE CVE-2026-23553 | known affected: 496 recommended: 106 | 2026-08-07T00:09:54+00:00 | Vulnerability · Source |
| CVE-2026-23554 | suse_vex | SUSE CVE CVE-2026-23554 | known affected: 376 known not affected: 106 recommended: 96 | 2026-08-07T00:09:51+00:00 | Vulnerability · Source |
| CVE-2026-23555 | suse_vex | SUSE CVE CVE-2026-23555 | known affected: 394 known not affected: 132 recommended: 53 | 2026-08-07T00:09:50+00:00 | Vulnerability · Source |
| CVE-2026-23557 | suse_vex | SUSE CVE CVE-2026-23557 | known affected: 428 recommended: 141 | 2026-08-07T00:09:48+00:00 | Vulnerability · Source |
| CVE-2026-23558 | suse_vex | SUSE CVE CVE-2026-23558 | known affected: 428 recommended: 141 | 2026-08-07T00:09:45+00:00 | Vulnerability · Source |
| CVE-2026-27448 | suse_vex | SUSE CVE CVE-2026-27448 | known affected: 433 recommended: 60 | 2026-08-07T00:09:29+00:00 | Vulnerability · Source |
| CVE-2026-31504 | suse_vex | SUSE CVE CVE-2026-31504 | first fixed: 2 known affected: 456 known not affected: 4 recommended: 719 | 2026-08-07T00:09:05+00:00 | Vulnerability · Source |
| CVE-2026-31554 | suse_vex | SUSE CVE CVE-2026-31554 | first fixed: 2 known affected: 394 known not affected: 300 recommended: 220 | 2026-08-07T00:08:56+00:00 | Vulnerability · Source |
| CVE-2026-40011 | suse_vex | SUSE CVE CVE-2026-40011 | first fixed: 2 known affected: 23 known not affected: 3 recommended: 2 | 2026-08-07T00:07:55+00:00 | Vulnerability · Source |
| CVE-2026-40209 | suse_vex | SUSE CVE CVE-2026-40209 | first fixed: 2 known affected: 23 known not affected: 3 recommended: 2 | 2026-08-07T00:07:52+00:00 | Vulnerability · Source |
| CVE-2026-40210 | suse_vex | SUSE CVE CVE-2026-40210 | first fixed: 2 known affected: 23 known not affected: 3 recommended: 2 | 2026-08-07T00:07:50+00:00 | Vulnerability · Source |
| CVE-2026-40211 | suse_vex | SUSE CVE CVE-2026-40211 | first fixed: 2 known affected: 23 known not affected: 3 recommended: 2 | 2026-08-07T00:07:48+00:00 | Vulnerability · Source |
| CVE-2026-40355 | suse_vex | SUSE CVE CVE-2026-40355 | known affected: 457 known not affected: 69 recommended: 157 | 2026-08-07T00:07:45+00:00 | Vulnerability · Source |
| CVE-2026-40356 | suse_vex | SUSE CVE CVE-2026-40356 | known affected: 457 known not affected: 69 recommended: 157 | 2026-08-07T00:07:42+00:00 | Vulnerability · Source |
| CVE-2026-41991 | suse_vex | SUSE CVE CVE-2026-41991 | known affected: 402 known not affected: 4 recommended: 33 | 2026-08-07T00:07:18+00:00 | Vulnerability · Source |
| CVE-2026-42004 | suse_vex | SUSE CVE CVE-2026-42004 | first fixed: 2 known affected: 23 known not affected: 3 recommended: 2 | 2026-08-07T00:07:16+00:00 | Vulnerability · Source |
| CVE-2026-42005 | suse_vex | SUSE CVE CVE-2026-42005 | first fixed: 2 known affected: 23 known not affected: 3 recommended: 2 | 2026-08-07T00:07:14+00:00 | Vulnerability · Source |
| CVE-2026-42304 | suse_vex | SUSE CVE CVE-2026-42304 | known affected: 406 recommended: 219 | 2026-08-07T00:07:06+00:00 | Vulnerability · Source |
| CVE-2026-42493 | suse_vex | SUSE CVE CVE-2026-42493 | first fixed: 26 known affected: 456 recommended: 108 | 2026-08-07T00:07:02+00:00 | Vulnerability · Source |
| CVE-2026-42494 | suse_vex | SUSE CVE CVE-2026-42494 | first fixed: 26 known affected: 456 recommended: 108 | 2026-08-07T00:07:01+00:00 | Vulnerability · Source |
| CVE-2026-42495 | suse_vex | SUSE CVE CVE-2026-42495 | first fixed: 26 known affected: 62 recommended: 101 | 2026-08-07T00:06:59+00:00 | Vulnerability · Source |