VEX records
Browse vendor VEX statements available in this Vulnerability-Lookup instance and pivot to the related vulnerability.
291935 VEX records
API response| Vulnerability | Source | Title | Product status | Imported | Links |
|---|---|---|---|---|---|
| CVE-2025-4086 | suse_vex | SUSE CVE CVE-2025-4086 | known affected: 69 recommended: 9 | 2026-07-26T16:43:54+00:00 | Vulnerability · Source |
| CVE-2025-4087 | suse_vex | SUSE CVE CVE-2025-4087 | known affected: 69 recommended: 117 | 2026-07-26T16:43:53+00:00 | Vulnerability · Source |
| CVE-2025-4092 | suse_vex | SUSE CVE CVE-2025-4092 | known affected: 69 recommended: 9 | 2026-07-26T16:43:51+00:00 | Vulnerability · Source |
| CVE-2025-4802 | suse_vex | SUSE CVE CVE-2025-4802 | known affected: 339 known not affected: 169 recommended: 957 | 2026-07-26T16:43:50+00:00 | Vulnerability · Source |
| CVE-2025-5271 | suse_vex | SUSE CVE CVE-2025-5271 | known affected: 37 recommended: 9 | 2026-07-26T16:43:48+00:00 | Vulnerability · Source |
| CVE-2025-5745 | suse_vex | SUSE CVE CVE-2025-5745 | known not affected: 516 recommended: 38 | 2026-07-26T16:43:45+00:00 | Vulnerability · Source |
| CVE-2025-5914 | suse_vex | SUSE CVE CVE-2025-5914 | known affected: 453 known not affected: 52 recommended: 97 | 2026-07-26T16:43:44+00:00 | Vulnerability · Source |
| CVE-2025-6075 | suse_vex | SUSE CVE CVE-2025-6075 | known affected: 541 recommended: 947 | 2026-07-26T16:43:40+00:00 | Vulnerability · Source |
| CVE-2025-7345 | suse_vex | SUSE CVE CVE-2025-7345 | known affected: 509 known not affected: 1004 recommended: 349 | 2026-07-26T16:43:38+00:00 | Vulnerability · Source |
| CVE-2025-8043 | suse_vex | SUSE CVE CVE-2025-8043 | known affected: 37 recommended: 9 | 2026-07-26T16:43:35+00:00 | Vulnerability · Source |
| CVE-2025-8044 | suse_vex | SUSE CVE CVE-2025-8044 | known affected: 37 recommended: 9 | 2026-07-26T16:43:33+00:00 | Vulnerability · Source |
| CVE-2025-9186 | suse_vex | SUSE CVE CVE-2025-9186 | known affected: 37 recommended: 9 | 2026-07-26T16:43:31+00:00 | Vulnerability · Source |
| CVE-2025-9187 | suse_vex | SUSE CVE CVE-2025-9187 | known affected: 37 recommended: 506 | 2026-07-26T16:43:30+00:00 | Vulnerability · Source |
| CVE-2025-10530 | suse_vex | SUSE CVE CVE-2025-10530 | known affected: 37 recommended: 9 | 2026-07-26T16:43:28+00:00 | Vulnerability · Source |
| CVE-2025-10534 | suse_vex | SUSE CVE CVE-2025-10534 | known affected: 37 recommended: 9 | 2026-07-26T16:43:26+00:00 | Vulnerability · Source |
| CVE-2025-11720 | suse_vex | SUSE CVE CVE-2025-11720 | known affected: 70 recommended: 9 | 2026-07-26T16:43:24+00:00 | Vulnerability · Source |
| CVE-2025-12380 | suse_vex | SUSE CVE CVE-2025-12380 | known not affected: 146 recommended: 9 | 2026-07-26T16:43:23+00:00 | Vulnerability · Source |
| CVE-2025-13013 | suse_vex | SUSE CVE CVE-2025-13013 | known affected: 14 recommended: 187 | 2026-07-26T16:43:21+00:00 | Vulnerability · Source |
| CVE-2025-13022 | suse_vex | SUSE CVE CVE-2025-13022 | known affected: 14 recommended: 9 | 2026-07-26T16:43:20+00:00 | Vulnerability · Source |
| CVE-2025-14326 | suse_vex | SUSE CVE CVE-2025-14326 | known affected: 37 recommended: 9 | 2026-07-26T16:43:18+00:00 | Vulnerability · Source |
| CVE-2025-14524 | suse_vex | SUSE CVE CVE-2025-14524 | known affected: 503 recommended: 127 | 2026-07-26T16:43:17+00:00 | Vulnerability · Source |
| CVE-2025-21788 | suse_vex | SUSE CVE CVE-2025-21788 | known affected: 59 known not affected: 295 recommended: 53 | 2026-07-26T16:43:09+00:00 | Vulnerability · Source |
| CVE-2025-30258 | suse_vex | SUSE CVE CVE-2025-30258 | known affected: 425 known not affected: 16 recommended: 95 | 2026-07-26T16:43:00+00:00 | Vulnerability · Source |
| CVE-2025-32050 | suse_vex | SUSE CVE CVE-2025-32050 | known affected: 55 recommended: 244 | 2026-07-26T16:42:58+00:00 | Vulnerability · Source |
| CVE-2025-38615 | suse_vex | SUSE CVE CVE-2025-38615 | known not affected: 431 | 2026-07-26T16:42:49+00:00 | Vulnerability · Source |
| CVE-2025-38677 | suse_vex | SUSE CVE CVE-2025-38677 | known not affected: 425 | 2026-07-26T16:42:48+00:00 | Vulnerability · Source |
| CVE-2025-39687 | suse_vex | SUSE CVE CVE-2025-39687 | first fixed: 2 known affected: 284 known not affected: 156 recommended: 154 | 2026-07-26T16:42:45+00:00 | Vulnerability · Source |
| CVE-2025-39822 | suse_vex | SUSE CVE CVE-2025-39822 | first fixed: 2 known affected: 456 known not affected: 319 recommended: 265 | 2026-07-26T16:42:43+00:00 | Vulnerability · Source |
| CVE-2025-40067 | suse_vex | SUSE CVE CVE-2025-40067 | known not affected: 407 recommended: 6 | 2026-07-26T16:42:39+00:00 | Vulnerability · Source |
| CVE-2025-43458 | suse_vex | SUSE CVE CVE-2025-43458 | known affected: 132 recommended: 632 | 2026-07-26T16:42:34+00:00 | Vulnerability · Source |
| CVE-2025-46399 | suse_vex | SUSE CVE CVE-2025-46399 | known affected: 7 recommended: 15 | 2026-07-26T16:42:32+00:00 | Vulnerability · Source |
| CVE-2025-49710 | suse_vex | SUSE CVE CVE-2025-49710 | known affected: 29 known not affected: 117 recommended: 9 | 2026-07-26T16:42:29+00:00 | Vulnerability · Source |
| CVE-2025-59466 | suse_vex | SUSE CVE CVE-2025-59466 | known affected: 164 recommended: 126 | 2026-07-26T16:42:24+00:00 | Vulnerability · Source |
| CVE-2025-68160 | suse_vex | SUSE CVE CVE-2025-68160 | known affected: 462 known not affected: 88 recommended: 441 | 2026-07-26T16:42:16+00:00 | Vulnerability · Source |
| CVE-2025-68210 | suse_vex | SUSE CVE CVE-2025-68210 | first fixed: 2 known affected: 394 known not affected: 415 recommended: 172 | 2026-07-26T16:42:14+00:00 | Vulnerability · Source |
| CVE-2026-2100 | suse_vex | SUSE CVE CVE-2026-2100 | known not affected: 232 recommended: 25 | 2026-07-26T16:42:10+00:00 | Vulnerability · Source |
| CVE-2026-4878 | suse_vex | SUSE CVE CVE-2026-4878 | known affected: 405 recommended: 183 | 2026-07-26T16:42:07+00:00 | Vulnerability · Source |
| CVE-2002-2443 | suse_vex | SUSE CVE CVE-2002-2443 | known affected: 2 recommended: 325 | 2026-07-26T02:01:51+00:00 | Vulnerability · Source |
| CVE-2002-20001 | suse_vex | SUSE CVE CVE-2002-20001 | known not affected: 162 recommended: 140 | 2026-07-26T02:01:49+00:00 | Vulnerability · Source |
| CVE-2003-1332 | suse_vex | SUSE CVE CVE-2003-1332 | known not affected: 2097 | 2026-07-26T02:01:47+00:00 | Vulnerability · Source |
| CVE-2004-0427 | suse_vex | SUSE CVE CVE-2004-0427 | known not affected: 25 | 2026-07-26T02:01:44+00:00 | Vulnerability · Source |
| CVE-2004-0791 | suse_vex | SUSE CVE CVE-2004-0791 | known not affected: 248 | 2026-07-26T02:01:41+00:00 | Vulnerability · Source |
| CVE-2004-1074 | suse_vex | SUSE CVE CVE-2004-1074 | known not affected: 372 | 2026-07-26T02:01:39+00:00 | Vulnerability · Source |
| CVE-2005-0066 | suse_vex | SUSE CVE CVE-2005-0066 | known not affected: 310 | 2026-07-26T02:01:34+00:00 | Vulnerability · Source |
| CVE-2005-0067 | suse_vex | SUSE CVE CVE-2005-0067 | known not affected: 261 | 2026-07-26T02:01:32+00:00 | Vulnerability · Source |
| CVE-2005-0068 | suse_vex | SUSE CVE CVE-2005-0068 | known not affected: 261 | 2026-07-26T02:01:29+00:00 | Vulnerability · Source |
| CVE-2005-0400 | suse_vex | SUSE CVE CVE-2005-0400 | known not affected: 372 | 2026-07-26T02:01:27+00:00 | Vulnerability · Source |
| CVE-2005-0749 | suse_vex | SUSE CVE CVE-2005-0749 | known not affected: 372 | 2026-07-26T02:01:24+00:00 | Vulnerability · Source |
| CVE-2005-1264 | suse_vex | SUSE CVE CVE-2005-1264 | known not affected: 409 | 2026-07-26T02:01:20+00:00 | Vulnerability · Source |
| CVE-2005-2458 | suse_vex | SUSE CVE CVE-2005-2458 | known not affected: 409 | 2026-07-26T02:01:17+00:00 | Vulnerability · Source |