VEX records
Browse vendor VEX statements available in this Vulnerability-Lookup instance and pivot to the related vulnerability.
290275 VEX records
API response| Vulnerability | Source | Title | Product status | Imported | Links |
|---|---|---|---|---|---|
| CVE-2017-3650 | suse_vex | SUSE CVE CVE-2017-3650 | known affected: 1 known not affected: 64 | 2026-08-01T00:21:54+00:00 | Vulnerability · Source |
| CVE-2017-3737 | suse_vex | SUSE CVE CVE-2017-3737 | known affected: 394 known not affected: 300 recommended: 297 | 2026-08-01T00:21:52+00:00 | Vulnerability · Source |
| CVE-2017-5384 | suse_vex | SUSE CVE CVE-2017-5384 | known affected: 1 known not affected: 38 recommended: 249 | 2026-08-01T00:21:50+00:00 | Vulnerability · Source |
| CVE-2017-5413 | suse_vex | SUSE CVE CVE-2017-5413 | known affected: 1 recommended: 333 | 2026-08-01T00:21:48+00:00 | Vulnerability · Source |
| CVE-2017-5421 | suse_vex | SUSE CVE CVE-2017-5421 | known affected: 1 recommended: 333 | 2026-08-01T00:21:47+00:00 | Vulnerability · Source |
| CVE-2017-5432 | suse_vex | SUSE CVE CVE-2017-5432 | known not affected: 42 recommended: 770 | 2026-08-01T00:21:45+00:00 | Vulnerability · Source |
| CVE-2017-5434 | suse_vex | SUSE CVE CVE-2017-5434 | known not affected: 42 recommended: 770 | 2026-08-01T00:21:44+00:00 | Vulnerability · Source |
| CVE-2017-5460 | suse_vex | SUSE CVE CVE-2017-5460 | known not affected: 42 recommended: 770 | 2026-08-01T00:21:42+00:00 | Vulnerability · Source |
| CVE-2017-5669 | suse_vex | SUSE CVE CVE-2017-5669 | known affected: 2 known not affected: 378 recommended: 233 | 2026-08-01T00:21:40+00:00 | Vulnerability · Source |
| CVE-2017-5835 | suse_vex | SUSE CVE CVE-2017-5835 | known affected: 34 recommended: 357 | 2026-08-01T00:21:39+00:00 | Vulnerability · Source |
| CVE-2017-6000 | suse_vex | SUSE CVE CVE-2017-6000 | known not affected: 73 | 2026-08-01T00:21:36+00:00 | Vulnerability · Source |
| CVE-2017-6440 | suse_vex | SUSE CVE CVE-2017-6440 | known affected: 34 recommended: 365 | 2026-08-01T00:21:35+00:00 | Vulnerability · Source |
| CVE-2017-7294 | suse_vex | SUSE CVE CVE-2017-7294 | known not affected: 339 recommended: 455 | 2026-08-01T00:21:31+00:00 | Vulnerability · Source |
| CVE-2017-7546 | suse_vex | SUSE CVE CVE-2017-7546 | known not affected: 45 recommended: 264 | 2026-08-01T00:21:29+00:00 | Vulnerability · Source |
| CVE-2017-7768 | suse_vex | SUSE CVE CVE-2017-7768 | known affected: 2 known not affected: 42 recommended: 376 | 2026-08-01T00:21:27+00:00 | Vulnerability · Source |
| CVE-2017-7808 | suse_vex | SUSE CVE CVE-2017-7808 | known affected: 1 known not affected: 42 recommended: 12 | 2026-08-01T00:21:26+00:00 | Vulnerability · Source |
| CVE-2017-8061 | suse_vex | SUSE CVE CVE-2017-8061 | known not affected: 34 | 2026-08-01T00:21:24+00:00 | Vulnerability · Source |
| CVE-2017-8072 | suse_vex | SUSE CVE CVE-2017-8072 | known not affected: 34 | 2026-08-01T00:21:22+00:00 | Vulnerability · Source |
| CVE-2017-8834 | suse_vex | SUSE CVE CVE-2017-8834 | known affected: 28 known not affected: 36 recommended: 232 | 2026-08-01T00:21:21+00:00 | Vulnerability · Source |
| CVE-2017-8904 | suse_vex | SUSE CVE CVE-2017-8904 | known affected: 13 | 2026-08-01T00:21:19+00:00 | Vulnerability · Source |
| CVE-2017-9038 | suse_vex | SUSE CVE CVE-2017-9038 | known affected: 1 known not affected: 134 recommended: 54 | 2026-08-01T00:21:17+00:00 | Vulnerability · Source |
| CVE-2017-9076 | suse_vex | SUSE CVE CVE-2017-9076 | known affected: 14 known not affected: 345 recommended: 444 | 2026-08-01T00:21:15+00:00 | Vulnerability · Source |
| CVE-2017-9114 | suse_vex | SUSE CVE CVE-2017-9114 | known affected: 1 known not affected: 87 recommended: 269 | 2026-08-01T00:21:14+00:00 | Vulnerability · Source |
| CVE-2017-9115 | suse_vex | SUSE CVE CVE-2017-9115 | known affected: 5 recommended: 278 | 2026-08-01T00:21:12+00:00 | Vulnerability · Source |
| CVE-2017-9445 | suse_vex | SUSE CVE CVE-2017-9445 | known affected: 450 known not affected: 52 recommended: 1150 | 2026-08-01T00:21:10+00:00 | Vulnerability · Source |
| CVE-2017-10081 | suse_vex | SUSE CVE CVE-2017-10081 | known affected: 409 known not affected: 109 recommended: 690 | 2026-08-01T00:21:08+00:00 | Vulnerability · Source |
| CVE-2017-10086 | suse_vex | SUSE CVE CVE-2017-10086 | recommended: 335 | 2026-08-01T00:21:06+00:00 | Vulnerability · Source |
| CVE-2017-10107 | suse_vex | SUSE CVE CVE-2017-10107 | known affected: 15 known not affected: 109 recommended: 690 | 2026-08-01T00:21:05+00:00 | Vulnerability · Source |
| CVE-2017-10243 | suse_vex | SUSE CVE CVE-2017-10243 | known affected: 15 known not affected: 109 recommended: 674 | 2026-08-01T00:21:03+00:00 | Vulnerability · Source |
| CVE-2017-11434 | suse_vex | SUSE CVE CVE-2017-11434 | known affected: 471 known not affected: 65 recommended: 2001 | 2026-08-01T00:21:01+00:00 | Vulnerability · Source |
| CVE-2017-11526 | suse_vex | SUSE CVE CVE-2017-11526 | known affected: 94 known not affected: 21 recommended: 186 | 2026-08-01T00:20:59+00:00 | Vulnerability · Source |
| CVE-2017-11697 | suse_vex | SUSE CVE CVE-2017-11697 | known not affected: 355 | 2026-08-01T00:20:58+00:00 | Vulnerability · Source |
| CVE-2017-12182 | suse_vex | SUSE CVE CVE-2017-12182 | known affected: 2 known not affected: 38 recommended: 42 | 2026-08-01T00:20:56+00:00 | Vulnerability · Source |
| CVE-2017-12184 | suse_vex | SUSE CVE CVE-2017-12184 | known affected: 2 known not affected: 51 recommended: 42 | 2026-08-01T00:20:55+00:00 | Vulnerability · Source |
| CVE-2017-13004 | suse_vex | SUSE CVE CVE-2017-13004 | known affected: 336 known not affected: 24 recommended: 151 | 2026-08-01T00:20:52+00:00 | Vulnerability · Source |
| CVE-2017-13132 | suse_vex | SUSE CVE CVE-2017-13132 | known affected: 10 known not affected: 144 | 2026-08-01T00:20:51+00:00 | Vulnerability · Source |
| CVE-2017-13144 | suse_vex | SUSE CVE CVE-2017-13144 | known affected: 10 known not affected: 144 | 2026-08-01T00:20:49+00:00 | Vulnerability · Source |
| CVE-2017-13166 | suse_vex | SUSE CVE CVE-2017-13166 | known affected: 76 known not affected: 393 recommended: 713 | 2026-08-01T00:20:48+00:00 | Vulnerability · Source |
| CVE-2017-13648 | suse_vex | SUSE CVE CVE-2017-13648 | known not affected: 14 recommended: 172 | 2026-08-01T00:20:47+00:00 | Vulnerability · Source |
| CVE-2017-13764 | suse_vex | SUSE CVE CVE-2017-13764 | known not affected: 292 recommended: 444 | 2026-08-01T00:20:45+00:00 | Vulnerability · Source |
| CVE-2017-14400 | suse_vex | SUSE CVE CVE-2017-14400 | known affected: 10 known not affected: 144 | 2026-08-01T00:20:43+00:00 | Vulnerability · Source |
| CVE-2017-15131 | suse_vex | SUSE CVE CVE-2017-15131 | known affected: 12 known not affected: 50 recommended: 2 | 2026-08-01T00:20:40+00:00 | Vulnerability · Source |
| CVE-2017-15865 | suse_vex | SUSE CVE CVE-2017-15865 | known affected: 23 known not affected: 60 recommended: 347 | 2026-08-01T00:20:39+00:00 | Vulnerability · Source |
| CVE-2017-16352 | suse_vex | SUSE CVE CVE-2017-16352 | known affected: 94 recommended: 186 | 2026-08-01T00:20:37+00:00 | Vulnerability · Source |
| CVE-2017-16913 | suse_vex | SUSE CVE CVE-2017-16913 | known affected: 36 known not affected: 331 recommended: 609 | 2026-08-01T00:20:35+00:00 | Vulnerability · Source |
| CVE-2017-16931 | suse_vex | SUSE CVE CVE-2017-16931 | known affected: 61 | 2026-08-01T00:20:34+00:00 | Vulnerability · Source |
| CVE-2017-17479 | suse_vex | SUSE CVE CVE-2017-17479 | recommended: 10 | 2026-08-01T00:20:32+00:00 | Vulnerability · Source |
| CVE-2017-17741 | suse_vex | SUSE CVE CVE-2017-17741 | known affected: 44 known not affected: 408 recommended: 652 | 2026-08-01T00:20:31+00:00 | Vulnerability · Source |
| CVE-2017-17855 | suse_vex | SUSE CVE CVE-2017-17855 | known not affected: 182 recommended: 299 | 2026-08-01T00:20:27+00:00 | Vulnerability · Source |
| CVE-2017-17879 | suse_vex | SUSE CVE CVE-2017-17879 | known affected: 94 known not affected: 21 recommended: 186 | 2026-08-01T00:20:26+00:00 | Vulnerability · Source |