VEX records
Browse vendor VEX statements available in this Vulnerability-Lookup instance and pivot to the related vulnerability.
291935 VEX records
API response| Vulnerability | Source | Title | Product status | Imported | Links |
|---|---|---|---|---|---|
| CVE-2017-1289 | suse_vex | SUSE CVE CVE-2017-1289 | known affected: 3 known not affected: 57 recommended: 372 | 2026-07-28T00:09:34+00:00 | Vulnerability · Source |
| CVE-2017-2580 | suse_vex | SUSE CVE CVE-2017-2580 | known affected: 13 recommended: 245 | 2026-07-28T00:09:32+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-3462 | suse_vex | SUSE CVE CVE-2017-3462 | known affected: 29 known not affected: 97 recommended: 28 | 2026-07-28T00:09:21+00:00 | Vulnerability · Source |
| CVE-2017-3464 | suse_vex | SUSE CVE CVE-2017-3464 | known affected: 29 known not affected: 97 recommended: 607 | 2026-07-28T00:09:19+00:00 | Vulnerability · Source |
| CVE-2017-3529 | suse_vex | SUSE CVE CVE-2017-3529 | known affected: 1 known not affected: 43 | 2026-07-28T00:09:18+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-5411 | suse_vex | SUSE CVE CVE-2017-5411 | known affected: 1 | 2026-07-28T00:09:08+00:00 | Vulnerability · Source |
| CVE-2017-5427 | suse_vex | SUSE CVE CVE-2017-5427 | known affected: 1 recommended: 249 | 2026-07-28T00:09:05+00:00 | Vulnerability · Source |
| CVE-2017-5439 | suse_vex | SUSE CVE CVE-2017-5439 | known not affected: 42 recommended: 719 | 2026-07-28T00:09:04+00:00 | Vulnerability · Source |
| CVE-2017-5482 | suse_vex | SUSE CVE CVE-2017-5482 | known affected: 300 recommended: 175 | 2026-07-28T00:08:59+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-5849 | suse_vex | SUSE CVE CVE-2017-5849 | known affected: 50 known not affected: 24 recommended: 73 | 2026-07-28T00:08:54+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-6346 | suse_vex | SUSE CVE CVE-2017-6346 | known not affected: 346 recommended: 184 | 2026-07-28T00:08:47+00:00 | Vulnerability · Source |
| CVE-2017-6347 | suse_vex | SUSE CVE CVE-2017-6347 | known not affected: 737 recommended: 166 | 2026-07-28T00:08:46+00:00 | Vulnerability · Source |
| CVE-2017-6386 | suse_vex | SUSE CVE CVE-2017-6386 | recommended: 130 | 2026-07-28T00:08:44+00:00 | Vulnerability · Source |
| CVE-2017-6418 | suse_vex | SUSE CVE CVE-2017-6418 | known affected: 1 known not affected: 78 recommended: 277 | 2026-07-28T00:08:43+00:00 | Vulnerability · Source |
| CVE-2017-6435 | suse_vex | SUSE CVE CVE-2017-6435 | recommended: 335 | 2026-07-28T00:08:41+00:00 | Vulnerability · Source |
| CVE-2017-6458 | suse_vex | SUSE CVE CVE-2017-6458 | known affected: 24 recommended: 90 | 2026-07-28T00:08:40+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-7056 | suse_vex | SUSE CVE CVE-2017-7056 | known affected: 6 known not affected: 321 recommended: 924 | 2026-07-28T00:08:30+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-7507 | suse_vex | SUSE CVE CVE-2017-7507 | known affected: 4 known not affected: 25 recommended: 35 | 2026-07-28T00:08:22+00:00 | Vulnerability · Source |
| CVE-2017-7541 | suse_vex | SUSE CVE CVE-2017-7541 | known not affected: 313 recommended: 480 | 2026-07-28T00:08:18+00:00 | Vulnerability · Source |
| CVE-2017-7555 | suse_vex | SUSE CVE CVE-2017-7555 | known affected: 311 known not affected: 75 recommended: 421 | 2026-07-28T00:08:16+00:00 | Vulnerability · Source |
| CVE-2017-7558 | suse_vex | SUSE CVE CVE-2017-7558 | known not affected: 14 recommended: 12 | 2026-07-28T00:08:15+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-7798 | suse_vex | SUSE CVE CVE-2017-7798 | known affected: 1 known not affected: 34 recommended: 406 | 2026-07-28T00:08:04+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-7824 | suse_vex | SUSE CVE CVE-2017-7824 | known not affected: 34 recommended: 610 | 2026-07-28T00:08:01+00:00 | Vulnerability · Source |
| CVE-2017-7868 | suse_vex | SUSE CVE CVE-2017-7868 | recommended: 124 | 2026-07-28T00:07:59+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-8872 | suse_vex | SUSE CVE CVE-2017-8872 | known affected: 53 known not affected: 131 recommended: 102 | 2026-07-28T00:07:53+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-9047 | suse_vex | SUSE CVE CVE-2017-9047 | known affected: 309 known not affected: 86 recommended: 550 | 2026-07-28T00:07:50+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 |