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-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 |
| CVE-2017-9148 | suse_vex | SUSE CVE CVE-2017-9148 | known not affected: 155 recommended: 607 | 2026-07-28T00:07:46+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 |
| CVE-2017-9375 | suse_vex | SUSE CVE CVE-2017-9375 | known affected: 13 recommended: 108 | 2026-07-28T00:07:40+00:00 | Vulnerability · Source |
| CVE-2017-9749 | suse_vex | SUSE CVE CVE-2017-9749 | known affected: 8 known not affected: 41 | 2026-07-28T00:07:36+00:00 | Vulnerability · Source |
| CVE-2017-10078 | suse_vex | SUSE CVE CVE-2017-10078 | known not affected: 57 recommended: 488 | 2026-07-28T00:07:35+00:00 | Vulnerability · Source |
| CVE-2017-10176 | suse_vex | SUSE CVE CVE-2017-10176 | recommended: 311 | 2026-07-28T00:07:33+00:00 | Vulnerability · Source |
| CVE-2017-10295 | suse_vex | SUSE CVE CVE-2017-10295 | known affected: 80 known not affected: 209 recommended: 713 | 2026-07-28T00:07:31+00:00 | Vulnerability · Source |
| CVE-2017-10348 | suse_vex | SUSE CVE CVE-2017-10348 | known affected: 64 known not affected: 245 recommended: 713 | 2026-07-28T00:07:30+00:00 | Vulnerability · Source |
| CVE-2017-10800 | suse_vex | SUSE CVE CVE-2017-10800 | recommended: 188 | 2026-07-28T00:07:28+00:00 | Vulnerability · Source |
| CVE-2017-10810 | suse_vex | SUSE CVE CVE-2017-10810 | known not affected: 277 recommended: 102 | 2026-07-28T00:07:26+00:00 | Vulnerability · Source |
| CVE-2017-10918 | suse_vex | SUSE CVE CVE-2017-10918 | known affected: 7 known not affected: 6 recommended: 43 | 2026-07-28T00:07:25+00:00 | Vulnerability · Source |
| CVE-2017-10923 | suse_vex | SUSE CVE CVE-2017-10923 | known not affected: 46 | 2026-07-28T00:07:23+00:00 | Vulnerability · Source |
| CVE-2017-11449 | suse_vex | SUSE CVE CVE-2017-11449 | known affected: 75 recommended: 180 | 2026-07-28T00:07:20+00:00 | Vulnerability · Source |
| CVE-2017-11465 | suse_vex | SUSE CVE CVE-2017-11465 | known not affected: 48 | 2026-07-28T00:07:18+00:00 | Vulnerability · Source |
| CVE-2017-11544 | suse_vex | SUSE CVE CVE-2017-11544 | known affected: 13 known not affected: 22 | 2026-07-28T00:07:15+00:00 | Vulnerability · Source |
| CVE-2017-11671 | suse_vex | SUSE CVE CVE-2017-11671 | known not affected: 57 recommended: 600 | 2026-07-28T00:07:14+00:00 | Vulnerability · Source |
| CVE-2017-12136 | suse_vex | SUSE CVE CVE-2017-12136 | known affected: 325 known not affected: 41 recommended: 418 | 2026-07-28T00:07:12+00:00 | Vulnerability · Source |
| CVE-2017-12143 | suse_vex | SUSE CVE CVE-2017-12143 | known affected: 2 known not affected: 82 | 2026-07-28T00:07:10+00:00 | Vulnerability · Source |
| CVE-2017-12151 | suse_vex | SUSE CVE CVE-2017-12151 | known affected: 708 known not affected: 272 recommended: 3640 | 2026-07-28T00:07:08+00:00 | Vulnerability · Source |
| CVE-2017-12153 | suse_vex | SUSE CVE CVE-2017-12153 | known affected: 300 known not affected: 172 recommended: 1217 | 2026-07-28T00:07:06+00:00 | Vulnerability · Source |
| CVE-2017-12877 | suse_vex | SUSE CVE CVE-2017-12877 | known not affected: 220 | 2026-07-28T00:06:58+00:00 | Vulnerability · Source |
| CVE-2017-12898 | suse_vex | SUSE CVE CVE-2017-12898 | known affected: 334 known not affected: 24 recommended: 148 | 2026-07-28T00:06:56+00:00 | Vulnerability · Source |
| CVE-2017-12942 | suse_vex | SUSE CVE CVE-2017-12942 | known affected: 79 known not affected: 91 recommended: 24 | 2026-07-28T00:06:55+00:00 | Vulnerability · Source |
| CVE-2017-12967 | suse_vex | SUSE CVE CVE-2017-12967 | known affected: 15 known not affected: 165 | 2026-07-28T00:06:53+00:00 | Vulnerability · Source |
| CVE-2017-13015 | suse_vex | SUSE CVE CVE-2017-13015 | known affected: 321 known not affected: 22 recommended: 143 | 2026-07-28T00:06:50+00:00 | Vulnerability · Source |
| CVE-2017-13032 | suse_vex | SUSE CVE CVE-2017-13032 | known affected: 313 known not affected: 22 recommended: 147 | 2026-07-28T00:06:47+00:00 | Vulnerability · Source |
| CVE-2017-13034 | suse_vex | SUSE CVE CVE-2017-13034 | known affected: 321 known not affected: 22 recommended: 147 | 2026-07-28T00:06:45+00:00 | Vulnerability · Source |
| CVE-2017-13064 | suse_vex | SUSE CVE CVE-2017-13064 | known affected: 3 known not affected: 108 recommended: 14 | 2026-07-28T00:06:43+00:00 | Vulnerability · Source |
| CVE-2017-13145 | suse_vex | SUSE CVE CVE-2017-13145 | known affected: 5 known not affected: 56 | 2026-07-28T00:06:42+00:00 | Vulnerability · Source |
| CVE-2017-13693 | suse_vex | SUSE CVE CVE-2017-13693 | known affected: 21 known not affected: 382 | 2026-07-28T00:06:37+00:00 | Vulnerability · Source |
| CVE-2017-13723 | suse_vex | SUSE CVE CVE-2017-13723 | known affected: 1 known not affected: 11 recommended: 263 | 2026-07-28T00:06:36+00:00 | Vulnerability · Source |
| CVE-2017-14497 | suse_vex | SUSE CVE CVE-2017-14497 | known not affected: 517 | 2026-07-28T00:06:30+00:00 | Vulnerability · Source |
| CVE-2017-14533 | suse_vex | SUSE CVE CVE-2017-14533 | recommended: 166 | 2026-07-28T00:06:29+00:00 | Vulnerability · Source |
| CVE-2017-14624 | suse_vex | SUSE CVE CVE-2017-14624 | known affected: 5 known not affected: 124 | 2026-07-28T00:06:28+00:00 | Vulnerability · Source |
| CVE-2017-14970 | suse_vex | SUSE CVE CVE-2017-14970 | known affected: 2 known not affected: 20 recommended: 16 | 2026-07-28T00:06:25+00:00 | Vulnerability · Source |
| CVE-2017-15016 | suse_vex | SUSE CVE CVE-2017-15016 | known affected: 75 recommended: 180 | 2026-07-28T00:06:24+00:00 | Vulnerability · Source |
| CVE-2017-15218 | suse_vex | SUSE CVE CVE-2017-15218 | known affected: 75 recommended: 180 | 2026-07-28T00:06:20+00:00 | Vulnerability · Source |
| CVE-2017-15232 | suse_vex | SUSE CVE CVE-2017-15232 | known affected: 394 known not affected: 97 recommended: 501 | 2026-07-28T00:06:19+00:00 | Vulnerability · Source |