VEX records
Browse vendor VEX statements available in this Vulnerability-Lookup instance and pivot to the related vulnerability.
289775 VEX records
API response| Vulnerability | Source | Title | Product status | Imported | Links |
|---|---|---|---|---|---|
| CVE-2016-7161 | suse_vex | SUSE CVE CVE-2016-7161 | known affected: 421 known not affected: 136 recommended: 1834 | 2026-08-06T02:14:43+00:00 | Vulnerability · Source |
| CVE-2016-7425 | suse_vex | SUSE CVE CVE-2016-7425 | known affected: 12 known not affected: 275 recommended: 517 | 2026-08-06T02:14:41+00:00 | Vulnerability · Source |
| CVE-2016-9065 | suse_vex | SUSE CVE CVE-2016-9065 | known affected: 1 known not affected: 38 recommended: 250 | 2026-08-06T02:14:38+00:00 | Vulnerability · Source |
| CVE-2016-9773 | suse_vex | SUSE CVE CVE-2016-9773 | known affected: 1 known not affected: 14 recommended: 204 | 2026-08-06T02:14:36+00:00 | Vulnerability · Source |
| CVE-2016-9777 | suse_vex | SUSE CVE CVE-2016-9777 | known not affected: 34 | 2026-08-06T02:14:34+00:00 | Vulnerability · Source |
| CVE-2016-9810 | suse_vex | SUSE CVE CVE-2016-9810 | known affected: 32 recommended: 129 | 2026-08-06T02:14:33+00:00 | Vulnerability · Source |
| CVE-2016-10130 | suse_vex | SUSE CVE CVE-2016-10130 | recommended: 156 | 2026-08-06T02:14:30+00:00 | Vulnerability · Source |
| CVE-2016-10155 | suse_vex | SUSE CVE CVE-2016-10155 | known affected: 421 known not affected: 137 recommended: 1943 | 2026-08-06T02:14:28+00:00 | Vulnerability · Source |
| CVE-2016-10741 | suse_vex | SUSE CVE CVE-2016-10741 | known affected: 2 known not affected: 535 recommended: 133 | 2026-08-06T02:14:25+00:00 | Vulnerability · Source |
| CVE-2017-0899 | suse_vex | SUSE CVE CVE-2017-0899 | known not affected: 54 recommended: 98 | 2026-08-06T02:14:23+00:00 | Vulnerability · Source |
| CVE-2017-2647 | suse_vex | SUSE CVE CVE-2017-2647 | known affected: 2 known not affected: 280 recommended: 272 | 2026-08-06T02:14:21+00:00 | Vulnerability · Source |
| CVE-2017-2818 | suse_vex | SUSE CVE CVE-2017-2818 | known not affected: 93 | 2026-08-06T02:14:20+00:00 | Vulnerability · Source |
| CVE-2017-3136 | suse_vex | SUSE CVE CVE-2017-3136 | known affected: 63 known not affected: 118 recommended: 1011 | 2026-08-06T02:14:18+00:00 | Vulnerability · Source |
| CVE-2017-3167 | suse_vex | SUSE CVE CVE-2017-3167 | recommended: 169 | 2026-08-06T02:14:17+00:00 | Vulnerability · Source |
| CVE-2017-5203 | suse_vex | SUSE CVE CVE-2017-5203 | known affected: 320 recommended: 186 | 2026-08-06T02:14:15+00:00 | Vulnerability · Source |
| CVE-2017-5412 | suse_vex | SUSE CVE CVE-2017-5412 | known affected: 1 recommended: 333 | 2026-08-06T02:14:13+00:00 | Vulnerability · Source |
| CVE-2017-7093 | suse_vex | SUSE CVE CVE-2017-7093 | known not affected: 87 recommended: 939 | 2026-08-06T02:14:09+00:00 | Vulnerability · Source |
| CVE-2017-7275 | suse_vex | SUSE CVE CVE-2017-7275 | known affected: 10 known not affected: 110 | 2026-08-06T02:14:07+00:00 | Vulnerability · Source |
| CVE-2017-7477 | suse_vex | SUSE CVE CVE-2017-7477 | known not affected: 136 recommended: 101 | 2026-08-06T02:14:05+00:00 | Vulnerability · Source |
| CVE-2017-7982 | suse_vex | SUSE CVE CVE-2017-7982 | known affected: 34 known not affected: 29 recommended: 357 | 2026-08-06T02:14:02+00:00 | Vulnerability · Source |
| CVE-2017-8345 | suse_vex | SUSE CVE CVE-2017-8345 | recommended: 184 | 2026-08-06T02:13:59+00:00 | Vulnerability · Source |
| CVE-2017-8386 | suse_vex | SUSE CVE CVE-2017-8386 | known affected: 130 recommended: 954 | 2026-08-06T02:13:58+00:00 | Vulnerability · Source |
| CVE-2017-9077 | suse_vex | SUSE CVE CVE-2017-9077 | known affected: 14 known not affected: 476 recommended: 454 | 2026-08-06T02:13:56+00:00 | Vulnerability · Source |
| CVE-2017-9432 | suse_vex | SUSE CVE CVE-2017-9432 | recommended: 1580 | 2026-08-06T02:13:54+00:00 | Vulnerability · Source |
| CVE-2017-11339 | suse_vex | SUSE CVE CVE-2017-11339 | known affected: 96 known not affected: 41 recommended: 157 | 2026-08-06T02:13:51+00:00 | Vulnerability · Source |
| CVE-2017-11408 | suse_vex | SUSE CVE CVE-2017-11408 | known affected: 86 known not affected: 115 recommended: 565 | 2026-08-06T02:13:49+00:00 | Vulnerability · Source |
| CVE-2017-11509 | suse_vex | SUSE CVE CVE-2017-11509 | known not affected: 5 recommended: 27 | 2026-08-06T02:13:48+00:00 | Vulnerability · Source |
| CVE-2017-11755 | suse_vex | SUSE CVE CVE-2017-11755 | known not affected: 91 | 2026-08-06T02:13:46+00:00 | Vulnerability · Source |
| CVE-2017-13775 | suse_vex | SUSE CVE CVE-2017-13775 | known affected: 10 known not affected: 144 | 2026-08-06T02:13:42+00:00 | Vulnerability · Source |
| CVE-2017-14120 | suse_vex | SUSE CVE CVE-2017-14120 | known not affected: 37 | 2026-08-06T02:13:40+00:00 | Vulnerability · Source |
| CVE-2017-14152 | suse_vex | SUSE CVE CVE-2017-14152 | known not affected: 110 recommended: 184 | 2026-08-06T02:13:38+00:00 | Vulnerability · Source |
| CVE-2017-14324 | suse_vex | SUSE CVE CVE-2017-14324 | known affected: 7 known not affected: 316 | 2026-08-06T02:13:36+00:00 | Vulnerability · Source |
| CVE-2017-15017 | suse_vex | SUSE CVE CVE-2017-15017 | known affected: 94 recommended: 186 | 2026-08-06T02:13:34+00:00 | Vulnerability · Source |
| CVE-2017-15033 | suse_vex | SUSE CVE CVE-2017-15033 | recommended: 186 | 2026-08-06T02:13:33+00:00 | Vulnerability · Source |
| CVE-2017-15595 | suse_vex | SUSE CVE CVE-2017-15595 | known affected: 32 known not affected: 63 recommended: 166 | 2026-08-06T02:13:30+00:00 | Vulnerability · Source |
| CVE-2017-16536 | suse_vex | SUSE CVE CVE-2017-16536 | known affected: 323 known not affected: 225 recommended: 1365 | 2026-08-06T02:13:26+00:00 | Vulnerability · Source |
| CVE-2017-16939 | suse_vex | SUSE CVE CVE-2017-16939 | known affected: 132 known not affected: 221 recommended: 766 | 2026-08-06T02:13:24+00:00 | Vulnerability · Source |
| CVE-2017-17724 | suse_vex | SUSE CVE CVE-2017-17724 | recommended: 4 | 2026-08-06T02:13:22+00:00 | Vulnerability · Source |
| CVE-2017-18030 | suse_vex | SUSE CVE CVE-2017-18030 | known not affected: 505 recommended: 237 | 2026-08-06T02:13:20+00:00 | Vulnerability · Source |
| CVE-2017-1000099 | suse_vex | SUSE CVE CVE-2017-1000099 | known affected: 320 known not affected: 122 recommended: 365 | 2026-08-06T02:13:16+00:00 | Vulnerability · Source |
| CVE-2017-1000366 | suse_vex | SUSE CVE CVE-2017-1000366 | known affected: 382 known not affected: 230 recommended: 1358 | 2026-08-06T02:13:13+00:00 | Vulnerability · Source |
| CVE-2018-4284 | suse_vex | SUSE CVE CVE-2018-4284 | known affected: 108 known not affected: 82 recommended: 969 | 2026-08-06T02:13:06+00:00 | Vulnerability · Source |
| CVE-2018-4700 | suse_vex | SUSE CVE CVE-2018-4700 | known affected: 376 known not affected: 21 recommended: 870 | 2026-08-06T02:13:04+00:00 | Vulnerability · Source |
| CVE-2018-5140 | suse_vex | SUSE CVE CVE-2018-5140 | known affected: 1 known not affected: 54 recommended: 12 | 2026-08-06T02:13:02+00:00 | Vulnerability · Source |
| CVE-2018-5333 | suse_vex | SUSE CVE CVE-2018-5333 | known affected: 57 known not affected: 352 recommended: 655 | 2026-08-06T02:12:59+00:00 | Vulnerability · Source |
| CVE-2018-5735 | suse_vex | SUSE CVE CVE-2018-5735 | known not affected: 105 | 2026-08-06T02:12:57+00:00 | Vulnerability · Source |
| CVE-2018-5738 | suse_vex | SUSE CVE CVE-2018-5738 | known affected: 27 known not affected: 378 recommended: 306 | 2026-08-06T02:12:56+00:00 | Vulnerability · Source |
| CVE-2018-6798 | suse_vex | SUSE CVE CVE-2018-6798 | known affected: 312 recommended: 428 | 2026-08-06T02:12:52+00:00 | Vulnerability · Source |
| CVE-2018-6872 | suse_vex | SUSE CVE CVE-2018-6872 | known affected: 452 known not affected: 62 recommended: 507 | 2026-08-06T02:12:51+00:00 | Vulnerability · Source |
| CVE-2018-6952 | suse_vex | SUSE CVE CVE-2018-6952 | known affected: 416 recommended: 47 | 2026-08-06T02:12:49+00:00 | Vulnerability · Source |