VEX records
Browse vendor VEX statements available in this Vulnerability-Lookup instance and pivot to the related vulnerability.
294121 VEX records
API response| Vulnerability | Source | Title | Product status | Imported | Links |
|---|---|---|---|---|---|
| CVE-2020-36787 | suse_vex | SUSE CVE CVE-2020-36787 | known not affected: 238 | 2026-07-27T23:57:23+00:00 | Vulnerability · Source |
| CVE-2021-1820 | suse_vex | SUSE CVE CVE-2021-1820 | known affected: 1 known not affected: 102 recommended: 908 | 2026-07-27T23:57:21+00:00 | Vulnerability · Source |
| CVE-2021-3493 | suse_vex | SUSE CVE CVE-2021-3493 | known not affected: 260 | 2026-07-27T23:57:15+00:00 | Vulnerability · Source |
| CVE-2021-27862 | suse_vex | SUSE CVE CVE-2021-27862 | known not affected: 475 | 2026-07-27T23:56:24+00:00 | Vulnerability · Source |
| CVE-2021-28710 | suse_vex | SUSE CVE CVE-2021-28710 | known not affected: 240 | 2026-07-27T23:56:20+00:00 | Vulnerability · Source |
| CVE-2021-29971 | suse_vex | SUSE CVE CVE-2021-29971 | known affected: 1 recommended: 9 | 2026-07-27T23:56:15+00:00 | Vulnerability · Source |
| CVE-2021-32606 | suse_vex | SUSE CVE CVE-2021-32606 | known not affected: 260 recommended: 6 | 2026-07-27T23:56:01+00:00 | Vulnerability · Source |
| CVE-2021-34337 | suse_vex | SUSE CVE CVE-2021-34337 | known not affected: 16 recommended: 2 | 2026-07-27T23:55:54+00:00 | Vulnerability · Source |
| CVE-2021-34557 | suse_vex | SUSE CVE CVE-2021-34557 | known affected: 45 known not affected: 24 recommended: 38 | 2026-07-27T23:55:53+00:00 | Vulnerability · Source |
| CVE-2021-38201 | suse_vex | SUSE CVE CVE-2021-38201 | known not affected: 260 recommended: 20 | 2026-07-27T23:55:43+00:00 | Vulnerability · Source |
| CVE-2021-43813 | suse_vex | SUSE CVE CVE-2021-43813 | recommended: 329 | 2026-07-27T23:55:29+00:00 | Vulnerability · Source |
| CVE-2021-46665 | suse_vex | SUSE CVE CVE-2021-46665 | known affected: 1 recommended: 484 | 2026-07-27T23:55:21+00:00 | Vulnerability · Source |
| CVE-2021-47090 | suse_vex | SUSE CVE CVE-2021-47090 | known not affected: 238 | 2026-07-27T23:55:01+00:00 | Vulnerability · Source |
| CVE-2021-47132 | suse_vex | SUSE CVE CVE-2021-47132 | known not affected: 238 | 2026-07-27T23:54:58+00:00 | Vulnerability · Source |
| CVE-2021-47140 | suse_vex | SUSE CVE CVE-2021-47140 | known not affected: 238 | 2026-07-27T23:54:57+00:00 | Vulnerability · Source |
| CVE-2022-21597 | suse_vex | SUSE CVE CVE-2022-21597 | known not affected: 426 | 2026-07-27T23:53:24+00:00 | Vulnerability · Source |
| CVE-2022-23133 | suse_vex | SUSE CVE CVE-2022-23133 | known not affected: 28 | 2026-07-27T23:53:20+00:00 | Vulnerability · Source |
| CVE-2022-23493 | suse_vex | SUSE CVE CVE-2022-23493 | known affected: 375 known not affected: 45 recommended: 170 | 2026-07-27T23:53:16+00:00 | Vulnerability · Source |
| CVE-2022-38126 | suse_vex | SUSE CVE CVE-2022-38126 | known affected: 395 known not affected: 1 recommended: 445 | 2026-07-27T23:52:48+00:00 | Vulnerability · Source |
| CVE-2022-44268 | suse_vex | SUSE CVE CVE-2022-44268 | known affected: 45 known not affected: 12 recommended: 534 | 2026-07-27T23:52:39+00:00 | Vulnerability · Source |
| CVE-2022-48867 | suse_vex | SUSE CVE CVE-2022-48867 | known not affected: 263 | 2026-07-27T23:52:20+00:00 | Vulnerability · Source |
| CVE-2022-48876 | suse_vex | SUSE CVE CVE-2022-48876 | known not affected: 264 | 2026-07-27T23:52:15+00:00 | Vulnerability · Source |
| CVE-2022-49405 | suse_vex | SUSE CVE CVE-2022-49405 | known not affected: 279 | 2026-07-27T23:51:29+00:00 | Vulnerability · Source |
| CVE-2022-49415 | suse_vex | SUSE CVE CVE-2022-49415 | known not affected: 279 | 2026-07-27T23:51:25+00:00 | Vulnerability · Source |
| CVE-2022-50380 | suse_vex | SUSE CVE CVE-2022-50380 | known not affected: 345 | 2026-07-27T23:49:57+00:00 | Vulnerability · Source |
| CVE-2022-50412 | suse_vex | SUSE CVE CVE-2022-50412 | known affected: 429 known not affected: 184 recommended: 198 | 2026-07-27T23:49:53+00:00 | Vulnerability · Source |
| CVE-2022-50627 | suse_vex | SUSE CVE CVE-2022-50627 | known not affected: 373 recommended: 49 | 2026-07-27T23:49:32+00:00 | Vulnerability · Source |
| CVE-2023-0458 | suse_vex | SUSE CVE CVE-2023-0458 | known affected: 2 known not affected: 276 recommended: 47 | 2026-07-27T23:49:19+00:00 | Vulnerability · Source |
| CVE-2023-4208 | suse_vex | SUSE CVE CVE-2023-4208 | recommended: 62 | 2026-07-27T23:48:59+00:00 | Vulnerability · Source |
| CVE-2023-32209 | suse_vex | SUSE CVE CVE-2023-32209 | known affected: 63 recommended: 9 | 2026-07-27T23:48:10+00:00 | Vulnerability · Source |
| CVE-2023-32725 | suse_vex | SUSE CVE CVE-2023-32725 | known not affected: 14 | 2026-07-27T23:48:08+00:00 | Vulnerability · Source |
| CVE-2023-34323 | suse_vex | SUSE CVE CVE-2023-34323 | known affected: 250 recommended: 447 | 2026-07-27T23:48:06+00:00 | Vulnerability · Source |
| CVE-2023-38431 | suse_vex | SUSE CVE CVE-2023-38431 | known not affected: 301 | 2026-07-27T23:47:59+00:00 | Vulnerability · Source |
| CVE-2023-40791 | suse_vex | SUSE CVE CVE-2023-40791 | known not affected: 289 | 2026-07-27T23:47:55+00:00 | Vulnerability · Source |
| CVE-2023-46047 | suse_vex | SUSE CVE CVE-2023-46047 | known affected: 125 | 2026-07-27T23:47:46+00:00 | Vulnerability · Source |
| CVE-2023-53253 | suse_vex | SUSE CVE CVE-2023-53253 | known not affected: 345 | 2026-07-27T23:47:09+00:00 | Vulnerability · Source |
| CVE-2023-53382 | suse_vex | SUSE CVE CVE-2023-53382 | known affected: 49 known not affected: 296 | 2026-07-27T23:47:04+00:00 | Vulnerability · Source |
| CVE-2023-53758 | suse_vex | SUSE CVE CVE-2023-53758 | known not affected: 337 | 2026-07-27T23:46:46+00:00 | Vulnerability · Source |
| CVE-2023-54062 | suse_vex | SUSE CVE CVE-2023-54062 | known not affected: 354 recommended: 29 | 2026-07-27T23:46:42+00:00 | Vulnerability · Source |
| CVE-2023-54068 | suse_vex | SUSE CVE CVE-2023-54068 | known affected: 96 known not affected: 258 | 2026-07-27T23:46:40+00:00 | Vulnerability · Source |
| CVE-2026-12413 | suse_vex | SUSE CVE CVE-2026-12413 | recommended: 4 | 2026-07-27T23:42:27+00:00 | Vulnerability · Source |
| CVE-2026-12892 | suse_vex | SUSE CVE CVE-2026-12892 | first fixed: 132 known affected: 181 known not affected: 83 recommended: 607 | 2026-07-27T23:42:23+00:00 | Vulnerability · Source |
| CVE-2026-23168 | suse_vex | SUSE CVE CVE-2026-23168 | first fixed: 2 known affected: 77 known not affected: 200 recommended: 337 | 2026-07-27T23:42:05+00:00 | Vulnerability · Source |
| CVE-2026-23193 | suse_vex | SUSE CVE CVE-2026-23193 | first fixed: 2 known affected: 631 known not affected: 4 recommended: 450 | 2026-07-27T23:42:03+00:00 | Vulnerability · Source |
| CVE-2026-23455 | suse_vex | SUSE CVE CVE-2026-23455 | first fixed: 2 known affected: 222 recommended: 448 | 2026-07-27T23:41:47+00:00 | Vulnerability · Source |
| CVE-2026-25547 | suse_vex | SUSE CVE CVE-2026-25547 | first fixed: 36 known affected: 552 known not affected: 255 recommended: 394 | 2026-07-27T23:41:42+00:00 | Vulnerability · Source |
| CVE-2026-26996 | suse_vex | SUSE CVE CVE-2026-26996 | first fixed: 36 known affected: 512 known not affected: 254 recommended: 214 | 2026-07-27T23:41:38+00:00 | Vulnerability · Source |
| CVE-2026-31505 | suse_vex | SUSE CVE CVE-2026-31505 | first fixed: 26 known affected: 411 known not affected: 138 recommended: 525 | 2026-07-27T23:41:17+00:00 | Vulnerability · Source |
| CVE-2026-31533 | suse_vex | SUSE CVE CVE-2026-31533 | first fixed: 26 known affected: 442 known not affected: 67 recommended: 631 | 2026-07-27T23:41:15+00:00 | Vulnerability · Source |
| CVE-2026-31586 | suse_vex | SUSE CVE CVE-2026-31586 | first fixed: 26 known affected: 507 known not affected: 4 recommended: 635 | 2026-07-27T23:41:09+00:00 | Vulnerability · Source |