VEX records
Browse vendor VEX statements available in this Vulnerability-Lookup instance and pivot to the related vulnerability.
285317 VEX records
API response| Vulnerability | Source | Title | Product status | Imported | Links |
|---|---|---|---|---|---|
| CVE-2016-4487 | suse_vex | SUSE CVE CVE-2016-4487 | known not affected: 1028 | 2026-07-26T01:00:38+00:00 | Vulnerability · Source |
| CVE-2016-4555 | suse_vex | SUSE CVE CVE-2016-4555 | known affected: 394 known not affected: 32 recommended: 49 | 2026-07-26T01:00:36+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-4563 | suse_vex | SUSE CVE CVE-2016-4563 | known affected: 97 recommended: 202 | 2026-07-26T01:00:33+00:00 | Vulnerability · Source |
| CVE-2016-4591 | suse_vex | SUSE CVE CVE-2016-4591 | known not affected: 162 recommended: 927 | 2026-07-26T01:00:31+00:00 | Vulnerability · Source |
| CVE-2016-4738 | suse_vex | SUSE CVE CVE-2016-4738 | known affected: 452 known not affected: 78 recommended: 331 | 2026-07-26T01:00:29+00:00 | Vulnerability · Source |
| CVE-2016-4794 | suse_vex | SUSE CVE CVE-2016-4794 | known affected: 3 known not affected: 459 recommended: 87 | 2026-07-26T01:00:27+00:00 | Vulnerability · Source |
| CVE-2016-4796 | suse_vex | SUSE CVE CVE-2016-4796 | known not affected: 98 | 2026-07-26T01:00:26+00:00 | Vulnerability · Source |
| CVE-2016-4809 | suse_vex | SUSE CVE CVE-2016-4809 | known affected: 425 recommended: 240 | 2026-07-26T01:00:24+00:00 | Vulnerability · Source |
| CVE-2016-4857 | suse_vex | SUSE CVE CVE-2016-4857 | known not affected: 443 | 2026-07-26T01:00:22+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-4953 | suse_vex | SUSE CVE CVE-2016-4953 | known affected: 31 recommended: 109 | 2026-07-26T01:00:19+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-4957 | suse_vex | SUSE CVE CVE-2016-4957 | known affected: 31 recommended: 109 | 2026-07-26T01:00:16+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-5011 | suse_vex | SUSE CVE CVE-2016-5011 | known affected: 320 known not affected: 111 recommended: 1664 | 2026-07-26T01:00:07+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-5105 | suse_vex | SUSE CVE CVE-2016-5105 | known affected: 396 known not affected: 162 recommended: 1855 | 2026-07-26T01:00:00+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-5118 | suse_vex | SUSE CVE CVE-2016-5118 | recommended: 838 | 2026-07-26T00:59:55+00:00 | Vulnerability · Source |
| CVE-2016-5158 | suse_vex | SUSE CVE CVE-2016-5158 | recommended: 200 | 2026-07-26T00:59:50+00:00 | Vulnerability · Source |
| CVE-2016-5180 | suse_vex | SUSE CVE CVE-2016-5180 | known affected: 320 known not affected: 80 recommended: 311 | 2026-07-26T00:59:48+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-5250 | suse_vex | SUSE CVE CVE-2016-5250 | known affected: 5 recommended: 332 | 2026-07-26T00:59:44+00:00 | Vulnerability · Source |
| CVE-2016-5254 | suse_vex | SUSE CVE CVE-2016-5254 | known affected: 5 recommended: 438 | 2026-07-26T00:59:41+00:00 | Vulnerability · Source |
| CVE-2016-5255 | suse_vex | SUSE CVE CVE-2016-5255 | known affected: 5 recommended: 250 | 2026-07-26T00:59:39+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-5260 | suse_vex | SUSE CVE CVE-2016-5260 | known affected: 1 recommended: 250 | 2026-07-26T00:59:34+00:00 | Vulnerability · Source |
| CVE-2016-5262 | suse_vex | SUSE CVE CVE-2016-5262 | known affected: 5 recommended: 438 | 2026-07-26T00:59:31+00:00 | Vulnerability · Source |
| CVE-2016-5263 | suse_vex | SUSE CVE CVE-2016-5263 | known affected: 5 recommended: 438 | 2026-07-26T00:59:29+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-5274 | suse_vex | SUSE CVE CVE-2016-5274 | known affected: 5 recommended: 332 | 2026-07-26T00:59:25+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-5282 | suse_vex | SUSE CVE CVE-2016-5282 | known affected: 5 recommended: 250 | 2026-07-26T00:59:19+00:00 | Vulnerability · Source |
| CVE-2016-5284 | suse_vex | SUSE CVE CVE-2016-5284 | known affected: 5 recommended: 332 | 2026-07-26T00:59:17+00:00 | Vulnerability · Source |
| CVE-2016-5287 | suse_vex | SUSE CVE CVE-2016-5287 | known affected: 1 known not affected: 52 recommended: 250 | 2026-07-26T00:59:15+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-5296 | suse_vex | SUSE CVE CVE-2016-5296 | known affected: 2 recommended: 655 | 2026-07-26T00:59:11+00:00 | Vulnerability · Source |
| CVE-2016-5298 | suse_vex | SUSE CVE CVE-2016-5298 | known affected: 1 known not affected: 38 recommended: 250 | 2026-07-26T00:59:09+00:00 | Vulnerability · Source |
| CVE-2016-5314 | suse_vex | SUSE CVE CVE-2016-5314 | known affected: 439 recommended: 295 | 2026-07-26T00:59:07+00:00 | Vulnerability · Source |
| CVE-2016-5315 | suse_vex | SUSE CVE CVE-2016-5315 | known affected: 1 known not affected: 133 recommended: 22 | 2026-07-26T00:59:06+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-5317 | suse_vex | SUSE CVE CVE-2016-5317 | known affected: 45 recommended: 295 | 2026-07-26T00:59:01+00:00 | Vulnerability · Source |
| CVE-2016-5320 | suse_vex | SUSE CVE CVE-2016-5320 | known affected: 394 known not affected: 335 recommended: 299 | 2026-07-26T00:58:58+00:00 | Vulnerability · Source |
| CVE-2016-5350 | suse_vex | SUSE CVE CVE-2016-5350 | known not affected: 115 recommended: 533 | 2026-07-26T00:58:56+00:00 | Vulnerability · Source |