VEX records
Browse vendor VEX statements available in this Vulnerability-Lookup instance and pivot to the related vulnerability.
292142 VEX records
API response| Vulnerability | Source | Title | Product status | Imported | Links |
|---|---|---|---|---|---|
| CVE-2015-4695 | suse_vex | SUSE CVE CVE-2015-4695 | known not affected: 59 recommended: 222 | 2026-07-19T18:41:12+00:00 | Vulnerability · Source |
| CVE-2015-5145 | suse_vex | SUSE CVE CVE-2015-5145 | known not affected: 5 recommended: 20 | 2026-07-19T18:41:01+00:00 | Vulnerability · Source |
| CVE-2015-6241 | suse_vex | SUSE CVE CVE-2015-6241 | known affected: 1 recommended: 470 | 2026-07-19T18:40:52+00:00 | Vulnerability · Source |
| CVE-2015-6245 | suse_vex | SUSE CVE CVE-2015-6245 | known affected: 1 recommended: 473 | 2026-07-19T18:40:49+00:00 | Vulnerability · Source |
| CVE-2015-7179 | suse_vex | SUSE CVE CVE-2015-7179 | known affected: 1 recommended: 332 | 2026-07-19T18:40:45+00:00 | Vulnerability · Source |
| CVE-2015-7204 | suse_vex | SUSE CVE CVE-2015-7204 | known affected: 2 recommended: 255 | 2026-07-19T18:40:36+00:00 | Vulnerability · Source |
| CVE-2015-7830 | suse_vex | SUSE CVE CVE-2015-7830 | known affected: 69 recommended: 534 | 2026-07-19T18:40:22+00:00 | Vulnerability · Source |
| CVE-2015-8804 | suse_vex | SUSE CVE CVE-2015-8804 | known affected: 320 recommended: 485 | 2026-07-19T18:40:06+00:00 | Vulnerability · Source |
| CVE-2016-1950 | suse_vex | SUSE CVE CVE-2016-1950 | known affected: 353 known not affected: 183 recommended: 1733 | 2026-07-19T18:39:41+00:00 | Vulnerability · Source |
| CVE-2016-2464 | suse_vex | SUSE CVE CVE-2016-2464 | known not affected: 42 recommended: 146 | 2026-07-19T18:39:24+00:00 | Vulnerability · Source |
| CVE-2016-3615 | suse_vex | SUSE CVE CVE-2016-3615 | known affected: 1 known not affected: 37 recommended: 633 | 2026-07-19T18:38:54+00:00 | Vulnerability · Source |
| CVE-2016-3630 | suse_vex | SUSE CVE CVE-2016-3630 | known not affected: 24 recommended: 61 | 2026-07-19T18:38:50+00:00 | Vulnerability · Source |
| CVE-2016-3959 | suse_vex | SUSE CVE CVE-2016-3959 | known not affected: 147 recommended: 45 | 2026-07-19T18:38:42+00:00 | Vulnerability · Source |
| CVE-2016-4476 | suse_vex | SUSE CVE CVE-2016-4476 | known affected: 3 known not affected: 41 recommended: 75 | 2026-07-19T18:38:33+00:00 | Vulnerability · Source |
| CVE-2016-4554 | suse_vex | SUSE CVE CVE-2016-4554 | known not affected: 23 recommended: 48 | 2026-07-19T18:38:30+00:00 | Vulnerability · Source |
| CVE-2016-5253 | suse_vex | SUSE CVE CVE-2016-5253 | known affected: 1 recommended: 250 | 2026-07-19T18:38:18+00:00 | Vulnerability · Source |
| CVE-2016-5256 | suse_vex | SUSE CVE CVE-2016-5256 | known affected: 3 recommended: 250 | 2026-07-19T18:38:17+00:00 | Vulnerability · Source |
| CVE-2016-5267 | suse_vex | SUSE CVE CVE-2016-5267 | known affected: 1 recommended: 250 | 2026-07-19T18:38:16+00:00 | Vulnerability · Source |
| CVE-2016-5337 | suse_vex | SUSE CVE CVE-2016-5337 | known affected: 396 known not affected: 138 recommended: 1783 | 2026-07-19T18:38:06+00:00 | Vulnerability · Source |
| CVE-2016-5410 | suse_vex | SUSE CVE CVE-2016-5410 | known affected: 394 recommended: 390 | 2026-07-19T18:38:01+00:00 | Vulnerability · Source |
| CVE-2016-5759 | suse_vex | SUSE CVE CVE-2016-5759 | known affected: 320 known not affected: 16 recommended: 157 | 2026-07-19T18:37:54+00:00 | Vulnerability · Source |
| CVE-2016-5766 | suse_vex | SUSE CVE CVE-2016-5766 | known affected: 944 known not affected: 970 recommended: 1554 | 2026-07-19T18:37:52+00:00 | Vulnerability · Source |
| CVE-2016-6313 | suse_vex | SUSE CVE CVE-2016-6313 | known affected: 321 known not affected: 10 recommended: 466 | 2026-07-19T18:37:41+00:00 | Vulnerability · Source |
| CVE-2016-6581 | suse_vex | SUSE CVE CVE-2016-6581 | known not affected: 16 recommended: 32 | 2026-07-19T18:37:35+00:00 | Vulnerability · Source |
| CVE-2016-7931 | suse_vex | SUSE CVE CVE-2016-7931 | known affected: 320 recommended: 180 | 2026-07-19T18:37:10+00:00 | Vulnerability · Source |
| CVE-2016-8667 | suse_vex | SUSE CVE CVE-2016-8667 | known affected: 334 known not affected: 142 recommended: 2300 | 2026-07-19T18:36:50+00:00 | Vulnerability · Source |
| CVE-2016-9062 | suse_vex | SUSE CVE CVE-2016-9062 | known affected: 1 known not affected: 34 recommended: 250 | 2026-07-19T18:36:39+00:00 | Vulnerability · Source |
| CVE-2016-9080 | suse_vex | SUSE CVE CVE-2016-9080 | known affected: 1 recommended: 250 | 2026-07-19T18:36:32+00:00 | Vulnerability · Source |
| CVE-2016-9085 | suse_vex | SUSE CVE CVE-2016-9085 | known not affected: 55 recommended: 226 | 2026-07-19T18:36:30+00:00 | Vulnerability · Source |
| CVE-2016-9102 | suse_vex | SUSE CVE CVE-2016-9102 | known affected: 395 known not affected: 183 recommended: 1769 | 2026-07-19T18:36:29+00:00 | Vulnerability · Source |
| CVE-2016-9381 | suse_vex | SUSE CVE CVE-2016-9381 | known affected: 328 known not affected: 170 recommended: 2187 | 2026-07-19T18:36:24+00:00 | Vulnerability · Source |
| CVE-2016-9584 | suse_vex | SUSE CVE CVE-2016-9584 | recommended: 242 | 2026-07-19T18:36:16+00:00 | Vulnerability · Source |
| CVE-2016-9622 | suse_vex | SUSE CVE CVE-2016-9622 | known affected: 1 recommended: 83 | 2026-07-19T18:36:15+00:00 | Vulnerability · Source |
| CVE-2016-9846 | suse_vex | SUSE CVE CVE-2016-9846 | known not affected: 154 recommended: 1656 | 2026-07-19T18:36:09+00:00 | Vulnerability · Source |
| CVE-2016-9913 | suse_vex | SUSE CVE CVE-2016-9913 | known not affected: 209 recommended: 1656 | 2026-07-19T18:35:59+00:00 | Vulnerability · Source |
| CVE-2016-10075 | suse_vex | SUSE CVE CVE-2016-10075 | recommended: 18 | 2026-07-19T18:35:48+00:00 | Vulnerability · Source |
| CVE-2016-10219 | suse_vex | SUSE CVE CVE-2016-10219 | known affected: 1 known not affected: 5 recommended: 260 | 2026-07-19T18:35:41+00:00 | Vulnerability · Source |
| CVE-2016-1000343 | suse_vex | SUSE CVE CVE-2016-1000343 | known not affected: 18 recommended: 134 | 2026-07-19T18:35:33+00:00 | Vulnerability · Source |
| CVE-2017-2885 | suse_vex | SUSE CVE CVE-2017-2885 | known not affected: 71 recommended: 450 | 2026-07-19T18:35:18+00:00 | Vulnerability · Source |
| CVE-2017-5338 | suse_vex | SUSE CVE CVE-2017-5338 | recommended: 153 | 2026-07-19T18:35:08+00:00 | Vulnerability · Source |
| CVE-2017-5389 | suse_vex | SUSE CVE CVE-2017-5389 | known affected: 1 known not affected: 34 recommended: 249 | 2026-07-19T18:34:59+00:00 | Vulnerability · Source |
| CVE-2017-5458 | suse_vex | SUSE CVE CVE-2017-5458 | known not affected: 42 recommended: 12 | 2026-07-19T18:34:46+00:00 | Vulnerability · Source |
| CVE-2017-5839 | suse_vex | SUSE CVE CVE-2017-5839 | known affected: 217 recommended: 923 | 2026-07-19T18:34:33+00:00 | Vulnerability · Source |
| CVE-2017-5843 | suse_vex | SUSE CVE CVE-2017-5843 | known affected: 13 known not affected: 41 recommended: 588 | 2026-07-19T18:34:30+00:00 | Vulnerability · Source |
| CVE-2017-6437 | suse_vex | SUSE CVE CVE-2017-6437 | recommended: 335 | 2026-07-19T18:34:13+00:00 | Vulnerability · Source |
| CVE-2017-6519 | suse_vex | SUSE CVE CVE-2017-6519 | known not affected: 300 recommended: 582 | 2026-07-19T18:34:06+00:00 | Vulnerability · Source |
| CVE-2017-7034 | suse_vex | SUSE CVE CVE-2017-7034 | known affected: 6 known not affected: 321 recommended: 912 | 2026-07-19T18:34:00+00:00 | Vulnerability · Source |
| CVE-2017-7550 | suse_vex | SUSE CVE CVE-2017-7550 | known not affected: 4 recommended: 30 | 2026-07-19T18:33:38+00:00 | Vulnerability · Source |
| CVE-2017-7770 | suse_vex | SUSE CVE CVE-2017-7770 | known affected: 2 known not affected: 42 | 2026-07-19T18:33:27+00:00 | Vulnerability · Source |
| CVE-2017-7777 | suse_vex | SUSE CVE CVE-2017-7777 | known affected: 2 known not affected: 42 recommended: 327 | 2026-07-19T18:33:26+00:00 | Vulnerability · Source |