VEX records
Browse vendor VEX statements available in this Vulnerability-Lookup instance and pivot to the related vulnerability.
293999 VEX records
API response| Vulnerability | Source | Title | Product status | Imported | Links |
|---|---|---|---|---|---|
| CVE-2016-9426 | suse_vex | SUSE CVE CVE-2016-9426 | known not affected: 15 | 2026-07-26T00:51:44+00:00 | Vulnerability · Source |
| CVE-2016-9431 | suse_vex | SUSE CVE CVE-2016-9431 | known not affected: 15 | 2026-07-26T00:51:42+00:00 | Vulnerability · Source |
| CVE-2016-9435 | suse_vex | SUSE CVE CVE-2016-9435 | known affected: 1 recommended: 87 | 2026-07-26T00:51:39+00:00 | Vulnerability · Source |
| CVE-2016-9444 | suse_vex | SUSE CVE CVE-2016-9444 | known affected: 58 known not affected: 386 recommended: 893 | 2026-07-26T00:51:33+00:00 | Vulnerability · Source |
| CVE-2016-9445 | suse_vex | SUSE CVE CVE-2016-9445 | known affected: 185 recommended: 552 | 2026-07-26T00:51:31+00:00 | Vulnerability · Source |
| CVE-2016-9534 | suse_vex | SUSE CVE CVE-2016-9534 | known not affected: 47 recommended: 4 | 2026-07-26T00:51:28+00:00 | Vulnerability · Source |
| CVE-2016-9540 | suse_vex | SUSE CVE CVE-2016-9540 | known not affected: 28 recommended: 26 | 2026-07-26T00:51:25+00:00 | Vulnerability · Source |
| CVE-2016-9560 | suse_vex | SUSE CVE CVE-2016-9560 | known affected: 37 known not affected: 125 recommended: 204 | 2026-07-26T00:51:23+00:00 | Vulnerability · Source |
| CVE-2016-9573 | suse_vex | SUSE CVE CVE-2016-9573 | recommended: 23 | 2026-07-26T00:51:22+00:00 | Vulnerability · Source |
| CVE-2016-9577 | suse_vex | SUSE CVE CVE-2016-9577 | known affected: 1 known not affected: 100 recommended: 137 | 2026-07-26T00:51:20+00:00 | Vulnerability · Source |
| CVE-2016-9580 | suse_vex | SUSE CVE CVE-2016-9580 | recommended: 20 | 2026-07-26T00:51:19+00:00 | Vulnerability · Source |
| CVE-2016-9581 | suse_vex | SUSE CVE CVE-2016-9581 | recommended: 20 | 2026-07-26T00:51:17+00:00 | Vulnerability · Source |
| CVE-2016-9632 | suse_vex | SUSE CVE CVE-2016-9632 | known affected: 1 recommended: 87 | 2026-07-26T00:51:05+00:00 | Vulnerability · Source |
| CVE-2016-9635 | suse_vex | SUSE CVE CVE-2016-9635 | known affected: 32 recommended: 86 | 2026-07-26T00:51:01+00:00 | Vulnerability · Source |
| CVE-2016-9644 | suse_vex | SUSE CVE CVE-2016-9644 | known not affected: 61 | 2026-07-26T00:50:59+00:00 | Vulnerability · Source |
| CVE-2016-9685 | suse_vex | SUSE CVE CVE-2016-9685 | known not affected: 47 recommended: 205 | 2026-07-26T00:50:58+00:00 | Vulnerability · Source |
| CVE-2016-9755 | suse_vex | SUSE CVE CVE-2016-9755 | known not affected: 34 | 2026-07-26T00:50:57+00:00 | Vulnerability · Source |
| CVE-2016-9799 | suse_vex | SUSE CVE CVE-2016-9799 | known not affected: 46 | 2026-07-26T00:50:53+00:00 | Vulnerability · Source |
| CVE-2016-9811 | suse_vex | SUSE CVE CVE-2016-9811 | known affected: 272 recommended: 845 | 2026-07-26T00:50:48+00:00 | Vulnerability · Source |
| CVE-2016-9815 | suse_vex | SUSE CVE CVE-2016-9815 | known not affected: 68 | 2026-07-26T00:50:45+00:00 | Vulnerability · Source |
| CVE-2016-9816 | suse_vex | SUSE CVE CVE-2016-9816 | known not affected: 68 | 2026-07-26T00:50:44+00:00 | Vulnerability · Source |
| CVE-2016-9818 | suse_vex | SUSE CVE CVE-2016-9818 | known not affected: 68 | 2026-07-26T00:50:42+00:00 | Vulnerability · Source |
| 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-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-9914 | suse_vex | SUSE CVE CVE-2016-9914 | known not affected: 251 | 2026-07-26T00:50:25+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-9961 | suse_vex | SUSE CVE CVE-2016-9961 | recommended: 153 | 2026-07-26T00:50:10+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-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-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-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-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-10254 | suse_vex | SUSE CVE CVE-2016-10254 | known affected: 136 recommended: 172 | 2026-07-26T00:48:50+00:00 | Vulnerability · Source |
| CVE-2016-10328 | suse_vex | SUSE CVE CVE-2016-10328 | known affected: 9 known not affected: 63 recommended: 22 | 2026-07-26T00:48:47+00:00 | Vulnerability · Source |
| CVE-2017-0605 | suse_vex | SUSE CVE CVE-2017-0605 | known not affected: 64 | 2026-07-26T00:48:35+00:00 | Vulnerability · Source |
| CVE-2017-0627 | suse_vex | SUSE CVE CVE-2017-0627 | known not affected: 64 | 2026-07-26T00:48:33+00:00 | Vulnerability · Source |
| CVE-2017-0630 | suse_vex | SUSE CVE CVE-2017-0630 | known not affected: 64 | 2026-07-26T00:48:32+00:00 | Vulnerability · Source |