VEX records
Browse vendor VEX statements available in this Vulnerability-Lookup instance and pivot to the related vulnerability.
81615 VEX records
API response| Vulnerability | Source | Title | Product status | Imported | Links |
|---|---|---|---|---|---|
| CVE-2014-0050 | suse_vex | SUSE CVE CVE-2014-0050 | known affected: 394 known not affected: 50 recommended: 254 | 2026-10-08T00:02:04+00:00 | Vulnerability · Source |
| CVE-2015-1197 | suse_vex | SUSE CVE CVE-2015-1197 | known not affected: 16 recommended: 83 | 2026-10-08T00:01:54+00:00 | Vulnerability · Source |
| CVE-2015-3245 | suse_vex | SUSE CVE CVE-2015-3245 | recommended: 3 | 2026-10-08T00:01:49+00:00 | Vulnerability · Source |
| CVE-2016-3092 | suse_vex | SUSE CVE CVE-2016-3092 | known affected: 395 known not affected: 157 recommended: 275 | 2026-10-08T00:01:37+00:00 | Vulnerability · Source |
| CVE-2016-1000031 | suse_vex | SUSE CVE CVE-2016-1000031 | known affected: 7 known not affected: 15 recommended: 76 | 2026-10-08T00:01:24+00:00 | Vulnerability · Source |
| CVE-2017-18191 | suse_vex | SUSE CVE CVE-2017-18191 | recommended: 15 | 2026-10-08T00:01:09+00:00 | Vulnerability · Source |
| CVE-2017-18361 | suse_vex | SUSE CVE CVE-2017-18361 | recommended: 8 | 2026-10-08T00:01:06+00:00 | Vulnerability · Source |
| CVE-2018-20852 | suse_vex | SUSE CVE CVE-2018-20852 | known affected: 468 recommended: 1874 | 2026-10-08T00:00:49+00:00 | Vulnerability · Source |
| CVE-2019-8720 | suse_vex | SUSE CVE CVE-2019-8720 | known not affected: 10 recommended: 1060 | 2026-10-08T00:00:42+00:00 | Vulnerability · Source |
| CVE-2019-9455 | suse_vex | SUSE CVE CVE-2019-9455 | known affected: 15 known not affected: 40 recommended: 644 | 2026-10-08T00:00:39+00:00 | Vulnerability · Source |
| CVE-2019-9740 | suse_vex | SUSE CVE CVE-2019-9740 | known affected: 375 known not affected: 710 recommended: 741 | 2026-10-08T00:00:34+00:00 | Vulnerability · Source |
| CVE-2019-9947 | suse_vex | SUSE CVE CVE-2019-9947 | known affected: 398 known not affected: 19 recommended: 1674 | 2026-10-08T00:00:30+00:00 | Vulnerability · Source |
| CVE-2019-10160 | suse_vex | SUSE CVE CVE-2019-10160 | known affected: 491 known not affected: 43 recommended: 1751 | 2026-10-08T00:00:28+00:00 | Vulnerability · Source |
| CVE-2019-10906 | suse_vex | SUSE CVE CVE-2019-10906 | known affected: 344 known not affected: 3 recommended: 470 | 2026-10-08T00:00:25+00:00 | Vulnerability · Source |
| CVE-2019-14866 | suse_vex | SUSE CVE CVE-2019-14866 | known affected: 339 recommended: 294 | 2026-10-08T00:00:19+00:00 | Vulnerability · Source |
| CVE-2019-16056 | suse_vex | SUSE CVE CVE-2019-16056 | known affected: 432 recommended: 1543 | 2026-10-08T00:00:15+00:00 | Vulnerability · Source |
| CVE-2019-16935 | suse_vex | SUSE CVE CVE-2019-16935 | known affected: 353 recommended: 1538 | 2026-10-08T00:00:12+00:00 | Vulnerability · Source |
| CVE-2019-17626 | suse_vex | SUSE CVE CVE-2019-17626 | recommended: 35 | 2026-10-08T00:00:09+00:00 | Vulnerability · Source |
| CVE-2019-18348 | suse_vex | SUSE CVE CVE-2019-18348 | known affected: 242 known not affected: 92 recommended: 1912 | 2026-10-08T00:00:07+00:00 | Vulnerability · Source |
| CVE-2019-18808 | suse_vex | SUSE CVE CVE-2019-18808 | known affected: 437 known not affected: 214 recommended: 1306 | 2026-10-08T00:00:04+00:00 | Vulnerability · Source |
| CVE-2019-20907 | suse_vex | SUSE CVE CVE-2019-20907 | known affected: 381 known not affected: 81 recommended: 1725 | 2026-10-07T23:59:59+00:00 | Vulnerability · Source |
| CVE-2019-25045 | suse_vex | SUSE CVE CVE-2019-25045 | known affected: 394 known not affected: 323 recommended: 71 | 2026-10-07T23:59:56+00:00 | Vulnerability · Source |
| CVE-2020-0433 | suse_vex | SUSE CVE CVE-2020-0433 | known affected: 400 known not affected: 59 recommended: 455 | 2026-10-07T23:59:53+00:00 | Vulnerability · Source |
| CVE-2020-8492 | suse_vex | SUSE CVE CVE-2020-8492 | known affected: 236 known not affected: 142 recommended: 2183 | 2026-10-07T23:59:47+00:00 | Vulnerability · Source |
| CVE-2020-14381 | suse_vex | SUSE CVE CVE-2020-14381 | known affected: 558 known not affected: 55 recommended: 821 | 2026-10-07T23:59:39+00:00 | Vulnerability · Source |
| CVE-2020-26137 | suse_vex | SUSE CVE CVE-2020-26137 | known affected: 326 known not affected: 40 recommended: 1331 | 2026-10-07T23:59:33+00:00 | Vulnerability · Source |
| CVE-2020-27675 | suse_vex | SUSE CVE CVE-2020-27675 | known affected: 439 known not affected: 25 recommended: 954 | 2026-10-07T23:59:30+00:00 | Vulnerability · Source |
| CVE-2021-21236 | suse_vex | SUSE CVE CVE-2021-21236 | recommended: 16 | 2026-10-07T23:59:18+00:00 | Vulnerability · Source |
| CVE-2021-21347 | suse_vex | SUSE CVE CVE-2021-21347 | known affected: 394 recommended: 67 | 2026-10-07T23:59:15+00:00 | Vulnerability · Source |
| CVE-2021-21350 | suse_vex | SUSE CVE CVE-2021-21350 | known affected: 394 recommended: 67 | 2026-10-07T23:59:12+00:00 | Vulnerability · Source |
| CVE-2021-22923 | suse_vex | SUSE CVE CVE-2021-22923 | known affected: 316 known not affected: 37 recommended: 429 | 2026-10-07T23:59:07+00:00 | Vulnerability · Source |
| CVE-2021-24112 | suse_vex | SUSE CVE CVE-2021-24112 | recommended: 22 | 2026-10-07T23:59:04+00:00 | Vulnerability · Source |
| CVE-2021-27058 | suse_vex | SUSE CVE CVE-2021-27058 | recommended: 8 | 2026-10-07T23:59:00+00:00 | Vulnerability · Source |
| CVE-2021-28972 | suse_vex | SUSE CVE CVE-2021-28972 | known affected: 300 known not affected: 63 recommended: 1496 | 2026-10-07T23:58:56+00:00 | Vulnerability · Source |
| CVE-2021-29063 | suse_vex | SUSE CVE CVE-2021-29063 | recommended: 5 | 2026-10-07T23:58:53+00:00 | Vulnerability · Source |
| CVE-2021-29425 | suse_vex | SUSE CVE CVE-2021-29425 | known affected: 394 recommended: 75 | 2026-10-07T23:58:50+00:00 | Vulnerability · Source |
| CVE-2021-29650 | suse_vex | SUSE CVE CVE-2021-29650 | known affected: 320 known not affected: 61 recommended: 1706 | 2026-10-07T23:58:47+00:00 | Vulnerability · Source |
| CVE-2021-46924 | suse_vex | SUSE CVE CVE-2021-46924 | known affected: 385 known not affected: 103 recommended: 699 | 2026-10-07T23:58:37+00:00 | Vulnerability · Source |
| CVE-2021-47189 | suse_vex | SUSE CVE CVE-2021-47189 | known affected: 351 known not affected: 198 recommended: 599 | 2026-10-07T23:58:32+00:00 | Vulnerability · Source |
| CVE-2021-47302 | suse_vex | SUSE CVE CVE-2021-47302 | known affected: 453 known not affected: 228 recommended: 205 | 2026-10-07T23:58:29+00:00 | Vulnerability · Source |
| CVE-2021-47455 | suse_vex | SUSE CVE CVE-2021-47455 | known affected: 460 known not affected: 65 recommended: 517 | 2026-10-07T23:58:24+00:00 | Vulnerability · Source |
| CVE-2021-47478 | suse_vex | SUSE CVE CVE-2021-47478 | known affected: 288 known not affected: 199 recommended: 627 | 2026-10-07T23:58:21+00:00 | Vulnerability · Source |
| CVE-2022-0235 | suse_vex | SUSE CVE CVE-2022-0235 | recommended: 412 | 2026-10-07T23:58:17+00:00 | Vulnerability · Source |
| CVE-2022-0330 | suse_vex | SUSE CVE CVE-2022-0330 | known affected: 351 known not affected: 87 recommended: 1569 | 2026-10-07T23:58:14+00:00 | Vulnerability · Source |
| CVE-2022-2590 | suse_vex | SUSE CVE CVE-2022-2590 | known not affected: 357 recommended: 6 | 2026-10-07T23:58:08+00:00 | Vulnerability · Source |
| CVE-2022-23042 | suse_vex | SUSE CVE CVE-2022-23042 | known affected: 344 known not affected: 65 recommended: 1298 | 2026-10-07T23:58:01+00:00 | Vulnerability · Source |
| CVE-2022-42003 | suse_vex | SUSE CVE CVE-2022-42003 | known affected: 394 recommended: 68 | 2026-10-07T23:57:51+00:00 | Vulnerability · Source |
| CVE-2022-42004 | suse_vex | SUSE CVE CVE-2022-42004 | known affected: 394 recommended: 66 | 2026-10-07T23:57:49+00:00 | Vulnerability · Source |
| CVE-2022-49098 | suse_vex | SUSE CVE CVE-2022-49098 | known affected: 394 known not affected: 287 recommended: 387 | 2026-10-07T23:57:40+00:00 | Vulnerability · Source |
| CVE-2022-49490 | suse_vex | SUSE CVE CVE-2022-49490 | known affected: 409 known not affected: 243 recommended: 319 | 2026-10-07T23:57:35+00:00 | Vulnerability · Source |