VEX records
Browse vendor VEX statements available in this Vulnerability-Lookup instance and pivot to the related vulnerability.
291911 VEX records
API response| Vulnerability | Source | Title | Product status | Imported | Links |
|---|---|---|---|---|---|
| CVE-2016-11066 | suse_vex | SUSE CVE CVE-2016-11066 | recommended: 1 | 2026-08-01T23:37:40+00:00 | Vulnerability · Source |
| CVE-2017-0861 | suse_vex | SUSE CVE CVE-2017-0861 | known affected: 71 known not affected: 277 recommended: 319 | 2026-08-01T23:37:34+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-3260 | suse_vex | SUSE CVE CVE-2017-3260 | known affected: 15 known not affected: 150 recommended: 331 | 2026-08-01T23:37:28+00:00 | Vulnerability · Source |
| CVE-2017-5386 | suse_vex | SUSE CVE CVE-2017-5386 | known affected: 1 recommended: 331 | 2026-08-01T23:37:26+00:00 | Vulnerability · Source |
| CVE-2017-5397 | suse_vex | SUSE CVE CVE-2017-5397 | known affected: 24 known not affected: 15 | 2026-08-01T23:37:25+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-5597 | suse_vex | SUSE CVE CVE-2017-5597 | known affected: 1 recommended: 588 | 2026-08-01T23:37:23+00:00 | Vulnerability · Source |
| CVE-2017-6196 | suse_vex | SUSE CVE CVE-2017-6196 | known affected: 6 known not affected: 54 | 2026-08-01T23:37:18+00:00 | Vulnerability · Source |
| CVE-2017-6264 | suse_vex | SUSE CVE CVE-2017-6264 | known not affected: 298 | 2026-08-01T23:37:17+00:00 | Vulnerability · Source |
| CVE-2017-6469 | suse_vex | SUSE CVE CVE-2017-6469 | known affected: 73 recommended: 444 | 2026-08-01T23:37:15+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-6951 | suse_vex | SUSE CVE CVE-2017-6951 | known affected: 2 known not affected: 108 recommended: 272 | 2026-08-01T23:37:13+00:00 | Vulnerability · Source |
| CVE-2017-7142 | suse_vex | SUSE CVE CVE-2017-7142 | known not affected: 87 recommended: 927 | 2026-08-01T23:37:11+00:00 | Vulnerability · Source |
| CVE-2017-7308 | suse_vex | SUSE CVE CVE-2017-7308 | known not affected: 377 recommended: 494 | 2026-08-01T23:37:07+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-7487 | suse_vex | SUSE CVE CVE-2017-7487 | known affected: 14 known not affected: 422 recommended: 432 | 2026-08-01T23:37:03+00:00 | Vulnerability · Source |
| CVE-2017-7614 | suse_vex | SUSE CVE CVE-2017-7614 | known affected: 1 known not affected: 134 recommended: 54 | 2026-08-01T23:37:01+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-7857 | suse_vex | SUSE CVE CVE-2017-7857 | known affected: 6 known not affected: 52 | 2026-08-01T23:36:55+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-8831 | suse_vex | SUSE CVE CVE-2017-8831 | known affected: 26 known not affected: 261 recommended: 616 | 2026-08-01T23:36:48+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-9040 | suse_vex | SUSE CVE CVE-2017-9040 | known affected: 1 known not affected: 134 recommended: 54 | 2026-08-01T23:36:46+00:00 | Vulnerability · Source |
| CVE-2017-9074 | suse_vex | SUSE CVE CVE-2017-9074 | known affected: 14 known not affected: 371 recommended: 444 | 2026-08-01T23:36:45+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 |
| CVE-2017-9503 | suse_vex | SUSE CVE CVE-2017-9503 | known affected: 421 known not affected: 136 recommended: 1867 | 2026-08-01T23:36:41+00:00 | Vulnerability · Source |
| CVE-2017-9614 | suse_vex | SUSE CVE CVE-2017-9614 | known affected: 46 known not affected: 284 | 2026-08-01T23:36:39+00:00 | Vulnerability · Source |
| CVE-2017-9744 | suse_vex | SUSE CVE CVE-2017-9744 | known affected: 8 known not affected: 42 | 2026-08-01T23:36:38+00:00 | Vulnerability · Source |
| CVE-2017-9782 | suse_vex | SUSE CVE CVE-2017-9782 | known affected: 46 known not affected: 16 recommended: 150 | 2026-08-01T23:36:37+00:00 | Vulnerability · Source |
| CVE-2017-9832 | suse_vex | SUSE CVE CVE-2017-9832 | known affected: 14 known not affected: 129 | 2026-08-01T23:36:36+00:00 | Vulnerability · Source |
| CVE-2017-10309 | suse_vex | SUSE CVE CVE-2017-10309 | known affected: 20 known not affected: 93 recommended: 232 | 2026-08-01T23:36:34+00:00 | Vulnerability · Source |
| CVE-2017-10981 | suse_vex | SUSE CVE CVE-2017-10981 | known affected: 24 known not affected: 111 recommended: 26 | 2026-08-01T23:36:31+00:00 | Vulnerability · Source |
| CVE-2017-10988 | suse_vex | SUSE CVE CVE-2017-10988 | known affected: 24 known not affected: 111 recommended: 613 | 2026-08-01T23:36:30+00:00 | Vulnerability · Source |
| CVE-2017-11089 | suse_vex | SUSE CVE CVE-2017-11089 | known not affected: 55 recommended: 80 | 2026-08-01T23:36:28+00:00 | Vulnerability · Source |
| CVE-2017-11409 | suse_vex | SUSE CVE CVE-2017-11409 | known affected: 86 known not affected: 115 | 2026-08-01T23:36:26+00:00 | Vulnerability · Source |
| CVE-2017-11624 | suse_vex | SUSE CVE CVE-2017-11624 | known affected: 4 known not affected: 33 recommended: 326 | 2026-08-01T23:36:21+00:00 | Vulnerability · Source |
| CVE-2017-12459 | suse_vex | SUSE CVE CVE-2017-12459 | known not affected: 137 | 2026-08-01T23:36:19+00:00 | Vulnerability · Source |
| CVE-2017-12642 | suse_vex | SUSE CVE CVE-2017-12642 | known affected: 94 recommended: 186 | 2026-08-01T23:36:17+00:00 | Vulnerability · Source |
| CVE-2017-12762 | suse_vex | SUSE CVE CVE-2017-12762 | known affected: 84 recommended: 217 | 2026-08-01T23:36:16+00:00 | Vulnerability · Source |
| CVE-2017-13027 | suse_vex | SUSE CVE CVE-2017-13027 | known affected: 336 known not affected: 24 recommended: 151 | 2026-08-01T23:36:15+00:00 | Vulnerability · Source |
| CVE-2017-13035 | suse_vex | SUSE CVE CVE-2017-13035 | known affected: 336 known not affected: 24 recommended: 151 | 2026-08-01T23:36:13+00:00 | Vulnerability · Source |
| CVE-2017-13140 | suse_vex | SUSE CVE CVE-2017-13140 | known affected: 10 known not affected: 77 | 2026-08-01T23:36:11+00:00 | Vulnerability · Source |