VEX records
Browse vendor VEX statements available in this Vulnerability-Lookup instance and pivot to the related vulnerability.
286392 VEX records
API response| Vulnerability | Source | Title | Product status | Imported | Links |
|---|---|---|---|---|---|
| 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-3639 | suse_vex | SUSE CVE CVE-2018-3639 | known affected: 446 known not affected: 2538 recommended: 6375 | 2026-07-26T23:44:16+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-5127 | suse_vex | SUSE CVE CVE-2018-5127 | known affected: 2 recommended: 396 | 2026-07-26T23:44:12+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-5784 | suse_vex | SUSE CVE CVE-2018-5784 | known affected: 441 known not affected: 79 recommended: 247 | 2026-07-26T23:44:09+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-7757 | suse_vex | SUSE CVE CVE-2018-7757 | known affected: 44 known not affected: 240 recommended: 395 | 2026-07-26T23:44:02+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-9256 | suse_vex | SUSE CVE CVE-2018-9256 | known affected: 89 known not affected: 115 recommended: 555 | 2026-07-26T23:43:56+00:00 | Vulnerability · Source |
| CVE-2018-9258 | suse_vex | SUSE CVE CVE-2018-9258 | known affected: 89 known not affected: 115 recommended: 444 | 2026-07-26T23:43:55+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-11235 | suse_vex | SUSE CVE CVE-2018-11235 | known affected: 128 known not affected: 38 recommended: 1099 | 2026-07-26T23:43:51+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-12389 | suse_vex | SUSE CVE CVE-2018-12389 | known affected: 1 recommended: 407 | 2026-07-26T23:43:47+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-14048 | suse_vex | SUSE CVE CVE-2018-14048 | known not affected: 153 recommended: 63 | 2026-07-26T23:43:42+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-14355 | suse_vex | SUSE CVE CVE-2018-14355 | known affected: 29 recommended: 202 | 2026-07-26T23:43:39+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-15120 | suse_vex | SUSE CVE CVE-2018-15120 | known affected: 394 known not affected: 49 recommended: 267 | 2026-07-26T23:43:36+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-16876 | suse_vex | SUSE CVE CVE-2018-16876 | known affected: 5 known not affected: 1 recommended: 247 | 2026-07-26T23:43:31+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-2018-20330 | suse_vex | SUSE CVE CVE-2018-20330 | known not affected: 163 recommended: 167 | 2026-07-26T23:43:24+00:00 | Vulnerability · Source |
| CVE-2018-20856 | suse_vex | SUSE CVE CVE-2018-20856 | known affected: 68 known not affected: 382 recommended: 216 | 2026-07-26T23:43:23+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-3690 | suse_vex | SUSE CVE CVE-2019-3690 | known affected: 344 known not affected: 37 recommended: 240 | 2026-07-26T23:43:18+00:00 | Vulnerability · Source |
| CVE-2019-3856 | suse_vex | SUSE CVE CVE-2019-3856 | known affected: 460 known not affected: 76 recommended: 357 | 2026-07-26T23:43:16+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-10164 | suse_vex | SUSE CVE CVE-2019-10164 | known affected: 129 known not affected: 208 recommended: 848 | 2026-07-26T23:42:59+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-12293 | suse_vex | SUSE CVE CVE-2019-12293 | known affected: 8 known not affected: 314 recommended: 66 | 2026-07-26T23:42:53+00:00 | Vulnerability · Source |