VEX records
Browse vendor VEX statements available in this Vulnerability-Lookup instance and pivot to the related vulnerability.
288888 VEX records
API response| Vulnerability | Source | Title | Product status | Imported | Links |
|---|---|---|---|---|---|
| CVE-2015-3809 | suse_vex | SUSE CVE CVE-2015-3809 | known affected: 73 recommended: 442 | 2026-08-04T00:10:06+00:00 | Vulnerability · Source |
| CVE-2015-5130 | suse_vex | SUSE CVE CVE-2015-5130 | recommended: 35 | 2026-08-04T00:10:02+00:00 | Vulnerability · Source |
| CVE-2015-5822 | suse_vex | SUSE CVE CVE-2015-5822 | known not affected: 18 recommended: 238 | 2026-08-04T00:10:00+00:00 | Vulnerability · Source |
| CVE-2015-7174 | suse_vex | SUSE CVE CVE-2015-7174 | known affected: 1 recommended: 472 | 2026-08-04T00:09:58+00:00 | Vulnerability · Source |
| CVE-2015-7504 | suse_vex | SUSE CVE CVE-2015-7504 | known affected: 321 known not affected: 12 recommended: 567 | 2026-08-04T00:09:56+00:00 | Vulnerability · Source |
| CVE-2015-7942 | suse_vex | SUSE CVE CVE-2015-7942 | known affected: 400 known not affected: 102 recommended: 539 | 2026-08-04T00:09:53+00:00 | Vulnerability · Source |
| CVE-2015-8712 | suse_vex | SUSE CVE CVE-2015-8712 | known affected: 86 recommended: 107 | 2026-08-04T00:09:51+00:00 | Vulnerability · Source |
| CVE-2015-8734 | suse_vex | SUSE CVE CVE-2015-8734 | recommended: 442 | 2026-08-04T00:09:49+00:00 | Vulnerability · Source |
| CVE-2015-8744 | suse_vex | SUSE CVE CVE-2015-8744 | known affected: 321 known not affected: 176 recommended: 2302 | 2026-08-04T00:09:47+00:00 | Vulnerability · Source |
| CVE-2015-8818 | suse_vex | SUSE CVE CVE-2015-8818 | known affected: 1 known not affected: 4 recommended: 188 | 2026-08-04T00:09:45+00:00 | Vulnerability · Source |
| CVE-2015-8902 | suse_vex | SUSE CVE CVE-2015-8902 | known affected: 97 known not affected: 14 recommended: 202 | 2026-08-04T00:09:43+00:00 | Vulnerability · Source |
| CVE-2016-0599 | suse_vex | SUSE CVE CVE-2016-0599 | known affected: 2 known not affected: 176 | 2026-08-04T00:09:40+00:00 | Vulnerability · Source |
| CVE-2016-0658 | suse_vex | SUSE CVE CVE-2016-0658 | known not affected: 121 | 2026-08-04T00:09:37+00:00 | Vulnerability · Source |
| CVE-2016-0764 | suse_vex | SUSE CVE CVE-2016-0764 | known affected: 394 known not affected: 473 recommended: 549 | 2026-08-04T00:09:35+00:00 | Vulnerability · Source |
| CVE-2016-1286 | suse_vex | SUSE CVE CVE-2016-1286 | known affected: 490 recommended: 1003 | 2026-08-04T00:09:33+00:00 | Vulnerability · Source |
| CVE-2016-1967 | suse_vex | SUSE CVE CVE-2016-1967 | known affected: 38 known not affected: 183 recommended: 250 | 2026-08-04T00:09:30+00:00 | Vulnerability · Source |
| CVE-2016-2118 | suse_vex | SUSE CVE CVE-2016-2118 | known affected: 321 known not affected: 91 recommended: 4410 | 2026-08-04T00:09:28+00:00 | Vulnerability · Source |
| CVE-2016-2178 | suse_vex | SUSE CVE CVE-2016-2178 | known affected: 365 known not affected: 1014 recommended: 1250 | 2026-08-04T00:09:25+00:00 | Vulnerability · Source |
| CVE-2016-2391 | suse_vex | SUSE CVE CVE-2016-2391 | known affected: 322 known not affected: 33 recommended: 624 | 2026-08-04T00:09:23+00:00 | Vulnerability · Source |
| CVE-2016-2806 | suse_vex | SUSE CVE CVE-2016-2806 | known affected: 1 known not affected: 42 recommended: 333 | 2026-08-04T00:09:22+00:00 | Vulnerability · Source |
| CVE-2016-2809 | suse_vex | SUSE CVE CVE-2016-2809 | known affected: 1 known not affected: 42 recommended: 250 | 2026-08-04T00:09:20+00:00 | Vulnerability · Source |
| 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 |