VEX records
Browse vendor VEX statements available in this Vulnerability-Lookup instance and pivot to the related vulnerability.
283001 VEX records
API response| Vulnerability | Source | Title | Product status | Imported | Links |
|---|---|---|---|---|---|
| CVE-2016-7970 | suse_vex | SUSE CVE CVE-2016-7970 | recommended: 137 | 2026-07-19T18:37:04+00:00 | Vulnerability · Source |
| CVE-2016-7975 | suse_vex | SUSE CVE CVE-2016-7975 | known affected: 320 recommended: 180 | 2026-07-19T18:37:02+00:00 | Vulnerability · Source |
| CVE-2016-7978 | suse_vex | SUSE CVE CVE-2016-7978 | recommended: 225 | 2026-07-19T18:37:01+00:00 | Vulnerability · Source |
| CVE-2016-7984 | suse_vex | SUSE CVE CVE-2016-7984 | known affected: 320 recommended: 180 | 2026-07-19T18:37:00+00:00 | Vulnerability · Source |
| CVE-2016-7992 | suse_vex | SUSE CVE CVE-2016-7992 | known affected: 320 recommended: 180 | 2026-07-19T18:36:59+00:00 | Vulnerability · Source |
| CVE-2016-7995 | suse_vex | SUSE CVE CVE-2016-7995 | known affected: 407 known not affected: 121 recommended: 1725 | 2026-07-19T18:36:57+00:00 | Vulnerability · Source |
| CVE-2016-8615 | suse_vex | SUSE CVE CVE-2016-8615 | known affected: 337 known not affected: 18 recommended: 437 | 2026-07-19T18:36:56+00:00 | Vulnerability · Source |
| CVE-2016-8617 | suse_vex | SUSE CVE CVE-2016-8617 | known affected: 337 known not affected: 18 recommended: 437 | 2026-07-19T18:36:54+00:00 | Vulnerability · Source |
| CVE-2016-8621 | suse_vex | SUSE CVE CVE-2016-8621 | known affected: 334 known not affected: 28 recommended: 437 | 2026-07-19T18:36:53+00:00 | Vulnerability · Source |
| CVE-2016-8624 | suse_vex | SUSE CVE CVE-2016-8624 | known affected: 337 known not affected: 18 recommended: 437 | 2026-07-19T18:36:52+00:00 | Vulnerability · Source |
| CVE-2016-8667 | suse_vex | SUSE CVE CVE-2016-8667 | known affected: 334 known not affected: 142 recommended: 2300 | 2026-07-19T18:36:50+00:00 | Vulnerability · Source |
| CVE-2016-8690 | suse_vex | SUSE CVE CVE-2016-8690 | known affected: 1 recommended: 196 | 2026-07-19T18:36:48+00:00 | Vulnerability · Source |
| CVE-2016-8691 | suse_vex | SUSE CVE CVE-2016-8691 | known affected: 1 recommended: 196 | 2026-07-19T18:36:47+00:00 | Vulnerability · Source |
| CVE-2016-8704 | suse_vex | SUSE CVE CVE-2016-8704 | known not affected: 22 recommended: 103 | 2026-07-19T18:36:46+00:00 | Vulnerability · Source |
| CVE-2016-8705 | suse_vex | SUSE CVE CVE-2016-8705 | known not affected: 12 recommended: 109 | 2026-07-19T18:36:45+00:00 | Vulnerability · Source |
| CVE-2016-8882 | suse_vex | SUSE CVE CVE-2016-8882 | known affected: 1 recommended: 192 | 2026-07-19T18:36:44+00:00 | Vulnerability · Source |
| CVE-2016-8909 | suse_vex | SUSE CVE CVE-2016-8909 | known affected: 408 known not affected: 123 recommended: 1869 | 2026-07-19T18:36:42+00:00 | Vulnerability · Source |
| CVE-2016-8910 | suse_vex | SUSE CVE CVE-2016-8910 | known affected: 320 known not affected: 764 recommended: 2300 | 2026-07-19T18:36:40+00:00 | Vulnerability · Source |
| CVE-2016-9062 | suse_vex | SUSE CVE CVE-2016-9062 | known affected: 1 known not affected: 34 recommended: 250 | 2026-07-19T18:36:39+00:00 | Vulnerability · Source |
| CVE-2016-9065 | suse_vex | SUSE CVE CVE-2016-9065 | known affected: 1 known not affected: 34 recommended: 250 | 2026-07-19T18:36:38+00:00 | Vulnerability · Source |
| CVE-2016-9069 | suse_vex | SUSE CVE CVE-2016-9069 | known affected: 1 known not affected: 56 recommended: 312 | 2026-07-19T18:36:36+00:00 | Vulnerability · Source |
| CVE-2016-9070 | suse_vex | SUSE CVE CVE-2016-9070 | known affected: 1 known not affected: 15 recommended: 250 | 2026-07-19T18:36:35+00:00 | Vulnerability · Source |
| CVE-2016-9072 | suse_vex | SUSE CVE CVE-2016-9072 | known affected: 1 known not affected: 34 recommended: 250 | 2026-07-19T18:36:34+00:00 | Vulnerability · Source |
| CVE-2016-9075 | suse_vex | SUSE CVE CVE-2016-9075 | known affected: 1 known not affected: 56 recommended: 312 | 2026-07-19T18:36:33+00:00 | Vulnerability · Source |
| CVE-2016-9080 | suse_vex | SUSE CVE CVE-2016-9080 | known affected: 1 recommended: 250 | 2026-07-19T18:36:32+00:00 | Vulnerability · Source |
| CVE-2016-9085 | suse_vex | SUSE CVE CVE-2016-9085 | known not affected: 55 recommended: 226 | 2026-07-19T18:36:30+00:00 | Vulnerability · Source |
| CVE-2016-9102 | suse_vex | SUSE CVE CVE-2016-9102 | known affected: 395 known not affected: 183 recommended: 1769 | 2026-07-19T18:36:29+00:00 | Vulnerability · Source |
| CVE-2016-9147 | suse_vex | SUSE CVE CVE-2016-9147 | known affected: 45 known not affected: 93 recommended: 862 | 2026-07-19T18:36:27+00:00 | Vulnerability · Source |
| CVE-2016-9372 | suse_vex | SUSE CVE CVE-2016-9372 | known affected: 70 recommended: 442 | 2026-07-19T18:36:26+00:00 | Vulnerability · Source |
| CVE-2016-9381 | suse_vex | SUSE CVE CVE-2016-9381 | known affected: 328 known not affected: 170 recommended: 2187 | 2026-07-19T18:36:24+00:00 | Vulnerability · Source |
| CVE-2016-9394 | suse_vex | SUSE CVE CVE-2016-9394 | known affected: 31 recommended: 188 | 2026-07-19T18:36:23+00:00 | Vulnerability · Source |
| CVE-2016-9401 | suse_vex | SUSE CVE CVE-2016-9401 | known affected: 320 recommended: 681 | 2026-07-19T18:36:22+00:00 | Vulnerability · Source |
| CVE-2016-9436 | suse_vex | SUSE CVE CVE-2016-9436 | known affected: 1 recommended: 83 | 2026-07-19T18:36:21+00:00 | Vulnerability · Source |
| CVE-2016-9438 | suse_vex | SUSE CVE CVE-2016-9438 | known affected: 1 recommended: 83 | 2026-07-19T18:36:20+00:00 | Vulnerability · Source |
| CVE-2016-9440 | suse_vex | SUSE CVE CVE-2016-9440 | known affected: 1 recommended: 83 | 2026-07-19T18:36:19+00:00 | Vulnerability · Source |
| CVE-2016-9442 | suse_vex | SUSE CVE CVE-2016-9442 | known affected: 1 recommended: 83 | 2026-07-19T18:36:18+00:00 | Vulnerability · Source |
| CVE-2016-9560 | suse_vex | SUSE CVE CVE-2016-9560 | known affected: 31 known not affected: 123 recommended: 196 | 2026-07-19T18:36:17+00:00 | Vulnerability · Source |
| CVE-2016-9584 | suse_vex | SUSE CVE CVE-2016-9584 | recommended: 242 | 2026-07-19T18:36:16+00:00 | Vulnerability · Source |
| CVE-2016-9622 | suse_vex | SUSE CVE CVE-2016-9622 | known affected: 1 recommended: 83 | 2026-07-19T18:36:15+00:00 | Vulnerability · Source |
| CVE-2016-9776 | suse_vex | SUSE CVE CVE-2016-9776 | known affected: 1 known not affected: 121 recommended: 1832 | 2026-07-19T18:36:13+00:00 | Vulnerability · Source |
| CVE-2016-9798 | suse_vex | SUSE CVE CVE-2016-9798 | known affected: 25 known not affected: 17 recommended: 304 | 2026-07-19T18:36:12+00:00 | Vulnerability · Source |
| CVE-2016-9800 | suse_vex | SUSE CVE CVE-2016-9800 | known not affected: 46 recommended: 306 | 2026-07-19T18:36:10+00:00 | Vulnerability · Source |
| CVE-2016-9846 | suse_vex | SUSE CVE CVE-2016-9846 | known not affected: 154 recommended: 1656 | 2026-07-19T18:36:09+00:00 | Vulnerability · Source |
| CVE-2016-9894 | suse_vex | SUSE CVE CVE-2016-9894 | known affected: 1 recommended: 250 | 2026-07-19T18:36:07+00:00 | Vulnerability · Source |
| CVE-2016-9897 | suse_vex | SUSE CVE CVE-2016-9897 | known affected: 1 recommended: 410 | 2026-07-19T18:36:06+00:00 | Vulnerability · Source |
| CVE-2016-9898 | suse_vex | SUSE CVE CVE-2016-9898 | known affected: 1 recommended: 410 | 2026-07-19T18:36:05+00:00 | Vulnerability · Source |
| CVE-2016-9907 | suse_vex | SUSE CVE CVE-2016-9907 | known affected: 395 known not affected: 146 recommended: 1827 | 2026-07-19T18:36:03+00:00 | Vulnerability · Source |
| CVE-2016-9908 | suse_vex | SUSE CVE CVE-2016-9908 | known not affected: 150 recommended: 1656 | 2026-07-19T18:36:02+00:00 | Vulnerability · Source |
| CVE-2016-9912 | suse_vex | SUSE CVE CVE-2016-9912 | known not affected: 150 recommended: 1656 | 2026-07-19T18:36:00+00:00 | Vulnerability · Source |
| CVE-2016-9913 | suse_vex | SUSE CVE CVE-2016-9913 | known not affected: 209 recommended: 1656 | 2026-07-19T18:35:59+00:00 | Vulnerability · Source |