VEX records
Browse vendor VEX statements available in this Vulnerability-Lookup instance and pivot to the related vulnerability.
293991 VEX records
API response| Vulnerability | Source | Title | Product status | Imported | Links |
|---|---|---|---|---|---|
| CVE-2014-9838 | suse_vex | SUSE CVE CVE-2014-9838 | known affected: 97 known not affected: 14 recommended: 202 | 2026-08-01T23:40:19+00:00 | Vulnerability · Source |
| CVE-2015-0374 | suse_vex | SUSE CVE CVE-2015-0374 | known not affected: 44 recommended: 319 | 2026-08-01T23:40:16+00:00 | Vulnerability · Source |
| CVE-2015-0407 | suse_vex | SUSE CVE CVE-2015-0407 | recommended: 95 | 2026-08-01T23:40:15+00:00 | Vulnerability · Source |
| CVE-2015-1120 | suse_vex | SUSE CVE CVE-2015-1120 | known not affected: 18 recommended: 238 | 2026-08-01T23:40:13+00:00 | Vulnerability · Source |
| CVE-2015-1395 | suse_vex | SUSE CVE CVE-2015-1395 | known not affected: 2 recommended: 20 | 2026-08-01T23:40:12+00:00 | Vulnerability · Source |
| CVE-2015-2710 | suse_vex | SUSE CVE CVE-2015-2710 | recommended: 416 | 2026-08-01T23:40:06+00:00 | Vulnerability · Source |
| CVE-2015-3748 | suse_vex | SUSE CVE CVE-2015-3748 | known not affected: 18 recommended: 238 | 2026-08-01T23:39:58+00:00 | Vulnerability · Source |
| CVE-2015-4042 | suse_vex | SUSE CVE CVE-2015-4042 | known affected: 320 known not affected: 2 recommended: 284 | 2026-08-01T23:39:56+00:00 | Vulnerability · Source |
| CVE-2015-4791 | suse_vex | SUSE CVE CVE-2015-4791 | known affected: 13 known not affected: 117 | 2026-08-01T23:39:54+00:00 | Vulnerability · Source |
| CVE-2015-5160 | suse_vex | SUSE CVE CVE-2015-5160 | recommended: 20 | 2026-08-01T23:39:49+00:00 | Vulnerability · Source |
| CVE-2015-5196 | suse_vex | SUSE CVE CVE-2015-5196 | known affected: 30 known not affected: 8 recommended: 5 | 2026-08-01T23:39:48+00:00 | Vulnerability · Source |
| CVE-2015-5801 | suse_vex | SUSE CVE CVE-2015-5801 | known not affected: 18 recommended: 238 | 2026-08-01T23:39:40+00:00 | Vulnerability · Source |
| CVE-2015-7222 | suse_vex | SUSE CVE CVE-2015-7222 | known affected: 2 recommended: 428 | 2026-08-01T23:39:36+00:00 | Vulnerability · Source |
| CVE-2015-8385 | suse_vex | SUSE CVE CVE-2015-8385 | known affected: 15 known not affected: 133 recommended: 128 | 2026-08-01T23:39:26+00:00 | Vulnerability · Source |
| CVE-2015-8388 | suse_vex | SUSE CVE CVE-2015-8388 | known affected: 15 known not affected: 133 recommended: 128 | 2026-08-01T23:39:25+00:00 | Vulnerability · Source |
| CVE-2015-8568 | suse_vex | SUSE CVE CVE-2015-8568 | known affected: 321 known not affected: 185 recommended: 2302 | 2026-08-01T23:39:21+00:00 | Vulnerability · Source |
| CVE-2015-8930 | suse_vex | SUSE CVE CVE-2015-8930 | known affected: 12 known not affected: 126 recommended: 40 | 2026-08-01T23:39:12+00:00 | Vulnerability · Source |
| CVE-2015-8982 | suse_vex | SUSE CVE CVE-2015-8982 | known not affected: 776 recommended: 44 | 2026-08-01T23:39:08+00:00 | Vulnerability · Source |
| CVE-2016-1255 | suse_vex | SUSE CVE CVE-2016-1255 | known affected: 18 known not affected: 11 | 2026-08-01T23:39:04+00:00 | Vulnerability · Source |
| CVE-2016-1405 | suse_vex | SUSE CVE CVE-2016-1405 | known not affected: 9 | 2026-08-01T23:39:02+00:00 | Vulnerability · Source |
| CVE-2016-3990 | suse_vex | SUSE CVE CVE-2016-3990 | known affected: 394 known not affected: 291 recommended: 285 | 2026-08-01T23:38:45+00:00 | Vulnerability · Source |
| CVE-2016-4962 | suse_vex | SUSE CVE CVE-2016-4962 | known affected: 1 known not affected: 3 recommended: 63 | 2026-08-01T23:38:39+00:00 | Vulnerability · Source |
| CVE-2016-5131 | suse_vex | SUSE CVE CVE-2016-5131 | known affected: 394 recommended: 164 | 2026-08-01T23:38:37+00:00 | Vulnerability · Source |
| CVE-2016-7166 | suse_vex | SUSE CVE CVE-2016-7166 | known affected: 30 known not affected: 108 recommended: 4 | 2026-08-01T23:38:19+00:00 | Vulnerability · Source |
| CVE-2016-7568 | suse_vex | SUSE CVE CVE-2016-7568 | known affected: 550 known not affected: 139 recommended: 1130 | 2026-08-01T23:38:14+00:00 | Vulnerability · Source |
| CVE-2016-7915 | suse_vex | SUSE CVE CVE-2016-7915 | known not affected: 234 recommended: 203 | 2026-08-01T23:38:09+00:00 | Vulnerability · Source |
| CVE-2016-7944 | suse_vex | SUSE CVE CVE-2016-7944 | known affected: 36 recommended: 270 | 2026-08-01T23:38:07+00:00 | Vulnerability · Source |
| CVE-2016-7948 | suse_vex | SUSE CVE CVE-2016-7948 | known not affected: 62 recommended: 463 | 2026-08-01T23:38:05+00:00 | Vulnerability · Source |
| CVE-2016-8678 | suse_vex | SUSE CVE CVE-2016-8678 | known not affected: 119 | 2026-08-01T23:38:02+00:00 | Vulnerability · Source |
| CVE-2016-9112 | suse_vex | SUSE CVE CVE-2016-9112 | recommended: 20 | 2026-08-01T23:37:58+00:00 | Vulnerability · Source |
| CVE-2016-9401 | suse_vex | SUSE CVE CVE-2016-9401 | known affected: 320 recommended: 686 | 2026-08-01T23:37:54+00:00 | Vulnerability · Source |
| CVE-2016-9430 | suse_vex | SUSE CVE CVE-2016-9430 | known not affected: 15 | 2026-08-01T23:37:53+00:00 | Vulnerability · Source |
| CVE-2016-10054 | suse_vex | SUSE CVE CVE-2016-10054 | known affected: 10 known not affected: 113 | 2026-08-01T23:37:47+00:00 | Vulnerability · Source |
| CVE-2016-10199 | suse_vex | SUSE CVE CVE-2016-10199 | recommended: 456 | 2026-08-01T23:37:45+00:00 | Vulnerability · Source |
| CVE-2016-11066 | suse_vex | SUSE CVE CVE-2016-11066 | recommended: 1 | 2026-08-01T23:37:40+00:00 | Vulnerability · Source |
| CVE-2017-0898 | suse_vex | SUSE CVE CVE-2017-0898 | known affected: 1 known not affected: 77 recommended: 98 | 2026-08-01T23:37:33+00:00 | Vulnerability · Source |
| CVE-2017-0903 | suse_vex | SUSE CVE CVE-2017-0903 | known affected: 3 known not affected: 7 recommended: 98 | 2026-08-01T23:37:32+00:00 | Vulnerability · Source |
| CVE-2017-2633 | suse_vex | SUSE CVE CVE-2017-2633 | known affected: 2 known not affected: 1409 recommended: 1730 | 2026-08-01T23:37:30+00:00 | Vulnerability · Source |
| CVE-2017-5420 | suse_vex | SUSE CVE CVE-2017-5420 | known affected: 1 recommended: 249 | 2026-08-01T23:37:24+00:00 | Vulnerability · Source |
| CVE-2017-6827 | suse_vex | SUSE CVE CVE-2017-6827 | known affected: 45 recommended: 196 | 2026-08-01T23:37:14+00:00 | Vulnerability · Source |
| CVE-2017-7377 | suse_vex | SUSE CVE CVE-2017-7377 | known affected: 26 known not affected: 43 recommended: 119 | 2026-08-01T23:37:06+00:00 | Vulnerability · Source |
| CVE-2017-7668 | suse_vex | SUSE CVE CVE-2017-7668 | known not affected: 43 recommended: 64 | 2026-08-01T23:37:00+00:00 | Vulnerability · Source |
| CVE-2017-7822 | suse_vex | SUSE CVE CVE-2017-7822 | known not affected: 42 recommended: 12 | 2026-08-01T23:36:57+00:00 | Vulnerability · Source |
| CVE-2017-7836 | suse_vex | SUSE CVE CVE-2017-7836 | known affected: 1 known not affected: 42 recommended: 12 | 2026-08-01T23:36:56+00:00 | Vulnerability · Source |
| CVE-2017-7980 | suse_vex | SUSE CVE CVE-2017-7980 | known affected: 27 known not affected: 1123 recommended: 235 | 2026-08-01T23:36:53+00:00 | Vulnerability · Source |
| CVE-2017-8068 | suse_vex | SUSE CVE CVE-2017-8068 | known not affected: 34 | 2026-08-01T23:36:52+00:00 | Vulnerability · Source |
| CVE-2017-8824 | suse_vex | SUSE CVE CVE-2017-8824 | known affected: 2 known not affected: 311 recommended: 634 | 2026-08-01T23:36:49+00:00 | Vulnerability · Source |
| CVE-2017-8890 | suse_vex | SUSE CVE CVE-2017-8890 | known affected: 95 known not affected: 167 recommended: 514 | 2026-08-01T23:36:47+00:00 | Vulnerability · Source |
| CVE-2017-9103 | suse_vex | SUSE CVE CVE-2017-9103 | known affected: 18 recommended: 49 | 2026-08-01T23:36:44+00:00 | Vulnerability · Source |
| CVE-2017-9330 | suse_vex | SUSE CVE CVE-2017-9330 | known affected: 360 known not affected: 76 recommended: 637 | 2026-08-01T23:36:42+00:00 | Vulnerability · Source |