VEX records
Browse vendor VEX statements available in this Vulnerability-Lookup instance and pivot to the related vulnerability.
293983 VEX records
API response| Vulnerability | Source | Title | Product status | Imported | Links |
|---|---|---|---|---|---|
| CVE-2021-28662 | suse_vex | SUSE CVE CVE-2021-28662 | known affected: 394 known not affected: 72 recommended: 52 | 2026-07-26T16:53:14+00:00 | Vulnerability · Source |
| CVE-2021-35604 | suse_vex | SUSE CVE CVE-2021-35604 | known not affected: 86 recommended: 446 | 2026-07-26T16:52:54+00:00 | Vulnerability · Source |
| CVE-2021-38604 | suse_vex | SUSE CVE CVE-2021-38604 | known not affected: 651 | 2026-07-26T16:52:52+00:00 | Vulnerability · Source |
| CVE-2021-46101 | suse_vex | SUSE CVE CVE-2021-46101 | known not affected: 573 | 2026-07-26T16:52:42+00:00 | Vulnerability · Source |
| CVE-2021-46935 | suse_vex | SUSE CVE CVE-2021-46935 | known not affected: 312 | 2026-07-26T16:52:39+00:00 | Vulnerability · Source |
| CVE-2022-2526 | suse_vex | SUSE CVE CVE-2022-2526 | known not affected: 598 recommended: 18 | 2026-07-26T16:51:52+00:00 | Vulnerability · Source |
| CVE-2022-49675 | suse_vex | SUSE CVE CVE-2022-49675 | known affected: 334 known not affected: 298 recommended: 243 | 2026-07-26T16:50:06+00:00 | Vulnerability · Source |
| CVE-2022-50033 | suse_vex | SUSE CVE CVE-2022-50033 | known affected: 429 known not affected: 196 recommended: 337 | 2026-07-26T16:49:51+00:00 | Vulnerability · Source |
| CVE-2022-50296 | suse_vex | SUSE CVE CVE-2022-50296 | known affected: 10 known not affected: 406 | 2026-07-26T16:49:41+00:00 | Vulnerability · Source |
| CVE-2022-50437 | suse_vex | SUSE CVE CVE-2022-50437 | known affected: 344 known not affected: 267 recommended: 273 | 2026-07-26T16:49:30+00:00 | Vulnerability · Source |
| CVE-2022-50518 | suse_vex | SUSE CVE CVE-2022-50518 | known not affected: 416 | 2026-07-26T16:49:22+00:00 | Vulnerability · Source |
| CVE-2022-50638 | suse_vex | SUSE CVE CVE-2022-50638 | known affected: 470 known not affected: 188 recommended: 282 | 2026-07-26T16:49:17+00:00 | Vulnerability · Source |
| CVE-2023-3326 | suse_vex | SUSE CVE CVE-2023-3326 | known not affected: 1172 | 2026-07-26T16:49:06+00:00 | Vulnerability · Source |
| CVE-2023-4156 | suse_vex | SUSE CVE CVE-2023-4156 | known affected: 184 recommended: 251 | 2026-07-26T16:49:00+00:00 | Vulnerability · Source |
| CVE-2023-29451 | suse_vex | SUSE CVE CVE-2023-29451 | known not affected: 21 | 2026-07-26T16:48:39+00:00 | Vulnerability · Source |
| CVE-2023-44431 | suse_vex | SUSE CVE CVE-2023-44431 | known not affected: 196 recommended: 5 | 2026-07-26T16:48:25+00:00 | Vulnerability · Source |
| CVE-2023-45872 | suse_vex | SUSE CVE CVE-2023-45872 | known not affected: 165 | 2026-07-26T16:48:19+00:00 | Vulnerability · Source |
| CVE-2023-52466 | suse_vex | SUSE CVE CVE-2023-52466 | known not affected: 312 | 2026-07-26T16:48:06+00:00 | Vulnerability · Source |
| CVE-2023-53378 | suse_vex | SUSE CVE CVE-2023-53378 | known affected: 369 known not affected: 359 recommended: 92 | 2026-07-26T16:47:23+00:00 | Vulnerability · Source |
| CVE-2023-53761 | suse_vex | SUSE CVE CVE-2023-53761 | known affected: 402 known not affected: 283 recommended: 229 | 2026-07-26T16:47:10+00:00 | Vulnerability · Source |
| CVE-2023-54180 | suse_vex | SUSE CVE CVE-2023-54180 | known affected: 260 known not affected: 195 | 2026-07-26T16:47:02+00:00 | Vulnerability · Source |
| CVE-2024-22121 | suse_vex | SUSE CVE CVE-2024-22121 | known not affected: 11 | 2026-07-26T16:46:27+00:00 | Vulnerability · Source |
| CVE-2025-0246 | suse_vex | SUSE CVE CVE-2025-0246 | known affected: 57 recommended: 9 | 2026-07-26T16:44:11+00:00 | Vulnerability · Source |
| CVE-2025-1941 | suse_vex | SUSE CVE CVE-2025-1941 | recommended: 9 | 2026-07-26T16:44:06+00:00 | Vulnerability · Source |
| CVE-2025-1943 | suse_vex | SUSE CVE CVE-2025-1943 | recommended: 9 | 2026-07-26T16:44:05+00:00 | Vulnerability · Source |
| CVE-2025-3033 | suse_vex | SUSE CVE CVE-2025-3033 | recommended: 9 | 2026-07-26T16:44:02+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-32050 | suse_vex | SUSE CVE CVE-2025-32050 | known affected: 55 recommended: 244 | 2026-07-26T16:42:58+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-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 |
| CVE-2005-2541 | suse_vex | SUSE CVE CVE-2005-2541 | known not affected: 150 | 2026-07-26T02:01:14+00:00 | Vulnerability · Source |
| CVE-2005-2553 | suse_vex | SUSE CVE CVE-2005-2553 | known not affected: 210 | 2026-07-26T02:01:12+00:00 | Vulnerability · Source |
| CVE-2005-3590 | suse_vex | SUSE CVE CVE-2005-3590 | known not affected: 233 | 2026-07-26T02:01:04+00:00 | Vulnerability · Source |
| CVE-2005-4881 | suse_vex | SUSE CVE CVE-2005-4881 | known not affected: 484 recommended: 42 | 2026-07-26T02:00:59+00:00 | Vulnerability · Source |
| CVE-2006-2607 | suse_vex | SUSE CVE CVE-2006-2607 | recommended: 81 | 2026-07-26T02:00:46+00:00 | Vulnerability · Source |
| CVE-2006-3376 | suse_vex | SUSE CVE CVE-2006-3376 | known not affected: 59 recommended: 50 | 2026-07-26T02:00:44+00:00 | Vulnerability · Source |
| CVE-2006-4197 | suse_vex | SUSE CVE CVE-2006-4197 | recommended: 50 | 2026-07-26T02:00:42+00:00 | Vulnerability · Source |
| CVE-2006-4226 | suse_vex | SUSE CVE CVE-2006-4226 | known not affected: 44 recommended: 186 | 2026-07-26T02:00:39+00:00 | Vulnerability · Source |