VEX records
Browse vendor VEX statements available in this Vulnerability-Lookup instance and pivot to the related vulnerability.
291994 VEX records
API response| Vulnerability | Source | Title | Product status | Imported | Links |
|---|---|---|---|---|---|
| CVE-2017-13089 | suse_vex | SUSE CVE CVE-2017-13089 | known affected: 320 known not affected: 29 recommended: 164 | 2026-07-26T23:44:47+00:00 | Vulnerability · Source |
| CVE-2017-13726 | suse_vex | SUSE CVE CVE-2017-13726 | known not affected: 45 recommended: 18 | 2026-07-26T23:44:45+00:00 | Vulnerability · Source |
| CVE-2017-14132 | suse_vex | SUSE CVE CVE-2017-14132 | known affected: 46 recommended: 154 | 2026-07-26T23:44:43+00:00 | Vulnerability · Source |
| CVE-2017-14333 | suse_vex | SUSE CVE CVE-2017-14333 | known affected: 394 known not affected: 21 recommended: 330 | 2026-07-26T23:44:42+00:00 | Vulnerability · Source |
| CVE-2017-15591 | suse_vex | SUSE CVE CVE-2017-15591 | known affected: 31 known not affected: 125 recommended: 86 | 2026-07-26T23:44:37+00:00 | Vulnerability · Source |
| CVE-2017-16353 | suse_vex | SUSE CVE CVE-2017-16353 | known affected: 94 recommended: 186 | 2026-07-26T23:44:35+00:00 | Vulnerability · Source |
| CVE-2017-17045 | suse_vex | SUSE CVE CVE-2017-17045 | known affected: 32 known not affected: 42 | 2026-07-26T23:44:33+00:00 | Vulnerability · Source |
| CVE-2017-18027 | suse_vex | SUSE CVE CVE-2017-18027 | known affected: 94 known not affected: 14 recommended: 172 | 2026-07-26T23:44:31+00:00 | Vulnerability · Source |
| CVE-2017-18219 | suse_vex | SUSE CVE CVE-2017-18219 | known not affected: 94 recommended: 50 | 2026-07-26T23:44:29+00:00 | Vulnerability · Source |
| CVE-2017-18235 | suse_vex | SUSE CVE CVE-2017-18235 | known not affected: 178 | 2026-07-26T23:44:28+00:00 | Vulnerability · Source |
| CVE-2017-1000407 | suse_vex | SUSE CVE CVE-2017-1000407 | known not affected: 41 recommended: 207 | 2026-07-26T23:44:23+00:00 | Vulnerability · Source |
| CVE-2018-1656 | suse_vex | SUSE CVE CVE-2018-1656 | known affected: 503 recommended: 415 | 2026-07-26T23:44:21+00:00 | Vulnerability · Source |
| CVE-2018-2814 | suse_vex | SUSE CVE CVE-2018-2814 | known affected: 527 known not affected: 179 recommended: 1098 | 2026-07-26T23:44:19+00:00 | Vulnerability · Source |
| CVE-2018-5093 | suse_vex | SUSE CVE CVE-2018-5093 | known affected: 1 known not affected: 42 recommended: 12 | 2026-07-26T23:44:14+00:00 | Vulnerability · Source |
| CVE-2018-5734 | suse_vex | SUSE CVE CVE-2018-5734 | known not affected: 95 | 2026-07-26T23:44:10+00:00 | Vulnerability · Source |
| CVE-2018-5873 | suse_vex | SUSE CVE CVE-2018-5873 | known not affected: 152 | 2026-07-26T23:44:07+00:00 | Vulnerability · Source |
| CVE-2018-6556 | suse_vex | SUSE CVE CVE-2018-6556 | known not affected: 72 recommended: 19 | 2026-07-26T23:44:06+00:00 | Vulnerability · Source |
| CVE-2018-7273 | suse_vex | SUSE CVE CVE-2018-7273 | known not affected: 49 | 2026-07-26T23:44:04+00:00 | Vulnerability · Source |
| CVE-2018-8020 | suse_vex | SUSE CVE CVE-2018-8020 | known not affected: 166 recommended: 16 | 2026-07-26T23:44:01+00:00 | Vulnerability · Source |
| CVE-2018-8104 | suse_vex | SUSE CVE CVE-2018-8104 | known not affected: 381 | 2026-07-26T23:43:59+00:00 | Vulnerability · Source |
| CVE-2018-9138 | suse_vex | SUSE CVE CVE-2018-9138 | known not affected: 297 | 2026-07-26T23:43:58+00:00 | Vulnerability · Source |
| CVE-2018-9517 | suse_vex | SUSE CVE CVE-2018-9517 | known affected: 388 known not affected: 365 recommended: 382 | 2026-07-26T23:43:53+00:00 | Vulnerability · Source |
| CVE-2018-12233 | suse_vex | SUSE CVE CVE-2018-12233 | known affected: 30 known not affected: 345 recommended: 505 | 2026-07-26T23:43:49+00:00 | Vulnerability · Source |
| CVE-2018-12928 | suse_vex | SUSE CVE CVE-2018-12928 | known not affected: 563 | 2026-07-26T23:43:45+00:00 | Vulnerability · Source |
| CVE-2018-13095 | suse_vex | SUSE CVE CVE-2018-13095 | known affected: 48 known not affected: 204 recommended: 577 | 2026-07-26T23:43:43+00:00 | Vulnerability · Source |
| CVE-2018-14353 | suse_vex | SUSE CVE CVE-2018-14353 | known affected: 29 recommended: 200 | 2026-07-26T23:43:40+00:00 | Vulnerability · Source |
| CVE-2018-14463 | suse_vex | SUSE CVE CVE-2018-14463 | known affected: 333 recommended: 145 | 2026-07-26T23:43:37+00:00 | Vulnerability · Source |
| CVE-2018-15469 | suse_vex | SUSE CVE CVE-2018-15469 | known affected: 320 known not affected: 97 recommended: 425 | 2026-07-26T23:43:35+00:00 | Vulnerability · Source |
| CVE-2018-15686 | suse_vex | SUSE CVE CVE-2018-15686 | known affected: 320 recommended: 1300 | 2026-07-26T23:43:33+00:00 | Vulnerability · Source |
| CVE-2018-19824 | suse_vex | SUSE CVE CVE-2018-19824 | known affected: 74 known not affected: 235 recommended: 788 | 2026-07-26T23:43:28+00:00 | Vulnerability · Source |
| CVE-2018-20030 | suse_vex | SUSE CVE CVE-2018-20030 | known affected: 27 recommended: 208 | 2026-07-26T23:43:26+00:00 | Vulnerability · Source |
| CVE-2019-2968 | suse_vex | SUSE CVE CVE-2019-2968 | known affected: 13 known not affected: 121 recommended: 10 | 2026-07-26T23:43:20+00:00 | Vulnerability · Source |
| CVE-2019-4473 | suse_vex | SUSE CVE CVE-2019-4473 | known affected: 88 known not affected: 9 recommended: 434 | 2026-07-26T23:43:15+00:00 | Vulnerability · Source |
| CVE-2019-5736 | suse_vex | SUSE CVE CVE-2019-5736 | known affected: 347 known not affected: 179 recommended: 1109 | 2026-07-26T23:43:13+00:00 | Vulnerability · Source |
| CVE-2019-8597 | suse_vex | SUSE CVE CVE-2019-8597 | known affected: 153 known not affected: 82 recommended: 298 | 2026-07-26T23:43:10+00:00 | Vulnerability · Source |
| CVE-2019-9162 | suse_vex | SUSE CVE CVE-2019-9162 | known not affected: 495 | 2026-07-26T23:43:08+00:00 | Vulnerability · Source |
| CVE-2019-9444 | suse_vex | SUSE CVE CVE-2019-9444 | known not affected: 52 | 2026-07-26T23:43:06+00:00 | Vulnerability · Source |
| CVE-2019-9446 | suse_vex | SUSE CVE CVE-2019-9446 | known not affected: 215 | 2026-07-26T23:43:05+00:00 | Vulnerability · Source |
| CVE-2019-9810 | suse_vex | SUSE CVE CVE-2019-9810 | known affected: 21 recommended: 420 | 2026-07-26T23:43:03+00:00 | Vulnerability · Source |
| CVE-2019-10072 | suse_vex | SUSE CVE CVE-2019-10072 | known affected: 484 known not affected: 129 recommended: 215 | 2026-07-26T23:43:01+00:00 | Vulnerability · Source |
| CVE-2019-11709 | suse_vex | SUSE CVE CVE-2019-11709 | known affected: 21 recommended: 1422 | 2026-07-26T23:42:56+00:00 | Vulnerability · Source |
| CVE-2019-12083 | suse_vex | SUSE CVE CVE-2019-12083 | known not affected: 44 recommended: 520 | 2026-07-26T23:42:54+00:00 | Vulnerability · Source |
| CVE-2019-12447 | suse_vex | SUSE CVE CVE-2019-12447 | known not affected: 150 recommended: 503 | 2026-07-26T23:42:51+00:00 | Vulnerability · Source |
| CVE-2019-12454 | suse_vex | SUSE CVE CVE-2019-12454 | known not affected: 332 | 2026-07-26T23:42:50+00:00 | Vulnerability · Source |
| CVE-2019-13109 | suse_vex | SUSE CVE CVE-2019-13109 | known affected: 32 known not affected: 55 recommended: 92 | 2026-07-26T23:42:48+00:00 | Vulnerability · Source |
| CVE-2019-13112 | suse_vex | SUSE CVE CVE-2019-13112 | known affected: 7 known not affected: 83 recommended: 27 | 2026-07-26T23:42:47+00:00 | Vulnerability · Source |
| CVE-2019-13309 | suse_vex | SUSE CVE CVE-2019-13309 | known affected: 45 known not affected: 371 recommended: 622 | 2026-07-26T23:42:45+00:00 | Vulnerability · Source |
| CVE-2019-14287 | suse_vex | SUSE CVE CVE-2019-14287 | known affected: 334 known not affected: 3 recommended: 340 | 2026-07-26T23:42:43+00:00 | Vulnerability · Source |
| CVE-2019-15118 | suse_vex | SUSE CVE CVE-2019-15118 | known not affected: 35 recommended: 914 | 2026-07-26T23:42:39+00:00 | Vulnerability · Source |
| CVE-2019-15163 | suse_vex | SUSE CVE CVE-2019-15163 | known affected: 12 known not affected: 8 recommended: 77 | 2026-07-26T23:42:38+00:00 | Vulnerability · Source |