VEX records
Browse vendor VEX statements available in this Vulnerability-Lookup instance and pivot to the related vulnerability.
292225 VEX records
API response| Vulnerability | Source | Title | Product status | Imported | Links |
|---|---|---|---|---|---|
| CVE-2026-8955 | suse_vex | SUSE CVE CVE-2026-8955 | known affected: 30 recommended: 125 | 2026-07-15T18:58:19+00:00 | Vulnerability · Source |
| CVE-2026-8959 | suse_vex | SUSE CVE CVE-2026-8959 | known affected: 30 recommended: 121 | 2026-07-15T18:58:18+00:00 | Vulnerability · Source |
| CVE-2026-15709 | suse_vex | SUSE CVE CVE-2026-15709 | known affected: 227 | 2026-07-15T18:57:36+00:00 | Vulnerability · Source |
| CVE-2026-15712 | suse_vex | SUSE CVE CVE-2026-15712 | known affected: 227 | 2026-07-15T18:57:35+00:00 | Vulnerability · Source |
| CVE-2026-15713 | suse_vex | SUSE CVE CVE-2026-15713 | known affected: 227 | 2026-07-15T18:57:34+00:00 | Vulnerability · Source |
| CVE-2026-15714 | suse_vex | SUSE CVE CVE-2026-15714 | known affected: 227 | 2026-07-15T18:57:32+00:00 | Vulnerability · Source |
| CVE-2026-20635 | suse_vex | SUSE CVE CVE-2026-20635 | known affected: 88 recommended: 503 | 2026-07-15T18:57:14+00:00 | Vulnerability · Source |
| CVE-2026-20636 | suse_vex | SUSE CVE CVE-2026-20636 | known affected: 88 recommended: 503 | 2026-07-15T18:57:13+00:00 | Vulnerability · Source |
| CVE-2026-20644 | suse_vex | SUSE CVE CVE-2026-20644 | known affected: 88 recommended: 503 | 2026-07-15T18:57:12+00:00 | Vulnerability · Source |
| CVE-2026-20652 | suse_vex | SUSE CVE CVE-2026-20652 | known affected: 88 recommended: 503 | 2026-07-15T18:57:11+00:00 | Vulnerability · Source |
| CVE-2026-20664 | suse_vex | SUSE CVE CVE-2026-20664 | known affected: 122 recommended: 311 | 2026-07-15T18:57:10+00:00 | Vulnerability · Source |
| CVE-2026-21413 | suse_vex | SUSE CVE CVE-2026-21413 | known not affected: 7 recommended: 44 | 2026-07-15T18:57:07+00:00 | Vulnerability · Source |
| CVE-2026-23401 | suse_vex | SUSE CVE CVE-2026-23401 | first fixed: 2 known affected: 213 known not affected: 96 recommended: 250 | 2026-07-15T18:56:35+00:00 | Vulnerability · Source |
| CVE-2026-24486 | suse_vex | SUSE CVE CVE-2026-24486 | recommended: 4 | 2026-07-15T18:56:24+00:00 | Vulnerability · Source |
| CVE-2026-24733 | suse_vex | SUSE CVE CVE-2026-24733 | known affected: 79 recommended: 423 | 2026-07-15T18:56:23+00:00 | Vulnerability · Source |
| CVE-2026-24734 | suse_vex | SUSE CVE CVE-2026-24734 | known affected: 28 known not affected: 70 recommended: 413 | 2026-07-15T18:56:21+00:00 | Vulnerability · Source |
| CVE-2026-24881 | suse_vex | SUSE CVE CVE-2026-24881 | known not affected: 96 recommended: 4 | 2026-07-15T18:56:19+00:00 | Vulnerability · Source |
| CVE-2026-26130 | suse_vex | SUSE CVE CVE-2026-26130 | recommended: 121 | 2026-07-15T18:56:07+00:00 | Vulnerability · Source |
| CVE-2026-27654 | suse_vex | SUSE CVE CVE-2026-27654 | known affected: 406 recommended: 73 | 2026-07-15T18:55:51+00:00 | Vulnerability · Source |
| CVE-2026-27784 | suse_vex | SUSE CVE CVE-2026-27784 | known affected: 406 recommended: 73 | 2026-07-15T18:55:50+00:00 | Vulnerability · Source |
| CVE-2026-27857 | suse_vex | SUSE CVE CVE-2026-27857 | known affected: 215 known not affected: 34 recommended: 59 | 2026-07-15T18:55:49+00:00 | Vulnerability · Source |
| CVE-2026-27858 | suse_vex | SUSE CVE CVE-2026-27858 | known affected: 215 known not affected: 34 recommended: 59 | 2026-07-15T18:55:48+00:00 | Vulnerability · Source |
| CVE-2026-28857 | suse_vex | SUSE CVE CVE-2026-28857 | known affected: 122 recommended: 311 | 2026-07-15T18:55:39+00:00 | Vulnerability · Source |
| CVE-2026-28859 | suse_vex | SUSE CVE CVE-2026-28859 | known affected: 122 recommended: 311 | 2026-07-15T18:55:38+00:00 | Vulnerability · Source |
| CVE-2026-29181 | suse_vex | SUSE CVE CVE-2026-29181 | recommended: 7 | 2026-07-15T18:55:30+00:00 | Vulnerability · Source |
| CVE-2026-32647 | suse_vex | SUSE CVE CVE-2026-32647 | known affected: 406 recommended: 73 | 2026-07-15T18:54:41+00:00 | Vulnerability · Source |
| CVE-2026-34588 | suse_vex | SUSE CVE CVE-2026-34588 | known not affected: 108 recommended: 61 | 2026-07-15T18:54:12+00:00 | Vulnerability · Source |
| CVE-2026-40169 | suse_vex | SUSE CVE CVE-2026-40169 | known affected: 75 known not affected: 42 recommended: 229 | 2026-07-15T18:53:37+00:00 | Vulnerability · Source |
| CVE-2026-40499 | suse_vex | SUSE CVE CVE-2026-40499 | recommended: 12 | 2026-07-15T18:53:35+00:00 | Vulnerability · Source |
| CVE-2026-40510 | suse_vex | SUSE CVE CVE-2026-40510 | known affected: 38 | 2026-07-15T18:53:34+00:00 | Vulnerability · Source |
| CVE-2026-41445 | suse_vex | SUSE CVE CVE-2026-41445 | recommended: 3 | 2026-07-15T18:53:27+00:00 | Vulnerability · Source |
| CVE-2026-41470 | suse_vex | SUSE CVE CVE-2026-41470 | recommended: 6 | 2026-07-15T18:53:26+00:00 | Vulnerability · Source |
| CVE-2026-41651 | suse_vex | SUSE CVE CVE-2026-41651 | known affected: 446 recommended: 202 | 2026-07-15T18:53:17+00:00 | Vulnerability · Source |
| CVE-2026-42050 | suse_vex | SUSE CVE CVE-2026-42050 | known affected: 85 recommended: 269 | 2026-07-15T18:53:05+00:00 | Vulnerability · Source |
| CVE-2026-42326 | suse_vex | SUSE CVE CVE-2026-42326 | known affected: 85 known not affected: 8 recommended: 245 | 2026-07-15T18:53:01+00:00 | Vulnerability · Source |
| CVE-2026-42371 | suse_vex | SUSE CVE CVE-2026-42371 | first fixed: 8 known affected: 13 recommended: 58 | 2026-07-15T18:52:59+00:00 | Vulnerability · Source |
| CVE-2026-42496 | suse_vex | SUSE CVE CVE-2026-42496 | recommended: 224 | 2026-07-15T18:52:57+00:00 | Vulnerability · Source |
| CVE-2026-44169 | suse_vex | SUSE CVE CVE-2026-44169 | known affected: 409 known not affected: 183 recommended: 107 | 2026-07-15T18:51:59+00:00 | Vulnerability · Source |
| CVE-2026-44927 | suse_vex | SUSE CVE CVE-2026-44927 | first fixed: 8 known affected: 1667 recommended: 58 | 2026-07-15T18:51:47+00:00 | Vulnerability · Source |
| CVE-2026-44928 | suse_vex | SUSE CVE CVE-2026-44928 | first fixed: 8 known affected: 1667 recommended: 58 | 2026-07-15T18:51:45+00:00 | Vulnerability · Source |
| CVE-2026-45358 | suse_vex | SUSE CVE CVE-2026-45358 | known affected: 158 known not affected: 8 recommended: 157 | 2026-07-15T18:51:43+00:00 | Vulnerability · Source |
| CVE-2026-45359 | suse_vex | SUSE CVE CVE-2026-45359 | known affected: 75 known not affected: 34 recommended: 229 | 2026-07-15T18:51:41+00:00 | Vulnerability · Source |
| CVE-2026-45363 | suse_vex | SUSE CVE CVE-2026-45363 | No product status | 2026-07-15T18:51:40+00:00 | Vulnerability · Source |
| CVE-2026-45624 | suse_vex | SUSE CVE CVE-2026-45624 | known affected: 101 known not affected: 8 recommended: 245 | 2026-07-15T18:51:38+00:00 | Vulnerability · Source |
| CVE-2026-45664 | suse_vex | SUSE CVE CVE-2026-45664 | known affected: 85 known not affected: 8 recommended: 245 | 2026-07-15T18:51:37+00:00 | Vulnerability · Source |
| CVE-2026-45907 | suse_vex | SUSE CVE CVE-2026-45907 | known not affected: 291 | 2026-07-15T18:51:30+00:00 | Vulnerability · Source |
| CVE-2026-46520 | suse_vex | SUSE CVE CVE-2026-46520 | known affected: 101 known not affected: 8 recommended: 245 | 2026-07-15T18:50:49+00:00 | Vulnerability · Source |
| CVE-2026-46521 | suse_vex | SUSE CVE CVE-2026-46521 | known affected: 85 known not affected: 8 recommended: 230 | 2026-07-15T18:50:48+00:00 | Vulnerability · Source |
| CVE-2026-46522 | suse_vex | SUSE CVE CVE-2026-46522 | known affected: 101 known not affected: 8 recommended: 245 | 2026-07-15T18:50:47+00:00 | Vulnerability · Source |
| CVE-2026-46523 | suse_vex | SUSE CVE CVE-2026-46523 | known affected: 101 recommended: 269 | 2026-07-15T18:50:46+00:00 | Vulnerability · Source |