VEX records
Browse vendor VEX statements available in this Vulnerability-Lookup instance and pivot to the related vulnerability.
291728 VEX records
API response| Vulnerability | Source | Title | Product status | Imported | Links |
|---|---|---|---|---|---|
| CVE-2015-4872 | suse_vex | SUSE CVE CVE-2015-4872 | known affected: 95 known not affected: 289 recommended: 771 | 2026-08-05T01:31:10+00:00 | Vulnerability · Source |
| CVE-2015-4895 | suse_vex | SUSE CVE CVE-2015-4895 | known affected: 13 known not affected: 117 recommended: 487 | 2026-08-05T01:31:08+00:00 | Vulnerability · Source |
| CVE-2015-4913 | suse_vex | SUSE CVE CVE-2015-4913 | known affected: 13 known not affected: 117 recommended: 711 | 2026-08-05T01:31:06+00:00 | Vulnerability · Source |
| CVE-2015-5180 | suse_vex | SUSE CVE CVE-2015-5180 | known affected: 321 known not affected: 321 recommended: 1254 | 2026-08-05T01:31:04+00:00 | Vulnerability · Source |
| CVE-2015-5213 | suse_vex | SUSE CVE CVE-2015-5213 | recommended: 5001 | 2026-08-05T01:31:01+00:00 | Vulnerability · Source |
| CVE-2015-5289 | suse_vex | SUSE CVE CVE-2015-5289 | known affected: 1 recommended: 283 | 2026-08-05T01:30:59+00:00 | Vulnerability · Source |
| CVE-2015-8567 | suse_vex | SUSE CVE CVE-2015-8567 | known affected: 1 known not affected: 185 recommended: 2228 | 2026-08-05T01:30:54+00:00 | Vulnerability · Source |
| CVE-2015-8722 | suse_vex | SUSE CVE CVE-2015-8722 | known affected: 86 recommended: 549 | 2026-08-05T01:30:52+00:00 | Vulnerability · Source |
| CVE-2015-8812 | suse_vex | SUSE CVE CVE-2015-8812 | known affected: 24 known not affected: 169 recommended: 447 | 2026-08-05T01:30:48+00:00 | Vulnerability · Source |
| CVE-2015-8984 | suse_vex | SUSE CVE CVE-2015-8984 | known affected: 1 known not affected: 133 | 2026-08-05T01:30:46+00:00 | Vulnerability · Source |
| CVE-2016-1978 | suse_vex | SUSE CVE CVE-2016-1978 | known affected: 51 recommended: 473 | 2026-08-05T01:30:42+00:00 | Vulnerability · Source |
| CVE-2016-2337 | suse_vex | SUSE CVE CVE-2016-2337 | known not affected: 37 | 2026-08-05T01:30:37+00:00 | Vulnerability · Source |
| CVE-2016-2390 | suse_vex | SUSE CVE CVE-2016-2390 | known not affected: 34 recommended: 43 | 2026-08-05T01:30:35+00:00 | Vulnerability · Source |
| CVE-2016-2815 | suse_vex | SUSE CVE CVE-2016-2815 | known affected: 2 recommended: 707 | 2026-08-05T01:30:32+00:00 | Vulnerability · Source |
| CVE-2016-3672 | suse_vex | SUSE CVE CVE-2016-3672 | known affected: 3 known not affected: 244 recommended: 238 | 2026-08-05T01:30:27+00:00 | Vulnerability · Source |
| CVE-2016-3955 | suse_vex | SUSE CVE CVE-2016-3955 | known affected: 24 known not affected: 99 recommended: 104 | 2026-08-05T01:30:25+00:00 | Vulnerability · Source |
| CVE-2016-4049 | suse_vex | SUSE CVE CVE-2016-4049 | known affected: 79 known not affected: 125 recommended: 319 | 2026-08-05T01:30:23+00:00 | Vulnerability · Source |
| CVE-2016-4856 | suse_vex | SUSE CVE CVE-2016-4856 | known not affected: 443 | 2026-08-05T01:30:21+00:00 | Vulnerability · Source |
| CVE-2016-5259 | suse_vex | SUSE CVE CVE-2016-5259 | known affected: 5 recommended: 438 | 2026-08-05T01:30:18+00:00 | Vulnerability · Source |
| CVE-2016-5388 | suse_vex | SUSE CVE CVE-2016-5388 | recommended: 103 | 2026-08-05T01:30:16+00:00 | Vulnerability · Source |
| CVE-2016-5547 | suse_vex | SUSE CVE CVE-2016-5547 | known affected: 124 known not affected: 166 recommended: 584 | 2026-08-05T01:30:15+00:00 | Vulnerability · Source |
| CVE-2016-5582 | suse_vex | SUSE CVE CVE-2016-5582 | known affected: 88 recommended: 364 | 2026-08-05T01:30:13+00:00 | Vulnerability · Source |
| CVE-2016-5699 | suse_vex | SUSE CVE CVE-2016-5699 | known affected: 395 recommended: 1456 | 2026-08-05T01:30:11+00:00 | Vulnerability · Source |
| CVE-2016-6511 | suse_vex | SUSE CVE CVE-2016-6511 | known affected: 75 recommended: 533 | 2026-08-05T01:30:09+00:00 | Vulnerability · Source |
| CVE-2016-6662 | suse_vex | SUSE CVE CVE-2016-6662 | known affected: 1 known not affected: 216 recommended: 671 | 2026-08-05T01:30:07+00:00 | Vulnerability · Source |
| CVE-2016-7155 | suse_vex | SUSE CVE CVE-2016-7155 | known not affected: 166 recommended: 1768 | 2026-08-05T01:30:03+00:00 | Vulnerability · Source |
| CVE-2016-7178 | suse_vex | SUSE CVE CVE-2016-7178 | known affected: 1 recommended: 586 | 2026-08-05T01:30:01+00:00 | Vulnerability · Source |
| CVE-2016-7933 | suse_vex | SUSE CVE CVE-2016-7933 | known affected: 320 recommended: 182 | 2026-08-05T01:29:58+00:00 | Vulnerability · Source |
| CVE-2016-8625 | suse_vex | SUSE CVE CVE-2016-8625 | known affected: 320 known not affected: 21 recommended: 365 | 2026-08-05T01:29:55+00:00 | Vulnerability · Source |
| CVE-2016-9298 | suse_vex | SUSE CVE CVE-2016-9298 | known not affected: 113 | 2026-08-05T01:29:52+00:00 | Vulnerability · Source |
| CVE-2016-9377 | suse_vex | SUSE CVE CVE-2016-9377 | known affected: 332 known not affected: 41 recommended: 459 | 2026-08-05T01:29:51+00:00 | Vulnerability · Source |
| CVE-2016-9379 | suse_vex | SUSE CVE CVE-2016-9379 | known affected: 334 known not affected: 6 recommended: 556 | 2026-08-05T01:29:49+00:00 | Vulnerability · Source |
| CVE-2016-9756 | suse_vex | SUSE CVE CVE-2016-9756 | known affected: 14 known not affected: 259 recommended: 314 | 2026-08-05T01:29:44+00:00 | Vulnerability · Source |
| CVE-2016-9801 | suse_vex | SUSE CVE CVE-2016-9801 | known affected: 20 known not affected: 13 recommended: 312 | 2026-08-05T01:29:43+00:00 | Vulnerability · Source |
| CVE-2016-10200 | suse_vex | SUSE CVE CVE-2016-10200 | known not affected: 364 recommended: 335 | 2026-08-05T01:29:40+00:00 | Vulnerability · Source |
| CVE-2016-10349 | suse_vex | SUSE CVE CVE-2016-10349 | known affected: 24 known not affected: 16 recommended: 25 | 2026-08-05T01:29:37+00:00 | Vulnerability · Source |
| CVE-2016-10507 | suse_vex | SUSE CVE CVE-2016-10507 | recommended: 21 | 2026-08-05T01:29:34+00:00 | Vulnerability · Source |
| CVE-2016-1000345 | suse_vex | SUSE CVE CVE-2016-1000345 | known not affected: 18 recommended: 134 | 2026-08-05T01:29:31+00:00 | Vulnerability · Source |
| CVE-2017-3533 | suse_vex | SUSE CVE CVE-2017-3533 | known affected: 1 known not affected: 109 recommended: 732 | 2026-08-05T01:29:28+00:00 | Vulnerability · Source |
| CVE-2017-3645 | suse_vex | SUSE CVE CVE-2017-3645 | known affected: 1 known not affected: 64 | 2026-08-05T01:29:25+00:00 | Vulnerability · Source |
| CVE-2017-5123 | suse_vex | SUSE CVE CVE-2017-5123 | known affected: 35 known not affected: 430 recommended: 6 | 2026-08-05T01:29:23+00:00 | Vulnerability · Source |
| CVE-2017-7099 | suse_vex | SUSE CVE CVE-2017-7099 | known not affected: 87 recommended: 927 | 2026-08-05T01:29:17+00:00 | Vulnerability · Source |
| CVE-2017-7102 | suse_vex | SUSE CVE CVE-2017-7102 | known not affected: 87 recommended: 927 | 2026-08-05T01:29:16+00:00 | Vulnerability · Source |
| CVE-2017-7645 | suse_vex | SUSE CVE CVE-2017-7645 | known affected: 12 known not affected: 274 recommended: 179 | 2026-08-05T01:29:12+00:00 | Vulnerability · Source |
| CVE-2017-8779 | suse_vex | SUSE CVE CVE-2017-8779 | known affected: 320 known not affected: 24 recommended: 249 | 2026-08-05T01:29:04+00:00 | Vulnerability · Source |
| CVE-2017-8797 | suse_vex | SUSE CVE CVE-2017-8797 | known not affected: 537 recommended: 22 | 2026-08-05T01:29:03+00:00 | Vulnerability · Source |
| CVE-2017-9108 | suse_vex | SUSE CVE CVE-2017-9108 | known affected: 18 recommended: 49 | 2026-08-05T01:29:01+00:00 | Vulnerability · Source |
| CVE-2017-9835 | suse_vex | SUSE CVE CVE-2017-9835 | known affected: 1 recommended: 85 | 2026-08-05T01:28:59+00:00 | Vulnerability · Source |
| CVE-2017-11140 | suse_vex | SUSE CVE CVE-2017-11140 | known affected: 3 known not affected: 85 recommended: 14 | 2026-08-05T01:28:57+00:00 | Vulnerability · Source |
| CVE-2017-11522 | suse_vex | SUSE CVE CVE-2017-11522 | known affected: 10 known not affected: 144 | 2026-08-05T01:28:55+00:00 | Vulnerability · Source |