VEX records
Browse vendor VEX statements available in this Vulnerability-Lookup instance and pivot to the related vulnerability.
283120 VEX records
API response| Vulnerability | Source | Title | Product status | Imported | Links |
|---|---|---|---|---|---|
| CVE-2016-2796 | suse_vex | SUSE CVE CVE-2016-2796 | known affected: 2 recommended: 604 | 2026-07-19T18:39:17+00:00 | Vulnerability · Source |
| CVE-2016-2797 | suse_vex | SUSE CVE CVE-2016-2797 | known affected: 2 recommended: 600 | 2026-07-19T18:39:15+00:00 | Vulnerability · Source |
| CVE-2016-2800 | suse_vex | SUSE CVE CVE-2016-2800 | known affected: 2 recommended: 604 | 2026-07-19T18:39:14+00:00 | Vulnerability · Source |
| CVE-2016-2801 | suse_vex | SUSE CVE CVE-2016-2801 | known affected: 2 recommended: 600 | 2026-07-19T18:39:13+00:00 | Vulnerability · Source |
| CVE-2016-2804 | suse_vex | SUSE CVE CVE-2016-2804 | known affected: 1 known not affected: 38 recommended: 250 | 2026-07-19T18:39:12+00:00 | Vulnerability · Source |
| CVE-2016-2806 | suse_vex | SUSE CVE CVE-2016-2806 | known affected: 1 known not affected: 38 recommended: 333 | 2026-07-19T18:39:10+00:00 | Vulnerability · Source |
| CVE-2016-2815 | suse_vex | SUSE CVE CVE-2016-2815 | known affected: 2 recommended: 661 | 2026-07-19T18:39:09+00:00 | Vulnerability · Source |
| CVE-2016-2816 | suse_vex | SUSE CVE CVE-2016-2816 | known affected: 1 known not affected: 38 recommended: 250 | 2026-07-19T18:39:08+00:00 | Vulnerability · Source |
| CVE-2016-2818 | suse_vex | SUSE CVE CVE-2016-2818 | known affected: 2 recommended: 659 | 2026-07-19T18:39:07+00:00 | Vulnerability · Source |
| CVE-2016-2821 | suse_vex | SUSE CVE CVE-2016-2821 | known affected: 2 recommended: 576 | 2026-07-19T18:39:05+00:00 | Vulnerability · Source |
| CVE-2016-2822 | suse_vex | SUSE CVE CVE-2016-2822 | known affected: 2 recommended: 576 | 2026-07-19T18:39:04+00:00 | Vulnerability · Source |
| CVE-2016-2824 | suse_vex | SUSE CVE CVE-2016-2824 | known affected: 2 recommended: 575 | 2026-07-19T18:39:03+00:00 | Vulnerability · Source |
| CVE-2016-2825 | suse_vex | SUSE CVE CVE-2016-2825 | known affected: 1 known not affected: 37 recommended: 250 | 2026-07-19T18:39:02+00:00 | Vulnerability · Source |
| CVE-2016-2828 | suse_vex | SUSE CVE CVE-2016-2828 | known affected: 2 recommended: 576 | 2026-07-19T18:39:00+00:00 | Vulnerability · Source |
| CVE-2016-2831 | suse_vex | SUSE CVE CVE-2016-2831 | known affected: 2 recommended: 576 | 2026-07-19T18:38:59+00:00 | Vulnerability · Source |
| CVE-2016-2836 | suse_vex | SUSE CVE CVE-2016-2836 | known affected: 3 recommended: 427 | 2026-07-19T18:38:58+00:00 | Vulnerability · Source |
| CVE-2016-3119 | suse_vex | SUSE CVE CVE-2016-3119 | known affected: 320 known not affected: 131 recommended: 695 | 2026-07-19T18:38:57+00:00 | Vulnerability · Source |
| CVE-2016-3492 | suse_vex | SUSE CVE CVE-2016-3492 | known affected: 1 known not affected: 86 recommended: 582 | 2026-07-19T18:38:55+00:00 | Vulnerability · Source |
| CVE-2016-3615 | suse_vex | SUSE CVE CVE-2016-3615 | known affected: 1 known not affected: 37 recommended: 633 | 2026-07-19T18:38:54+00:00 | Vulnerability · Source |
| CVE-2016-3623 | suse_vex | SUSE CVE CVE-2016-3623 | known affected: 455 recommended: 272 | 2026-07-19T18:38:53+00:00 | Vulnerability · Source |
| CVE-2016-3627 | suse_vex | SUSE CVE CVE-2016-3627 | known affected: 321 known not affected: 83 recommended: 561 | 2026-07-19T18:38:51+00:00 | Vulnerability · Source |
| CVE-2016-3630 | suse_vex | SUSE CVE CVE-2016-3630 | known not affected: 24 recommended: 61 | 2026-07-19T18:38:50+00:00 | Vulnerability · Source |
| CVE-2016-3695 | suse_vex | SUSE CVE CVE-2016-3695 | known affected: 239 known not affected: 485 recommended: 1213 | 2026-07-19T18:38:48+00:00 | Vulnerability · Source |
| CVE-2016-3698 | suse_vex | SUSE CVE CVE-2016-3698 | known not affected: 38 recommended: 145 | 2026-07-19T18:38:47+00:00 | Vulnerability · Source |
| CVE-2016-3705 | suse_vex | SUSE CVE CVE-2016-3705 | known not affected: 90 recommended: 507 | 2026-07-19T18:38:46+00:00 | Vulnerability · Source |
| CVE-2016-3712 | suse_vex | SUSE CVE CVE-2016-3712 | known affected: 395 known not affected: 134 recommended: 1802 | 2026-07-19T18:38:44+00:00 | Vulnerability · Source |
| CVE-2016-3716 | suse_vex | SUSE CVE CVE-2016-3716 | known not affected: 125 recommended: 806 | 2026-07-19T18:38:43+00:00 | Vulnerability · Source |
| CVE-2016-3959 | suse_vex | SUSE CVE CVE-2016-3959 | known not affected: 147 recommended: 45 | 2026-07-19T18:38:42+00:00 | Vulnerability · Source |
| CVE-2016-3977 | suse_vex | SUSE CVE CVE-2016-3977 | known affected: 474 recommended: 250 | 2026-07-19T18:38:40+00:00 | Vulnerability · Source |
| CVE-2016-3990 | suse_vex | SUSE CVE CVE-2016-3990 | known affected: 394 known not affected: 280 recommended: 276 | 2026-07-19T18:38:39+00:00 | Vulnerability · Source |
| CVE-2016-4441 | suse_vex | SUSE CVE CVE-2016-4441 | known affected: 320 known not affected: 167 recommended: 2264 | 2026-07-19T18:38:37+00:00 | Vulnerability · Source |
| CVE-2016-4454 | suse_vex | SUSE CVE CVE-2016-4454 | known affected: 394 known not affected: 136 recommended: 1827 | 2026-07-19T18:38:36+00:00 | Vulnerability · Source |
| CVE-2016-4472 | suse_vex | SUSE CVE CVE-2016-4472 | known affected: 320 known not affected: 56 recommended: 459 | 2026-07-19T18:38:34+00:00 | Vulnerability · Source |
| CVE-2016-4476 | suse_vex | SUSE CVE CVE-2016-4476 | known affected: 3 known not affected: 41 recommended: 75 | 2026-07-19T18:38:33+00:00 | Vulnerability · Source |
| CVE-2016-4488 | suse_vex | SUSE CVE CVE-2016-4488 | known not affected: 986 | 2026-07-19T18:38:32+00:00 | Vulnerability · Source |
| CVE-2016-4554 | suse_vex | SUSE CVE CVE-2016-4554 | known not affected: 23 recommended: 48 | 2026-07-19T18:38:30+00:00 | Vulnerability · Source |
| CVE-2016-4556 | suse_vex | SUSE CVE CVE-2016-4556 | known affected: 2 known not affected: 28 recommended: 44 | 2026-07-19T18:38:29+00:00 | Vulnerability · Source |
| CVE-2016-4574 | suse_vex | SUSE CVE CVE-2016-4574 | known affected: 321 recommended: 269 | 2026-07-19T18:38:28+00:00 | Vulnerability · Source |
| CVE-2016-4692 | suse_vex | SUSE CVE CVE-2016-4692 | known not affected: 87 recommended: 924 | 2026-07-19T18:38:26+00:00 | Vulnerability · Source |
| CVE-2016-4743 | suse_vex | SUSE CVE CVE-2016-4743 | known not affected: 87 recommended: 924 | 2026-07-19T18:38:25+00:00 | Vulnerability · Source |
| CVE-2016-5011 | suse_vex | SUSE CVE CVE-2016-5011 | known affected: 320 known not affected: 91 recommended: 1613 | 2026-07-19T18:38:23+00:00 | Vulnerability · Source |
| CVE-2016-5107 | suse_vex | SUSE CVE CVE-2016-5107 | known affected: 395 known not affected: 135 recommended: 1783 | 2026-07-19T18:38:22+00:00 | Vulnerability · Source |
| CVE-2016-5139 | suse_vex | SUSE CVE CVE-2016-5139 | recommended: 200 | 2026-07-19T18:38:21+00:00 | Vulnerability · Source |
| CVE-2016-5152 | suse_vex | SUSE CVE CVE-2016-5152 | recommended: 197 | 2026-07-19T18:38:19+00:00 | Vulnerability · Source |
| CVE-2016-5253 | suse_vex | SUSE CVE CVE-2016-5253 | known affected: 1 recommended: 250 | 2026-07-19T18:38:18+00:00 | Vulnerability · Source |
| CVE-2016-5256 | suse_vex | SUSE CVE CVE-2016-5256 | known affected: 3 recommended: 250 | 2026-07-19T18:38:17+00:00 | Vulnerability · Source |
| CVE-2016-5267 | suse_vex | SUSE CVE CVE-2016-5267 | known affected: 1 recommended: 250 | 2026-07-19T18:38:16+00:00 | Vulnerability · Source |
| CVE-2016-5277 | suse_vex | SUSE CVE CVE-2016-5277 | known affected: 3 recommended: 324 | 2026-07-19T18:38:14+00:00 | Vulnerability · Source |
| CVE-2016-5278 | suse_vex | SUSE CVE CVE-2016-5278 | known affected: 3 recommended: 324 | 2026-07-19T18:38:13+00:00 | Vulnerability · Source |
| CVE-2016-5287 | suse_vex | SUSE CVE CVE-2016-5287 | known affected: 1 known not affected: 48 recommended: 250 | 2026-07-19T18:38:12+00:00 | Vulnerability · Source |