VEX records
Browse vendor VEX statements available in this Vulnerability-Lookup instance and pivot to the related vulnerability.
291935 VEX records
API response| Vulnerability | Source | Title | Product status | Imported | Links |
|---|---|---|---|---|---|
| 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 |
| CVE-2017-12434 | suse_vex | SUSE CVE CVE-2017-12434 | known not affected: 14 recommended: 172 | 2026-07-26T00:35:22+00:00 | Vulnerability · Source |
| CVE-2017-12565 | suse_vex | SUSE CVE CVE-2017-12565 | known affected: 94 recommended: 186 | 2026-07-26T00:35:17+00:00 | Vulnerability · Source |
| CVE-2017-12566 | suse_vex | SUSE CVE CVE-2017-12566 | known affected: 95 recommended: 186 | 2026-07-26T00:35:15+00:00 | Vulnerability · Source |
| CVE-2017-12588 | suse_vex | SUSE CVE CVE-2017-12588 | known affected: 30 known not affected: 229 | 2026-07-26T00:35:13+00:00 | Vulnerability · Source |
| CVE-2017-12613 | suse_vex | SUSE CVE CVE-2017-12613 | known affected: 18 recommended: 46 | 2026-07-26T00:35:10+00:00 | Vulnerability · Source |
| CVE-2017-12615 | suse_vex | SUSE CVE CVE-2017-12615 | known affected: 46 known not affected: 179 recommended: 19 | 2026-07-26T00:35:09+00:00 | Vulnerability · Source |
| CVE-2017-12616 | suse_vex | SUSE CVE CVE-2017-12616 | known not affected: 73 recommended: 9 | 2026-07-26T00:35:07+00:00 | Vulnerability · Source |
| CVE-2017-12640 | suse_vex | SUSE CVE CVE-2017-12640 | known affected: 94 recommended: 186 | 2026-07-26T00:35:04+00:00 | Vulnerability · Source |
| CVE-2017-12644 | suse_vex | SUSE CVE CVE-2017-12644 | known affected: 94 known not affected: 20 recommended: 186 | 2026-07-26T00:35:02+00:00 | Vulnerability · Source |
| CVE-2017-12664 | suse_vex | SUSE CVE CVE-2017-12664 | known affected: 95 known not affected: 14 recommended: 172 | 2026-07-26T00:35:00+00:00 | Vulnerability · Source |
| CVE-2017-12665 | suse_vex | SUSE CVE CVE-2017-12665 | known affected: 95 known not affected: 14 recommended: 172 | 2026-07-26T00:34:58+00:00 | Vulnerability · Source |
| CVE-2017-12666 | suse_vex | SUSE CVE CVE-2017-12666 | known affected: 94 known not affected: 50 | 2026-07-26T00:34:55+00:00 | Vulnerability · Source |
| CVE-2017-12669 | suse_vex | SUSE CVE CVE-2017-12669 | known affected: 94 known not affected: 15 recommended: 172 | 2026-07-26T00:34:53+00:00 | Vulnerability · Source |
| CVE-2017-12672 | suse_vex | SUSE CVE CVE-2017-12672 | known not affected: 276 recommended: 172 | 2026-07-26T00:34:51+00:00 | Vulnerability · Source |
| CVE-2017-12675 | suse_vex | SUSE CVE CVE-2017-12675 | known not affected: 276 recommended: 172 | 2026-07-26T00:34:48+00:00 | Vulnerability · Source |
| CVE-2017-12676 | suse_vex | SUSE CVE CVE-2017-12676 | known affected: 94 recommended: 186 | 2026-07-26T00:34:46+00:00 | Vulnerability · Source |
| CVE-2017-12691 | suse_vex | SUSE CVE CVE-2017-12691 | known affected: 16 known not affected: 170 recommended: 186 | 2026-07-26T00:34:43+00:00 | Vulnerability · Source |
| CVE-2017-12692 | suse_vex | SUSE CVE CVE-2017-12692 | known affected: 94 recommended: 172 | 2026-07-26T00:34:41+00:00 | Vulnerability · Source |
| CVE-2017-12805 | suse_vex | SUSE CVE CVE-2017-12805 | known affected: 96 known not affected: 46 recommended: 168 | 2026-07-26T00:34:39+00:00 | Vulnerability · Source |
| CVE-2017-12843 | suse_vex | SUSE CVE CVE-2017-12843 | known not affected: 34 | 2026-07-26T00:34:34+00:00 | Vulnerability · Source |
| CVE-2017-12985 | suse_vex | SUSE CVE CVE-2017-12985 | known affected: 336 known not affected: 24 recommended: 151 | 2026-07-26T00:34:20+00:00 | Vulnerability · Source |
| CVE-2017-12993 | suse_vex | SUSE CVE CVE-2017-12993 | known affected: 336 known not affected: 24 recommended: 151 | 2026-07-26T00:34:12+00:00 | Vulnerability · Source |
| CVE-2017-12997 | suse_vex | SUSE CVE CVE-2017-12997 | known affected: 336 known not affected: 24 recommended: 147 | 2026-07-26T00:34:07+00:00 | Vulnerability · Source |
| CVE-2017-13007 | suse_vex | SUSE CVE CVE-2017-13007 | known affected: 336 known not affected: 24 recommended: 147 | 2026-07-26T00:33:56+00:00 | Vulnerability · Source |
| CVE-2017-13011 | suse_vex | SUSE CVE CVE-2017-13011 | known affected: 336 known not affected: 24 recommended: 151 | 2026-07-26T00:33:52+00:00 | Vulnerability · Source |
| CVE-2017-13019 | suse_vex | SUSE CVE CVE-2017-13019 | known affected: 336 known not affected: 24 recommended: 151 | 2026-07-26T00:33:47+00:00 | Vulnerability · Source |