VEX records
Browse vendor VEX statements available in this Vulnerability-Lookup instance and pivot to the related vulnerability.
308665 VEX records
API response| Vulnerability | Source | Title | Product status | Imported | Links |
|---|---|---|---|---|---|
| CVE-2016-7976 | suse_vex | SUSE CVE CVE-2016-7976 | recommended: 199 | 2026-10-17T02:23:43+00:00 | Vulnerability · Source |
| CVE-2016-7986 | suse_vex | SUSE CVE CVE-2016-7986 | known affected: 320 recommended: 182 | 2026-10-17T02:23:41+00:00 | Vulnerability · Source |
| CVE-2016-7995 | suse_vex | SUSE CVE CVE-2016-7995 | known affected: 420 known not affected: 140 recommended: 1814 | 2026-10-17T02:23:40+00:00 | Vulnerability · Source |
| CVE-2016-8283 | suse_vex | SUSE CVE CVE-2016-8283 | known affected: 35 known not affected: 163 recommended: 638 | 2026-10-17T02:23:38+00:00 | Vulnerability · Source |
| CVE-2016-8568 | suse_vex | SUSE CVE CVE-2016-8568 | recommended: 154 | 2026-10-17T02:23:37+00:00 | Vulnerability · Source |
| CVE-2016-8576 | suse_vex | SUSE CVE CVE-2016-8576 | known affected: 421 known not affected: 141 recommended: 1928 | 2026-10-17T02:23:35+00:00 | Vulnerability · Source |
| CVE-2016-8578 | suse_vex | SUSE CVE CVE-2016-8578 | known affected: 421 known not affected: 140 recommended: 1865 | 2026-10-17T02:23:34+00:00 | Vulnerability · Source |
| CVE-2016-8617 | suse_vex | SUSE CVE CVE-2016-8617 | known affected: 340 known not affected: 21 recommended: 458 | 2026-10-17T02:23:32+00:00 | Vulnerability · Source |
| CVE-2016-8619 | suse_vex | SUSE CVE CVE-2016-8619 | known affected: 340 known not affected: 21 recommended: 458 | 2026-10-17T02:23:30+00:00 | Vulnerability · Source |
| CVE-2016-8632 | suse_vex | SUSE CVE CVE-2016-8632 | known affected: 68 known not affected: 359 recommended: 444 | 2026-10-17T02:23:29+00:00 | Vulnerability · Source |
| CVE-2016-8654 | suse_vex | SUSE CVE CVE-2016-8654 | known affected: 37 known not affected: 124 recommended: 202 | 2026-10-17T02:23:27+00:00 | Vulnerability · Source |
| CVE-2016-8658 | suse_vex | SUSE CVE CVE-2016-8658 | known affected: 0 known not affected: 361 recommended: 202 | 2026-10-17T02:23:26+00:00 | Vulnerability · Source |
| CVE-2016-8668 | suse_vex | SUSE CVE CVE-2016-8668 | known affected: 420 known not affected: 140 recommended: 1785 | 2026-10-17T02:23:24+00:00 | Vulnerability · Source |
| CVE-2016-8687 | suse_vex | SUSE CVE CVE-2016-8687 | known affected: 394 recommended: 224 | 2026-10-17T02:23:23+00:00 | Vulnerability · Source |
| CVE-2016-8689 | suse_vex | SUSE CVE CVE-2016-8689 | known affected: 394 known not affected: 20 recommended: 222 | 2026-10-17T02:23:21+00:00 | Vulnerability · Source |
| CVE-2016-8691 | suse_vex | SUSE CVE CVE-2016-8691 | known affected: 1 recommended: 202 | 2026-10-17T02:23:20+00:00 | Vulnerability · Source |
| CVE-2016-8693 | suse_vex | SUSE CVE CVE-2016-8693 | known affected: 1 recommended: 202 | 2026-10-17T02:23:19+00:00 | Vulnerability · Source |
| CVE-2016-8704 | suse_vex | SUSE CVE CVE-2016-8704 | known affected: 0 known not affected: 24 recommended: 107 | 2026-10-17T02:23:17+00:00 | Vulnerability · Source |
| CVE-2016-8706 | suse_vex | SUSE CVE CVE-2016-8706 | recommended: 107 | 2026-10-17T02:23:16+00:00 | Vulnerability · Source |
| CVE-2016-8745 | suse_vex | SUSE CVE CVE-2016-8745 | known affected: 440 known not affected: 129 recommended: 312 | 2026-10-17T02:23:15+00:00 | Vulnerability · Source |
| CVE-2016-8864 | suse_vex | SUSE CVE CVE-2016-8864 | known affected: 378 known not affected: 402 recommended: 1000 | 2026-10-17T02:23:13+00:00 | Vulnerability · Source |
| CVE-2016-8883 | suse_vex | SUSE CVE CVE-2016-8883 | known affected: 1 recommended: 202 | 2026-10-17T02:23:12+00:00 | Vulnerability · Source |
| CVE-2016-8909 | suse_vex | SUSE CVE CVE-2016-8909 | known affected: 421 known not affected: 142 recommended: 1972 | 2026-10-17T02:23:08+00:00 | Vulnerability · Source |
| CVE-2016-9062 | suse_vex | SUSE CVE CVE-2016-9062 | known affected: 1 known not affected: 43 recommended: 250 | 2026-10-17T02:23:07+00:00 | Vulnerability · Source |
| CVE-2016-9063 | suse_vex | SUSE CVE CVE-2016-9063 | known affected: 323 known not affected: 77 recommended: 976 | 2026-10-17T02:23:05+00:00 | Vulnerability · Source |
| CVE-2016-9064 | suse_vex | SUSE CVE CVE-2016-9064 | known affected: 2 recommended: 569 | 2026-10-17T02:23:04+00:00 | Vulnerability · Source |
| CVE-2016-9071 | suse_vex | SUSE CVE CVE-2016-9071 | known affected: 1 known not affected: 69 recommended: 321 | 2026-10-17T02:23:03+00:00 | Vulnerability · Source |
| CVE-2016-9072 | suse_vex | SUSE CVE CVE-2016-9072 | known affected: 1 known not affected: 43 recommended: 250 | 2026-10-17T02:23:01+00:00 | Vulnerability · Source |
| CVE-2016-9075 | suse_vex | SUSE CVE CVE-2016-9075 | known affected: 1 known not affected: 69 recommended: 321 | 2026-10-17T02:23:00+00:00 | Vulnerability · Source |
| CVE-2016-9078 | suse_vex | SUSE CVE CVE-2016-9078 | known affected: 1 known not affected: 43 recommended: 250 | 2026-10-17T02:22:59+00:00 | Vulnerability · Source |
| CVE-2016-9104 | suse_vex | SUSE CVE CVE-2016-9104 | known affected: 421 known not affected: 147 recommended: 1865 | 2026-10-17T02:22:57+00:00 | Vulnerability · Source |
| CVE-2016-9318 | suse_vex | SUSE CVE CVE-2016-9318 | recommended: 184 | 2026-10-17T02:22:55+00:00 | Vulnerability · Source |
| CVE-2016-9373 | suse_vex | SUSE CVE CVE-2016-9373 | known affected: 1 recommended: 582 | 2026-10-17T02:22:54+00:00 | Vulnerability · Source |
| CVE-2016-9387 | suse_vex | SUSE CVE CVE-2016-9387 | known affected: 0 known not affected: 140 recommended: 134 | 2026-10-17T02:22:53+00:00 | Vulnerability · Source |
| CVE-2016-9388 | suse_vex | SUSE CVE CVE-2016-9388 | known affected: 37 recommended: 192 | 2026-10-17T02:22:51+00:00 | Vulnerability · Source |
| CVE-2016-9392 | suse_vex | SUSE CVE CVE-2016-9392 | known affected: 37 recommended: 192 | 2026-10-17T02:22:50+00:00 | Vulnerability · Source |
| CVE-2016-9394 | suse_vex | SUSE CVE CVE-2016-9394 | known affected: 37 recommended: 192 | 2026-10-17T02:22:48+00:00 | Vulnerability · Source |
| CVE-2016-9395 | suse_vex | SUSE CVE CVE-2016-9395 | known affected: 45 known not affected: 121 recommended: 198 | 2026-10-17T02:22:47+00:00 | Vulnerability · Source |
| CVE-2016-9436 | suse_vex | SUSE CVE CVE-2016-9436 | known affected: 1 recommended: 89 | 2026-10-17T02:22:45+00:00 | Vulnerability · Source |
| CVE-2016-9437 | suse_vex | SUSE CVE CVE-2016-9437 | known affected: 1 recommended: 89 | 2026-10-17T02:22:44+00:00 | Vulnerability · Source |
| CVE-2016-9442 | suse_vex | SUSE CVE CVE-2016-9442 | known affected: 1 recommended: 89 | 2026-10-17T02:22:43+00:00 | Vulnerability · Source |
| CVE-2016-9448 | suse_vex | SUSE CVE CVE-2016-9448 | recommended: 274 | 2026-10-17T02:22:41+00:00 | Vulnerability · Source |
| CVE-2016-9453 | suse_vex | SUSE CVE CVE-2016-9453 | known affected: 394 known not affected: 97 recommended: 296 | 2026-10-17T02:22:40+00:00 | Vulnerability · Source |
| CVE-2016-9560 | suse_vex | SUSE CVE CVE-2016-9560 | known affected: 37 known not affected: 124 recommended: 202 | 2026-10-17T02:22:39+00:00 | Vulnerability · Source |
| CVE-2016-9626 | suse_vex | SUSE CVE CVE-2016-9626 | known affected: 1 recommended: 89 | 2026-10-17T02:22:37+00:00 | Vulnerability · Source |
| CVE-2016-9629 | suse_vex | SUSE CVE CVE-2016-9629 | known affected: 1 recommended: 89 | 2026-10-17T02:22:36+00:00 | Vulnerability · Source |
| CVE-2016-9632 | suse_vex | SUSE CVE CVE-2016-9632 | known affected: 1 recommended: 89 | 2026-10-17T02:22:34+00:00 | Vulnerability · Source |
| CVE-2016-9793 | suse_vex | SUSE CVE CVE-2016-9793 | known affected: 12 known not affected: 75 recommended: 410 | 2026-10-17T02:22:33+00:00 | Vulnerability · Source |
| CVE-2016-9801 | suse_vex | SUSE CVE CVE-2016-9801 | known affected: 23 known not affected: 16 recommended: 316 | 2026-10-17T02:22:31+00:00 | Vulnerability · Source |
| CVE-2016-9804 | suse_vex | SUSE CVE CVE-2016-9804 | known affected: 0 known not affected: 55 recommended: 300 | 2026-10-17T02:22:30+00:00 | Vulnerability · Source |