VEX records
Browse vendor VEX statements available in this Vulnerability-Lookup instance and pivot to the related vulnerability.
288586 VEX records
API response| Vulnerability | Source | Title | Product status | Imported | Links |
|---|---|---|---|---|---|
| CVE-2016-2836 | suse_vex | SUSE CVE CVE-2016-2836 | known affected: 5 recommended: 435 | 2026-08-04T00:09:19+00:00 | Vulnerability · Source |
| CVE-2016-3068 | suse_vex | SUSE CVE CVE-2016-3068 | known not affected: 24 recommended: 65 | 2026-08-04T00:09:17+00:00 | Vulnerability · Source |
| CVE-2016-3714 | suse_vex | SUSE CVE CVE-2016-3714 | known affected: 63 known not affected: 57 recommended: 840 | 2026-08-04T00:09:14+00:00 | Vulnerability · Source |
| CVE-2016-4036 | suse_vex | SUSE CVE CVE-2016-4036 | known affected: 1 known not affected: 125 | 2026-08-04T00:09:12+00:00 | Vulnerability · Source |
| CVE-2016-4448 | suse_vex | SUSE CVE CVE-2016-4448 | known affected: 1 recommended: 116 | 2026-08-04T00:09:10+00:00 | Vulnerability · Source |
| CVE-2016-5126 | suse_vex | SUSE CVE CVE-2016-5126 | known affected: 396 known not affected: 166 recommended: 1862 | 2026-08-04T00:09:05+00:00 | Vulnerability · Source |
| CVE-2016-5289 | suse_vex | SUSE CVE CVE-2016-5289 | known affected: 1 known not affected: 84 recommended: 321 | 2026-08-04T00:09:03+00:00 | Vulnerability · Source |
| CVE-2016-5338 | suse_vex | SUSE CVE CVE-2016-5338 | known affected: 323 known not affected: 454 recommended: 2341 | 2026-08-04T00:09:01+00:00 | Vulnerability · Source |
| CVE-2016-6855 | suse_vex | SUSE CVE CVE-2016-6855 | known not affected: 57 recommended: 229 | 2026-08-04T00:08:57+00:00 | Vulnerability · Source |
| CVE-2016-6912 | suse_vex | SUSE CVE CVE-2016-6912 | known affected: 406 known not affected: 1259 recommended: 236 | 2026-08-04T00:08:54+00:00 | Vulnerability · Source |
| CVE-2016-7431 | suse_vex | SUSE CVE CVE-2016-7431 | known affected: 30 recommended: 109 | 2026-08-04T00:08:50+00:00 | Vulnerability · Source |
| CVE-2016-7515 | suse_vex | SUSE CVE CVE-2016-7515 | known affected: 95 recommended: 182 | 2026-08-04T00:08:48+00:00 | Vulnerability · Source |
| CVE-2016-7799 | suse_vex | SUSE CVE CVE-2016-7799 | known affected: 95 known not affected: 14 recommended: 168 | 2026-08-04T00:08:46+00:00 | Vulnerability · Source |
| CVE-2016-7910 | suse_vex | SUSE CVE CVE-2016-7910 | known affected: 14 known not affected: 386 recommended: 315 | 2026-08-04T00:08:43+00:00 | Vulnerability · Source |
| CVE-2016-9178 | suse_vex | SUSE CVE CVE-2016-9178 | known not affected: 210 | 2026-08-04T00:08:39+00:00 | Vulnerability · Source |
| CVE-2016-9297 | suse_vex | SUSE CVE CVE-2016-9297 | known affected: 394 recommended: 276 | 2026-08-04T00:08:36+00:00 | Vulnerability · Source |
| CVE-2016-9373 | suse_vex | SUSE CVE CVE-2016-9373 | known affected: 1 recommended: 586 | 2026-08-04T00:08:34+00:00 | Vulnerability · Source |
| CVE-2016-10013 | suse_vex | SUSE CVE CVE-2016-10013 | known affected: 333 known not affected: 55 recommended: 545 | 2026-08-04T00:08:30+00:00 | Vulnerability · Source |
| CVE-2016-10048 | suse_vex | SUSE CVE CVE-2016-10048 | known affected: 1 recommended: 218 | 2026-08-04T00:08:27+00:00 | Vulnerability · Source |
| CVE-2016-10156 | suse_vex | SUSE CVE CVE-2016-10156 | known affected: 451 known not affected: 45 recommended: 1132 | 2026-08-04T00:08:24+00:00 | Vulnerability · Source |
| CVE-2016-10198 | suse_vex | SUSE CVE CVE-2016-10198 | recommended: 466 | 2026-08-04T00:08:21+00:00 | Vulnerability · Source |
| CVE-2017-2862 | suse_vex | SUSE CVE CVE-2017-2862 | known affected: 396 known not affected: 87 recommended: 1096 | 2026-08-04T00:08:15+00:00 | Vulnerability · Source |
| CVE-2017-3651 | suse_vex | SUSE CVE CVE-2017-3651 | known affected: 1 known not affected: 44 recommended: 36 | 2026-08-04T00:08:12+00:00 | Vulnerability · Source |
| CVE-2017-5342 | suse_vex | SUSE CVE CVE-2017-5342 | known affected: 320 recommended: 182 | 2026-08-04T00:08:08+00:00 | Vulnerability · Source |
| CVE-2017-5416 | suse_vex | SUSE CVE CVE-2017-5416 | known affected: 1 recommended: 333 | 2026-08-04T00:08:06+00:00 | Vulnerability · Source |
| CVE-2017-5437 | suse_vex | SUSE CVE CVE-2017-5437 | known not affected: 42 recommended: 737 | 2026-08-04T00:08:03+00:00 | Vulnerability · Source |
| CVE-2017-5472 | suse_vex | SUSE CVE CVE-2017-5472 | known affected: 2 known not affected: 42 recommended: 462 | 2026-08-04T00:08:00+00:00 | Vulnerability · Source |
| CVE-2017-5503 | suse_vex | SUSE CVE CVE-2017-5503 | known affected: 46 recommended: 154 | 2026-08-04T00:07:57+00:00 | Vulnerability · Source |
| CVE-2017-6014 | suse_vex | SUSE CVE CVE-2017-6014 | known affected: 1 recommended: 144 | 2026-08-04T00:07:54+00:00 | Vulnerability · Source |
| CVE-2017-6471 | suse_vex | SUSE CVE CVE-2017-6471 | known affected: 73 recommended: 444 | 2026-08-04T00:07:51+00:00 | Vulnerability · Source |
| CVE-2017-7012 | suse_vex | SUSE CVE CVE-2017-7012 | known affected: 12 known not affected: 329 recommended: 927 | 2026-08-04T00:07:47+00:00 | Vulnerability · Source |
| CVE-2017-7040 | suse_vex | SUSE CVE CVE-2017-7040 | known affected: 12 known not affected: 329 recommended: 927 | 2026-08-04T00:07:44+00:00 | Vulnerability · Source |
| CVE-2017-7742 | suse_vex | SUSE CVE CVE-2017-7742 | known affected: 1 recommended: 68 | 2026-08-04T00:07:40+00:00 | Vulnerability · Source |
| CVE-2017-7780 | suse_vex | SUSE CVE CVE-2017-7780 | known affected: 1 known not affected: 42 recommended: 12 | 2026-08-04T00:07:38+00:00 | Vulnerability · Source |
| CVE-2017-9107 | suse_vex | SUSE CVE CVE-2017-9107 | known affected: 18 recommended: 49 | 2026-08-04T00:07:34+00:00 | Vulnerability · Source |
| CVE-2017-9239 | suse_vex | SUSE CVE CVE-2017-9239 | known affected: 21 recommended: 164 | 2026-08-04T00:07:31+00:00 | Vulnerability · Source |
| CVE-2017-9747 | suse_vex | SUSE CVE CVE-2017-9747 | known affected: 394 known not affected: 345 recommended: 340 | 2026-08-04T00:07:28+00:00 | Vulnerability · Source |
| CVE-2017-9751 | suse_vex | SUSE CVE CVE-2017-9751 | known affected: 8 known not affected: 42 | 2026-08-04T00:07:26+00:00 | Vulnerability · Source |
| CVE-2017-10662 | suse_vex | SUSE CVE CVE-2017-10662 | known not affected: 28 | 2026-08-04T00:07:22+00:00 | Vulnerability · Source |
| CVE-2017-10922 | suse_vex | SUSE CVE CVE-2017-10922 | recommended: 35 | 2026-08-04T00:07:19+00:00 | Vulnerability · Source |
| CVE-2017-11536 | suse_vex | SUSE CVE CVE-2017-11536 | known affected: 10 known not affected: 144 | 2026-08-04T00:07:16+00:00 | Vulnerability · Source |
| CVE-2017-11600 | suse_vex | SUSE CVE CVE-2017-11600 | known affected: 46 known not affected: 284 recommended: 657 | 2026-08-04T00:07:13+00:00 | Vulnerability · Source |
| CVE-2017-11641 | suse_vex | SUSE CVE CVE-2017-11641 | known affected: 3 known not affected: 128 recommended: 14 | 2026-08-04T00:07:11+00:00 | Vulnerability · Source |
| CVE-2017-12188 | suse_vex | SUSE CVE CVE-2017-12188 | known not affected: 357 recommended: 26 | 2026-08-04T00:07:09+00:00 | Vulnerability · Source |
| CVE-2017-12193 | suse_vex | SUSE CVE CVE-2017-12193 | known not affected: 182 recommended: 499 | 2026-08-04T00:07:07+00:00 | Vulnerability · Source |
| CVE-2017-12430 | suse_vex | SUSE CVE CVE-2017-12430 | known affected: 94 recommended: 186 | 2026-08-04T00:07:05+00:00 | Vulnerability · Source |
| CVE-2017-12940 | suse_vex | SUSE CVE CVE-2017-12940 | known affected: 5 recommended: 28 | 2026-08-04T00:07:03+00:00 | Vulnerability · Source |
| CVE-2017-12941 | suse_vex | SUSE CVE CVE-2017-12941 | known affected: 5 recommended: 28 | 2026-08-04T00:07:02+00:00 | Vulnerability · Source |
| CVE-2017-13686 | suse_vex | SUSE CVE CVE-2017-13686 | known not affected: 28 | 2026-08-04T00:06:59+00:00 | Vulnerability · Source |
| CVE-2017-13749 | suse_vex | SUSE CVE CVE-2017-13749 | known affected: 6 known not affected: 56 | 2026-08-04T00:06:57+00:00 | Vulnerability · Source |