VEX records
Browse vendor VEX statements available in this Vulnerability-Lookup instance and pivot to the related vulnerability.
284835 VEX records
API response| Vulnerability | Source | Title | Product status | Imported | Links |
|---|---|---|---|---|---|
| CVE-2016-9840 | suse_vex | SUSE CVE CVE-2016-9840 | known affected: 545 known not affected: 278 recommended: 2545 | 2026-07-26T00:50:40+00:00 | Vulnerability · Source |
| CVE-2016-9842 | suse_vex | SUSE CVE CVE-2016-9842 | known affected: 22 known not affected: 200 recommended: 825 | 2026-07-26T00:50:39+00:00 | Vulnerability · Source |
| CVE-2016-9845 | suse_vex | SUSE CVE CVE-2016-9845 | known not affected: 183 recommended: 1707 | 2026-07-26T00:50:37+00:00 | Vulnerability · Source |
| CVE-2016-9895 | suse_vex | SUSE CVE CVE-2016-9895 | known affected: 1 recommended: 419 | 2026-07-26T00:50:36+00:00 | Vulnerability · Source |
| CVE-2016-9897 | suse_vex | SUSE CVE CVE-2016-9897 | known affected: 1 recommended: 418 | 2026-07-26T00:50:34+00:00 | Vulnerability · Source |
| CVE-2016-9899 | suse_vex | SUSE CVE CVE-2016-9899 | known affected: 1 recommended: 419 | 2026-07-26T00:50:32+00:00 | Vulnerability · Source |
| CVE-2016-9900 | suse_vex | SUSE CVE CVE-2016-9900 | known affected: 1 recommended: 419 | 2026-07-26T00:50:31+00:00 | Vulnerability · Source |
| CVE-2016-9901 | suse_vex | SUSE CVE CVE-2016-9901 | known affected: 1 recommended: 335 | 2026-07-26T00:50:29+00:00 | Vulnerability · Source |
| CVE-2016-9904 | suse_vex | SUSE CVE CVE-2016-9904 | known affected: 1 recommended: 418 | 2026-07-26T00:50:27+00:00 | Vulnerability · Source |
| CVE-2016-9914 | suse_vex | SUSE CVE CVE-2016-9914 | known not affected: 251 | 2026-07-26T00:50:25+00:00 | Vulnerability · Source |
| CVE-2016-9917 | suse_vex | SUSE CVE CVE-2016-9917 | known affected: 50 known not affected: 106 recommended: 308 | 2026-07-26T00:50:24+00:00 | Vulnerability · Source |
| CVE-2016-9918 | suse_vex | SUSE CVE CVE-2016-9918 | known affected: 50 known not affected: 119 recommended: 312 | 2026-07-26T00:50:21+00:00 | Vulnerability · Source |
| CVE-2016-9932 | suse_vex | SUSE CVE CVE-2016-9932 | known affected: 333 known not affected: 55 recommended: 545 | 2026-07-26T00:50:20+00:00 | Vulnerability · Source |
| CVE-2016-9941 | suse_vex | SUSE CVE CVE-2016-9941 | known affected: 44 known not affected: 4 recommended: 70 | 2026-07-26T00:50:18+00:00 | Vulnerability · Source |
| CVE-2016-9953 | suse_vex | SUSE CVE CVE-2016-9953 | known not affected: 63 | 2026-07-26T00:50:16+00:00 | Vulnerability · Source |
| CVE-2016-9957 | suse_vex | SUSE CVE CVE-2016-9957 | recommended: 156 | 2026-07-26T00:50:15+00:00 | Vulnerability · Source |
| CVE-2016-9958 | suse_vex | SUSE CVE CVE-2016-9958 | recommended: 153 | 2026-07-26T00:50:13+00:00 | Vulnerability · Source |
| CVE-2016-9959 | suse_vex | SUSE CVE CVE-2016-9959 | recommended: 156 | 2026-07-26T00:50:12+00:00 | Vulnerability · Source |
| CVE-2016-9961 | suse_vex | SUSE CVE CVE-2016-9961 | recommended: 153 | 2026-07-26T00:50:10+00:00 | Vulnerability · Source |
| CVE-2016-10002 | suse_vex | SUSE CVE CVE-2016-10002 | known affected: 394 known not affected: 30 recommended: 63 | 2026-07-26T00:50:08+00:00 | Vulnerability · Source |
| CVE-2016-10003 | suse_vex | SUSE CVE CVE-2016-10003 | known affected: 394 known not affected: 59 recommended: 53 | 2026-07-26T00:50:07+00:00 | Vulnerability · Source |
| CVE-2016-10024 | suse_vex | SUSE CVE CVE-2016-10024 | known affected: 333 known not affected: 55 recommended: 545 | 2026-07-26T00:50:05+00:00 | Vulnerability · Source |
| CVE-2016-10040 | suse_vex | SUSE CVE CVE-2016-10040 | recommended: 308 | 2026-07-26T00:50:03+00:00 | Vulnerability · Source |
| CVE-2016-10049 | suse_vex | SUSE CVE CVE-2016-10049 | known affected: 1 recommended: 218 | 2026-07-26T00:50:01+00:00 | Vulnerability · Source |
| CVE-2016-10051 | suse_vex | SUSE CVE CVE-2016-10051 | known affected: 1 recommended: 218 | 2026-07-26T00:50:00+00:00 | Vulnerability · Source |
| CVE-2016-10052 | suse_vex | SUSE CVE CVE-2016-10052 | known affected: 1 recommended: 204 | 2026-07-26T00:49:58+00:00 | Vulnerability · Source |
| CVE-2016-10053 | suse_vex | SUSE CVE CVE-2016-10053 | known not affected: 99 | 2026-07-26T00:49:57+00:00 | Vulnerability · Source |
| CVE-2016-10056 | suse_vex | SUSE CVE CVE-2016-10056 | known affected: 10 known not affected: 113 | 2026-07-26T00:49:55+00:00 | Vulnerability · Source |
| CVE-2016-10062 | suse_vex | SUSE CVE CVE-2016-10062 | known affected: 1 known not affected: 14 recommended: 168 | 2026-07-26T00:49:54+00:00 | Vulnerability · Source |
| CVE-2016-10063 | suse_vex | SUSE CVE CVE-2016-10063 | known affected: 1 known not affected: 14 recommended: 204 | 2026-07-26T00:49:52+00:00 | Vulnerability · Source |
| CVE-2016-10068 | suse_vex | SUSE CVE CVE-2016-10068 | known affected: 1 recommended: 218 | 2026-07-26T00:49:51+00:00 | Vulnerability · Source |
| CVE-2016-10069 | suse_vex | SUSE CVE CVE-2016-10069 | known not affected: 49 recommended: 168 | 2026-07-26T00:49:49+00:00 | Vulnerability · Source |
| CVE-2016-10087 | suse_vex | SUSE CVE CVE-2016-10087 | known affected: 320 recommended: 628 | 2026-07-26T00:49:47+00:00 | Vulnerability · Source |
| CVE-2016-10088 | suse_vex | SUSE CVE CVE-2016-10088 | known not affected: 379 recommended: 331 | 2026-07-26T00:49:46+00:00 | Vulnerability · Source |
| CVE-2016-10092 | suse_vex | SUSE CVE CVE-2016-10092 | known affected: 456 known not affected: 13 recommended: 294 | 2026-07-26T00:49:44+00:00 | Vulnerability · Source |
| CVE-2016-10093 | suse_vex | SUSE CVE CVE-2016-10093 | known affected: 62 known not affected: 13 recommended: 289 | 2026-07-26T00:49:42+00:00 | Vulnerability · Source |
| CVE-2016-10094 | suse_vex | SUSE CVE CVE-2016-10094 | known affected: 62 known not affected: 13 recommended: 289 | 2026-07-26T00:49:41+00:00 | Vulnerability · Source |
| CVE-2016-10095 | suse_vex | SUSE CVE CVE-2016-10095 | known affected: 438 known not affected: 79 recommended: 286 | 2026-07-26T00:49:39+00:00 | Vulnerability · Source |
| CVE-2016-10109 | suse_vex | SUSE CVE CVE-2016-10109 | known affected: 394 known not affected: 13 recommended: 339 | 2026-07-26T00:49:38+00:00 | Vulnerability · Source |
| CVE-2016-10145 | suse_vex | SUSE CVE CVE-2016-10145 | known affected: 1 known not affected: 14 recommended: 204 | 2026-07-26T00:49:36+00:00 | Vulnerability · Source |
| CVE-2016-10147 | suse_vex | SUSE CVE CVE-2016-10147 | known affected: 14 known not affected: 421 recommended: 12 | 2026-07-26T00:49:35+00:00 | Vulnerability · Source |
| CVE-2016-10166 | suse_vex | SUSE CVE CVE-2016-10166 | known affected: 1456 known not affected: 45 recommended: 1719 | 2026-07-26T00:49:32+00:00 | Vulnerability · Source |
| CVE-2016-10167 | suse_vex | SUSE CVE CVE-2016-10167 | known affected: 1456 known not affected: 33 recommended: 1797 | 2026-07-26T00:49:30+00:00 | Vulnerability · Source |
| CVE-2016-10168 | suse_vex | SUSE CVE CVE-2016-10168 | known affected: 394 known not affected: 33 recommended: 1797 | 2026-07-26T00:49:28+00:00 | Vulnerability · Source |
| CVE-2016-10171 | suse_vex | SUSE CVE CVE-2016-10171 | known affected: 30 recommended: 57 | 2026-07-26T00:49:27+00:00 | Vulnerability · Source |
| CVE-2016-10209 | suse_vex | SUSE CVE CVE-2016-10209 | known affected: 24 known not affected: 16 recommended: 25 | 2026-07-26T00:49:25+00:00 | Vulnerability · Source |
| CVE-2016-10220 | suse_vex | SUSE CVE CVE-2016-10220 | known affected: 36 known not affected: 32 recommended: 240 | 2026-07-26T00:49:24+00:00 | Vulnerability · Source |
| CVE-2016-10243 | suse_vex | SUSE CVE CVE-2016-10243 | known not affected: 9311 recommended: 227408 | 2026-07-26T00:48:53+00:00 | Vulnerability · Source |
| CVE-2016-10248 | suse_vex | SUSE CVE CVE-2016-10248 | known not affected: 94 recommended: 4 | 2026-07-26T00:48:51+00:00 | Vulnerability · Source |
| CVE-2016-10254 | suse_vex | SUSE CVE CVE-2016-10254 | known affected: 136 recommended: 172 | 2026-07-26T00:48:50+00:00 | Vulnerability · Source |