VEX records
Browse vendor VEX statements available in this Vulnerability-Lookup instance and pivot to the related vulnerability.
127033 VEX records
API response| Vulnerability | Source | Title | Product status | Imported | Links |
|---|---|---|---|---|---|
| CVE-2016-4992 | suse_vex | SUSE CVE CVE-2016-4992 | known not affected: 204 recommended: 157 | 2026-11-14T17:56:03+00:00 | Vulnerability · Source |
| CVE-2016-5260 | suse_vex | SUSE CVE CVE-2016-5260 | known affected: 1 recommended: 250 | 2026-11-14T17:56:00+00:00 | Vulnerability · Source |
| CVE-2016-5274 | suse_vex | SUSE CVE CVE-2016-5274 | known affected: 5 recommended: 332 | 2026-11-14T17:55:58+00:00 | Vulnerability · Source |
| CVE-2016-7132 | suse_vex | SUSE CVE CVE-2016-7132 | known not affected: 517 recommended: 1785 | 2026-11-14T17:55:52+00:00 | Vulnerability · Source |
| CVE-2016-7598 | suse_vex | SUSE CVE CVE-2016-7598 | known not affected: 105 recommended: 927 | 2026-11-14T17:55:49+00:00 | Vulnerability · Source |
| CVE-2016-8867 | suse_vex | SUSE CVE CVE-2016-8867 | known affected: 320 known not affected: 156 recommended: 349 | 2026-11-14T17:55:45+00:00 | Vulnerability · Source |
| CVE-2016-9387 | suse_vex | SUSE CVE CVE-2016-9387 | known not affected: 140 recommended: 134 | 2026-11-14T17:55:42+00:00 | Vulnerability · Source |
| CVE-2016-9901 | suse_vex | SUSE CVE CVE-2016-9901 | known affected: 1 recommended: 335 | 2026-11-14T17:55:38+00:00 | Vulnerability · Source |
| CVE-2016-10093 | suse_vex | SUSE CVE CVE-2016-10093 | known affected: 69 known not affected: 10 recommended: 287 | 2026-11-14T17:55:35+00:00 | Vulnerability · Source |
| CVE-2016-10517 | suse_vex | SUSE CVE CVE-2016-10517 | recommended: 38 | 2026-11-14T17:55:30+00:00 | Vulnerability · Source |
| CVE-2016-10713 | suse_vex | SUSE CVE CVE-2016-10713 | known affected: 411 known not affected: 26 recommended: 77 | 2026-11-14T17:55:28+00:00 | Vulnerability · Source |
| CVE-2016-1000338 | suse_vex | SUSE CVE CVE-2016-1000338 | known not affected: 18 recommended: 142 | 2026-11-14T17:55:24+00:00 | Vulnerability · Source |
| CVE-2017-3512 | suse_vex | SUSE CVE CVE-2017-3512 | known affected: 1 known not affected: 117 recommended: 540 | 2026-11-14T17:55:20+00:00 | Vulnerability · Source |
| CVE-2017-3640 | suse_vex | SUSE CVE CVE-2017-3640 | known affected: 1 known not affected: 84 | 2026-11-14T17:55:18+00:00 | Vulnerability · Source |
| CVE-2017-5383 | suse_vex | SUSE CVE CVE-2017-5383 | known affected: 1 recommended: 416 | 2026-11-14T17:55:15+00:00 | Vulnerability · Source |
| CVE-2017-5386 | suse_vex | SUSE CVE CVE-2017-5386 | known affected: 1 recommended: 331 | 2026-11-14T17:55:12+00:00 | Vulnerability · Source |
| CVE-2017-5427 | suse_vex | SUSE CVE CVE-2017-5427 | known affected: 1 recommended: 249 | 2026-11-14T17:55:10+00:00 | Vulnerability · Source |
| CVE-2017-5429 | suse_vex | SUSE CVE CVE-2017-5429 | known not affected: 50 recommended: 770 | 2026-11-14T17:55:08+00:00 | Vulnerability · Source |
| CVE-2017-5433 | suse_vex | SUSE CVE CVE-2017-5433 | known not affected: 50 recommended: 770 | 2026-11-14T17:55:05+00:00 | Vulnerability · Source |
| CVE-2017-5446 | suse_vex | SUSE CVE CVE-2017-5446 | known not affected: 50 recommended: 770 | 2026-11-14T17:55:03+00:00 | Vulnerability · Source |
| CVE-2017-5459 | suse_vex | SUSE CVE CVE-2017-5459 | known not affected: 50 recommended: 770 | 2026-11-14T17:55:00+00:00 | Vulnerability · Source |
| CVE-2017-5468 | suse_vex | SUSE CVE CVE-2017-5468 | known not affected: 50 recommended: 12 | 2026-11-14T17:54:58+00:00 | Vulnerability · Source |
| CVE-2017-7768 | suse_vex | SUSE CVE CVE-2017-7768 | known affected: 2 known not affected: 50 recommended: 376 | 2026-11-14T17:54:50+00:00 | Vulnerability · Source |
| CVE-2017-7776 | suse_vex | SUSE CVE CVE-2017-7776 | known affected: 2 known not affected: 50 recommended: 324 | 2026-11-14T17:54:48+00:00 | Vulnerability · Source |
| CVE-2017-7787 | suse_vex | SUSE CVE CVE-2017-7787 | known affected: 1 known not affected: 50 recommended: 417 | 2026-11-14T17:54:46+00:00 | Vulnerability · Source |
| CVE-2017-7859 | suse_vex | SUSE CVE CVE-2017-7859 | recommended: 701 | 2026-11-14T17:54:43+00:00 | Vulnerability · Source |
| CVE-2017-7862 | suse_vex | SUSE CVE CVE-2017-7862 | recommended: 672 | 2026-11-14T17:54:41+00:00 | Vulnerability · Source |
| CVE-2017-10320 | suse_vex | SUSE CVE CVE-2017-10320 | known not affected: 309 recommended: 423 | 2026-11-14T17:54:35+00:00 | Vulnerability · Source |
| CVE-2017-12188 | suse_vex | SUSE CVE CVE-2017-12188 | known not affected: 380 recommended: 26 | 2026-11-14T17:54:29+00:00 | Vulnerability · Source |
| CVE-2017-14061 | suse_vex | SUSE CVE CVE-2017-14061 | known affected: 16 known not affected: 276 | 2026-11-14T17:54:23+00:00 | Vulnerability · Source |
| CVE-2017-14804 | suse_vex | SUSE CVE CVE-2017-14804 | known affected: 1 recommended: 206 | 2026-11-14T17:54:21+00:00 | Vulnerability · Source |
| CVE-2017-15042 | suse_vex | SUSE CVE CVE-2017-15042 | known not affected: 171 recommended: 63 | 2026-11-14T17:54:18+00:00 | Vulnerability · Source |
| CVE-2017-17084 | suse_vex | SUSE CVE CVE-2017-17084 | known not affected: 127 recommended: 602 | 2026-11-14T17:54:14+00:00 | Vulnerability · Source |
| CVE-2017-17840 | suse_vex | SUSE CVE CVE-2017-17840 | known affected: 1 known not affected: 121 recommended: 1 | 2026-11-14T17:54:11+00:00 | Vulnerability · Source |
| CVE-2017-18017 | suse_vex | SUSE CVE CVE-2017-18017 | known affected: 76 known not affected: 412 recommended: 385 | 2026-11-14T17:54:08+00:00 | Vulnerability · Source |
| CVE-2017-18269 | suse_vex | SUSE CVE CVE-2017-18269 | known affected: 454 known not affected: 166 recommended: 1247 | 2026-11-14T17:54:05+00:00 | Vulnerability · Source |
| CVE-2017-18884 | suse_vex | SUSE CVE CVE-2017-18884 | recommended: 2 | 2026-11-14T17:54:01+00:00 | Vulnerability · Source |
| CVE-2017-18903 | suse_vex | SUSE CVE CVE-2017-18903 | recommended: 2 | 2026-11-14T17:53:57+00:00 | Vulnerability · Source |
| CVE-2018-3646 | suse_vex | SUSE CVE CVE-2018-3646 | known affected: 349 known not affected: 563 recommended: 1492 | 2026-11-14T17:53:50+00:00 | Vulnerability · Source |
| CVE-2018-4232 | suse_vex | SUSE CVE CVE-2018-4232 | known affected: 171 known not affected: 82 recommended: 900 | 2026-11-14T17:53:47+00:00 | Vulnerability · Source |
| CVE-2018-4266 | suse_vex | SUSE CVE CVE-2018-4266 | known affected: 116 known not affected: 82 recommended: 945 | 2026-11-14T17:53:45+00:00 | Vulnerability · Source |
| CVE-2018-4378 | suse_vex | SUSE CVE CVE-2018-4378 | known affected: 116 recommended: 947 | 2026-11-14T17:53:42+00:00 | Vulnerability · Source |
| CVE-2018-5178 | suse_vex | SUSE CVE CVE-2018-5178 | known affected: 30 recommended: 447 | 2026-11-14T17:53:35+00:00 | Vulnerability · Source |
| CVE-2018-6553 | suse_vex | SUSE CVE CVE-2018-6553 | known not affected: 154 | 2026-11-14T17:53:31+00:00 | Vulnerability · Source |
| CVE-2018-6574 | suse_vex | SUSE CVE CVE-2018-6574 | known not affected: 157 recommended: 69 | 2026-11-14T17:53:29+00:00 | Vulnerability · Source |
| CVE-2018-9270 | suse_vex | SUSE CVE CVE-2018-9270 | known affected: 89 known not affected: 127 recommended: 545 | 2026-11-14T17:53:24+00:00 | Vulnerability · Source |
| CVE-2018-10902 | suse_vex | SUSE CVE CVE-2018-10902 | known affected: 427 known not affected: 567 recommended: 968 | 2026-11-14T17:53:20+00:00 | Vulnerability · Source |
| CVE-2018-12121 | suse_vex | SUSE CVE CVE-2018-12121 | known affected: 25 known not affected: 199 recommended: 298 | 2026-11-14T17:53:16+00:00 | Vulnerability · Source |
| CVE-2018-12392 | suse_vex | SUSE CVE CVE-2018-12392 | known affected: 1 recommended: 416 | 2026-11-14T17:53:12+00:00 | Vulnerability · Source |
| CVE-2018-12399 | suse_vex | SUSE CVE CVE-2018-12399 | known affected: 1 recommended: 9 | 2026-11-14T17:53:09+00:00 | Vulnerability · Source |