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-11176 | suse_vex | SUSE CVE CVE-2017-11176 | known affected: 16 known not affected: 514 recommended: 243 | 2026-07-26T00:36:55+00:00 | Vulnerability · Source |
| CVE-2017-11334 | suse_vex | SUSE CVE CVE-2017-11334 | known affected: 437 known not affected: 1188 recommended: 1903 | 2026-07-26T00:36:53+00:00 | Vulnerability · Source |
| CVE-2017-11360 | suse_vex | SUSE CVE CVE-2017-11360 | known affected: 47 known not affected: 79 | 2026-07-26T00:36:49+00:00 | Vulnerability · Source |
| CVE-2017-11411 | suse_vex | SUSE CVE CVE-2017-11411 | known affected: 86 known not affected: 115 recommended: 559 | 2026-07-26T00:36:45+00:00 | Vulnerability · Source |
| CVE-2017-11423 | suse_vex | SUSE CVE CVE-2017-11423 | known not affected: 138 recommended: 412 | 2026-07-26T00:36:43+00:00 | Vulnerability · Source |
| CVE-2017-11446 | suse_vex | SUSE CVE CVE-2017-11446 | known not affected: 36 recommended: 136 | 2026-07-26T00:36:41+00:00 | Vulnerability · Source |
| CVE-2017-11447 | suse_vex | SUSE CVE CVE-2017-11447 | known affected: 10 known not affected: 101 | 2026-07-26T00:36:39+00:00 | Vulnerability · Source |
| CVE-2017-11448 | suse_vex | SUSE CVE CVE-2017-11448 | known affected: 95 recommended: 186 | 2026-07-26T00:36:37+00:00 | Vulnerability · Source |
| CVE-2017-11450 | suse_vex | SUSE CVE CVE-2017-11450 | known affected: 95 recommended: 186 | 2026-07-26T00:36:36+00:00 | Vulnerability · Source |
| CVE-2017-11464 | suse_vex | SUSE CVE CVE-2017-11464 | known not affected: 16 recommended: 360 | 2026-07-26T00:36:34+00:00 | Vulnerability · Source |
| CVE-2017-11478 | suse_vex | SUSE CVE CVE-2017-11478 | known affected: 94 known not affected: 14 recommended: 172 | 2026-07-26T00:36:31+00:00 | Vulnerability · Source |
| CVE-2017-11528 | suse_vex | SUSE CVE CVE-2017-11528 | known affected: 94 recommended: 186 | 2026-07-26T00:36:29+00:00 | Vulnerability · Source |
| CVE-2017-11529 | suse_vex | SUSE CVE CVE-2017-11529 | known not affected: 14 recommended: 172 | 2026-07-26T00:36:28+00:00 | Vulnerability · Source |
| CVE-2017-11532 | suse_vex | SUSE CVE CVE-2017-11532 | known affected: 97 known not affected: 1 recommended: 152 | 2026-07-26T00:36:26+00:00 | Vulnerability · Source |
| CVE-2017-11533 | suse_vex | SUSE CVE CVE-2017-11533 | known affected: 94 recommended: 186 | 2026-07-26T00:36:25+00:00 | Vulnerability · Source |
| CVE-2017-11535 | suse_vex | SUSE CVE CVE-2017-11535 | known affected: 94 known not affected: 14 recommended: 172 | 2026-07-26T00:36:23+00:00 | Vulnerability · Source |
| CVE-2017-11538 | suse_vex | SUSE CVE CVE-2017-11538 | known affected: 10 known not affected: 144 | 2026-07-26T00:36:22+00:00 | Vulnerability · Source |
| CVE-2017-11539 | suse_vex | SUSE CVE CVE-2017-11539 | known affected: 94 recommended: 186 | 2026-07-26T00:36:20+00:00 | Vulnerability · Source |
| CVE-2017-11541 | suse_vex | SUSE CVE CVE-2017-11541 | known affected: 336 known not affected: 24 recommended: 151 | 2026-07-26T00:36:18+00:00 | Vulnerability · Source |
| CVE-2017-11545 | suse_vex | SUSE CVE CVE-2017-11545 | known affected: 2 known not affected: 14 | 2026-07-26T00:36:17+00:00 | Vulnerability · Source |
| CVE-2017-11548 | suse_vex | SUSE CVE CVE-2017-11548 | known not affected: 298 | 2026-07-26T00:36:15+00:00 | Vulnerability · Source |
| CVE-2017-11592 | suse_vex | SUSE CVE CVE-2017-11592 | known affected: 28 known not affected: 93 recommended: 157 | 2026-07-26T00:36:12+00:00 | Vulnerability · Source |
| CVE-2017-11626 | suse_vex | SUSE CVE CVE-2017-11626 | known affected: 4 known not affected: 33 recommended: 326 | 2026-07-26T00:36:09+00:00 | Vulnerability · Source |
| CVE-2017-11636 | suse_vex | SUSE CVE CVE-2017-11636 | known affected: 3 known not affected: 128 recommended: 14 | 2026-07-26T00:36:07+00:00 | Vulnerability · Source |
| CVE-2017-11637 | suse_vex | SUSE CVE CVE-2017-11637 | known affected: 1 known not affected: 133 recommended: 50 | 2026-07-26T00:36:06+00:00 | Vulnerability · Source |
| CVE-2017-11639 | suse_vex | SUSE CVE CVE-2017-11639 | known affected: 94 known not affected: 14 recommended: 172 | 2026-07-26T00:36:04+00:00 | Vulnerability · Source |
| CVE-2017-11644 | suse_vex | SUSE CVE CVE-2017-11644 | known not affected: 37 recommended: 172 | 2026-07-26T00:36:03+00:00 | Vulnerability · Source |
| CVE-2017-11696 | suse_vex | SUSE CVE CVE-2017-11696 | known not affected: 525 | 2026-07-26T00:35:59+00:00 | Vulnerability · Source |
| CVE-2017-11698 | suse_vex | SUSE CVE CVE-2017-11698 | known not affected: 525 | 2026-07-26T00:35:58+00:00 | Vulnerability · Source |
| CVE-2017-11722 | suse_vex | SUSE CVE CVE-2017-11722 | known affected: 10 known not affected: 144 | 2026-07-26T00:35:56+00:00 | Vulnerability · Source |
| CVE-2017-11750 | suse_vex | SUSE CVE CVE-2017-11750 | known affected: 94 known not affected: 21 recommended: 186 | 2026-07-26T00:35:55+00:00 | Vulnerability · Source |
| CVE-2017-11751 | suse_vex | SUSE CVE CVE-2017-11751 | known affected: 94 known not affected: 91 recommended: 172 | 2026-07-26T00:35:53+00:00 | Vulnerability · Source |
| CVE-2017-11753 | suse_vex | SUSE CVE CVE-2017-11753 | known not affected: 130 | 2026-07-26T00:35:52+00:00 | Vulnerability · Source |
| CVE-2017-12134 | suse_vex | SUSE CVE CVE-2017-12134 | known affected: 24 known not affected: 188 recommended: 114 | 2026-07-26T00:35:48+00:00 | Vulnerability · Source |
| CVE-2017-12135 | suse_vex | SUSE CVE CVE-2017-12135 | known affected: 352 known not affected: 21 recommended: 519 | 2026-07-26T00:35:47+00:00 | Vulnerability · Source |
| CVE-2017-12140 | suse_vex | SUSE CVE CVE-2017-12140 | known affected: 94 recommended: 186 | 2026-07-26T00:35:45+00:00 | Vulnerability · Source |
| CVE-2017-12146 | suse_vex | SUSE CVE CVE-2017-12146 | known not affected: 78 | 2026-07-26T00:35:43+00:00 | Vulnerability · Source |
| CVE-2017-12154 | suse_vex | SUSE CVE CVE-2017-12154 | known not affected: 182 recommended: 499 | 2026-07-26T00:35:42+00:00 | Vulnerability · Source |
| CVE-2017-12164 | suse_vex | SUSE CVE CVE-2017-12164 | known affected: 10 known not affected: 130 recommended: 438 | 2026-07-26T00:35:40+00:00 | Vulnerability · Source |
| CVE-2017-12168 | suse_vex | SUSE CVE CVE-2017-12168 | known not affected: 28 | 2026-07-26T00:35:39+00:00 | Vulnerability · Source |
| CVE-2017-12176 | suse_vex | SUSE CVE CVE-2017-12176 | known affected: 396 known not affected: 51 recommended: 278 | 2026-07-26T00:35:37+00:00 | Vulnerability · Source |
| CVE-2017-12178 | suse_vex | SUSE CVE CVE-2017-12178 | known affected: 1 known not affected: 1 recommended: 42 | 2026-07-26T00:35:35+00:00 | Vulnerability · Source |
| CVE-2017-12180 | suse_vex | SUSE CVE CVE-2017-12180 | known affected: 2 known not affected: 38 recommended: 42 | 2026-07-26T00:35:34+00:00 | Vulnerability · Source |
| CVE-2017-12186 | suse_vex | SUSE CVE CVE-2017-12186 | known affected: 2 known not affected: 51 recommended: 42 | 2026-07-26T00:35:32+00:00 | Vulnerability · Source |
| CVE-2017-12187 | suse_vex | SUSE CVE CVE-2017-12187 | known affected: 396 known not affected: 51 recommended: 278 | 2026-07-26T00:35:31+00:00 | Vulnerability · Source |
| CVE-2017-12190 | suse_vex | SUSE CVE CVE-2017-12190 | known not affected: 135 recommended: 508 | 2026-07-26T00:35:29+00:00 | Vulnerability · Source |
| CVE-2017-12375 | suse_vex | SUSE CVE CVE-2017-12375 | known affected: 1 known not affected: 78 recommended: 280 | 2026-07-26T00:35:28+00:00 | Vulnerability · Source |
| CVE-2017-12418 | suse_vex | SUSE CVE CVE-2017-12418 | known affected: 95 known not affected: 37 recommended: 172 | 2026-07-26T00:35:26+00:00 | Vulnerability · Source |
| CVE-2017-12428 | suse_vex | SUSE CVE CVE-2017-12428 | known not affected: 316 recommended: 136 | 2026-07-26T00:35:25+00:00 | Vulnerability · Source |
| CVE-2017-12432 | suse_vex | SUSE CVE CVE-2017-12432 | known affected: 95 recommended: 186 | 2026-07-26T00:35:24+00:00 | Vulnerability · Source |