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-2016-2069 | suse_vex | SUSE CVE CVE-2016-2069 | known not affected: 119 recommended: 343 | 2026-08-01T00:23:10+00:00 | Vulnerability · Source |
| CVE-2016-2074 | suse_vex | SUSE CVE CVE-2016-2074 | known not affected: 18 | 2026-08-01T00:23:09+00:00 | Vulnerability · Source |
| CVE-2016-2821 | suse_vex | SUSE CVE CVE-2016-2821 | known affected: 2 recommended: 622 | 2026-08-01T00:23:02+00:00 | Vulnerability · Source |
| CVE-2016-2842 | suse_vex | SUSE CVE CVE-2016-2842 | known not affected: 69 recommended: 5 | 2026-08-01T00:23:00+00:00 | Vulnerability · Source |
| CVE-2016-3634 | suse_vex | SUSE CVE CVE-2016-3634 | known not affected: 53 | 2026-08-01T00:22:56+00:00 | Vulnerability · Source |
| CVE-2016-4488 | suse_vex | SUSE CVE CVE-2016-4488 | known not affected: 1028 | 2026-08-01T00:22:53+00:00 | Vulnerability · Source |
| CVE-2016-4580 | suse_vex | SUSE CVE CVE-2016-4580 | known affected: 2 known not affected: 27 recommended: 187 | 2026-08-01T00:22:52+00:00 | Vulnerability · Source |
| CVE-2016-4802 | suse_vex | SUSE CVE CVE-2016-4802 | known not affected: 49 | 2026-08-01T00:22:50+00:00 | Vulnerability · Source |
| CVE-2016-4859 | suse_vex | SUSE CVE CVE-2016-4859 | known not affected: 443 | 2026-08-01T00:22:49+00:00 | Vulnerability · Source |
| CVE-2016-5573 | suse_vex | SUSE CVE CVE-2016-5573 | known not affected: 263 recommended: 805 | 2026-08-01T00:22:45+00:00 | Vulnerability · Source |
| CVE-2016-6153 | suse_vex | SUSE CVE CVE-2016-6153 | known affected: 394 known not affected: 139 recommended: 162 | 2026-08-01T00:22:43+00:00 | Vulnerability · Source |
| CVE-2016-7162 | suse_vex | SUSE CVE CVE-2016-7162 | known not affected: 130 | 2026-08-01T00:22:41+00:00 | Vulnerability · Source |
| CVE-2016-7446 | suse_vex | SUSE CVE CVE-2016-7446 | known affected: 3 known not affected: 103 recommended: 14 | 2026-08-01T00:22:39+00:00 | Vulnerability · Source |
| CVE-2016-7800 | suse_vex | SUSE CVE CVE-2016-7800 | known affected: 95 recommended: 190 | 2026-08-01T00:22:37+00:00 | Vulnerability · Source |
| CVE-2016-7911 | suse_vex | SUSE CVE CVE-2016-7911 | known affected: 4 recommended: 314 | 2026-08-01T00:22:35+00:00 | Vulnerability · Source |
| CVE-2016-7958 | suse_vex | SUSE CVE CVE-2016-7958 | known not affected: 92 | 2026-08-01T00:22:33+00:00 | Vulnerability · Source |
| CVE-2016-7977 | suse_vex | SUSE CVE CVE-2016-7977 | recommended: 287 | 2026-08-01T00:22:31+00:00 | Vulnerability · Source |
| CVE-2016-8637 | suse_vex | SUSE CVE CVE-2016-8637 | known affected: 321 known not affected: 22 recommended: 321 | 2026-08-01T00:22:27+00:00 | Vulnerability · Source |
| CVE-2016-9071 | suse_vex | SUSE CVE CVE-2016-9071 | known affected: 1 known not affected: 60 recommended: 321 | 2026-08-01T00:22:23+00:00 | Vulnerability · Source |
| CVE-2016-9428 | suse_vex | SUSE CVE CVE-2016-9428 | known not affected: 15 | 2026-08-01T00:22:18+00:00 | Vulnerability · Source |
| CVE-2016-9437 | suse_vex | SUSE CVE CVE-2016-9437 | known affected: 1 recommended: 87 | 2026-08-01T00:22:17+00:00 | Vulnerability · Source |
| CVE-2016-9535 | suse_vex | SUSE CVE CVE-2016-9535 | known not affected: 28 recommended: 26 | 2026-08-01T00:22:14+00:00 | Vulnerability · Source |
| CVE-2016-10047 | suse_vex | SUSE CVE CVE-2016-10047 | known not affected: 99 | 2026-08-01T00:22:08+00:00 | Vulnerability · Source |
| CVE-2016-10172 | suse_vex | SUSE CVE CVE-2016-10172 | known affected: 30 recommended: 57 | 2026-08-01T00:22:06+00:00 | Vulnerability · Source |
| CVE-2017-2626 | suse_vex | SUSE CVE CVE-2017-2626 | known affected: 430 known not affected: 18 recommended: 413 | 2026-08-01T00:21:59+00:00 | Vulnerability · Source |
| CVE-2017-3544 | suse_vex | SUSE CVE CVE-2017-3544 | known not affected: 109 recommended: 732 | 2026-08-01T00:21:56+00:00 | Vulnerability · Source |
| 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-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-6000 | suse_vex | SUSE CVE CVE-2017-6000 | known not affected: 73 | 2026-08-01T00:21:36+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-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 |