VEX records
Browse vendor VEX statements available in this Vulnerability-Lookup instance and pivot to the related vulnerability.
294016 VEX records
API response| Vulnerability | Source | Title | Product status | Imported | Links |
|---|---|---|---|---|---|
| CVE-2017-9984 | suse_vex | SUSE CVE CVE-2017-9984 | known not affected: 235 | 2026-07-26T00:38:06+00:00 | Vulnerability · Source |
| CVE-2017-9986 | suse_vex | SUSE CVE CVE-2017-9986 | known not affected: 343 | 2026-07-26T00:38:05+00:00 | Vulnerability · Source |
| CVE-2017-10090 | suse_vex | SUSE CVE CVE-2017-10090 | known affected: 15 known not affected: 109 recommended: 690 | 2026-07-26T00:37:59+00:00 | Vulnerability · Source |
| CVE-2017-10101 | suse_vex | SUSE CVE CVE-2017-10101 | known affected: 15 known not affected: 109 recommended: 690 | 2026-07-26T00:37:57+00:00 | Vulnerability · Source |
| CVE-2017-10108 | suse_vex | SUSE CVE CVE-2017-10108 | known affected: 15 known not affected: 109 recommended: 690 | 2026-07-26T00:37:54+00:00 | Vulnerability · Source |
| CVE-2017-10135 | suse_vex | SUSE CVE CVE-2017-10135 | recommended: 358 | 2026-07-26T00:37:45+00:00 | Vulnerability · Source |
| CVE-2017-10274 | suse_vex | SUSE CVE CVE-2017-10274 | known affected: 66 known not affected: 65 recommended: 358 | 2026-07-26T00:37:42+00:00 | Vulnerability · Source |
| CVE-2017-10350 | suse_vex | SUSE CVE CVE-2017-10350 | known affected: 87 known not affected: 328 recommended: 758 | 2026-07-26T00:37:31+00:00 | Vulnerability · Source |
| CVE-2017-10661 | suse_vex | SUSE CVE CVE-2017-10661 | known affected: 68 known not affected: 485 recommended: 283 | 2026-07-26T00:37:22+00:00 | Vulnerability · Source |
| CVE-2017-10685 | suse_vex | SUSE CVE CVE-2017-10685 | known affected: 1 recommended: 231 | 2026-07-26T00:37:20+00:00 | Vulnerability · Source |
| CVE-2017-10862 | suse_vex | SUSE CVE CVE-2017-10862 | known affected: 95 | 2026-07-26T00:37:15+00:00 | Vulnerability · Source |
| CVE-2017-10913 | suse_vex | SUSE CVE CVE-2017-10913 | known not affected: 1 recommended: 35 | 2026-07-26T00:37:14+00:00 | Vulnerability · Source |
| CVE-2017-10914 | suse_vex | SUSE CVE CVE-2017-10914 | known not affected: 1 recommended: 35 | 2026-07-26T00:37:12+00:00 | Vulnerability · Source |
| CVE-2017-10916 | suse_vex | SUSE CVE CVE-2017-10916 | known affected: 12 known not affected: 40 recommended: 21 | 2026-07-26T00:37:11+00:00 | Vulnerability · Source |
| CVE-2017-10917 | suse_vex | SUSE CVE CVE-2017-10917 | known affected: 13 known not affected: 3 recommended: 35 | 2026-07-26T00:37:09+00:00 | Vulnerability · Source |
| CVE-2017-10919 | suse_vex | SUSE CVE CVE-2017-10919 | known not affected: 73 | 2026-07-26T00:37:08+00:00 | Vulnerability · Source |
| CVE-2017-10972 | suse_vex | SUSE CVE CVE-2017-10972 | known affected: 11 known not affected: 15 recommended: 254 | 2026-07-26T00:37:07+00:00 | Vulnerability · Source |
| CVE-2017-10982 | suse_vex | SUSE CVE CVE-2017-10982 | known affected: 24 known not affected: 111 recommended: 26 | 2026-07-26T00:37:03+00:00 | Vulnerability · Source |
| CVE-2017-10989 | suse_vex | SUSE CVE CVE-2017-10989 | known affected: 464 known not affected: 151 recommended: 119 | 2026-07-26T00:37:00+00:00 | Vulnerability · Source |
| CVE-2017-11171 | suse_vex | SUSE CVE CVE-2017-11171 | known not affected: 24 recommended: 8 | 2026-07-26T00:36:57+00:00 | Vulnerability · Source |
| 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-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-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-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-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-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-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-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-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-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-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-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 |