VEX records
Browse vendor VEX statements available in this Vulnerability-Lookup instance and pivot to the related vulnerability.
290392 VEX records
API response| Vulnerability | Source | Title | Product status | Imported | Links |
|---|---|---|---|---|---|
| CVE-2016-2109 | suse_vex | SUSE CVE CVE-2016-2109 | known affected: 350 known not affected: 314 recommended: 1079 | 2026-08-01T00:23:07+00:00 | Vulnerability · Source |
| CVE-2016-2399 | suse_vex | SUSE CVE CVE-2016-2399 | recommended: 224 | 2026-08-01T00:23:05+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-2827 | suse_vex | SUSE CVE CVE-2016-2827 | known affected: 5 recommended: 250 | 2026-08-01T00:23:01+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-8606 | suse_vex | SUSE CVE CVE-2016-8606 | known not affected: 49 recommended: 288 | 2026-08-01T00:22:29+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-9015 | suse_vex | SUSE CVE CVE-2016-9015 | known affected: 344 known not affected: 131 recommended: 428 | 2026-08-01T00:22:25+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-9073 | suse_vex | SUSE CVE CVE-2016-9073 | known affected: 1 known not affected: 60 recommended: 321 | 2026-08-01T00:22:22+00:00 | Vulnerability · Source |
| CVE-2016-9394 | suse_vex | SUSE CVE CVE-2016-9394 | known affected: 37 recommended: 194 | 2026-08-01T00:22:20+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-9448 | suse_vex | SUSE CVE CVE-2016-9448 | recommended: 276 | 2026-08-01T00:22:15+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-9626 | suse_vex | SUSE CVE CVE-2016-9626 | known affected: 1 recommended: 87 | 2026-08-01T00:22:12+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-2373 | suse_vex | SUSE CVE CVE-2017-2373 | known not affected: 248 recommended: 939 | 2026-08-01T00:22:01+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-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 |