VEX records
Browse vendor VEX statements available in this Vulnerability-Lookup instance and pivot to the related vulnerability.
290399 VEX records
API response| Vulnerability | Source | Title | Product status | Imported | Links |
|---|---|---|---|---|---|
| CVE-2015-3814 | suse_vex | SUSE CVE CVE-2015-3814 | known affected: 73 recommended: 540 | 2026-08-07T00:31:12+00:00 | Vulnerability · Source |
| CVE-2015-4803 | suse_vex | SUSE CVE CVE-2015-4803 | known affected: 95 known not affected: 289 recommended: 771 | 2026-08-07T00:31:10+00:00 | Vulnerability · Source |
| CVE-2015-4860 | suse_vex | SUSE CVE CVE-2015-4860 | known affected: 489 known not affected: 289 recommended: 771 | 2026-08-07T00:31:08+00:00 | Vulnerability · Source |
| CVE-2015-5203 | suse_vex | SUSE CVE CVE-2015-5203 | known affected: 1 recommended: 204 | 2026-08-07T00:31:05+00:00 | Vulnerability · Source |
| CVE-2015-6749 | suse_vex | SUSE CVE CVE-2015-6749 | known affected: 30 recommended: 162 | 2026-08-07T00:31:03+00:00 | Vulnerability · Source |
| CVE-2015-8140 | suse_vex | SUSE CVE CVE-2015-8140 | known affected: 30 recommended: 80 | 2026-08-07T00:31:00+00:00 | Vulnerability · Source |
| CVE-2015-8842 | suse_vex | SUSE CVE CVE-2015-8842 | recommended: 124 | 2026-08-07T00:30:57+00:00 | Vulnerability · Source |
| CVE-2015-8983 | suse_vex | SUSE CVE CVE-2015-8983 | known not affected: 776 recommended: 44 | 2026-08-07T00:30:55+00:00 | Vulnerability · Source |
| CVE-2015-9104 | suse_vex | SUSE CVE CVE-2015-9104 | known affected: 143 known not affected: 84 | 2026-08-07T00:30:54+00:00 | Vulnerability · Source |
| CVE-2015-1142857 | suse_vex | SUSE CVE CVE-2015-1142857 | known affected: 12 known not affected: 34 recommended: 204 | 2026-08-07T00:30:52+00:00 | Vulnerability · Source |
| CVE-2016-1924 | suse_vex | SUSE CVE CVE-2016-1924 | known affected: 30 known not affected: 107 recommended: 20 | 2026-08-07T00:30:48+00:00 | Vulnerability · Source |
| CVE-2016-1945 | suse_vex | SUSE CVE CVE-2016-1945 | known affected: 21 recommended: 246 | 2026-08-07T00:30:46+00:00 | Vulnerability · Source |
| CVE-2016-1976 | suse_vex | SUSE CVE CVE-2016-1976 | known affected: 38 known not affected: 183 recommended: 250 | 2026-08-07T00:30:44+00:00 | Vulnerability · Source |
| CVE-2016-2838 | suse_vex | SUSE CVE CVE-2016-2838 | known affected: 5 recommended: 438 | 2026-08-07T00:30:37+00:00 | Vulnerability · Source |
| CVE-2016-3186 | suse_vex | SUSE CVE CVE-2016-3186 | known affected: 463 recommended: 299 | 2026-08-07T00:30:35+00:00 | Vulnerability · Source |
| CVE-2016-3633 | suse_vex | SUSE CVE CVE-2016-3633 | known not affected: 53 | 2026-08-07T00:30:33+00:00 | Vulnerability · Source |
| CVE-2016-4913 | suse_vex | SUSE CVE CVE-2016-4913 | known affected: 2 known not affected: 369 recommended: 189 | 2026-08-07T00:30:30+00:00 | Vulnerability · Source |
| CVE-2016-5273 | suse_vex | SUSE CVE CVE-2016-5273 | known affected: 5 recommended: 250 | 2026-08-07T00:30:28+00:00 | Vulnerability · Source |
| CVE-2016-5300 | suse_vex | SUSE CVE CVE-2016-5300 | known affected: 320 known not affected: 24 recommended: 445 | 2026-08-07T00:30:26+00:00 | Vulnerability · Source |
| CVE-2016-5823 | suse_vex | SUSE CVE CVE-2016-5823 | known affected: 1 known not affected: 104 recommended: 14 | 2026-08-07T00:30:23+00:00 | Vulnerability · Source |
| CVE-2016-6132 | suse_vex | SUSE CVE CVE-2016-6132 | known affected: 394 known not affected: 1227 recommended: 234 | 2026-08-07T00:30:22+00:00 | Vulnerability · Source |
| CVE-2016-7042 | suse_vex | SUSE CVE CVE-2016-7042 | known affected: 12 known not affected: 239 recommended: 529 | 2026-08-07T00:30:18+00:00 | Vulnerability · Source |
| CVE-2016-7525 | suse_vex | SUSE CVE CVE-2016-7525 | known affected: 95 known not affected: 14 recommended: 168 | 2026-08-07T00:30:15+00:00 | Vulnerability · Source |
| CVE-2016-7528 | suse_vex | SUSE CVE CVE-2016-7528 | known affected: 95 recommended: 182 | 2026-08-07T00:30:13+00:00 | Vulnerability · Source |
| CVE-2016-7640 | suse_vex | SUSE CVE CVE-2016-7640 | known not affected: 87 | 2026-08-07T00:30:12+00:00 | Vulnerability · Source |
| CVE-2016-7927 | suse_vex | SUSE CVE CVE-2016-7927 | known affected: 320 recommended: 186 | 2026-08-07T00:30:10+00:00 | Vulnerability · Source |
| CVE-2016-7950 | suse_vex | SUSE CVE CVE-2016-7950 | known affected: 36 recommended: 270 | 2026-08-07T00:30:08+00:00 | Vulnerability · Source |
| CVE-2016-8740 | suse_vex | SUSE CVE CVE-2016-8740 | known affected: 394 known not affected: 57 recommended: 386 | 2026-08-07T00:30:06+00:00 | Vulnerability · Source |
| CVE-2016-9101 | suse_vex | SUSE CVE CVE-2016-9101 | known affected: 421 known not affected: 136 recommended: 1941 | 2026-08-07T00:30:03+00:00 | Vulnerability · Source |
| CVE-2016-9804 | suse_vex | SUSE CVE CVE-2016-9804 | known not affected: 46 recommended: 296 | 2026-08-07T00:30:01+00:00 | Vulnerability · Source |
| CVE-2016-10217 | suse_vex | SUSE CVE CVE-2016-10217 | known not affected: 32 recommended: 200 | 2026-08-07T00:29:57+00:00 | Vulnerability · Source |
| CVE-2017-2636 | suse_vex | SUSE CVE CVE-2017-2636 | known not affected: 336 recommended: 551 | 2026-08-07T00:29:54+00:00 | Vulnerability · Source |
| CVE-2017-5337 | suse_vex | SUSE CVE CVE-2017-5337 | known affected: 8 known not affected: 4 recommended: 176 | 2026-08-07T00:29:51+00:00 | Vulnerability · Source |
| CVE-2017-5841 | suse_vex | SUSE CVE CVE-2017-5841 | known not affected: 6 recommended: 448 | 2026-08-07T00:29:48+00:00 | Vulnerability · Source |
| CVE-2017-7156 | suse_vex | SUSE CVE CVE-2017-7156 | known not affected: 96 recommended: 939 | 2026-08-07T00:29:45+00:00 | Vulnerability · Source |
| CVE-2017-7479 | suse_vex | SUSE CVE CVE-2017-7479 | known affected: 30 recommended: 41 | 2026-08-07T00:29:42+00:00 | Vulnerability · Source |
| CVE-2017-7601 | suse_vex | SUSE CVE CVE-2017-7601 | known affected: 439 known not affected: 80 recommended: 286 | 2026-08-07T00:29:40+00:00 | Vulnerability · Source |
| CVE-2017-7799 | suse_vex | SUSE CVE CVE-2017-7799 | known affected: 1 known not affected: 42 recommended: 12 | 2026-08-07T00:29:38+00:00 | Vulnerability · Source |
| CVE-2017-7816 | suse_vex | SUSE CVE CVE-2017-7816 | known not affected: 42 recommended: 12 | 2026-08-07T00:29:37+00:00 | Vulnerability · Source |
| CVE-2017-9404 | suse_vex | SUSE CVE CVE-2017-9404 | known affected: 438 known not affected: 99 recommended: 264 | 2026-08-07T00:29:33+00:00 | Vulnerability · Source |
| CVE-2017-9612 | suse_vex | SUSE CVE CVE-2017-9612 | known affected: 1 recommended: 85 | 2026-08-07T00:29:31+00:00 | Vulnerability · Source |
| CVE-2017-9789 | suse_vex | SUSE CVE CVE-2017-9789 | known not affected: 63 recommended: 87 | 2026-08-07T00:29:29+00:00 | Vulnerability · Source |
| CVE-2017-11462 | suse_vex | SUSE CVE CVE-2017-11462 | known affected: 320 known not affected: 33 recommended: 690 | 2026-08-07T00:29:25+00:00 | Vulnerability · Source |
| CVE-2017-12424 | suse_vex | SUSE CVE CVE-2017-12424 | recommended: 15 | 2026-08-07T00:29:22+00:00 | Vulnerability · Source |
| CVE-2017-13079 | suse_vex | SUSE CVE CVE-2017-13079 | known affected: 6 known not affected: 354 recommended: 121 | 2026-08-07T00:29:19+00:00 | Vulnerability · Source |
| CVE-2017-13086 | suse_vex | SUSE CVE CVE-2017-13086 | known affected: 6 known not affected: 354 recommended: 95 | 2026-08-07T00:29:14+00:00 | Vulnerability · Source |
| CVE-2017-13729 | suse_vex | SUSE CVE CVE-2017-13729 | known affected: 157 recommended: 201 | 2026-08-07T00:29:10+00:00 | Vulnerability · Source |
| CVE-2017-13752 | suse_vex | SUSE CVE CVE-2017-13752 | known affected: 6 known not affected: 56 | 2026-08-07T00:29:08+00:00 | Vulnerability · Source |
| CVE-2017-14528 | suse_vex | SUSE CVE CVE-2017-14528 | known affected: 36 known not affected: 271 | 2026-08-07T00:29:06+00:00 | Vulnerability · Source |
| CVE-2017-16852 | suse_vex | SUSE CVE CVE-2017-16852 | known not affected: 74 recommended: 217 | 2026-08-07T00:29:02+00:00 | Vulnerability · Source |