VEX records
Browse vendor VEX statements available in this Vulnerability-Lookup instance and pivot to the related vulnerability.
291935 VEX records
API response| Vulnerability | Source | Title | Product status | Imported | Links |
|---|---|---|---|---|---|
| CVE-2016-2808 | suse_vex | SUSE CVE CVE-2016-2808 | known affected: 2 recommended: 417 | 2026-07-26T01:02:45+00:00 | Vulnerability · Source |
| CVE-2016-2817 | suse_vex | SUSE CVE CVE-2016-2817 | known affected: 1 known not affected: 42 recommended: 250 | 2026-07-26T01:02:41+00:00 | Vulnerability · Source |
| CVE-2016-2819 | suse_vex | SUSE CVE CVE-2016-2819 | known affected: 2 recommended: 622 | 2026-07-26T01:02:38+00:00 | Vulnerability · Source |
| CVE-2016-2822 | suse_vex | SUSE CVE CVE-2016-2822 | known affected: 2 recommended: 622 | 2026-07-26T01:02:36+00:00 | Vulnerability · Source |
| CVE-2016-2826 | suse_vex | SUSE CVE CVE-2016-2826 | known not affected: 41 | 2026-07-26T01:02:33+00:00 | Vulnerability · Source |
| CVE-2016-2831 | suse_vex | SUSE CVE CVE-2016-2831 | known affected: 2 recommended: 622 | 2026-07-26T01:02:28+00:00 | Vulnerability · Source |
| CVE-2016-2835 | suse_vex | SUSE CVE CVE-2016-2835 | known affected: 5 recommended: 351 | 2026-07-26T01:02:26+00:00 | Vulnerability · Source |
| CVE-2016-2841 | suse_vex | SUSE CVE CVE-2016-2841 | known affected: 320 known not affected: 144 recommended: 621 | 2026-07-26T01:02:24+00:00 | Vulnerability · Source |
| CVE-2016-2857 | suse_vex | SUSE CVE CVE-2016-2857 | recommended: 110 | 2026-07-26T01:02:21+00:00 | Vulnerability · Source |
| CVE-2016-3065 | suse_vex | SUSE CVE CVE-2016-3065 | known not affected: 410 recommended: 94 | 2026-07-26T01:02:19+00:00 | Vulnerability · Source |
| CVE-2016-3075 | suse_vex | SUSE CVE CVE-2016-3075 | known affected: 321 known not affected: 121 recommended: 1361 | 2026-07-26T01:02:16+00:00 | Vulnerability · Source |
| CVE-2016-3156 | suse_vex | SUSE CVE CVE-2016-3156 | known affected: 24 known not affected: 109 recommended: 397 | 2026-07-26T01:02:09+00:00 | Vulnerability · Source |
| CVE-2016-3158 | suse_vex | SUSE CVE CVE-2016-3158 | known affected: 1 recommended: 126 | 2026-07-26T01:02:08+00:00 | Vulnerability · Source |
| CVE-2016-3159 | suse_vex | SUSE CVE CVE-2016-3159 | known affected: 1 recommended: 126 | 2026-07-26T01:02:06+00:00 | Vulnerability · Source |
| CVE-2016-3177 | suse_vex | SUSE CVE CVE-2016-3177 | known not affected: 56 | 2026-07-26T01:02:04+00:00 | Vulnerability · Source |
| CVE-2016-3183 | suse_vex | SUSE CVE CVE-2016-3183 | known not affected: 66 recommended: 20 | 2026-07-26T01:02:01+00:00 | Vulnerability · Source |
| CVE-2016-3190 | suse_vex | SUSE CVE CVE-2016-3190 | known not affected: 25 recommended: 48 | 2026-07-26T01:01:59+00:00 | Vulnerability · Source |
| CVE-2016-3425 | suse_vex | SUSE CVE CVE-2016-3425 | known affected: 112 known not affected: 93 recommended: 364 | 2026-07-26T01:01:57+00:00 | Vulnerability · Source |
| CVE-2016-3461 | suse_vex | SUSE CVE CVE-2016-3461 | known not affected: 121 | 2026-07-26T01:01:54+00:00 | Vulnerability · Source |
| CVE-2016-3477 | suse_vex | SUSE CVE CVE-2016-3477 | known affected: 1 known not affected: 44 recommended: 671 | 2026-07-26T01:01:52+00:00 | Vulnerability · Source |
| CVE-2016-3485 | suse_vex | SUSE CVE CVE-2016-3485 | known affected: 464 known not affected: 109 recommended: 749 | 2026-07-26T01:01:50+00:00 | Vulnerability · Source |
| CVE-2016-3500 | suse_vex | SUSE CVE CVE-2016-3500 | known not affected: 96 recommended: 351 | 2026-07-26T01:01:47+00:00 | Vulnerability · Source |
| CVE-2016-3550 | suse_vex | SUSE CVE CVE-2016-3550 | known not affected: 96 recommended: 351 | 2026-07-26T01:01:44+00:00 | Vulnerability · Source |
| CVE-2016-3552 | suse_vex | SUSE CVE CVE-2016-3552 | recommended: 255 | 2026-07-26T01:01:42+00:00 | Vulnerability · Source |
| CVE-2016-3587 | suse_vex | SUSE CVE CVE-2016-3587 | known not affected: 1483 recommended: 815 | 2026-07-26T01:01:40+00:00 | Vulnerability · Source |
| CVE-2016-3610 | suse_vex | SUSE CVE CVE-2016-3610 | recommended: 346 | 2026-07-26T01:01:39+00:00 | Vulnerability · Source |
| CVE-2016-3619 | suse_vex | SUSE CVE CVE-2016-3619 | known not affected: 30 recommended: 22 | 2026-07-26T01:01:37+00:00 | Vulnerability · Source |
| 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-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-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-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-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-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 |