VEX records
Browse vendor VEX statements available in this Vulnerability-Lookup instance and pivot to the related vulnerability.
291994 VEX records
API response| Vulnerability | Source | Title | Product status | Imported | Links |
|---|---|---|---|---|---|
| CVE-2017-2356 | suse_vex | SUSE CVE CVE-2017-2356 | known not affected: 248 recommended: 927 | 2026-07-26T00:48:25+00:00 | Vulnerability · Source |
| CVE-2017-2363 | suse_vex | SUSE CVE CVE-2017-2363 | known not affected: 248 recommended: 927 | 2026-07-26T00:48:23+00:00 | Vulnerability · Source |
| CVE-2017-2371 | suse_vex | SUSE CVE CVE-2017-2371 | known not affected: 248 recommended: 939 | 2026-07-26T00:48:20+00:00 | Vulnerability · Source |
| CVE-2017-2496 | suse_vex | SUSE CVE CVE-2017-2496 | known affected: 98 known not affected: 169 recommended: 939 | 2026-07-26T00:48:19+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-2584 | suse_vex | SUSE CVE CVE-2017-2584 | known affected: 12 known not affected: 447 recommended: 222 | 2026-07-26T00:48:13+00:00 | Vulnerability · Source |
| CVE-2017-2586 | suse_vex | SUSE CVE CVE-2017-2586 | known affected: 16 recommended: 56 | 2026-07-26T00:48:12+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-2620 | suse_vex | SUSE CVE CVE-2017-2620 | known affected: 360 known not affected: 191 recommended: 2385 | 2026-07-26T00:48:09+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-3143 | suse_vex | SUSE CVE CVE-2017-3143 | known not affected: 405 recommended: 869 | 2026-07-26T00:47:51+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-3238 | suse_vex | SUSE CVE CVE-2017-3238 | known not affected: 93 recommended: 667 | 2026-07-26T00:47:46+00:00 | Vulnerability · Source |
| CVE-2017-3253 | suse_vex | SUSE CVE CVE-2017-3253 | known affected: 124 known not affected: 166 recommended: 584 | 2026-07-26T00:47:44+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-3259 | suse_vex | SUSE CVE CVE-2017-3259 | known affected: 36 known not affected: 150 recommended: 270 | 2026-07-26T00:47:41+00:00 | Vulnerability · Source |
| CVE-2017-3261 | suse_vex | SUSE CVE CVE-2017-3261 | known affected: 518 known not affected: 166 recommended: 584 | 2026-07-26T00:47:40+00:00 | Vulnerability · Source |
| CVE-2017-3302 | suse_vex | SUSE CVE CVE-2017-3302 | known affected: 35 known not affected: 104 recommended: 657 | 2026-07-26T00:47:39+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-3308 | suse_vex | SUSE CVE CVE-2017-3308 | known affected: 35 known not affected: 104 recommended: 649 | 2026-07-26T00:47:36+00:00 | Vulnerability · Source |
| CVE-2017-3317 | suse_vex | SUSE CVE CVE-2017-3317 | known not affected: 93 recommended: 667 | 2026-07-26T00:47:35+00:00 | Vulnerability · Source |
| CVE-2017-3318 | suse_vex | SUSE CVE CVE-2017-3318 | known not affected: 93 recommended: 677 | 2026-07-26T00:47:33+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-3320 | suse_vex | SUSE CVE CVE-2017-3320 | known not affected: 93 | 2026-07-26T00:47:30+00:00 | Vulnerability · Source |
| CVE-2017-3450 | suse_vex | SUSE CVE CVE-2017-3450 | known affected: 35 known not affected: 66 | 2026-07-26T00:47:29+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-3456 | suse_vex | SUSE CVE CVE-2017-3456 | known affected: 35 known not affected: 104 recommended: 649 | 2026-07-26T00:47:25+00:00 | Vulnerability · Source |
| CVE-2017-3461 | suse_vex | SUSE CVE CVE-2017-3461 | known affected: 35 known not affected: 104 recommended: 28 | 2026-07-26T00:47:24+00:00 | Vulnerability · Source |
| CVE-2017-3463 | suse_vex | SUSE CVE CVE-2017-3463 | known affected: 35 known not affected: 104 recommended: 28 | 2026-07-26T00:47:22+00:00 | Vulnerability · Source |
| CVE-2017-3509 | suse_vex | SUSE CVE CVE-2017-3509 | known affected: 395 known not affected: 109 recommended: 732 | 2026-07-26T00:47:21+00:00 | Vulnerability · Source |
| CVE-2017-3512 | suse_vex | SUSE CVE CVE-2017-3512 | known affected: 1 known not affected: 109 recommended: 552 | 2026-07-26T00:47:19+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-3640 | suse_vex | SUSE CVE CVE-2017-3640 | known affected: 1 known not affected: 64 | 2026-07-26T00:47:12+00:00 | Vulnerability · Source |
| CVE-2017-3641 | suse_vex | SUSE CVE CVE-2017-3641 | known affected: 35 known not affected: 104 recommended: 609 | 2026-07-26T00:47:11+00:00 | Vulnerability · Source |
| CVE-2017-3647 | suse_vex | SUSE CVE CVE-2017-3647 | known affected: 1 known not affected: 64 | 2026-07-26T00:47:09+00:00 | Vulnerability · Source |
| CVE-2017-3648 | suse_vex | SUSE CVE CVE-2017-3648 | known affected: 1 known not affected: 44 recommended: 28 | 2026-07-26T00:47:08+00:00 | Vulnerability · Source |
| CVE-2017-3731 | suse_vex | SUSE CVE CVE-2017-3731 | known affected: 386 known not affected: 329 recommended: 1047 | 2026-07-26T00:47:05+00:00 | Vulnerability · Source |
| CVE-2017-3735 | suse_vex | SUSE CVE CVE-2017-3735 | known affected: 360 known not affected: 478 recommended: 1014 | 2026-07-26T00:46:51+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-5334 | suse_vex | SUSE CVE CVE-2017-5334 | known not affected: 82 recommended: 5 | 2026-07-26T00:46:42+00:00 | Vulnerability · Source |