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-1549 | suse_vex | SUSE CVE CVE-2016-1549 | known affected: 24 known not affected: 20 recommended: 131 | 2026-07-31T01:49:41+00:00 | Vulnerability · Source |
| CVE-2016-1550 | suse_vex | SUSE CVE CVE-2016-1550 | known affected: 30 recommended: 114 | 2026-07-31T01:49:40+00:00 | Vulnerability · Source |
| CVE-2016-1957 | suse_vex | SUSE CVE CVE-2016-1957 | known affected: 2 recommended: 648 | 2026-07-31T01:49:35+00:00 | Vulnerability · Source |
| CVE-2016-2108 | suse_vex | SUSE CVE CVE-2016-2108 | known affected: 4 recommended: 211 | 2026-07-31T01:49:33+00:00 | Vulnerability · Source |
| CVE-2016-2318 | suse_vex | SUSE CVE CVE-2016-2318 | known not affected: 551 recommended: 14 | 2026-07-31T01:49:30+00:00 | Vulnerability · Source |
| CVE-2016-2538 | suse_vex | SUSE CVE CVE-2016-2538 | known affected: 321 known not affected: 12 recommended: 631 | 2026-07-31T01:49:28+00:00 | Vulnerability · Source |
| CVE-2016-2544 | suse_vex | SUSE CVE CVE-2016-2544 | known not affected: 139 recommended: 185 | 2026-07-31T01:49:27+00:00 | Vulnerability · Source |
| CVE-2016-2550 | suse_vex | SUSE CVE CVE-2016-2550 | known not affected: 49 | 2026-07-31T01:49:25+00:00 | Vulnerability · Source |
| CVE-2016-2824 | suse_vex | SUSE CVE CVE-2016-2824 | known affected: 2 recommended: 621 | 2026-07-31T01:49:16+00:00 | Vulnerability · Source |
| CVE-2016-2825 | suse_vex | SUSE CVE CVE-2016-2825 | known affected: 1 known not affected: 41 recommended: 250 | 2026-07-31T01:49:14+00:00 | Vulnerability · Source |
| CVE-2016-2830 | suse_vex | SUSE CVE CVE-2016-2830 | known affected: 3 known not affected: 83 recommended: 494 | 2026-07-31T01:49:13+00:00 | Vulnerability · Source |
| CVE-2016-3182 | suse_vex | SUSE CVE CVE-2016-3182 | known not affected: 108 | 2026-07-31T01:49:11+00:00 | Vulnerability · Source |
| CVE-2016-3189 | suse_vex | SUSE CVE CVE-2016-3189 | known affected: 395 recommended: 465 | 2026-07-31T01:49:09+00:00 | Vulnerability · Source |
| CVE-2016-3492 | suse_vex | SUSE CVE CVE-2016-3492 | known affected: 1 known not affected: 93 recommended: 620 | 2026-07-31T01:49:07+00:00 | Vulnerability · Source |
| CVE-2016-3621 | suse_vex | SUSE CVE CVE-2016-3621 | known not affected: 30 recommended: 22 | 2026-07-31T01:49:06+00:00 | Vulnerability · Source |
| CVE-2016-4020 | suse_vex | SUSE CVE CVE-2016-4020 | known affected: 395 known not affected: 162 recommended: 1886 | 2026-07-31T01:49:01+00:00 | Vulnerability · Source |
| CVE-2016-4053 | suse_vex | SUSE CVE CVE-2016-4053 | known not affected: 55 recommended: 48 | 2026-07-31T01:49:00+00:00 | Vulnerability · Source |
| CVE-2016-4447 | suse_vex | SUSE CVE CVE-2016-4447 | known affected: 1 recommended: 116 | 2026-07-31T01:48:57+00:00 | Vulnerability · Source |
| CVE-2016-4454 | suse_vex | SUSE CVE CVE-2016-4454 | known affected: 394 known not affected: 164 recommended: 1899 | 2026-07-31T01:48:55+00:00 | Vulnerability · Source |
| CVE-2016-4622 | suse_vex | SUSE CVE CVE-2016-4622 | known not affected: 162 recommended: 927 | 2026-07-31T01:48:53+00:00 | Vulnerability · Source |
| CVE-2016-4963 | suse_vex | SUSE CVE CVE-2016-4963 | known affected: 1 known not affected: 3 recommended: 63 | 2026-07-31T01:48:51+00:00 | Vulnerability · Source |
| CVE-2016-5258 | suse_vex | SUSE CVE CVE-2016-5258 | known affected: 5 recommended: 438 | 2026-07-31T01:48:44+00:00 | Vulnerability · Source |
| CVE-2016-5420 | suse_vex | SUSE CVE CVE-2016-5420 | known affected: 17 known not affected: 21 recommended: 135 | 2026-07-31T01:48:39+00:00 | Vulnerability · Source |
| CVE-2016-5542 | suse_vex | SUSE CVE CVE-2016-5542 | known affected: 394 known not affected: 109 recommended: 805 | 2026-07-31T01:48:37+00:00 | Vulnerability · Source |
| CVE-2016-5630 | suse_vex | SUSE CVE CVE-2016-5630 | known affected: 1 known not affected: 93 recommended: 10 | 2026-07-31T01:48:35+00:00 | Vulnerability · Source |
| CVE-2016-5691 | suse_vex | SUSE CVE CVE-2016-5691 | known affected: 95 recommended: 202 | 2026-07-31T01:48:33+00:00 | Vulnerability · Source |
| CVE-2016-5825 | suse_vex | SUSE CVE CVE-2016-5825 | known affected: 1 known not affected: 41 recommended: 14 | 2026-07-31T01:48:30+00:00 | Vulnerability · Source |
| CVE-2016-6261 | suse_vex | SUSE CVE CVE-2016-6261 | known affected: 321 recommended: 808 | 2026-07-31T01:48:27+00:00 | Vulnerability · Source |
| CVE-2016-6506 | suse_vex | SUSE CVE CVE-2016-6506 | known affected: 75 recommended: 91 | 2026-07-31T01:48:21+00:00 | Vulnerability · Source |
| CVE-2016-6507 | suse_vex | SUSE CVE CVE-2016-6507 | known affected: 75 recommended: 91 | 2026-07-31T01:48:19+00:00 | Vulnerability · Source |
| CVE-2016-6836 | suse_vex | SUSE CVE CVE-2016-6836 | known affected: 395 known not affected: 178 recommended: 1878 | 2026-07-31T01:48:14+00:00 | Vulnerability · Source |
| CVE-2016-7094 | suse_vex | SUSE CVE CVE-2016-7094 | known affected: 322 known not affected: 18 recommended: 549 | 2026-07-31T01:48:12+00:00 | Vulnerability · Source |
| CVE-2016-7176 | suse_vex | SUSE CVE CVE-2016-7176 | known affected: 1 recommended: 586 | 2026-07-31T01:48:10+00:00 | Vulnerability · Source |
| CVE-2016-7179 | suse_vex | SUSE CVE CVE-2016-7179 | known affected: 1 recommended: 586 | 2026-07-31T01:48:07+00:00 | Vulnerability · Source |
| CVE-2016-7448 | suse_vex | SUSE CVE CVE-2016-7448 | known affected: 3 known not affected: 103 recommended: 14 | 2026-07-31T01:48:05+00:00 | Vulnerability · Source |
| CVE-2016-7530 | suse_vex | SUSE CVE CVE-2016-7530 | known affected: 1 recommended: 206 | 2026-07-31T01:48:04+00:00 | Vulnerability · Source |
| CVE-2016-7535 | suse_vex | SUSE CVE CVE-2016-7535 | known affected: 95 known not affected: 2 recommended: 168 | 2026-07-31T01:48:02+00:00 | Vulnerability · Source |
| CVE-2016-7545 | suse_vex | SUSE CVE CVE-2016-7545 | known affected: 394 known not affected: 17 recommended: 373 | 2026-07-31T01:48:00+00:00 | Vulnerability · Source |
| CVE-2016-7589 | suse_vex | SUSE CVE CVE-2016-7589 | known not affected: 87 recommended: 939 | 2026-07-31T01:47:58+00:00 | Vulnerability · Source |
| CVE-2016-7592 | suse_vex | SUSE CVE CVE-2016-7592 | known not affected: 87 recommended: 927 | 2026-07-31T01:47:57+00:00 | Vulnerability · Source |
| CVE-2016-7796 | suse_vex | SUSE CVE CVE-2016-7796 | known not affected: 196 recommended: 90 | 2026-07-31T01:47:55+00:00 | Vulnerability · Source |
| CVE-2016-7917 | suse_vex | SUSE CVE CVE-2016-7917 | known affected: 12 known not affected: 107 recommended: 89 | 2026-07-31T01:47:53+00:00 | Vulnerability · Source |
| CVE-2016-7952 | suse_vex | SUSE CVE CVE-2016-7952 | known affected: 36 recommended: 270 | 2026-07-31T01:47:51+00:00 | Vulnerability · Source |
| CVE-2016-7957 | suse_vex | SUSE CVE CVE-2016-7957 | known not affected: 92 | 2026-07-31T01:47:50+00:00 | Vulnerability · Source |
| CVE-2016-7974 | suse_vex | SUSE CVE CVE-2016-7974 | known affected: 320 recommended: 186 | 2026-07-31T01:47:48+00:00 | Vulnerability · Source |
| CVE-2016-8399 | suse_vex | SUSE CVE CVE-2016-8399 | known not affected: 29 recommended: 315 | 2026-07-31T01:47:46+00:00 | Vulnerability · Source |
| CVE-2016-8655 | suse_vex | SUSE CVE CVE-2016-8655 | known not affected: 510 recommended: 365 | 2026-07-31T01:47:42+00:00 | Vulnerability · Source |
| CVE-2016-8705 | suse_vex | SUSE CVE CVE-2016-8705 | known not affected: 14 recommended: 111 | 2026-07-31T01:47:41+00:00 | Vulnerability · Source |
| CVE-2016-8743 | suse_vex | SUSE CVE CVE-2016-8743 | known affected: 87 known not affected: 24 recommended: 516 | 2026-07-31T01:47:39+00:00 | Vulnerability · Source |
| CVE-2016-8747 | suse_vex | SUSE CVE CVE-2016-8747 | known not affected: 54 | 2026-07-31T01:47:38+00:00 | Vulnerability · Source |