VEX records
Browse vendor VEX statements available in this Vulnerability-Lookup instance and pivot to the related vulnerability.
283882 VEX records
API response| Vulnerability | Source | Title | Product status | Imported | Links |
|---|---|---|---|---|---|
| CVE-2016-5629 | suse_vex | SUSE CVE CVE-2016-5629 | known affected: 1 known not affected: 93 recommended: 620 | 2026-07-26T00:58:04+00:00 | Vulnerability · Source |
| CVE-2016-5636 | suse_vex | SUSE CVE CVE-2016-5636 | known affected: 432 known not affected: 211 recommended: 1488 | 2026-07-26T00:58:01+00:00 | Vulnerability · Source |
| CVE-2016-5688 | suse_vex | SUSE CVE CVE-2016-5688 | known affected: 95 recommended: 216 | 2026-07-26T00:57:58+00:00 | Vulnerability · Source |
| CVE-2016-5696 | suse_vex | SUSE CVE CVE-2016-5696 | known affected: 17 known not affected: 412 recommended: 371 | 2026-07-26T00:57:56+00:00 | Vulnerability · Source |
| CVE-2016-5829 | suse_vex | SUSE CVE CVE-2016-5829 | known affected: 44 known not affected: 106 recommended: 523 | 2026-07-26T00:57:53+00:00 | Vulnerability · Source |
| CVE-2016-5841 | suse_vex | SUSE CVE CVE-2016-5841 | known affected: 95 known not affected: 14 recommended: 202 | 2026-07-26T00:57:50+00:00 | Vulnerability · Source |
| CVE-2016-5842 | suse_vex | SUSE CVE CVE-2016-5842 | known affected: 95 known not affected: 14 recommended: 202 | 2026-07-26T00:57:47+00:00 | Vulnerability · Source |
| CVE-2016-5844 | suse_vex | SUSE CVE CVE-2016-5844 | known affected: 394 known not affected: 17 recommended: 226 | 2026-07-26T00:57:44+00:00 | Vulnerability · Source |
| CVE-2016-5857 | suse_vex | SUSE CVE CVE-2016-5857 | known not affected: 55 | 2026-07-26T00:57:42+00:00 | Vulnerability · Source |
| CVE-2016-5875 | suse_vex | SUSE CVE CVE-2016-5875 | known affected: 452 recommended: 298 | 2026-07-26T00:57:40+00:00 | Vulnerability · Source |
| CVE-2016-6162 | suse_vex | SUSE CVE CVE-2016-6162 | known not affected: 42 | 2026-07-26T00:57:37+00:00 | Vulnerability · Source |
| CVE-2016-6163 | suse_vex | SUSE CVE CVE-2016-6163 | known not affected: 267 recommended: 10 | 2026-07-26T00:57:35+00:00 | Vulnerability · Source |
| CVE-2016-6170 | suse_vex | SUSE CVE CVE-2016-6170 | known affected: 31 known not affected: 221 recommended: 539 | 2026-07-26T00:57:32+00:00 | Vulnerability · Source |
| CVE-2016-6207 | suse_vex | SUSE CVE CVE-2016-6207 | known affected: 1530 known not affected: 389 recommended: 1329 | 2026-07-26T00:57:29+00:00 | Vulnerability · Source |
| CVE-2016-6214 | suse_vex | SUSE CVE CVE-2016-6214 | known affected: 394 known not affected: 13 recommended: 234 | 2026-07-26T00:57:27+00:00 | Vulnerability · Source |
| CVE-2016-6224 | suse_vex | SUSE CVE CVE-2016-6224 | known not affected: 14 recommended: 29 | 2026-07-26T00:57:24+00:00 | Vulnerability · Source |
| CVE-2016-6252 | suse_vex | SUSE CVE CVE-2016-6252 | known affected: 12 known not affected: 22 recommended: 24 | 2026-07-26T00:57:22+00:00 | Vulnerability · Source |
| CVE-2016-6258 | suse_vex | SUSE CVE CVE-2016-6258 | known affected: 320 known not affected: 18 recommended: 549 | 2026-07-26T00:57:19+00:00 | Vulnerability · Source |
| CVE-2016-6262 | suse_vex | SUSE CVE CVE-2016-6262 | known affected: 1 recommended: 518 | 2026-07-26T00:57:16+00:00 | Vulnerability · Source |
| CVE-2016-6293 | suse_vex | SUSE CVE CVE-2016-6293 | known affected: 2 known not affected: 509 recommended: 136 | 2026-07-26T00:57:14+00:00 | Vulnerability · Source |
| CVE-2016-6294 | suse_vex | SUSE CVE CVE-2016-6294 | known affected: 2 known not affected: 1228 recommended: 1250 | 2026-07-26T00:57:11+00:00 | Vulnerability · Source |
| CVE-2016-6301 | suse_vex | SUSE CVE CVE-2016-6301 | known affected: 2 known not affected: 1 recommended: 136 | 2026-07-26T00:57:09+00:00 | Vulnerability · Source |
| CVE-2016-6303 | suse_vex | SUSE CVE CVE-2016-6303 | known affected: 325 known not affected: 370 recommended: 1062 | 2026-07-26T00:57:06+00:00 | Vulnerability · Source |
| CVE-2016-6305 | suse_vex | SUSE CVE CVE-2016-6305 | known not affected: 65 | 2026-07-26T00:57:04+00:00 | Vulnerability · Source |
| CVE-2016-6306 | suse_vex | SUSE CVE CVE-2016-6306 | known affected: 325 known not affected: 370 recommended: 1254 | 2026-07-26T00:57:01+00:00 | Vulnerability · Source |
| CVE-2016-6309 | suse_vex | SUSE CVE CVE-2016-6309 | known not affected: 72 | 2026-07-26T00:56:58+00:00 | Vulnerability · Source |
| CVE-2016-6321 | suse_vex | SUSE CVE CVE-2016-6321 | known affected: 322 known not affected: 55 recommended: 313 | 2026-07-26T00:56:56+00:00 | Vulnerability · Source |
| CVE-2016-6351 | suse_vex | SUSE CVE CVE-2016-6351 | known affected: 322 known not affected: 436 recommended: 2261 | 2026-07-26T00:56:53+00:00 | Vulnerability · Source |
| CVE-2016-6508 | suse_vex | SUSE CVE CVE-2016-6508 | known affected: 75 recommended: 533 | 2026-07-26T00:56:50+00:00 | Vulnerability · Source |
| CVE-2016-6510 | suse_vex | SUSE CVE CVE-2016-6510 | known affected: 75 recommended: 533 | 2026-07-26T00:56:48+00:00 | Vulnerability · Source |
| CVE-2016-6796 | suse_vex | SUSE CVE CVE-2016-6796 | known affected: 46 known not affected: 110 recommended: 202 | 2026-07-26T00:56:45+00:00 | Vulnerability · Source |
| CVE-2016-6823 | suse_vex | SUSE CVE CVE-2016-6823 | known affected: 61 recommended: 218 | 2026-07-26T00:56:42+00:00 | Vulnerability · Source |
| CVE-2016-6833 | suse_vex | SUSE CVE CVE-2016-6833 | known affected: 1 known not affected: 178 recommended: 1831 | 2026-07-26T00:56:39+00:00 | Vulnerability · Source |
| CVE-2016-6835 | suse_vex | SUSE CVE CVE-2016-6835 | known affected: 1 known not affected: 53 recommended: 116 | 2026-07-26T00:56:36+00:00 | Vulnerability · Source |
| CVE-2016-6893 | suse_vex | SUSE CVE CVE-2016-6893 | known affected: 15 recommended: 30 | 2026-07-26T00:56:34+00:00 | Vulnerability · Source |
| CVE-2016-6905 | suse_vex | SUSE CVE CVE-2016-6905 | known affected: 394 known not affected: 1227 recommended: 234 | 2026-07-26T00:56:31+00:00 | Vulnerability · Source |
| CVE-2016-7031 | suse_vex | SUSE CVE CVE-2016-7031 | known not affected: 583 | 2026-07-26T00:56:28+00:00 | Vulnerability · Source |
| CVE-2016-7069 | suse_vex | SUSE CVE CVE-2016-7069 | recommended: 81 | 2026-07-26T00:56:25+00:00 | Vulnerability · Source |
| CVE-2016-7091 | suse_vex | SUSE CVE CVE-2016-7091 | known not affected: 24 recommended: 2 | 2026-07-26T00:56:22+00:00 | Vulnerability · Source |
| CVE-2016-7093 | suse_vex | SUSE CVE CVE-2016-7093 | known affected: 321 known not affected: 16 recommended: 486 | 2026-07-26T00:56:20+00:00 | Vulnerability · Source |
| CVE-2016-7097 | suse_vex | SUSE CVE CVE-2016-7097 | known not affected: 361 recommended: 390 | 2026-07-26T00:56:17+00:00 | Vulnerability · Source |
| CVE-2016-7101 | suse_vex | SUSE CVE CVE-2016-7101 | known affected: 95 recommended: 182 | 2026-07-26T00:56:15+00:00 | Vulnerability · Source |
| CVE-2016-7141 | suse_vex | SUSE CVE CVE-2016-7141 | known affected: 17 known not affected: 21 recommended: 135 | 2026-07-26T00:56:11+00:00 | Vulnerability · Source |
| CVE-2016-7156 | suse_vex | SUSE CVE CVE-2016-7156 | known affected: 394 known not affected: 166 recommended: 1815 | 2026-07-26T00:56:08+00:00 | Vulnerability · Source |
| CVE-2016-7163 | suse_vex | SUSE CVE CVE-2016-7163 | recommended: 203 | 2026-07-26T00:56:06+00:00 | Vulnerability · Source |
| CVE-2016-7170 | suse_vex | SUSE CVE CVE-2016-7170 | known affected: 421 known not affected: 136 recommended: 1834 | 2026-07-26T00:56:03+00:00 | Vulnerability · Source |
| CVE-2016-7423 | suse_vex | SUSE CVE CVE-2016-7423 | known affected: 394 known not affected: 177 recommended: 1688 | 2026-07-26T00:55:59+00:00 | Vulnerability · Source |
| CVE-2016-7426 | suse_vex | SUSE CVE CVE-2016-7426 | known affected: 30 recommended: 114 | 2026-07-26T00:55:57+00:00 | Vulnerability · Source |
| CVE-2016-7427 | suse_vex | SUSE CVE CVE-2016-7427 | known affected: 30 recommended: 109 | 2026-07-26T00:55:55+00:00 | Vulnerability · Source |
| CVE-2016-7428 | suse_vex | SUSE CVE CVE-2016-7428 | known affected: 30 recommended: 109 | 2026-07-26T00:55:52+00:00 | Vulnerability · Source |