VEX records
Browse vendor VEX statements available in this Vulnerability-Lookup instance and pivot to the related vulnerability.
291935 VEX records
API response| Vulnerability | Source | Title | Product status | Imported | Links |
|---|---|---|---|---|---|
| CVE-2019-14982 | suse_vex | SUSE CVE CVE-2019-14982 | known not affected: 48 | 2026-07-28T23:58:25+00:00 | Vulnerability · Source |
| CVE-2019-15917 | suse_vex | SUSE CVE CVE-2019-15917 | known affected: 113 known not affected: 203 recommended: 714 | 2026-07-28T23:58:21+00:00 | Vulnerability · Source |
| CVE-2019-15918 | suse_vex | SUSE CVE CVE-2019-15918 | known not affected: 346 | 2026-07-28T23:58:20+00:00 | Vulnerability · Source |
| CVE-2019-16167 | suse_vex | SUSE CVE CVE-2019-16167 | known affected: 420 known not affected: 3 recommended: 135 | 2026-07-28T23:58:18+00:00 | Vulnerability · Source |
| CVE-2019-16230 | suse_vex | SUSE CVE CVE-2019-16230 | known affected: 28 known not affected: 136 | 2026-07-28T23:58:17+00:00 | Vulnerability · Source |
| CVE-2019-16413 | suse_vex | SUSE CVE CVE-2019-16413 | known affected: 3 known not affected: 257 recommended: 271 | 2026-07-28T23:58:14+00:00 | Vulnerability · Source |
| CVE-2019-16905 | suse_vex | SUSE CVE CVE-2019-16905 | known not affected: 82 | 2026-07-28T23:58:12+00:00 | Vulnerability · Source |
| CVE-2019-17017 | suse_vex | SUSE CVE CVE-2019-17017 | known affected: 20 recommended: 414 | 2026-07-28T23:58:11+00:00 | Vulnerability · Source |
| CVE-2019-17052 | suse_vex | SUSE CVE CVE-2019-17052 | known not affected: 186 recommended: 55 | 2026-07-28T23:58:09+00:00 | Vulnerability · Source |
| CVE-2019-17054 | suse_vex | SUSE CVE CVE-2019-17054 | known not affected: 193 recommended: 55 | 2026-07-28T23:58:07+00:00 | Vulnerability · Source |
| CVE-2019-17350 | suse_vex | SUSE CVE CVE-2019-17350 | known not affected: 76 recommended: 49 | 2026-07-28T23:58:06+00:00 | Vulnerability · Source |
| CVE-2019-17514 | suse_vex | SUSE CVE CVE-2019-17514 | known affected: 36 known not affected: 432 | 2026-07-28T23:58:04+00:00 | Vulnerability · Source |
| CVE-2019-17569 | suse_vex | SUSE CVE CVE-2019-17569 | known affected: 484 known not affected: 56 recommended: 386 | 2026-07-28T23:58:02+00:00 | Vulnerability · Source |
| CVE-2019-18421 | suse_vex | SUSE CVE CVE-2019-18421 | recommended: 269 | 2026-07-28T23:58:01+00:00 | Vulnerability · Source |
| CVE-2019-18678 | suse_vex | SUSE CVE CVE-2019-18678 | known affected: 395 recommended: 74 | 2026-07-28T23:57:59+00:00 | Vulnerability · Source |
| CVE-2019-18680 | suse_vex | SUSE CVE CVE-2019-18680 | known affected: 3 known not affected: 271 recommended: 173 | 2026-07-28T23:57:58+00:00 | Vulnerability · Source |
| CVE-2019-18808 | suse_vex | SUSE CVE CVE-2019-18808 | known affected: 420 known not affected: 197 recommended: 1335 | 2026-07-28T23:57:56+00:00 | Vulnerability · Source |
| CVE-2019-19043 | suse_vex | SUSE CVE CVE-2019-19043 | known not affected: 320 recommended: 707 | 2026-07-28T23:57:54+00:00 | Vulnerability · Source |
| CVE-2019-19065 | suse_vex | SUSE CVE CVE-2019-19065 | known affected: 452 known not affected: 115 recommended: 1453 | 2026-07-28T23:57:52+00:00 | Vulnerability · Source |
| CVE-2019-19079 | suse_vex | SUSE CVE CVE-2019-19079 | known not affected: 208 | 2026-07-28T23:57:51+00:00 | Vulnerability · Source |
| CVE-2019-19204 | suse_vex | SUSE CVE CVE-2019-19204 | known affected: 245 recommended: 305 | 2026-07-28T23:57:49+00:00 | Vulnerability · Source |
| CVE-2019-19234 | suse_vex | SUSE CVE CVE-2019-19234 | known not affected: 92 recommended: 1 | 2026-07-28T23:57:48+00:00 | Vulnerability · Source |
| CVE-2019-19447 | suse_vex | SUSE CVE CVE-2019-19447 | known affected: 476 known not affected: 67 recommended: 1538 | 2026-07-28T23:57:46+00:00 | Vulnerability · Source |
| CVE-2019-19481 | suse_vex | SUSE CVE CVE-2019-19481 | known not affected: 79 recommended: 5 | 2026-07-28T23:57:44+00:00 | Vulnerability · Source |
| CVE-2019-1010180 | suse_vex | SUSE CVE CVE-2019-1010180 | known affected: 465 recommended: 660 | 2026-07-28T23:57:42+00:00 | Vulnerability · Source |
| CVE-2020-0499 | suse_vex | SUSE CVE CVE-2020-0499 | known affected: 472 known not affected: 4 recommended: 363 | 2026-07-28T23:57:40+00:00 | Vulnerability · Source |
| CVE-2020-0549 | suse_vex | SUSE CVE CVE-2020-0549 | known affected: 15 known not affected: 35 recommended: 185 | 2026-07-28T23:57:39+00:00 | Vulnerability · Source |
| CVE-2020-1931 | suse_vex | SUSE CVE CVE-2020-1931 | known affected: 24 recommended: 224 | 2026-07-28T23:57:37+00:00 | Vulnerability · Source |
| CVE-2020-1938 | suse_vex | SUSE CVE CVE-2020-1938 | known affected: 484 known not affected: 56 recommended: 690 | 2026-07-28T23:57:35+00:00 | Vulnerability · Source |
| CVE-2020-2754 | suse_vex | SUSE CVE CVE-2020-2754 | known affected: 454 recommended: 961 | 2026-07-28T23:57:32+00:00 | Vulnerability · Source |
| CVE-2020-6582 | suse_vex | SUSE CVE CVE-2020-6582 | known not affected: 39 | 2026-07-28T23:57:26+00:00 | Vulnerability · Source |
| CVE-2020-6816 | suse_vex | SUSE CVE CVE-2020-6816 | recommended: 19 | 2026-07-28T23:57:25+00:00 | Vulnerability · Source |
| CVE-2020-9366 | suse_vex | SUSE CVE CVE-2020-9366 | known not affected: 36 | 2026-07-28T23:57:21+00:00 | Vulnerability · Source |
| CVE-2020-10732 | suse_vex | SUSE CVE CVE-2020-10732 | known affected: 438 known not affected: 137 recommended: 1628 | 2026-07-28T23:57:18+00:00 | Vulnerability · Source |
| CVE-2020-11565 | suse_vex | SUSE CVE CVE-2020-11565 | recommended: 33 | 2026-07-28T23:57:15+00:00 | Vulnerability · Source |
| CVE-2020-12059 | suse_vex | SUSE CVE CVE-2020-12059 | known not affected: 288 recommended: 198 | 2026-07-28T23:57:13+00:00 | Vulnerability · Source |
| CVE-2020-12409 | suse_vex | SUSE CVE CVE-2020-12409 | known affected: 48 recommended: 9 | 2026-07-28T23:57:11+00:00 | Vulnerability · Source |
| CVE-2020-12865 | suse_vex | SUSE CVE CVE-2020-12865 | known affected: 18 known not affected: 3 recommended: 222 | 2026-07-28T23:57:09+00:00 | Vulnerability · Source |
| CVE-2020-13253 | suse_vex | SUSE CVE CVE-2020-13253 | known affected: 394 known not affected: 2441 recommended: 133 | 2026-07-28T23:57:08+00:00 | Vulnerability · Source |
| CVE-2020-13950 | suse_vex | SUSE CVE CVE-2020-13950 | known affected: 419 known not affected: 186 recommended: 199 | 2026-07-28T23:57:04+00:00 | Vulnerability · Source |
| CVE-2020-14792 | suse_vex | SUSE CVE CVE-2020-14792 | known affected: 484 recommended: 1243 | 2026-07-28T23:56:57+00:00 | Vulnerability · Source |
| CVE-2020-15663 | suse_vex | SUSE CVE CVE-2020-15663 | known affected: 21 recommended: 401 | 2026-07-28T23:56:55+00:00 | Vulnerability · Source |
| CVE-2020-15780 | suse_vex | SUSE CVE CVE-2020-15780 | known affected: 470 known not affected: 143 recommended: 1551 | 2026-07-28T23:56:53+00:00 | Vulnerability · Source |
| CVE-2020-16125 | suse_vex | SUSE CVE CVE-2020-16125 | known affected: 65 known not affected: 4 recommended: 547 | 2026-07-28T23:56:50+00:00 | Vulnerability · Source |
| CVE-2020-16166 | suse_vex | SUSE CVE CVE-2020-16166 | known affected: 407 known not affected: 2 recommended: 1603 | 2026-07-28T23:56:48+00:00 | Vulnerability · Source |
| CVE-2020-17438 | suse_vex | SUSE CVE CVE-2020-17438 | known affected: 9 known not affected: 42 recommended: 289 | 2026-07-28T23:56:47+00:00 | Vulnerability · Source |
| CVE-2020-18651 | suse_vex | SUSE CVE CVE-2020-18651 | known affected: 82 recommended: 70 | 2026-07-28T23:56:45+00:00 | Vulnerability · Source |
| CVE-2020-23903 | suse_vex | SUSE CVE CVE-2020-23903 | known affected: 71 recommended: 138 | 2026-07-28T23:56:42+00:00 | Vulnerability · Source |
| CVE-2020-25662 | suse_vex | SUSE CVE CVE-2020-25662 | known not affected: 327 recommended: 20 | 2026-07-28T23:56:35+00:00 | Vulnerability · Source |
| CVE-2020-26421 | suse_vex | SUSE CVE CVE-2020-26421 | known affected: 104 known not affected: 21 recommended: 683 | 2026-07-28T23:56:27+00:00 | Vulnerability · Source |