VEX records
Browse vendor VEX statements available in this Vulnerability-Lookup instance and pivot to the related vulnerability.
293999 VEX records
API response| Vulnerability | Source | Title | Product status | Imported | Links |
|---|---|---|---|---|---|
| CVE-2020-0435 | suse_vex | SUSE CVE CVE-2020-0435 | known not affected: 356 | 2026-07-31T01:38:39+00:00 | Vulnerability · Source |
| CVE-2020-2764 | suse_vex | SUSE CVE CVE-2020-2764 | known affected: 60 | 2026-07-31T01:38:35+00:00 | Vulnerability · Source |
| CVE-2020-8025 | suse_vex | SUSE CVE CVE-2020-8025 | known affected: 311 known not affected: 534 recommended: 539 | 2026-07-31T01:38:22+00:00 | Vulnerability · Source |
| CVE-2020-8315 | suse_vex | SUSE CVE CVE-2020-8315 | known affected: 14 known not affected: 685 | 2026-07-31T01:38:20+00:00 | Vulnerability · Source |
| CVE-2020-10742 | suse_vex | SUSE CVE CVE-2020-10742 | known not affected: 520 recommended: 13 | 2026-07-31T01:38:11+00:00 | Vulnerability · Source |
| CVE-2020-11740 | suse_vex | SUSE CVE CVE-2020-11740 | known affected: 400 known not affected: 80 recommended: 522 | 2026-07-31T01:37:55+00:00 | Vulnerability · Source |
| CVE-2020-11947 | suse_vex | SUSE CVE CVE-2020-11947 | known affected: 370 known not affected: 219 recommended: 870 | 2026-07-31T01:37:50+00:00 | Vulnerability · Source |
| CVE-2020-21680 | suse_vex | SUSE CVE CVE-2020-21680 | recommended: 47 | 2026-07-31T01:37:17+00:00 | Vulnerability · Source |
| CVE-2020-26560 | suse_vex | SUSE CVE CVE-2020-26560 | known not affected: 670 | 2026-07-31T01:37:03+00:00 | Vulnerability · Source |
| CVE-2020-27616 | suse_vex | SUSE CVE CVE-2020-27616 | known affected: 394 known not affected: 432 recommended: 231 | 2026-07-31T01:36:57+00:00 | Vulnerability · Source |
| CVE-2020-36332 | suse_vex | SUSE CVE CVE-2020-36332 | known affected: 394 known not affected: 152 recommended: 227 | 2026-07-31T01:36:43+00:00 | Vulnerability · Source |
| CVE-2020-36387 | suse_vex | SUSE CVE CVE-2020-36387 | known not affected: 320 | 2026-07-31T01:36:40+00:00 | Vulnerability · Source |
| CVE-2021-0076 | suse_vex | SUSE CVE CVE-2021-0076 | known not affected: 71 recommended: 130 | 2026-07-31T01:36:38+00:00 | Vulnerability · Source |
| CVE-2021-2369 | suse_vex | SUSE CVE CVE-2021-2369 | known affected: 394 known not affected: 3 recommended: 1107 | 2026-07-31T01:36:24+00:00 | Vulnerability · Source |
| CVE-2021-3744 | suse_vex | SUSE CVE CVE-2021-3744 | known affected: 326 known not affected: 162 recommended: 1414 | 2026-07-31T01:36:07+00:00 | Vulnerability · Source |
| CVE-2021-3892 | suse_vex | SUSE CVE CVE-2021-3892 | known not affected: 316 | 2026-07-31T01:36:03+00:00 | Vulnerability · Source |
| CVE-2021-32000 | suse_vex | SUSE CVE CVE-2021-32000 | known affected: 24 known not affected: 5 recommended: 36 | 2026-07-31T01:35:21+00:00 | Vulnerability · Source |
| CVE-2021-35550 | suse_vex | SUSE CVE CVE-2021-35550 | known affected: 397 recommended: 729 | 2026-07-31T01:35:16+00:00 | Vulnerability · Source |
| CVE-2021-38497 | suse_vex | SUSE CVE CVE-2021-38497 | known affected: 1 recommended: 487 | 2026-07-31T01:35:12+00:00 | Vulnerability · Source |
| CVE-2021-44038 | suse_vex | SUSE CVE CVE-2021-44038 | known not affected: 304 recommended: 7 | 2026-07-31T01:35:03+00:00 | Vulnerability · Source |
| CVE-2021-44573 | suse_vex | SUSE CVE CVE-2021-44573 | known not affected: 323 | 2026-07-31T01:35:01+00:00 | Vulnerability · Source |
| CVE-2021-46973 | suse_vex | SUSE CVE CVE-2021-46973 | known not affected: 292 | 2026-07-31T01:34:49+00:00 | Vulnerability · Source |
| CVE-2021-46977 | suse_vex | SUSE CVE CVE-2021-46977 | known not affected: 292 | 2026-07-31T01:34:47+00:00 | Vulnerability · Source |
| CVE-2021-47147 | suse_vex | SUSE CVE CVE-2021-47147 | known not affected: 292 | 2026-07-31T01:34:40+00:00 | Vulnerability · Source |
| CVE-2022-0286 | suse_vex | SUSE CVE CVE-2022-0286 | known affected: 344 known not affected: 580 recommended: 433 | 2026-07-31T01:33:56+00:00 | Vulnerability · Source |
| CVE-2022-1678 | suse_vex | SUSE CVE CVE-2022-1678 | known not affected: 390 | 2026-07-31T01:33:42+00:00 | Vulnerability · Source |
| CVE-2022-21538 | suse_vex | SUSE CVE CVE-2022-21538 | recommended: 17 | 2026-07-31T01:32:58+00:00 | Vulnerability · Source |
| CVE-2022-23478 | suse_vex | SUSE CVE CVE-2022-23478 | known affected: 394 known not affected: 3 recommended: 171 | 2026-07-31T01:32:48+00:00 | Vulnerability · Source |
| CVE-2022-28349 | suse_vex | SUSE CVE CVE-2022-28349 | known not affected: 390 | 2026-07-31T01:32:39+00:00 | Vulnerability · Source |
| CVE-2022-31624 | suse_vex | SUSE CVE CVE-2022-31624 | known not affected: 233 recommended: 16 | 2026-07-31T01:32:34+00:00 | Vulnerability · Source |
| CVE-2022-40897 | suse_vex | SUSE CVE CVE-2022-40897 | known affected: 272 known not affected: 95 recommended: 350 | 2026-07-31T01:32:21+00:00 | Vulnerability · Source |
| CVE-2022-45786 | suse_vex | SUSE CVE CVE-2022-45786 | No product status | 2026-07-31T01:32:11+00:00 | Vulnerability · Source |
| CVE-2022-48554 | suse_vex | SUSE CVE CVE-2022-48554 | known not affected: 247 recommended: 4 | 2026-07-31T01:32:08+00:00 | Vulnerability · Source |
| CVE-2022-49497 | suse_vex | SUSE CVE CVE-2022-49497 | known affected: 545 known not affected: 91 recommended: 140 | 2026-07-31T01:31:15+00:00 | Vulnerability · Source |
| CVE-2022-49580 | suse_vex | SUSE CVE CVE-2022-49580 | known not affected: 163 recommended: 27 | 2026-07-31T01:31:04+00:00 | Vulnerability · Source |
| CVE-2022-50128 | suse_vex | SUSE CVE CVE-2022-50128 | known not affected: 401 | 2026-07-31T01:30:45+00:00 | Vulnerability · Source |
| CVE-2022-50628 | suse_vex | SUSE CVE CVE-2022-50628 | known affected: 112 known not affected: 296 recommended: 49 | 2026-07-31T01:30:15+00:00 | Vulnerability · Source |
| CVE-2023-0030 | suse_vex | SUSE CVE CVE-2023-0030 | known not affected: 402 | 2026-07-31T01:30:04+00:00 | Vulnerability · Source |
| CVE-2023-2255 | suse_vex | SUSE CVE CVE-2023-2255 | known affected: 163 recommended: 1819 | 2026-07-31T01:29:38+00:00 | Vulnerability · Source |
| CVE-2023-32210 | suse_vex | SUSE CVE CVE-2023-32210 | known affected: 65 recommended: 9 | 2026-07-31T01:29:09+00:00 | Vulnerability · Source |
| CVE-2023-34620 | suse_vex | SUSE CVE CVE-2023-34620 | No product status | 2026-07-31T01:29:04+00:00 | Vulnerability · Source |
| CVE-2023-39804 | suse_vex | SUSE CVE CVE-2023-39804 | known affected: 312 recommended: 291 | 2026-07-31T01:28:57+00:00 | Vulnerability · Source |
| CVE-2023-43361 | suse_vex | SUSE CVE CVE-2023-43361 | known affected: 23 recommended: 91 | 2026-07-31T01:28:54+00:00 | Vulnerability · Source |
| CVE-2023-53298 | suse_vex | SUSE CVE CVE-2023-53298 | known affected: 462 known not affected: 187 recommended: 243 | 2026-07-31T01:28:22+00:00 | Vulnerability · Source |
| CVE-2023-53802 | suse_vex | SUSE CVE CVE-2023-53802 | known affected: 476 known not affected: 182 recommended: 219 | 2026-07-31T01:28:14+00:00 | Vulnerability · Source |
| CVE-2023-53845 | suse_vex | SUSE CVE CVE-2023-53845 | known affected: 476 known not affected: 214 recommended: 196 | 2026-07-31T01:28:12+00:00 | Vulnerability · Source |
| CVE-2026-9029 | redhat_vex | grafana: Grafana: Arbitrary code execution and information disclosure via Cross-Site Scripting in geomap panel | known not affected: 31 | 2026-07-31T01:28:09+00:00 | Vulnerability · Source |
| CVE-2024-21635 | suse_vex | SUSE CVE CVE-2024-21635 | No product status | 2026-07-31T01:27:37+00:00 | Vulnerability · Source |
| CVE-2024-31074 | suse_vex | SUSE CVE CVE-2024-31074 | known affected: 8 known not affected: 2 recommended: 126 | 2026-07-31T01:27:15+00:00 | Vulnerability · Source |
| CVE-2024-53412 | suse_vex | SUSE CVE CVE-2024-53412 | No product status | 2026-07-31T01:25:01+00:00 | Vulnerability · Source |