VEX records
Browse vendor VEX statements available in this Vulnerability-Lookup instance and pivot to the related vulnerability.
288586 VEX records
API response| Vulnerability | Source | Title | Product status | Imported | Links |
|---|---|---|---|---|---|
| CVE-2019-7283 | suse_vex | SUSE CVE CVE-2019-7283 | known affected: 6 | 2026-08-05T01:26:56+00:00 | Vulnerability · Source |
| CVE-2019-8676 | suse_vex | SUSE CVE CVE-2019-8676 | known affected: 107 known not affected: 82 recommended: 1124 | 2026-08-05T01:26:54+00:00 | Vulnerability · Source |
| CVE-2019-9448 | suse_vex | SUSE CVE CVE-2019-9448 | known not affected: 215 | 2026-08-05T01:26:51+00:00 | Vulnerability · Source |
| CVE-2019-9514 | suse_vex | SUSE CVE CVE-2019-9514 | known affected: 82 known not affected: 262 recommended: 563 | 2026-08-05T01:26:50+00:00 | Vulnerability · Source |
| CVE-2019-9674 | suse_vex | SUSE CVE CVE-2019-9674 | known affected: 402 known not affected: 233 recommended: 1602 | 2026-08-05T01:26:48+00:00 | Vulnerability · Source |
| CVE-2019-9704 | suse_vex | SUSE CVE CVE-2019-9704 | known affected: 405 recommended: 155 | 2026-08-05T01:26:46+00:00 | Vulnerability · Source |
| CVE-2019-9717 | suse_vex | SUSE CVE CVE-2019-9717 | No product status | 2026-08-05T01:26:45+00:00 | Vulnerability · Source |
| CVE-2019-9720 | suse_vex | SUSE CVE CVE-2019-9720 | No product status | 2026-08-05T01:26:43+00:00 | Vulnerability · Source |
| CVE-2019-10098 | suse_vex | SUSE CVE CVE-2019-10098 | known affected: 510 known not affected: 52 recommended: 402 | 2026-08-05T01:26:41+00:00 | Vulnerability · Source |
| CVE-2019-11085 | suse_vex | SUSE CVE CVE-2019-11085 | known affected: 87 known not affected: 85 recommended: 666 | 2026-08-05T01:26:38+00:00 | Vulnerability · Source |
| CVE-2019-11692 | suse_vex | SUSE CVE CVE-2019-11692 | known affected: 20 known not affected: 8 recommended: 412 | 2026-08-05T01:26:36+00:00 | Vulnerability · Source |
| CVE-2019-11707 | suse_vex | SUSE CVE CVE-2019-11707 | recommended: 429 | 2026-08-05T01:26:34+00:00 | Vulnerability · Source |
| CVE-2019-11716 | suse_vex | SUSE CVE CVE-2019-11716 | known affected: 21 recommended: 613 | 2026-08-05T01:26:32+00:00 | Vulnerability · Source |
| CVE-2019-13306 | suse_vex | SUSE CVE CVE-2019-13306 | known affected: 46 known not affected: 340 recommended: 638 | 2026-08-05T01:26:28+00:00 | Vulnerability · Source |
| CVE-2019-15794 | suse_vex | SUSE CVE CVE-2019-15794 | known not affected: 458 recommended: 20 | 2026-08-05T01:26:25+00:00 | Vulnerability · Source |
| CVE-2019-17016 | suse_vex | SUSE CVE CVE-2019-17016 | known affected: 21 recommended: 414 | 2026-08-05T01:26:22+00:00 | Vulnerability · Source |
| CVE-2019-17351 | suse_vex | SUSE CVE CVE-2019-17351 | known affected: 89 known not affected: 211 | 2026-08-05T01:26:20+00:00 | Vulnerability · Source |
| CVE-2019-18197 | suse_vex | SUSE CVE CVE-2019-18197 | known affected: 415 recommended: 303 | 2026-08-05T01:26:18+00:00 | Vulnerability · Source |
| CVE-2019-18388 | suse_vex | SUSE CVE CVE-2019-18388 | known affected: 16 recommended: 148 | 2026-08-05T01:26:16+00:00 | Vulnerability · Source |
| CVE-2019-19039 | suse_vex | SUSE CVE CVE-2019-19039 | known affected: 2 known not affected: 223 | 2026-08-05T01:26:14+00:00 | Vulnerability · Source |
| 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-12100 | suse_vex | SUSE CVE CVE-2020-12100 | known affected: 8 recommended: 482 | 2026-08-05T01:25:58+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-2020-25697 | suse_vex | SUSE CVE CVE-2020-25697 | known affected: 394 recommended: 33 | 2026-08-05T01:25:42+00:00 | Vulnerability · Source |
| CVE-2020-26976 | suse_vex | SUSE CVE CVE-2020-26976 | recommended: 483 | 2026-08-05T01:25:40+00:00 | Vulnerability · Source |
| CVE-2020-27755 | suse_vex | SUSE CVE CVE-2020-27755 | recommended: 785 | 2026-08-05T01:25:38+00:00 | Vulnerability · Source |
| CVE-2020-29362 | suse_vex | SUSE CVE CVE-2020-29362 | known affected: 357 known not affected: 185 recommended: 327 | 2026-08-05T01:25:34+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-3468 | suse_vex | SUSE CVE CVE-2021-3468 | known affected: 301 recommended: 1717 | 2026-08-05T01:25:23+00:00 | Vulnerability · Source |
| CVE-2021-3537 | suse_vex | SUSE CVE CVE-2021-3537 | known affected: 188 known not affected: 82 recommended: 646 | 2026-08-05T01:25:21+00:00 | Vulnerability · Source |
| CVE-2021-3748 | suse_vex | SUSE CVE CVE-2021-3748 | known affected: 389 known not affected: 1 recommended: 1931 | 2026-08-05T01:25:18+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-29945 | suse_vex | SUSE CVE CVE-2021-29945 | known affected: 1 recommended: 444 | 2026-08-05T01:24:53+00:00 | Vulnerability · Source |
| CVE-2021-44224 | suse_vex | SUSE CVE CVE-2021-44224 | known affected: 395 known not affected: 7 recommended: 500 | 2026-08-05T01:24:47+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-47159 | suse_vex | SUSE CVE CVE-2021-47159 | known affected: 122 known not affected: 210 recommended: 70 | 2026-08-05T01:22:51+00:00 | Vulnerability · Source |