VEX records
Browse vendor VEX statements available in this Vulnerability-Lookup instance and pivot to the related vulnerability.
286713 VEX records
API response| Vulnerability | Source | Title | Product status | Imported | Links |
|---|---|---|---|---|---|
| CVE-2019-9797 | suse_vex | SUSE CVE CVE-2019-9797 | known affected: 20 known not affected: 8 recommended: 104 | 2026-07-28T23:59:00+00:00 | Vulnerability · Source |
| CVE-2019-10081 | suse_vex | SUSE CVE CVE-2019-10081 | known affected: 516 known not affected: 88 recommended: 382 | 2026-07-28T23:58:58+00:00 | Vulnerability · Source |
| CVE-2019-10129 | suse_vex | SUSE CVE CVE-2019-10129 | known not affected: 198 recommended: 11 | 2026-07-28T23:58:57+00:00 | Vulnerability · Source |
| CVE-2019-10131 | suse_vex | SUSE CVE CVE-2019-10131 | known affected: 96 known not affected: 46 recommended: 168 | 2026-07-28T23:58:56+00:00 | Vulnerability · Source |
| CVE-2019-11038 | suse_vex | SUSE CVE CVE-2019-11038 | known affected: 1490 known not affected: 500 recommended: 911 | 2026-07-28T23:58:53+00:00 | Vulnerability · Source |
| CVE-2019-11324 | suse_vex | SUSE CVE CVE-2019-11324 | known affected: 373 known not affected: 19 recommended: 686 | 2026-07-28T23:58:51+00:00 | Vulnerability · Source |
| CVE-2019-11697 | suse_vex | SUSE CVE CVE-2019-11697 | known affected: 20 known not affected: 8 recommended: 9 | 2026-07-28T23:58:49+00:00 | Vulnerability · Source |
| CVE-2019-11724 | suse_vex | SUSE CVE CVE-2019-11724 | known affected: 21 recommended: 613 | 2026-07-28T23:58:48+00:00 | Vulnerability · Source |
| CVE-2019-11815 | suse_vex | SUSE CVE CVE-2019-11815 | known affected: 99 known not affected: 109 recommended: 724 | 2026-07-28T23:58:46+00:00 | Vulnerability · Source |
| CVE-2019-12526 | suse_vex | SUSE CVE CVE-2019-12526 | known affected: 408 known not affected: 4 recommended: 74 | 2026-07-28T23:58:44+00:00 | Vulnerability · Source |
| CVE-2019-12854 | suse_vex | SUSE CVE CVE-2019-12854 | known affected: 401 known not affected: 21 recommended: 50 | 2026-07-28T23:58:42+00:00 | Vulnerability · Source |
| CVE-2019-13118 | suse_vex | SUSE CVE CVE-2019-13118 | known affected: 415 recommended: 236 | 2026-07-28T23:58:40+00:00 | Vulnerability · Source |
| CVE-2019-13134 | suse_vex | SUSE CVE CVE-2019-13134 | known affected: 142 recommended: 728 | 2026-07-28T23:58:39+00:00 | Vulnerability · Source |
| CVE-2019-13164 | suse_vex | SUSE CVE CVE-2019-13164 | known affected: 394 known not affected: 667 recommended: 1891 | 2026-07-28T23:58:37+00:00 | Vulnerability · Source |
| CVE-2019-13307 | suse_vex | SUSE CVE CVE-2019-13307 | known affected: 142 known not affected: 117 recommended: 708 | 2026-07-28T23:58:35+00:00 | Vulnerability · Source |
| CVE-2019-13627 | suse_vex | SUSE CVE CVE-2019-13627 | known affected: 388 recommended: 501 | 2026-07-28T23:58:34+00:00 | Vulnerability · Source |
| CVE-2019-14193 | suse_vex | SUSE CVE CVE-2019-14193 | known affected: 19 recommended: 46 | 2026-07-28T23:58:32+00:00 | Vulnerability · Source |
| CVE-2019-14197 | suse_vex | SUSE CVE CVE-2019-14197 | known affected: 19 recommended: 46 | 2026-07-28T23:58:31+00:00 | Vulnerability · Source |
| CVE-2019-14562 | suse_vex | SUSE CVE CVE-2019-14562 | known affected: 62 recommended: 260 | 2026-07-28T23:58:29+00:00 | Vulnerability · Source |
| CVE-2019-14902 | suse_vex | SUSE CVE CVE-2019-14902 | known affected: 675 known not affected: 1263 recommended: 3471 | 2026-07-28T23:58:27+00:00 | Vulnerability · Source |
| 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-15145 | suse_vex | SUSE CVE CVE-2019-15145 | known affected: 46 known not affected: 27 recommended: 152 | 2026-07-28T23:58:23+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-16319 | suse_vex | SUSE CVE CVE-2019-16319 | known not affected: 116 recommended: 677 | 2026-07-28T23:58:15+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 |