VEX records
Browse vendor VEX statements available in this Vulnerability-Lookup instance and pivot to the related vulnerability.
294114 VEX records
API response| Vulnerability | Source | Title | Product status | Imported | Links |
|---|---|---|---|---|---|
| CVE-2014-8176 | suse_vex | SUSE CVE CVE-2014-8176 | known affected: 3 known not affected: 42 recommended: 21 | 2026-07-29T00:11:13+00:00 | Vulnerability · Source |
| CVE-2014-9157 | suse_vex | SUSE CVE CVE-2014-9157 | known not affected: 18 | 2026-07-29T00:11:05+00:00 | Vulnerability · Source |
| CVE-2014-9278 | suse_vex | SUSE CVE CVE-2014-9278 | known not affected: 13 recommended: 8 | 2026-07-29T00:11:03+00:00 | Vulnerability · Source |
| CVE-2014-9293 | suse_vex | SUSE CVE CVE-2014-9293 | known not affected: 1 recommended: 109 | 2026-07-29T00:11:02+00:00 | Vulnerability · Source |
| CVE-2014-9449 | suse_vex | SUSE CVE CVE-2014-9449 | known not affected: 48 recommended: 138 | 2026-07-29T00:11:00+00:00 | Vulnerability · Source |
| CVE-2014-9808 | suse_vex | SUSE CVE CVE-2014-9808 | known affected: 97 recommended: 216 | 2026-07-29T00:10:50+00:00 | Vulnerability · Source |
| CVE-2014-9892 | suse_vex | SUSE CVE CVE-2014-9892 | known not affected: 52 | 2026-07-29T00:10:44+00:00 | Vulnerability · Source |
| CVE-2015-0252 | suse_vex | SUSE CVE CVE-2015-0252 | known not affected: 35 recommended: 61 | 2026-07-29T00:10:40+00:00 | Vulnerability · Source |
| CVE-2015-0296 | suse_vex | SUSE CVE CVE-2015-0296 | known not affected: 316 | 2026-07-29T00:10:38+00:00 | Vulnerability · Source |
| CVE-2015-0361 | suse_vex | SUSE CVE CVE-2015-0361 | known not affected: 2 recommended: 63 | 2026-07-29T00:10:37+00:00 | Vulnerability · Source |
| CVE-2015-0395 | suse_vex | SUSE CVE CVE-2015-0395 | recommended: 95 | 2026-07-29T00:10:35+00:00 | Vulnerability · Source |
| CVE-2015-0488 | suse_vex | SUSE CVE CVE-2015-0488 | known affected: 507 known not affected: 93 recommended: 515 | 2026-07-29T00:10:34+00:00 | Vulnerability · Source |
| CVE-2015-1081 | suse_vex | SUSE CVE CVE-2015-1081 | known not affected: 18 recommended: 238 | 2026-07-29T00:10:26+00:00 | Vulnerability · Source |
| CVE-2015-1822 | suse_vex | SUSE CVE CVE-2015-1822 | known not affected: 116 recommended: 1 | 2026-07-29T00:10:19+00:00 | Vulnerability · Source |
| CVE-2015-2666 | suse_vex | SUSE CVE CVE-2015-2666 | known not affected: 399 recommended: 139 | 2026-07-29T00:10:14+00:00 | Vulnerability · Source |
| CVE-2015-3418 | suse_vex | SUSE CVE CVE-2015-3418 | known not affected: 1 recommended: 89 | 2026-07-29T00:10:05+00:00 | Vulnerability · Source |
| CVE-2015-3455 | suse_vex | SUSE CVE CVE-2015-3455 | known affected: 3 known not affected: 9 recommended: 5 | 2026-07-29T00:10:04+00:00 | Vulnerability · Source |
| CVE-2015-3741 | suse_vex | SUSE CVE CVE-2015-3741 | known not affected: 18 recommended: 238 | 2026-07-29T00:10:03+00:00 | Vulnerability · Source |
| CVE-2015-4047 | suse_vex | SUSE CVE CVE-2015-4047 | recommended: 18 | 2026-07-29T00:10:01+00:00 | Vulnerability · Source |
| CVE-2015-4177 | suse_vex | SUSE CVE CVE-2015-4177 | known not affected: 47 | 2026-07-29T00:09:58+00:00 | Vulnerability · Source |
| CVE-2015-4470 | suse_vex | SUSE CVE CVE-2015-4470 | known affected: 24 recommended: 62 | 2026-07-29T00:09:56+00:00 | Vulnerability · Source |
| CVE-2015-5352 | suse_vex | SUSE CVE CVE-2015-5352 | known affected: 2 recommended: 90 | 2026-07-29T00:09:43+00:00 | Vulnerability · Source |
| CVE-2015-8076 | suse_vex | SUSE CVE CVE-2015-8076 | known affected: 1 recommended: 32 | 2026-07-29T00:09:27+00:00 | Vulnerability · Source |
| CVE-2015-8327 | suse_vex | SUSE CVE CVE-2015-8327 | recommended: 211 | 2026-07-29T00:09:25+00:00 | Vulnerability · Source |
| CVE-2015-8895 | suse_vex | SUSE CVE CVE-2015-8895 | known affected: 94 known not affected: 51 recommended: 172 | 2026-07-29T00:09:10+00:00 | Vulnerability · Source |
| CVE-2015-8916 | suse_vex | SUSE CVE CVE-2015-8916 | recommended: 24 | 2026-07-29T00:09:09+00:00 | Vulnerability · Source |
| CVE-2015-8955 | suse_vex | SUSE CVE CVE-2015-8955 | known not affected: 350 | 2026-07-29T00:09:06+00:00 | Vulnerability · Source |
| CVE-2015-8970 | suse_vex | SUSE CVE CVE-2015-8970 | known affected: 37 known not affected: 274 recommended: 176 | 2026-07-29T00:09:03+00:00 | Vulnerability · Source |
| CVE-2015-9096 | suse_vex | SUSE CVE CVE-2015-9096 | known not affected: 55 recommended: 83 | 2026-07-29T00:09:01+00:00 | Vulnerability · Source |
| CVE-2016-1585 | suse_vex | SUSE CVE CVE-2016-1585 | known not affected: 270 recommended: 157 | 2026-07-29T00:08:39+00:00 | Vulnerability · Source |
| CVE-2016-1602 | suse_vex | SUSE CVE CVE-2016-1602 | known not affected: 51 recommended: 24 | 2026-07-29T00:08:38+00:00 | Vulnerability · Source |
| CVE-2016-1944 | suse_vex | SUSE CVE CVE-2016-1944 | known affected: 21 recommended: 250 | 2026-07-29T00:08:33+00:00 | Vulnerability · Source |
| CVE-2016-1951 | suse_vex | SUSE CVE CVE-2016-1951 | known not affected: 40 | 2026-07-29T00:08:31+00:00 | Vulnerability · Source |
| CVE-2016-2185 | suse_vex | SUSE CVE CVE-2016-2185 | known affected: 21 known not affected: 210 recommended: 510 | 2026-07-29T00:08:19+00:00 | Vulnerability · Source |
| CVE-2016-2517 | suse_vex | SUSE CVE CVE-2016-2517 | known affected: 30 recommended: 109 | 2026-07-29T00:08:17+00:00 | Vulnerability · Source |
| CVE-2016-2571 | suse_vex | SUSE CVE CVE-2016-2571 | known affected: 397 known not affected: 33 recommended: 50 | 2026-07-29T00:08:12+00:00 | Vulnerability · Source |
| CVE-2016-2814 | suse_vex | SUSE CVE CVE-2016-2814 | known affected: 2 known not affected: 3 recommended: 417 | 2026-07-29T00:08:08+00:00 | Vulnerability · Source |
| CVE-2016-2851 | suse_vex | SUSE CVE CVE-2016-2851 | known affected: 31 known not affected: 31 recommended: 97 | 2026-07-29T00:08:05+00:00 | Vulnerability · Source |
| CVE-2016-4492 | suse_vex | SUSE CVE CVE-2016-4492 | known affected: 2 known not affected: 416 | 2026-07-29T00:07:52+00:00 | Vulnerability · Source |
| CVE-2016-4553 | suse_vex | SUSE CVE CVE-2016-4553 | known affected: 396 known not affected: 31 recommended: 49 | 2026-07-29T00:07:50+00:00 | Vulnerability · Source |
| CVE-2016-5271 | suse_vex | SUSE CVE CVE-2016-5271 | known affected: 5 recommended: 250 | 2026-07-29T00:07:39+00:00 | Vulnerability · Source |
| CVE-2016-5863 | suse_vex | SUSE CVE CVE-2016-5863 | known not affected: 78 | 2026-07-29T00:07:30+00:00 | Vulnerability · Source |
| CVE-2016-6787 | suse_vex | SUSE CVE CVE-2016-6787 | known not affected: 529 | 2026-07-29T00:07:20+00:00 | Vulnerability · Source |
| CVE-2016-6906 | suse_vex | SUSE CVE CVE-2016-6906 | known affected: 12 known not affected: 1226 recommended: 56 | 2026-07-29T00:07:17+00:00 | Vulnerability · Source |
| CVE-2016-7039 | suse_vex | SUSE CVE CVE-2016-7039 | known affected: 27 known not affected: 409 recommended: 215 | 2026-07-29T00:07:16+00:00 | Vulnerability · Source |
| CVE-2016-7531 | suse_vex | SUSE CVE CVE-2016-7531 | known affected: 95 recommended: 182 | 2026-07-29T00:07:10+00:00 | Vulnerability · Source |
| CVE-2016-7533 | suse_vex | SUSE CVE CVE-2016-7533 | known affected: 95 recommended: 182 | 2026-07-29T00:07:08+00:00 | Vulnerability · Source |
| CVE-2016-7540 | suse_vex | SUSE CVE CVE-2016-7540 | known affected: 94 known not affected: 51 recommended: 132 | 2026-07-29T00:07:07+00:00 | Vulnerability · Source |
| CVE-2016-7649 | suse_vex | SUSE CVE CVE-2016-7649 | known not affected: 87 | 2026-07-29T00:07:04+00:00 | Vulnerability · Source |
| CVE-2016-7949 | suse_vex | SUSE CVE CVE-2016-7949 | known affected: 36 recommended: 270 | 2026-07-29T00:06:56+00:00 | Vulnerability · Source |