VEX records
Browse vendor VEX statements available in this Vulnerability-Lookup instance and pivot to the related vulnerability.
290590 VEX records
API response| Vulnerability | Source | Title | Product status | Imported | Links |
|---|---|---|---|---|---|
| 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 |
| CVE-2026-43964 | suse_vex | SUSE CVE CVE-2026-43964 | known affected: 95 recommended: 104 | 2026-08-07T00:05:43+00:00 | Vulnerability · Source |
| CVE-2026-44210 | suse_vex | SUSE CVE CVE-2026-44210 | No product status | 2026-08-07T00:05:41+00:00 | Vulnerability · Source |
| CVE-2026-54465 | suse_vex | SUSE CVE CVE-2026-54465 | known affected: 14 known not affected: 377 | 2026-08-07T00:02:56+00:00 | Vulnerability · Source |
| CVE-2026-54466 | suse_vex | SUSE CVE CVE-2026-54466 | known affected: 11 known not affected: 298 recommended: 1 | 2026-08-07T00:02:54+00:00 | Vulnerability · Source |
| CVE-2026-54513 | suse_vex | SUSE CVE CVE-2026-54513 | known affected: 6 recommended: 147 | 2026-08-07T00:02:52+00:00 | Vulnerability · Source |
| CVE-2026-54522 | suse_vex | SUSE CVE CVE-2026-54522 | No product status | 2026-08-07T00:02:50+00:00 | Vulnerability · Source |
| CVE-2026-54876 | suse_vex | SUSE CVE CVE-2026-54876 | known not affected: 486 | 2026-08-07T00:02:47+00:00 | Vulnerability · Source |
| CVE-2026-57062 | suse_vex | SUSE CVE CVE-2026-57062 | known affected: 411 known not affected: 56 recommended: 33 | 2026-08-07T00:02:18+00:00 | Vulnerability · Source |
| CVE-2026-59676 | suse_vex | SUSE CVE CVE-2026-59676 | known affected: 184 | 2026-08-07T00:01:37+00:00 | Vulnerability · Source |
| CVE-2026-59677 | suse_vex | SUSE CVE CVE-2026-59677 | known affected: 184 | 2026-08-07T00:01:35+00:00 | Vulnerability · Source |
| CVE-2026-59856 | suse_vex | SUSE CVE CVE-2026-59856 | first fixed: 2 known affected: 442 recommended: 150 | 2026-08-07T00:01:17+00:00 | Vulnerability · Source |
| CVE-2026-59857 | suse_vex | SUSE CVE CVE-2026-59857 | first fixed: 2 known affected: 442 recommended: 138 | 2026-08-07T00:01:15+00:00 | Vulnerability · Source |
| CVE-2026-59858 | suse_vex | SUSE CVE CVE-2026-59858 | first fixed: 2 known affected: 442 recommended: 155 | 2026-08-07T00:01:13+00:00 | Vulnerability · Source |
| CVE-2026-62423 | suse_vex | SUSE CVE CVE-2026-62423 | first fixed: 26 known affected: 456 recommended: 108 | 2026-08-07T00:00:57+00:00 | Vulnerability · Source |
| CVE-2026-62424 | suse_vex | SUSE CVE CVE-2026-62424 | first fixed: 26 known affected: 62 recommended: 101 | 2026-08-07T00:00:55+00:00 | Vulnerability · Source |
| CVE-2026-62425 | suse_vex | SUSE CVE CVE-2026-62425 | first fixed: 26 known affected: 62 recommended: 101 | 2026-08-07T00:00:53+00:00 | Vulnerability · Source |
| CVE-2026-62426 | suse_vex | SUSE CVE CVE-2026-62426 | first fixed: 26 known affected: 456 recommended: 108 | 2026-08-07T00:00:51+00:00 | Vulnerability · Source |
| CVE-2026-62427 | suse_vex | SUSE CVE CVE-2026-62427 | first fixed: 26 known affected: 62 recommended: 101 | 2026-08-07T00:00:49+00:00 | Vulnerability · Source |
| CVE-2026-62428 | suse_vex | SUSE CVE CVE-2026-62428 | first fixed: 26 known affected: 456 recommended: 108 | 2026-08-07T00:00:47+00:00 | Vulnerability · Source |