VEX records
Browse vendor VEX statements available in this Vulnerability-Lookup instance and pivot to the related vulnerability.
291352 VEX records
API response| Vulnerability | Source | Title | Product status | Imported | Links |
|---|---|---|---|---|---|
| CVE-2019-1010305 | suse_vex | SUSE CVE CVE-2019-1010305 | known affected: 32 recommended: 143 | 2026-08-05T01:26:08+00:00 | Vulnerability · Source |
| CVE-2020-0067 | suse_vex | SUSE CVE CVE-2020-0067 | known not affected: 215 | 2026-08-05T01:26:06+00:00 | Vulnerability · Source |
| CVE-2020-14145 | suse_vex | SUSE CVE CVE-2020-14145 | known affected: 388 known not affected: 131 recommended: 246 | 2026-08-05T01:25:53+00:00 | Vulnerability · Source |
| CVE-2020-14351 | suse_vex | SUSE CVE CVE-2020-14351 | known affected: 455 known not affected: 25 recommended: 1572 | 2026-08-05T01:25:51+00:00 | Vulnerability · Source |
| CVE-2020-15859 | suse_vex | SUSE CVE CVE-2020-15859 | known affected: 1438 known not affected: 1706 | 2026-08-05T01:25:48+00:00 | Vulnerability · Source |
| CVE-2020-19144 | suse_vex | SUSE CVE CVE-2020-19144 | known not affected: 142 | 2026-08-05T01:25:46+00:00 | Vulnerability · Source |
| CVE-2021-0172 | suse_vex | SUSE CVE CVE-2021-0172 | known not affected: 71 recommended: 130 | 2026-08-05T01:25:26+00:00 | Vulnerability · Source |
| CVE-2021-20718 | suse_vex | SUSE CVE CVE-2021-20718 | known affected: 1 known not affected: 18 recommended: 9 | 2026-08-05T01:25:05+00:00 | Vulnerability · Source |
| CVE-2021-26720 | suse_vex | SUSE CVE CVE-2021-26720 | known affected: 293 known not affected: 668 recommended: 1291 | 2026-08-05T01:25:00+00:00 | Vulnerability · Source |
| CVE-2021-27365 | suse_vex | SUSE CVE CVE-2021-27365 | known affected: 300 known not affected: 71 recommended: 1871 | 2026-08-05T01:24:57+00:00 | Vulnerability · Source |
| CVE-2021-46910 | suse_vex | SUSE CVE CVE-2021-46910 | known not affected: 312 | 2026-08-05T01:24:44+00:00 | Vulnerability · Source |
| CVE-2021-46948 | suse_vex | SUSE CVE CVE-2021-46948 | known not affected: 292 | 2026-08-05T01:24:31+00:00 | Vulnerability · Source |
| CVE-2021-46967 | suse_vex | SUSE CVE CVE-2021-46967 | known not affected: 304 | 2026-08-05T01:24:23+00:00 | Vulnerability · Source |
| CVE-2021-46993 | suse_vex | SUSE CVE CVE-2021-46993 | known not affected: 292 | 2026-08-05T01:24:10+00:00 | Vulnerability · Source |
| CVE-2021-47011 | suse_vex | SUSE CVE CVE-2021-47011 | known not affected: 292 recommended: 20 | 2026-08-05T01:24:02+00:00 | Vulnerability · Source |
| CVE-2021-47036 | suse_vex | SUSE CVE CVE-2021-47036 | known not affected: 292 | 2026-08-05T01:23:46+00:00 | Vulnerability · Source |
| CVE-2021-47081 | suse_vex | SUSE CVE CVE-2021-47081 | known not affected: 292 | 2026-08-05T01:23:27+00:00 | Vulnerability · Source |
| CVE-2021-47129 | suse_vex | SUSE CVE CVE-2021-47129 | known affected: 55 known not affected: 298 | 2026-08-05T01:23:04+00:00 | Vulnerability · Source |
| CVE-2021-47135 | suse_vex | SUSE CVE CVE-2021-47135 | known not affected: 292 | 2026-08-05T01:22:59+00:00 | Vulnerability · Source |
| CVE-2021-47162 | suse_vex | SUSE CVE CVE-2021-47162 | known affected: 540 known not affected: 186 recommended: 109 | 2026-08-05T01:22:48+00:00 | Vulnerability · Source |
| CVE-2021-47226 | suse_vex | SUSE CVE CVE-2021-47226 | known affected: 55 known not affected: 271 | 2026-08-05T01:22:15+00:00 | Vulnerability · Source |
| CVE-2021-47243 | suse_vex | SUSE CVE CVE-2021-47243 | known affected: 55 known not affected: 271 | 2026-08-05T01:22:11+00:00 | Vulnerability · Source |
| CVE-2021-47300 | suse_vex | SUSE CVE CVE-2021-47300 | known not affected: 330 | 2026-08-05T01:21:52+00:00 | Vulnerability · Source |
| CVE-2021-47311 | suse_vex | SUSE CVE CVE-2021-47311 | known affected: 421 known not affected: 255 recommended: 253 | 2026-08-05T01:21:45+00:00 | Vulnerability · Source |
| CVE-2021-47346 | suse_vex | SUSE CVE CVE-2021-47346 | known not affected: 330 | 2026-08-05T01:21:37+00:00 | Vulnerability · Source |
| CVE-2021-47351 | suse_vex | SUSE CVE CVE-2021-47351 | known not affected: 288 | 2026-08-05T01:21:34+00:00 | Vulnerability · Source |
| CVE-2021-47613 | suse_vex | SUSE CVE CVE-2021-47613 | known not affected: 318 | 2026-08-05T01:19:41+00:00 | Vulnerability · Source |
| CVE-2022-0635 | suse_vex | SUSE CVE CVE-2022-0635 | known not affected: 598 recommended: 25 | 2026-08-05T01:19:21+00:00 | Vulnerability · Source |
| CVE-2022-1586 | suse_vex | SUSE CVE CVE-2022-1586 | known affected: 210 known not affected: 2 recommended: 1204 | 2026-08-05T01:19:18+00:00 | Vulnerability · Source |
| CVE-2022-21546 | suse_vex | SUSE CVE CVE-2022-21546 | known affected: 637 known not affected: 141 recommended: 37 | 2026-08-05T01:18:58+00:00 | Vulnerability · Source |
| CVE-2022-25258 | suse_vex | SUSE CVE CVE-2022-25258 | known affected: 210 known not affected: 252 recommended: 556 | 2026-08-05T01:18:52+00:00 | Vulnerability · Source |
| CVE-2022-30333 | suse_vex | SUSE CVE CVE-2022-30333 | known affected: 13 recommended: 12 | 2026-08-05T01:18:49+00:00 | Vulnerability · Source |
| CVE-2022-48636 | suse_vex | SUSE CVE CVE-2022-48636 | known affected: 362 known not affected: 70 recommended: 643 | 2026-08-05T01:18:34+00:00 | Vulnerability · Source |
| CVE-2022-48637 | suse_vex | SUSE CVE CVE-2022-48637 | known affected: 275 known not affected: 287 recommended: 462 | 2026-08-05T01:18:33+00:00 | Vulnerability · Source |
| CVE-2022-48658 | suse_vex | SUSE CVE CVE-2022-48658 | known affected: 377 known not affected: 263 recommended: 318 | 2026-08-05T01:18:28+00:00 | Vulnerability · Source |
| CVE-2022-48666 | suse_vex | SUSE CVE CVE-2022-48666 | known affected: 138 known not affected: 265 | 2026-08-05T01:18:26+00:00 | Vulnerability · Source |
| CVE-2022-48697 | suse_vex | SUSE CVE CVE-2022-48697 | known affected: 396 known not affected: 81 recommended: 541 | 2026-08-05T01:18:16+00:00 | Vulnerability · Source |
| CVE-2022-48720 | suse_vex | SUSE CVE CVE-2022-48720 | known affected: 330 known not affected: 205 recommended: 391 | 2026-08-05T01:18:08+00:00 | Vulnerability · Source |
| CVE-2022-48726 | suse_vex | SUSE CVE CVE-2022-48726 | known affected: 324 known not affected: 169 recommended: 482 | 2026-08-05T01:18:04+00:00 | Vulnerability · Source |
| CVE-2022-48729 | suse_vex | SUSE CVE CVE-2022-48729 | known affected: 330 known not affected: 205 recommended: 391 | 2026-08-05T01:18:00+00:00 | Vulnerability · Source |
| CVE-2022-48733 | suse_vex | SUSE CVE CVE-2022-48733 | known affected: 538 known not affected: 76 recommended: 382 | 2026-08-05T01:17:58+00:00 | Vulnerability · Source |
| CVE-2022-48734 | suse_vex | SUSE CVE CVE-2022-48734 | known affected: 499 known not affected: 125 recommended: 391 | 2026-08-05T01:17:55+00:00 | Vulnerability · Source |
| CVE-2022-48739 | suse_vex | SUSE CVE CVE-2022-48739 | known affected: 330 known not affected: 205 recommended: 391 | 2026-08-05T01:17:51+00:00 | Vulnerability · Source |
| CVE-2022-48742 | suse_vex | SUSE CVE CVE-2022-48742 | known affected: 642 known not affected: 82 recommended: 150 | 2026-08-05T01:17:49+00:00 | Vulnerability · Source |
| CVE-2022-48744 | suse_vex | SUSE CVE CVE-2022-48744 | known affected: 433 known not affected: 133 recommended: 391 | 2026-08-05T01:17:45+00:00 | Vulnerability · Source |
| CVE-2022-48751 | suse_vex | SUSE CVE CVE-2022-48751 | known affected: 437 known not affected: 97 recommended: 461 | 2026-08-05T01:17:43+00:00 | Vulnerability · Source |
| CVE-2022-48762 | suse_vex | SUSE CVE CVE-2022-48762 | known not affected: 318 | 2026-08-05T01:17:36+00:00 | Vulnerability · Source |
| CVE-2022-48771 | suse_vex | SUSE CVE CVE-2022-48771 | known not affected: 139 recommended: 546 | 2026-08-05T01:17:35+00:00 | Vulnerability · Source |
| CVE-2022-48788 | suse_vex | SUSE CVE CVE-2022-48788 | known affected: 385 known not affected: 116 recommended: 619 | 2026-08-05T01:17:28+00:00 | Vulnerability · Source |
| CVE-2022-48790 | suse_vex | SUSE CVE CVE-2022-48790 | known affected: 381 known not affected: 119 recommended: 605 | 2026-08-05T01:17:25+00:00 | Vulnerability · Source |