VEX records
Browse vendor VEX statements available in this Vulnerability-Lookup instance and pivot to the related vulnerability.
286824 VEX records
API response| Vulnerability | Source | Title | Product status | Imported | Links |
|---|---|---|---|---|---|
| CVE-2017-13221 | suse_vex | SUSE CVE CVE-2017-13221 | known not affected: 48 | 2026-08-01T23:36:10+00:00 | Vulnerability · Source |
| CVE-2017-13689 | suse_vex | SUSE CVE CVE-2017-13689 | known affected: 336 known not affected: 24 recommended: 151 | 2026-08-01T23:36:09+00:00 | Vulnerability · Source |
| CVE-2017-13798 | suse_vex | SUSE CVE CVE-2017-13798 | known not affected: 87 recommended: 939 | 2026-08-01T23:36:07+00:00 | Vulnerability · Source |
| CVE-2017-14160 | suse_vex | SUSE CVE CVE-2017-14160 | known affected: 516 known not affected: 120 recommended: 367 | 2026-08-01T23:36:06+00:00 | Vulnerability · Source |
| CVE-2017-14341 | suse_vex | SUSE CVE CVE-2017-14341 | known affected: 94 recommended: 186 | 2026-08-01T23:36:04+00:00 | Vulnerability · Source |
| CVE-2017-14342 | suse_vex | SUSE CVE CVE-2017-14342 | known affected: 94 recommended: 186 | 2026-08-01T23:36:03+00:00 | Vulnerability · Source |
| CVE-2017-14859 | suse_vex | SUSE CVE CVE-2017-14859 | known affected: 13 known not affected: 149 recommended: 186 | 2026-08-01T23:36:02+00:00 | Vulnerability · Source |
| CVE-2017-14861 | suse_vex | SUSE CVE CVE-2017-14861 | known affected: 4 known not affected: 53 | 2026-08-01T23:36:01+00:00 | Vulnerability · Source |
| CVE-2017-14954 | suse_vex | SUSE CVE CVE-2017-14954 | known not affected: 28 | 2026-08-01T23:36:00+00:00 | Vulnerability · Source |
| CVE-2017-15085 | suse_vex | SUSE CVE CVE-2017-15085 | known affected: 534 known not affected: 263 | 2026-08-01T23:35:59+00:00 | Vulnerability · Source |
| CVE-2017-15086 | suse_vex | SUSE CVE CVE-2017-15086 | known affected: 533 known not affected: 355 | 2026-08-01T23:35:57+00:00 | Vulnerability · Source |
| CVE-2017-15130 | suse_vex | SUSE CVE CVE-2017-15130 | known affected: 62 known not affected: 37 recommended: 473 | 2026-08-01T23:35:56+00:00 | Vulnerability · Source |
| CVE-2017-15306 | suse_vex | SUSE CVE CVE-2017-15306 | known not affected: 14 | 2026-08-01T23:35:55+00:00 | Vulnerability · Source |
| CVE-2017-15631 | suse_vex | SUSE CVE CVE-2017-15631 | known not affected: 15 recommended: 62 | 2026-08-01T23:35:54+00:00 | Vulnerability · Source |
| CVE-2017-15868 | suse_vex | SUSE CVE CVE-2017-15868 | known affected: 16 known not affected: 374 recommended: 260 | 2026-08-01T23:35:52+00:00 | Vulnerability · Source |
| CVE-2017-15930 | suse_vex | SUSE CVE CVE-2017-15930 | known affected: 94 recommended: 186 | 2026-08-01T23:35:51+00:00 | Vulnerability · Source |
| CVE-2017-16528 | suse_vex | SUSE CVE CVE-2017-16528 | known affected: 36 known not affected: 559 recommended: 407 | 2026-08-01T23:35:50+00:00 | Vulnerability · Source |
| CVE-2017-16644 | suse_vex | SUSE CVE CVE-2017-16644 | known affected: 36 known not affected: 358 recommended: 609 | 2026-08-01T23:35:48+00:00 | Vulnerability · Source |
| CVE-2017-16650 | suse_vex | SUSE CVE CVE-2017-16650 | known affected: 21 known not affected: 304 recommended: 373 | 2026-08-01T23:35:47+00:00 | Vulnerability · Source |
| CVE-2017-17083 | suse_vex | SUSE CVE CVE-2017-17083 | known not affected: 115 recommended: 606 | 2026-08-01T23:35:45+00:00 | Vulnerability · Source |
| CVE-2017-17558 | suse_vex | SUSE CVE CVE-2017-17558 | known affected: 23 known not affected: 569 recommended: 514 | 2026-08-01T23:35:44+00:00 | Vulnerability · Source |
| CVE-2017-17669 | suse_vex | SUSE CVE CVE-2017-17669 | known not affected: 22 recommended: 23 | 2026-08-01T23:35:43+00:00 | Vulnerability · Source |
| CVE-2017-18184 | suse_vex | SUSE CVE CVE-2017-18184 | known not affected: 157 | 2026-08-01T23:35:42+00:00 | Vulnerability · Source |
| CVE-2017-18233 | suse_vex | SUSE CVE CVE-2017-18233 | known affected: 4 known not affected: 17 recommended: 26 | 2026-08-01T23:35:40+00:00 | Vulnerability · Source |
| CVE-2017-18870 | suse_vex | SUSE CVE CVE-2017-18870 | No product status | 2026-08-01T23:35:39+00:00 | Vulnerability · Source |
| CVE-2017-18871 | suse_vex | SUSE CVE CVE-2017-18871 | No product status | 2026-08-01T23:35:38+00:00 | Vulnerability · Source |
| CVE-2017-18872 | suse_vex | SUSE CVE CVE-2017-18872 | recommended: 1 | 2026-08-01T23:35:37+00:00 | Vulnerability · Source |
| CVE-2017-18883 | suse_vex | SUSE CVE CVE-2017-18883 | No product status | 2026-08-01T23:35:35+00:00 | Vulnerability · Source |
| CVE-2017-18884 | suse_vex | SUSE CVE CVE-2017-18884 | No product status | 2026-08-01T23:35:34+00:00 | Vulnerability · Source |
| CVE-2017-18885 | suse_vex | SUSE CVE CVE-2017-18885 | No product status | 2026-08-01T23:35:33+00:00 | Vulnerability · Source |
| CVE-2017-18886 | suse_vex | SUSE CVE CVE-2017-18886 | No product status | 2026-08-01T23:35:32+00:00 | Vulnerability · Source |
| CVE-2017-18888 | suse_vex | SUSE CVE CVE-2017-18888 | No product status | 2026-08-01T23:35:31+00:00 | Vulnerability · Source |
| CVE-2017-18894 | suse_vex | SUSE CVE CVE-2017-18894 | No product status | 2026-08-01T23:35:28+00:00 | Vulnerability · Source |
| CVE-2017-18900 | suse_vex | SUSE CVE CVE-2017-18900 | No product status | 2026-08-01T23:35:26+00:00 | Vulnerability · Source |
| CVE-2017-1000253 | suse_vex | SUSE CVE CVE-2017-1000253 | known affected: 2 known not affected: 62 recommended: 137 | 2026-08-01T23:35:22+00:00 | Vulnerability · Source |
| CVE-2018-1100 | suse_vex | SUSE CVE CVE-2018-1100 | known affected: 398 known not affected: 40 recommended: 91 | 2026-08-01T23:35:20+00:00 | Vulnerability · Source |
| CVE-2018-2582 | suse_vex | SUSE CVE CVE-2018-2582 | known affected: 73 known not affected: 279 recommended: 669 | 2026-08-01T23:35:18+00:00 | Vulnerability · Source |
| CVE-2018-2612 | suse_vex | SUSE CVE CVE-2018-2612 | known affected: 1 known not affected: 130 recommended: 593 | 2026-08-01T23:35:17+00:00 | Vulnerability · Source |
| CVE-2018-2641 | suse_vex | SUSE CVE CVE-2018-2641 | known affected: 73 known not affected: 263 recommended: 730 | 2026-08-01T23:35:15+00:00 | Vulnerability · Source |
| CVE-2018-3064 | suse_vex | SUSE CVE CVE-2018-3064 | known affected: 65 known not affected: 59 recommended: 590 | 2026-08-01T23:35:14+00:00 | Vulnerability · Source |
| CVE-2018-3180 | suse_vex | SUSE CVE CVE-2018-3180 | known affected: 411 known not affected: 55 recommended: 1133 | 2026-08-01T23:35:12+00:00 | Vulnerability · Source |
| CVE-2018-3639 | suse_vex | SUSE CVE CVE-2018-3639 | known affected: 446 known not affected: 2538 recommended: 6375 | 2026-08-01T23:35:10+00:00 | Vulnerability · Source |
| CVE-2018-4101 | suse_vex | SUSE CVE CVE-2018-4101 | known affected: 116 known not affected: 169 recommended: 915 | 2026-08-01T23:35:08+00:00 | Vulnerability · Source |
| CVE-2018-4127 | suse_vex | SUSE CVE CVE-2018-4127 | known affected: 116 known not affected: 169 recommended: 915 | 2026-08-01T23:35:07+00:00 | Vulnerability · Source |
| CVE-2018-4213 | suse_vex | SUSE CVE CVE-2018-4213 | known affected: 108 known not affected: 82 recommended: 959 | 2026-08-01T23:35:05+00:00 | Vulnerability · Source |
| CVE-2018-4265 | suse_vex | SUSE CVE CVE-2018-4265 | known affected: 108 known not affected: 82 recommended: 957 | 2026-08-01T23:35:03+00:00 | Vulnerability · Source |
| CVE-2018-4311 | suse_vex | SUSE CVE CVE-2018-4311 | known affected: 108 known not affected: 82 | 2026-08-01T23:35:02+00:00 | Vulnerability · Source |
| CVE-2018-5095 | suse_vex | SUSE CVE CVE-2018-5095 | known affected: 2 recommended: 408 | 2026-08-01T23:35:01+00:00 | Vulnerability · Source |
| CVE-2018-5097 | suse_vex | SUSE CVE CVE-2018-5097 | known affected: 2 recommended: 408 | 2026-08-01T23:34:59+00:00 | Vulnerability · Source |
| CVE-2018-5130 | suse_vex | SUSE CVE CVE-2018-5130 | known affected: 2 recommended: 311 | 2026-08-01T23:34:58+00:00 | Vulnerability · Source |