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-4418 | suse_vex | SUSE CVE CVE-2016-4418 | known not affected: 71 | 2026-07-26T01:00:58+00:00 | Vulnerability · Source |
| CVE-2016-4421 | suse_vex | SUSE CVE CVE-2016-4421 | known not affected: 71 | 2026-07-26T01:00:56+00:00 | Vulnerability · Source |
| CVE-2016-4425 | suse_vex | SUSE CVE CVE-2016-4425 | known affected: 4 known not affected: 131 | 2026-07-26T01:00:54+00:00 | Vulnerability · Source |
| CVE-2016-4440 | suse_vex | SUSE CVE CVE-2016-4440 | known not affected: 390 | 2026-07-26T01:00:53+00:00 | Vulnerability · Source |
| CVE-2016-4456 | suse_vex | SUSE CVE CVE-2016-4456 | known not affected: 86 | 2026-07-26T01:00:47+00:00 | Vulnerability · Source |
| CVE-2016-4484 | suse_vex | SUSE CVE CVE-2016-4484 | known not affected: 55 | 2026-07-26T01:00:42+00:00 | Vulnerability · Source |
| CVE-2016-4558 | suse_vex | SUSE CVE CVE-2016-4558 | known affected: 31 known not affected: 161 recommended: 189 | 2026-07-26T01:00:35+00:00 | Vulnerability · Source |
| CVE-2016-4951 | suse_vex | SUSE CVE CVE-2016-4951 | known affected: 31 known not affected: 141 recommended: 189 | 2026-07-26T01:00:21+00:00 | Vulnerability · Source |
| CVE-2016-4954 | suse_vex | SUSE CVE CVE-2016-4954 | known affected: 31 recommended: 109 | 2026-07-26T01:00:18+00:00 | Vulnerability · Source |
| CVE-2016-4973 | suse_vex | SUSE CVE CVE-2016-4973 | known not affected: 701 | 2026-07-26T01:00:15+00:00 | Vulnerability · Source |
| CVE-2016-4979 | suse_vex | SUSE CVE CVE-2016-4979 | known affected: 394 known not affected: 200 recommended: 387 | 2026-07-26T01:00:13+00:00 | Vulnerability · Source |
| CVE-2016-5008 | suse_vex | SUSE CVE CVE-2016-5008 | known affected: 1 known not affected: 665 recommended: 148 | 2026-07-26T01:00:11+00:00 | Vulnerability · Source |
| CVE-2016-5010 | suse_vex | SUSE CVE CVE-2016-5010 | known not affected: 467 recommended: 166 | 2026-07-26T01:00:10+00:00 | Vulnerability · Source |
| CVE-2016-5018 | suse_vex | SUSE CVE CVE-2016-5018 | known affected: 46 known not affected: 110 recommended: 202 | 2026-07-26T01:00:05+00:00 | Vulnerability · Source |
| CVE-2016-5102 | suse_vex | SUSE CVE CVE-2016-5102 | recommended: 57 | 2026-07-26T01:00:03+00:00 | Vulnerability · Source |
| CVE-2016-5116 | suse_vex | SUSE CVE CVE-2016-5116 | known affected: 394 known not affected: 13 recommended: 234 | 2026-07-26T00:59:57+00:00 | Vulnerability · Source |
| CVE-2016-5244 | suse_vex | SUSE CVE CVE-2016-5244 | known affected: 24 known not affected: 422 recommended: 527 | 2026-07-26T00:59:46+00:00 | Vulnerability · Source |
| CVE-2016-5257 | suse_vex | SUSE CVE CVE-2016-5257 | known affected: 5 recommended: 333 | 2026-07-26T00:59:36+00:00 | Vulnerability · Source |
| CVE-2016-5270 | suse_vex | SUSE CVE CVE-2016-5270 | known affected: 5 recommended: 332 | 2026-07-26T00:59:27+00:00 | Vulnerability · Source |
| CVE-2016-5277 | suse_vex | SUSE CVE CVE-2016-5277 | known affected: 5 recommended: 332 | 2026-07-26T00:59:23+00:00 | Vulnerability · Source |
| CVE-2016-5281 | suse_vex | SUSE CVE CVE-2016-5281 | known affected: 5 recommended: 332 | 2026-07-26T00:59:21+00:00 | Vulnerability · Source |
| CVE-2016-5294 | suse_vex | SUSE CVE CVE-2016-5294 | known affected: 4 known not affected: 36 recommended: 250 | 2026-07-26T00:59:13+00:00 | Vulnerability · Source |
| CVE-2016-5316 | suse_vex | SUSE CVE CVE-2016-5316 | known affected: 439 recommended: 295 | 2026-07-26T00:59:04+00:00 | Vulnerability · Source |
| CVE-2016-5352 | suse_vex | SUSE CVE CVE-2016-5352 | known not affected: 115 recommended: 533 | 2026-07-26T00:58:53+00:00 | Vulnerability · Source |
| CVE-2016-5361 | suse_vex | SUSE CVE CVE-2016-5361 | known affected: 72 known not affected: 53 recommended: 1 | 2026-07-26T00:58:43+00:00 | Vulnerability · Source |
| CVE-2016-5384 | suse_vex | SUSE CVE CVE-2016-5384 | known not affected: 44 recommended: 71 | 2026-07-26T00:58:41+00:00 | Vulnerability · Source |
| CVE-2016-5387 | suse_vex | SUSE CVE CVE-2016-5387 | known affected: 426 recommended: 463 | 2026-07-26T00:58:38+00:00 | Vulnerability · Source |
| CVE-2016-5408 | suse_vex | SUSE CVE CVE-2016-5408 | known not affected: 26 | 2026-07-26T00:58:33+00:00 | Vulnerability · Source |
| CVE-2016-5412 | suse_vex | SUSE CVE CVE-2016-5412 | known not affected: 585 recommended: 87 | 2026-07-26T00:58:31+00:00 | Vulnerability · Source |
| CVE-2016-5552 | suse_vex | SUSE CVE CVE-2016-5552 | known affected: 518 known not affected: 166 recommended: 584 | 2026-07-26T00:58:20+00:00 | Vulnerability · Source |
| CVE-2016-5597 | suse_vex | SUSE CVE CVE-2016-5597 | known not affected: 263 recommended: 805 | 2026-07-26T00:58:10+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-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-5857 | suse_vex | SUSE CVE CVE-2016-5857 | known not affected: 55 | 2026-07-26T00:57:42+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-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-6305 | suse_vex | SUSE CVE CVE-2016-6305 | known not affected: 65 | 2026-07-26T00:57:04+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-6508 | suse_vex | SUSE CVE CVE-2016-6508 | known affected: 75 recommended: 533 | 2026-07-26T00:56:50+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-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-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-7429 | suse_vex | SUSE CVE CVE-2016-7429 | known affected: 30 recommended: 114 | 2026-07-26T00:55:50+00:00 | Vulnerability · Source |
| CVE-2016-7444 | suse_vex | SUSE CVE CVE-2016-7444 | known affected: 8 recommended: 148 | 2026-07-26T00:55:47+00:00 | Vulnerability · Source |