VEX records
Browse vendor VEX statements available in this Vulnerability-Lookup instance and pivot to the related vulnerability.
294140 VEX records
API response| Vulnerability | Source | Title | Product status | Imported | Links |
|---|---|---|---|---|---|
| CVE-2016-1572 | suse_vex | SUSE CVE CVE-2016-1572 | known affected: 11 recommended: 232 | 2026-07-26T01:05:06+00:00 | Vulnerability · Source |
| CVE-2016-1949 | suse_vex | SUSE CVE CVE-2016-1949 | known affected: 1 known not affected: 43 recommended: 250 | 2026-07-26T01:04:37+00:00 | Vulnerability · Source |
| CVE-2016-1959 | suse_vex | SUSE CVE CVE-2016-1959 | known affected: 38 known not affected: 183 recommended: 250 | 2026-07-26T01:04:29+00:00 | Vulnerability · Source |
| CVE-2016-2114 | suse_vex | SUSE CVE CVE-2016-2114 | known not affected: 635 recommended: 53 | 2026-07-26T01:04:06+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-2335 | suse_vex | SUSE CVE CVE-2016-2335 | recommended: 100 | 2026-07-26T01:03:30+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-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-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-2819 | suse_vex | SUSE CVE CVE-2016-2819 | known affected: 2 recommended: 622 | 2026-07-26T01:02:38+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-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-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-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-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-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-4418 | suse_vex | SUSE CVE CVE-2016-4418 | known not affected: 71 | 2026-07-26T01:00:58+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-4484 | suse_vex | SUSE CVE CVE-2016-4484 | known not affected: 55 | 2026-07-26T01:00:42+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-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-4954 | suse_vex | SUSE CVE CVE-2016-4954 | known affected: 31 recommended: 109 | 2026-07-26T01:00:18+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-5018 | suse_vex | SUSE CVE CVE-2016-5018 | known affected: 46 known not affected: 110 recommended: 202 | 2026-07-26T01:00:05+00:00 | Vulnerability · Source |
| CVE-2016-5102 | suse_vex | SUSE CVE CVE-2016-5102 | recommended: 57 | 2026-07-26T01:00:03+00:00 | Vulnerability · Source |
| CVE-2016-5116 | suse_vex | SUSE CVE CVE-2016-5116 | known affected: 394 known not affected: 13 recommended: 234 | 2026-07-26T00:59:57+00:00 | Vulnerability · Source |
| CVE-2016-5244 | suse_vex | SUSE CVE CVE-2016-5244 | known affected: 24 known not affected: 422 recommended: 527 | 2026-07-26T00:59:46+00:00 | Vulnerability · Source |
| CVE-2016-5270 | suse_vex | SUSE CVE CVE-2016-5270 | known affected: 5 recommended: 332 | 2026-07-26T00:59:27+00:00 | Vulnerability · Source |
| CVE-2016-5277 | suse_vex | SUSE CVE CVE-2016-5277 | known affected: 5 recommended: 332 | 2026-07-26T00:59:23+00:00 | Vulnerability · Source |
| CVE-2016-5281 | suse_vex | SUSE CVE CVE-2016-5281 | known affected: 5 recommended: 332 | 2026-07-26T00:59:21+00:00 | Vulnerability · Source |
| CVE-2016-5294 | suse_vex | SUSE CVE CVE-2016-5294 | known affected: 4 known not affected: 36 recommended: 250 | 2026-07-26T00:59:13+00:00 | Vulnerability · Source |
| CVE-2016-5316 | suse_vex | SUSE CVE CVE-2016-5316 | known affected: 439 recommended: 295 | 2026-07-26T00:59:04+00:00 | Vulnerability · Source |
| CVE-2016-5352 | suse_vex | SUSE CVE CVE-2016-5352 | known not affected: 115 recommended: 533 | 2026-07-26T00:58:53+00:00 | Vulnerability · Source |
| CVE-2016-5361 | suse_vex | SUSE CVE CVE-2016-5361 | known affected: 72 known not affected: 53 recommended: 1 | 2026-07-26T00:58:43+00:00 | Vulnerability · Source |
| CVE-2016-5384 | suse_vex | SUSE CVE CVE-2016-5384 | known not affected: 44 recommended: 71 | 2026-07-26T00:58:41+00:00 | Vulnerability · Source |