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-3623 | suse_vex | SUSE CVE CVE-2016-3623 | known affected: 463 recommended: 281 | 2026-07-26T01:01:36+00:00 | Vulnerability · Source |
| CVE-2016-3627 | suse_vex | SUSE CVE CVE-2016-3627 | known affected: 321 known not affected: 102 recommended: 586 | 2026-07-26T01:01:34+00:00 | Vulnerability · Source |
| CVE-2026-64294 | microsoft_vex | mm: do file ownership checks with the proper mount idmap | under investigation: 1 | 2026-07-26T01:01:33+00:00 | Vulnerability · Source |
| CVE-2016-3697 | suse_vex | SUSE CVE CVE-2016-3697 | known affected: 320 known not affected: 147 recommended: 291 | 2026-07-26T01:01:32+00:00 | Vulnerability · Source |
| CVE-2026-64219 | microsoft_vex | drm/amd/display: Validate payload length and link_index in dc_process_dmub_aux_transfer_async | under investigation: 1 | 2026-07-26T01:01:30+00:00 | Vulnerability · Source |
| CVE-2016-3699 | suse_vex | SUSE CVE CVE-2016-3699 | known affected: 24 known not affected: 310 recommended: 12 | 2026-07-26T01:01:30+00:00 | Vulnerability · Source |
| CVE-2016-3709 | suse_vex | SUSE CVE CVE-2016-3709 | known affected: 376 known not affected: 97 recommended: 300 | 2026-07-26T01:01:28+00:00 | Vulnerability · Source |
| CVE-2016-3712 | suse_vex | SUSE CVE CVE-2016-3712 | known affected: 395 known not affected: 162 recommended: 1881 | 2026-07-26T01:01:26+00:00 | Vulnerability · Source |
| CVE-2016-3716 | suse_vex | SUSE CVE CVE-2016-3716 | known not affected: 140 recommended: 816 | 2026-07-26T01:01:24+00:00 | Vulnerability · Source |
| CVE-2016-3841 | suse_vex | SUSE CVE CVE-2016-3841 | known not affected: 524 recommended: 205 | 2026-07-26T01:01:21+00:00 | Vulnerability · Source |
| CVE-2016-3947 | suse_vex | SUSE CVE CVE-2016-3947 | known affected: 396 known not affected: 36 recommended: 47 | 2026-07-26T01:01:19+00:00 | Vulnerability · Source |
| CVE-2016-3960 | suse_vex | SUSE CVE CVE-2016-3960 | known affected: 1 recommended: 126 | 2026-07-26T01:01:16+00:00 | Vulnerability · Source |
| CVE-2016-3977 | suse_vex | SUSE CVE CVE-2016-3977 | known affected: 482 recommended: 265 | 2026-07-26T01:01:14+00:00 | Vulnerability · Source |
| CVE-2016-4051 | suse_vex | SUSE CVE CVE-2016-4051 | known affected: 394 known not affected: 26 recommended: 53 | 2026-07-26T01:01:12+00:00 | Vulnerability · Source |
| CVE-2016-4054 | suse_vex | SUSE CVE CVE-2016-4054 | known not affected: 55 recommended: 48 | 2026-07-26T01:01:10+00:00 | Vulnerability · Source |
| CVE-2016-4300 | suse_vex | SUSE CVE CVE-2016-4300 | known affected: 30 known not affected: 17 recommended: 225 | 2026-07-26T01:01:07+00:00 | Vulnerability · Source |
| CVE-2016-4302 | suse_vex | SUSE CVE CVE-2016-4302 | known affected: 30 known not affected: 17 recommended: 40 | 2026-07-26T01:01:05+00:00 | Vulnerability · Source |
| CVE-2016-4347 | suse_vex | SUSE CVE CVE-2016-4347 | known not affected: 161 | 2026-07-26T01:01:03+00:00 | Vulnerability · Source |
| CVE-2016-4416 | suse_vex | SUSE CVE CVE-2016-4416 | known not affected: 71 | 2026-07-26T01:01:02+00:00 | Vulnerability · Source |
| CVE-2016-4417 | suse_vex | SUSE CVE CVE-2016-4417 | known not affected: 71 | 2026-07-26T01:01:00+00:00 | Vulnerability · Source |
| 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-4441 | suse_vex | SUSE CVE CVE-2016-4441 | known affected: 320 known not affected: 201 recommended: 2368 | 2026-07-26T01:00:51+00:00 | Vulnerability · Source |
| CVE-2016-4453 | suse_vex | SUSE CVE CVE-2016-4453 | known affected: 394 known not affected: 162 recommended: 1899 | 2026-07-26T01:00:49+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-4463 | suse_vex | SUSE CVE CVE-2016-4463 | recommended: 196 | 2026-07-26T01:00:45+00:00 | Vulnerability · Source |
| CVE-2016-4477 | suse_vex | SUSE CVE CVE-2016-4477 | known not affected: 66 recommended: 74 | 2026-07-26T01:00:43+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-4485 | suse_vex | SUSE CVE CVE-2016-4485 | known affected: 2 known not affected: 418 recommended: 290 | 2026-07-26T01:00:40+00:00 | Vulnerability · Source |
| 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 |