VEX records
Browse vendor VEX statements available in this Vulnerability-Lookup instance and pivot to the related vulnerability.
293999 VEX records
API response| Vulnerability | Source | Title | Product status | Imported | Links |
|---|---|---|---|---|---|
| CVE-2017-1376 | suse_vex | SUSE CVE CVE-2017-1376 | known affected: 72 known not affected: 65 | 2026-07-26T00:48:27+00:00 | Vulnerability · Source |
| CVE-2017-2579 | suse_vex | SUSE CVE CVE-2017-2579 | known affected: 16 recommended: 251 | 2026-07-26T00:48:16+00:00 | Vulnerability · Source |
| CVE-2017-2581 | suse_vex | SUSE CVE CVE-2017-2581 | known affected: 16 recommended: 78 | 2026-07-26T00:48:15+00:00 | Vulnerability · Source |
| CVE-2017-2618 | suse_vex | SUSE CVE CVE-2017-2618 | known not affected: 781 recommended: 12 | 2026-07-26T00:48:11+00:00 | Vulnerability · Source |
| CVE-2017-2628 | suse_vex | SUSE CVE CVE-2017-2628 | known not affected: 63 | 2026-07-26T00:48:07+00:00 | Vulnerability · Source |
| CVE-2017-2634 | suse_vex | SUSE CVE CVE-2017-2634 | known not affected: 54 | 2026-07-26T00:48:05+00:00 | Vulnerability · Source |
| CVE-2017-2669 | suse_vex | SUSE CVE CVE-2017-2669 | recommended: 82 | 2026-07-26T00:48:02+00:00 | Vulnerability · Source |
| CVE-2017-2671 | suse_vex | SUSE CVE CVE-2017-2671 | known affected: 14 known not affected: 320 recommended: 335 | 2026-07-26T00:48:00+00:00 | Vulnerability · Source |
| CVE-2017-3135 | suse_vex | SUSE CVE CVE-2017-3135 | known affected: 377 known not affected: 387 recommended: 958 | 2026-07-26T00:47:57+00:00 | Vulnerability · Source |
| CVE-2017-3139 | suse_vex | SUSE CVE CVE-2017-3139 | known affected: 63 known not affected: 118 | 2026-07-26T00:47:54+00:00 | Vulnerability · Source |
| CVE-2017-3169 | suse_vex | SUSE CVE CVE-2017-3169 | recommended: 169 | 2026-07-26T00:47:47+00:00 | Vulnerability · Source |
| CVE-2017-3256 | suse_vex | SUSE CVE CVE-2017-3256 | known not affected: 93 | 2026-07-26T00:47:43+00:00 | Vulnerability · Source |
| CVE-2017-3305 | suse_vex | SUSE CVE CVE-2017-3305 | known not affected: 93 recommended: 28 | 2026-07-26T00:47:37+00:00 | Vulnerability · Source |
| CVE-2017-3319 | suse_vex | SUSE CVE CVE-2017-3319 | known not affected: 93 | 2026-07-26T00:47:32+00:00 | Vulnerability · Source |
| CVE-2017-3452 | suse_vex | SUSE CVE CVE-2017-3452 | known affected: 35 known not affected: 66 | 2026-07-26T00:47:28+00:00 | Vulnerability · Source |
| CVE-2017-3453 | suse_vex | SUSE CVE CVE-2017-3453 | known affected: 35 known not affected: 104 recommended: 639 | 2026-07-26T00:47:26+00:00 | Vulnerability · Source |
| CVE-2017-3600 | suse_vex | SUSE CVE CVE-2017-3600 | known affected: 35 known not affected: 104 recommended: 36 | 2026-07-26T00:47:18+00:00 | Vulnerability · Source |
| CVE-2017-3633 | suse_vex | SUSE CVE CVE-2017-3633 | known affected: 1 known not affected: 64 | 2026-07-26T00:47:15+00:00 | Vulnerability · Source |
| CVE-2017-3637 | suse_vex | SUSE CVE CVE-2017-3637 | known affected: 1 known not affected: 64 | 2026-07-26T00:47:14+00:00 | Vulnerability · Source |
| CVE-2017-3738 | suse_vex | SUSE CVE CVE-2017-3738 | known affected: 320 known not affected: 398 recommended: 972 | 2026-07-26T00:46:49+00:00 | Vulnerability · Source |
| CVE-2017-5130 | suse_vex | SUSE CVE CVE-2017-5130 | recommended: 116 | 2026-07-26T00:46:46+00:00 | Vulnerability · Source |
| CVE-2017-5335 | suse_vex | SUSE CVE CVE-2017-5335 | known affected: 8 known not affected: 4 recommended: 176 | 2026-07-26T00:46:41+00:00 | Vulnerability · Source |
| CVE-2017-5341 | suse_vex | SUSE CVE CVE-2017-5341 | known affected: 320 recommended: 182 | 2026-07-26T00:46:40+00:00 | Vulnerability · Source |
| CVE-2017-5378 | suse_vex | SUSE CVE CVE-2017-5378 | known affected: 1 recommended: 416 | 2026-07-26T00:46:38+00:00 | Vulnerability · Source |
| CVE-2017-5387 | suse_vex | SUSE CVE CVE-2017-5387 | known affected: 1 known not affected: 38 recommended: 249 | 2026-07-26T00:46:30+00:00 | Vulnerability · Source |
| CVE-2017-5396 | suse_vex | SUSE CVE CVE-2017-5396 | known affected: 1 recommended: 416 | 2026-07-26T00:46:24+00:00 | Vulnerability · Source |
| CVE-2017-5425 | suse_vex | SUSE CVE CVE-2017-5425 | known affected: 1 | 2026-07-26T00:46:09+00:00 | Vulnerability · Source |
| CVE-2017-5426 | suse_vex | SUSE CVE CVE-2017-5426 | known affected: 1 recommended: 333 | 2026-07-26T00:46:08+00:00 | Vulnerability · Source |
| CVE-2017-5459 | suse_vex | SUSE CVE CVE-2017-5459 | known not affected: 42 recommended: 770 | 2026-07-26T00:45:47+00:00 | Vulnerability · Source |
| CVE-2017-5506 | suse_vex | SUSE CVE CVE-2017-5506 | known affected: 1 known not affected: 14 recommended: 204 | 2026-07-26T00:45:36+00:00 | Vulnerability · Source |
| CVE-2017-5508 | suse_vex | SUSE CVE CVE-2017-5508 | known affected: 1 known not affected: 14 recommended: 204 | 2026-07-26T00:45:35+00:00 | Vulnerability · Source |
| CVE-2017-5509 | suse_vex | SUSE CVE CVE-2017-5509 | known not affected: 113 | 2026-07-26T00:45:34+00:00 | Vulnerability · Source |
| CVE-2017-5510 | suse_vex | SUSE CVE CVE-2017-5510 | known not affected: 49 recommended: 168 | 2026-07-26T00:45:33+00:00 | Vulnerability · Source |
| CVE-2017-5511 | suse_vex | SUSE CVE CVE-2017-5511 | known affected: 1 recommended: 218 | 2026-07-26T00:45:31+00:00 | Vulnerability · Source |
| CVE-2017-5548 | suse_vex | SUSE CVE CVE-2017-5548 | known not affected: 34 | 2026-07-26T00:45:29+00:00 | Vulnerability · Source |
| CVE-2017-5577 | suse_vex | SUSE CVE CVE-2017-5577 | known affected: 12 known not affected: 258 recommended: 101 | 2026-07-26T00:45:24+00:00 | Vulnerability · Source |
| CVE-2017-5579 | suse_vex | SUSE CVE CVE-2017-5579 | known affected: 420 known not affected: 804 recommended: 1875 | 2026-07-26T00:45:21+00:00 | Vulnerability · Source |
| CVE-2017-5754 | suse_vex | SUSE CVE CVE-2017-5754 | known affected: 358 known not affected: 198 recommended: 2030 | 2026-07-26T00:45:06+00:00 | Vulnerability · Source |
| CVE-2017-5951 | suse_vex | SUSE CVE CVE-2017-5951 | known affected: 36 known not affected: 164 recommended: 240 | 2026-07-26T00:44:51+00:00 | Vulnerability · Source |
| CVE-2017-5957 | suse_vex | SUSE CVE CVE-2017-5957 | recommended: 134 | 2026-07-26T00:44:49+00:00 | Vulnerability · Source |
| CVE-2017-6056 | suse_vex | SUSE CVE CVE-2017-6056 | known not affected: 54 | 2026-07-26T00:44:39+00:00 | Vulnerability · Source |
| CVE-2017-6181 | suse_vex | SUSE CVE CVE-2017-6181 | known not affected: 58 | 2026-07-26T00:44:38+00:00 | Vulnerability · Source |
| CVE-2017-6311 | suse_vex | SUSE CVE CVE-2017-6311 | known affected: 14 known not affected: 60 | 2026-07-26T00:44:35+00:00 | Vulnerability · Source |
| CVE-2017-6317 | suse_vex | SUSE CVE CVE-2017-6317 | recommended: 29 | 2026-07-26T00:44:32+00:00 | Vulnerability · Source |
| CVE-2017-6439 | suse_vex | SUSE CVE CVE-2017-6439 | recommended: 338 | 2026-07-26T00:44:18+00:00 | Vulnerability · Source |
| CVE-2017-6462 | suse_vex | SUSE CVE CVE-2017-6462 | known affected: 31 recommended: 103 | 2026-07-26T00:44:16+00:00 | Vulnerability · Source |
| CVE-2017-6590 | suse_vex | SUSE CVE CVE-2017-6590 | known not affected: 172 recommended: 253 | 2026-07-26T00:44:09+00:00 | Vulnerability · Source |
| CVE-2017-6830 | suse_vex | SUSE CVE CVE-2017-6830 | known affected: 45 recommended: 202 | 2026-07-26T00:44:05+00:00 | Vulnerability · Source |
| CVE-2017-6835 | suse_vex | SUSE CVE CVE-2017-6835 | known affected: 45 recommended: 202 | 2026-07-26T00:44:00+00:00 | Vulnerability · Source |
| CVE-2017-6852 | suse_vex | SUSE CVE CVE-2017-6852 | known not affected: 100 | 2026-07-26T00:43:58+00:00 | Vulnerability · Source |