VEX records
Browse vendor VEX statements available in this Vulnerability-Lookup instance and pivot to the related vulnerability.
291989 VEX records
API response| Vulnerability | Source | Title | Product status | Imported | Links |
|---|---|---|---|---|---|
| CVE-2016-2126 | suse_vex | SUSE CVE CVE-2016-2126 | known affected: 411 known not affected: 709 recommended: 4211 | 2026-07-26T01:03:53+00:00 | Vulnerability · Source |
| CVE-2016-2150 | suse_vex | SUSE CVE CVE-2016-2150 | known not affected: 85 recommended: 138 | 2026-07-26T01:03:51+00:00 | Vulnerability · Source |
| CVE-2016-2161 | suse_vex | SUSE CVE CVE-2016-2161 | known affected: 87 recommended: 456 | 2026-07-26T01:03:49+00:00 | Vulnerability · Source |
| CVE-2016-2182 | suse_vex | SUSE CVE CVE-2016-2182 | known affected: 325 known not affected: 314 recommended: 1067 | 2026-07-26T01:03:44+00:00 | Vulnerability · Source |
| CVE-2016-2186 | suse_vex | SUSE CVE CVE-2016-2186 | known not affected: 274 recommended: 510 | 2026-07-26T01:03:41+00:00 | Vulnerability · Source |
| CVE-2016-2188 | suse_vex | SUSE CVE CVE-2016-2188 | known affected: 3 known not affected: 204 recommended: 396 | 2026-07-26T01:03:39+00:00 | Vulnerability · Source |
| CVE-2016-2270 | suse_vex | SUSE CVE CVE-2016-2270 | known affected: 320 known not affected: 12 recommended: 544 | 2026-07-26T01:03:36+00:00 | Vulnerability · Source |
| CVE-2016-2334 | suse_vex | SUSE CVE CVE-2016-2334 | known not affected: 3 recommended: 78 | 2026-07-26T01:03:32+00:00 | Vulnerability · Source |
| CVE-2016-2335 | suse_vex | SUSE CVE CVE-2016-2335 | recommended: 100 | 2026-07-26T01:03:30+00:00 | Vulnerability · Source |
| CVE-2016-2338 | suse_vex | SUSE CVE CVE-2016-2338 | known not affected: 300 | 2026-07-26T01:03:27+00:00 | Vulnerability · Source |
| CVE-2016-2339 | suse_vex | SUSE CVE CVE-2016-2339 | known affected: 5 known not affected: 50 recommended: 140 | 2026-07-26T01:03:25+00:00 | Vulnerability · Source |
| CVE-2016-2381 | suse_vex | SUSE CVE CVE-2016-2381 | known affected: 59 recommended: 115 | 2026-07-26T01:03:23+00:00 | Vulnerability · Source |
| CVE-2016-2383 | suse_vex | SUSE CVE CVE-2016-2383 | known affected: 31 known not affected: 79 recommended: 75 | 2026-07-26T01:03:20+00:00 | Vulnerability · Source |
| CVE-2016-2524 | suse_vex | SUSE CVE CVE-2016-2524 | known affected: 3 recommended: 442 | 2026-07-26T01:03:18+00:00 | Vulnerability · Source |
| CVE-2016-2547 | suse_vex | SUSE CVE CVE-2016-2547 | known not affected: 201 recommended: 185 | 2026-07-26T01:03:12+00:00 | Vulnerability · Source |
| CVE-2016-2549 | suse_vex | SUSE CVE CVE-2016-2549 | known not affected: 230 recommended: 185 | 2026-07-26T01:03:10+00:00 | Vulnerability · Source |
| CVE-2016-2553 | suse_vex | SUSE CVE CVE-2016-2553 | known affected: 12 known not affected: 111 | 2026-07-26T01:03:08+00:00 | Vulnerability · Source |
| CVE-2016-2790 | suse_vex | SUSE CVE CVE-2016-2790 | known affected: 2 recommended: 644 | 2026-07-26T01:02:58+00:00 | Vulnerability · Source |
| CVE-2016-2791 | suse_vex | SUSE CVE CVE-2016-2791 | known affected: 2 recommended: 644 | 2026-07-26T01:02:55+00:00 | Vulnerability · Source |
| CVE-2016-2799 | suse_vex | SUSE CVE CVE-2016-2799 | known affected: 2 recommended: 644 | 2026-07-26T01:02:53+00:00 | Vulnerability · Source |
| CVE-2016-2800 | suse_vex | SUSE CVE CVE-2016-2800 | known affected: 2 recommended: 648 | 2026-07-26T01:02:50+00:00 | Vulnerability · Source |
| 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 |