VEX records
Browse vendor VEX statements available in this Vulnerability-Lookup instance and pivot to the related vulnerability.
294119 VEX records
API response| Vulnerability | Source | Title | Product status | Imported | Links |
|---|---|---|---|---|---|
| CVE-2016-5239 | suse_vex | SUSE CVE CVE-2016-5239 | known not affected: 109 recommended: 6 | 2026-07-28T00:11:25+00:00 | Vulnerability · Source |
| CVE-2016-5288 | suse_vex | SUSE CVE CVE-2016-5288 | known affected: 1 known not affected: 48 recommended: 250 | 2026-07-28T00:11:19+00:00 | Vulnerability · Source |
| CVE-2016-5319 | suse_vex | SUSE CVE CVE-2016-5319 | recommended: 58 | 2026-07-28T00:11:17+00:00 | Vulnerability · Source |
| CVE-2016-5322 | suse_vex | SUSE CVE CVE-2016-5322 | known not affected: 43 | 2026-07-28T00:11:16+00:00 | Vulnerability · Source |
| CVE-2016-5359 | suse_vex | SUSE CVE CVE-2016-5359 | known not affected: 103 recommended: 77 | 2026-07-28T00:11:13+00:00 | Vulnerability · Source |
| CVE-2016-5689 | suse_vex | SUSE CVE CVE-2016-5689 | known affected: 76 recommended: 194 | 2026-07-28T00:11:07+00:00 | Vulnerability · Source |
| CVE-2016-6136 | suse_vex | SUSE CVE CVE-2016-6136 | known affected: 3 known not affected: 436 recommended: 12 | 2026-07-28T00:11:04+00:00 | Vulnerability · Source |
| CVE-2016-6349 | suse_vex | SUSE CVE CVE-2016-6349 | known not affected: 72 | 2026-07-28T00:10:59+00:00 | Vulnerability · Source |
| CVE-2016-7053 | suse_vex | SUSE CVE CVE-2016-7053 | known not affected: 46 | 2026-07-28T00:10:56+00:00 | Vulnerability · Source |
| CVE-2016-7513 | suse_vex | SUSE CVE CVE-2016-7513 | known affected: 75 known not affected: 49 recommended: 126 | 2026-07-28T00:10:48+00:00 | Vulnerability · Source |
| CVE-2016-7524 | suse_vex | SUSE CVE CVE-2016-7524 | known affected: 76 recommended: 176 | 2026-07-28T00:10:47+00:00 | Vulnerability · Source |
| CVE-2016-7578 | suse_vex | SUSE CVE CVE-2016-7578 | known affected: 57 known not affected: 18 | 2026-07-28T00:10:43+00:00 | Vulnerability · Source |
| CVE-2016-8577 | suse_vex | SUSE CVE CVE-2016-8577 | known affected: 408 known not affected: 121 recommended: 1769 | 2026-07-28T00:10:32+00:00 | Vulnerability · Source |
| CVE-2016-8636 | suse_vex | SUSE CVE CVE-2016-8636 | known affected: 6 known not affected: 175 recommended: 88 | 2026-07-28T00:10:28+00:00 | Vulnerability · Source |
| CVE-2016-8883 | suse_vex | SUSE CVE CVE-2016-8883 | known affected: 1 recommended: 194 | 2026-07-28T00:10:22+00:00 | Vulnerability · Source |
| CVE-2016-9115 | suse_vex | SUSE CVE CVE-2016-9115 | recommended: 17 | 2026-07-28T00:10:17+00:00 | Vulnerability · Source |
| CVE-2016-9117 | suse_vex | SUSE CVE CVE-2016-9117 | recommended: 17 | 2026-07-28T00:10:16+00:00 | Vulnerability · Source |
| CVE-2016-9532 | suse_vex | SUSE CVE CVE-2016-9532 | known not affected: 133 | 2026-07-28T00:10:06+00:00 | Vulnerability · Source |
| CVE-2016-9556 | suse_vex | SUSE CVE CVE-2016-9556 | known affected: 1 recommended: 210 | 2026-07-28T00:10:03+00:00 | Vulnerability · Source |
| CVE-2016-9559 | suse_vex | SUSE CVE CVE-2016-9559 | known affected: 1 recommended: 210 | 2026-07-28T00:10:00+00:00 | Vulnerability · Source |
| CVE-2016-9942 | suse_vex | SUSE CVE CVE-2016-9942 | known affected: 33 known not affected: 3 recommended: 59 | 2026-07-28T00:09:47+00:00 | Vulnerability · Source |
| CVE-2016-10060 | suse_vex | SUSE CVE CVE-2016-10060 | known affected: 1 known not affected: 14 recommended: 196 | 2026-07-28T00:09:46+00:00 | Vulnerability · Source |
| CVE-2016-10146 | suse_vex | SUSE CVE CVE-2016-10146 | known affected: 1 recommended: 210 | 2026-07-28T00:09:44+00:00 | Vulnerability · Source |
| CVE-2016-10207 | suse_vex | SUSE CVE CVE-2016-10207 | recommended: 29 | 2026-07-28T00:09:42+00:00 | Vulnerability · Source |
| CVE-2016-11070 | suse_vex | SUSE CVE CVE-2016-11070 | recommended: 1 | 2026-07-28T00:09:36+00:00 | Vulnerability · Source |
| CVE-2017-3272 | suse_vex | SUSE CVE CVE-2017-3272 | known affected: 98 known not affected: 139 recommended: 540 | 2026-07-28T00:09:24+00:00 | Vulnerability · Source |
| CVE-2017-3599 | suse_vex | SUSE CVE CVE-2017-3599 | known affected: 29 known not affected: 45 | 2026-07-28T00:09:16+00:00 | Vulnerability · Source |
| CVE-2017-3642 | suse_vex | SUSE CVE CVE-2017-3642 | known affected: 29 known not affected: 43 | 2026-07-28T00:09:15+00:00 | Vulnerability · Source |
| CVE-2017-3643 | suse_vex | SUSE CVE CVE-2017-3643 | known affected: 1 known not affected: 43 | 2026-07-28T00:09:13+00:00 | Vulnerability · Source |
| CVE-2017-3646 | suse_vex | SUSE CVE CVE-2017-3646 | known affected: 1 known not affected: 43 | 2026-07-28T00:09:12+00:00 | Vulnerability · Source |
| CVE-2017-5357 | suse_vex | SUSE CVE CVE-2017-5357 | known affected: 9 recommended: 9 | 2026-07-28T00:09:10+00:00 | Vulnerability · Source |
| CVE-2017-5547 | suse_vex | SUSE CVE CVE-2017-5547 | known not affected: 13 | 2026-07-28T00:08:57+00:00 | Vulnerability · Source |
| CVE-2017-5956 | suse_vex | SUSE CVE CVE-2017-5956 | recommended: 26 | 2026-07-28T00:08:52+00:00 | Vulnerability · Source |
| CVE-2017-5972 | suse_vex | SUSE CVE CVE-2017-5972 | known not affected: 266 | 2026-07-28T00:08:51+00:00 | Vulnerability · Source |
| CVE-2017-6473 | suse_vex | SUSE CVE CVE-2017-6473 | known affected: 61 recommended: 444 | 2026-07-28T00:08:39+00:00 | Vulnerability · Source |
| CVE-2017-6502 | suse_vex | SUSE CVE CVE-2017-6502 | known not affected: 47 recommended: 128 | 2026-07-28T00:08:37+00:00 | Vulnerability · Source |
| CVE-2017-6837 | suse_vex | SUSE CVE CVE-2017-6837 | known affected: 34 recommended: 190 | 2026-07-28T00:08:35+00:00 | Vulnerability · Source |
| CVE-2017-7041 | suse_vex | SUSE CVE CVE-2017-7041 | known affected: 6 known not affected: 321 recommended: 912 | 2026-07-28T00:08:32+00:00 | Vulnerability · Source |
| CVE-2017-7089 | suse_vex | SUSE CVE CVE-2017-7089 | known not affected: 69 recommended: 906 | 2026-07-28T00:08:29+00:00 | Vulnerability · Source |
| CVE-2017-7608 | suse_vex | SUSE CVE CVE-2017-7608 | known affected: 494 known not affected: 1 recommended: 806 | 2026-07-28T00:08:12+00:00 | Vulnerability · Source |
| CVE-2017-7763 | suse_vex | SUSE CVE CVE-2017-7763 | known affected: 2 known not affected: 42 recommended: 216 | 2026-07-28T00:08:10+00:00 | Vulnerability · Source |
| CVE-2017-7789 | suse_vex | SUSE CVE CVE-2017-7789 | known not affected: 60 recommended: 74 | 2026-07-28T00:08:06+00:00 | Vulnerability · Source |
| CVE-2017-7812 | suse_vex | SUSE CVE CVE-2017-7812 | known not affected: 34 recommended: 12 | 2026-07-28T00:08:03+00:00 | Vulnerability · Source |
| CVE-2017-8347 | suse_vex | SUSE CVE CVE-2017-8347 | known not affected: 48 recommended: 128 | 2026-07-28T00:07:58+00:00 | Vulnerability · Source |
| CVE-2017-8355 | suse_vex | SUSE CVE CVE-2017-8355 | recommended: 178 | 2026-07-28T00:07:57+00:00 | Vulnerability · Source |
| CVE-2017-8356 | suse_vex | SUSE CVE CVE-2017-8356 | known not affected: 48 recommended: 128 | 2026-07-28T00:07:55+00:00 | Vulnerability · Source |
| CVE-2017-8905 | suse_vex | SUSE CVE CVE-2017-8905 | known not affected: 13 recommended: 83 | 2026-07-28T00:07:52+00:00 | Vulnerability · Source |
| CVE-2017-9060 | suse_vex | SUSE CVE CVE-2017-9060 | known not affected: 57 | 2026-07-28T00:07:49+00:00 | Vulnerability · Source |
| CVE-2017-9144 | suse_vex | SUSE CVE CVE-2017-9144 | recommended: 178 | 2026-07-28T00:07:47+00:00 | Vulnerability · Source |
| CVE-2017-9262 | suse_vex | SUSE CVE CVE-2017-9262 | known affected: 75 recommended: 180 | 2026-07-28T00:07:44+00:00 | Vulnerability · Source |