VEX records
Browse vendor VEX statements available in this Vulnerability-Lookup instance and pivot to the related vulnerability.
292115 VEX records
API response| Vulnerability | Source | Title | Product status | Imported | Links |
|---|---|---|---|---|---|
| CVE-2017-8816 | suse_vex | SUSE CVE CVE-2017-8816 | known affected: 322 known not affected: 80 recommended: 399 | 2026-07-26T00:39:34+00:00 | Vulnerability · Source |
| CVE-2017-8871 | suse_vex | SUSE CVE CVE-2017-8871 | known affected: 28 known not affected: 36 recommended: 232 | 2026-07-26T00:39:29+00:00 | Vulnerability · Source |
| CVE-2017-8908 | suse_vex | SUSE CVE CVE-2017-8908 | known affected: 6 known not affected: 59 | 2026-07-26T00:39:26+00:00 | Vulnerability · Source |
| CVE-2017-8924 | suse_vex | SUSE CVE CVE-2017-8924 | known affected: 2 known not affected: 7 recommended: 297 | 2026-07-26T00:39:25+00:00 | Vulnerability · Source |
| CVE-2017-8925 | suse_vex | SUSE CVE CVE-2017-8925 | known not affected: 643 recommended: 297 | 2026-07-26T00:39:23+00:00 | Vulnerability · Source |
| CVE-2017-9059 | suse_vex | SUSE CVE CVE-2017-9059 | known not affected: 136 recommended: 89 | 2026-07-26T00:39:20+00:00 | Vulnerability · Source |
| CVE-2017-9083 | suse_vex | SUSE CVE CVE-2017-9083 | known affected: 14 recommended: 12 | 2026-07-26T00:39:16+00:00 | Vulnerability · Source |
| CVE-2017-9105 | suse_vex | SUSE CVE CVE-2017-9105 | known affected: 18 recommended: 44 | 2026-07-26T00:39:14+00:00 | Vulnerability · Source |
| CVE-2017-9126 | suse_vex | SUSE CVE CVE-2017-9126 | known affected: 30 recommended: 208 | 2026-07-26T00:39:08+00:00 | Vulnerability · Source |
| CVE-2017-9147 | suse_vex | SUSE CVE CVE-2017-9147 | known not affected: 13 recommended: 22 | 2026-07-26T00:39:06+00:00 | Vulnerability · Source |
| CVE-2017-9150 | suse_vex | SUSE CVE CVE-2017-9150 | known not affected: 585 recommended: 101 | 2026-07-26T00:39:04+00:00 | Vulnerability · Source |
| CVE-2017-9217 | suse_vex | SUSE CVE CVE-2017-9217 | known affected: 130 known not affected: 71 recommended: 172 | 2026-07-26T00:39:00+00:00 | Vulnerability · Source |
| CVE-2017-9226 | suse_vex | SUSE CVE CVE-2017-9226 | known not affected: 2 recommended: 1295 | 2026-07-26T00:38:59+00:00 | Vulnerability · Source |
| CVE-2017-9227 | suse_vex | SUSE CVE CVE-2017-9227 | known affected: 1051 known not affected: 1408 recommended: 1295 | 2026-07-26T00:38:57+00:00 | Vulnerability · Source |
| CVE-2017-9228 | suse_vex | SUSE CVE CVE-2017-9228 | known affected: 3 known not affected: 1113 recommended: 1378 | 2026-07-26T00:38:55+00:00 | Vulnerability · Source |
| CVE-2017-9344 | suse_vex | SUSE CVE CVE-2017-9344 | known affected: 3 known not affected: 217 recommended: 559 | 2026-07-26T00:38:51+00:00 | Vulnerability · Source |
| CVE-2017-9347 | suse_vex | SUSE CVE CVE-2017-9347 | known affected: 3 known not affected: 217 recommended: 559 | 2026-07-26T00:38:49+00:00 | Vulnerability · Source |
| CVE-2017-9373 | suse_vex | SUSE CVE CVE-2017-9373 | known affected: 26 recommended: 124 | 2026-07-26T00:38:45+00:00 | Vulnerability · Source |
| CVE-2017-9405 | suse_vex | SUSE CVE CVE-2017-9405 | known affected: 94 recommended: 186 | 2026-07-26T00:38:43+00:00 | Vulnerability · Source |
| CVE-2017-9409 | suse_vex | SUSE CVE CVE-2017-9409 | known affected: 94 known not affected: 37 recommended: 172 | 2026-07-26T00:38:42+00:00 | Vulnerability · Source |
| CVE-2017-9439 | suse_vex | SUSE CVE CVE-2017-9439 | known affected: 60 recommended: 186 | 2026-07-26T00:38:40+00:00 | Vulnerability · Source |
| CVE-2017-9440 | suse_vex | SUSE CVE CVE-2017-9440 | known affected: 60 known not affected: 50 recommended: 136 | 2026-07-26T00:38:39+00:00 | Vulnerability · Source |
| CVE-2017-9461 | suse_vex | SUSE CVE CVE-2017-9461 | known not affected: 94 recommended: 26 | 2026-07-26T00:38:38+00:00 | Vulnerability · Source |
| CVE-2017-9499 | suse_vex | SUSE CVE CVE-2017-9499 | known not affected: 94 | 2026-07-26T00:38:37+00:00 | Vulnerability · Source |
| CVE-2017-9501 | suse_vex | SUSE CVE CVE-2017-9501 | known affected: 60 recommended: 186 | 2026-07-26T00:38:35+00:00 | Vulnerability · Source |
| CVE-2017-9606 | suse_vex | SUSE CVE CVE-2017-9606 | known not affected: 10 | 2026-07-26T00:38:34+00:00 | Vulnerability · Source |
| CVE-2017-9611 | suse_vex | SUSE CVE CVE-2017-9611 | known not affected: 31 recommended: 54 | 2026-07-26T00:38:33+00:00 | Vulnerability · Source |
| CVE-2017-9670 | suse_vex | SUSE CVE CVE-2017-9670 | known affected: 13 known not affected: 41 recommended: 89 | 2026-07-26T00:38:31+00:00 | Vulnerability · Source |
| CVE-2017-9725 | suse_vex | SUSE CVE CVE-2017-9725 | known not affected: 78 recommended: 12 | 2026-07-26T00:38:30+00:00 | Vulnerability · Source |
| CVE-2017-9726 | suse_vex | SUSE CVE CVE-2017-9726 | known affected: 1 recommended: 85 | 2026-07-26T00:38:29+00:00 | Vulnerability · Source |
| CVE-2017-9727 | suse_vex | SUSE CVE CVE-2017-9727 | known affected: 1 recommended: 85 | 2026-07-26T00:38:27+00:00 | Vulnerability · Source |
| CVE-2017-9739 | suse_vex | SUSE CVE CVE-2017-9739 | known affected: 2 known not affected: 137 recommended: 85 | 2026-07-26T00:38:26+00:00 | Vulnerability · Source |
| CVE-2017-9743 | suse_vex | SUSE CVE CVE-2017-9743 | known affected: 8 known not affected: 42 | 2026-07-26T00:38:25+00:00 | Vulnerability · Source |
| CVE-2017-9745 | suse_vex | SUSE CVE CVE-2017-9745 | known affected: 8 known not affected: 42 | 2026-07-26T00:38:24+00:00 | Vulnerability · Source |
| CVE-2017-9754 | suse_vex | SUSE CVE CVE-2017-9754 | known affected: 8 known not affected: 42 | 2026-07-26T00:38:23+00:00 | Vulnerability · Source |
| CVE-2017-9766 | suse_vex | SUSE CVE CVE-2017-9766 | known affected: 86 recommended: 162 | 2026-07-26T00:38:20+00:00 | Vulnerability · Source |
| CVE-2017-9775 | suse_vex | SUSE CVE CVE-2017-9775 | known affected: 60 known not affected: 39 recommended: 161 | 2026-07-26T00:38:18+00:00 | Vulnerability · Source |
| CVE-2017-9778 | suse_vex | SUSE CVE CVE-2017-9778 | known not affected: 64 | 2026-07-26T00:38:17+00:00 | Vulnerability · Source |
| CVE-2017-9788 | suse_vex | SUSE CVE CVE-2017-9788 | known not affected: 1 recommended: 160 | 2026-07-26T00:38:16+00:00 | Vulnerability · Source |
| CVE-2017-9865 | suse_vex | SUSE CVE CVE-2017-9865 | known affected: 60 known not affected: 39 recommended: 95 | 2026-07-26T00:38:13+00:00 | Vulnerability · Source |
| CVE-2017-9936 | suse_vex | SUSE CVE CVE-2017-9936 | known affected: 403 known not affected: 197 recommended: 232 | 2026-07-26T00:38:12+00:00 | Vulnerability · Source |
| CVE-2017-9954 | suse_vex | SUSE CVE CVE-2017-9954 | known not affected: 20 recommended: 54 | 2026-07-26T00:38:09+00:00 | Vulnerability · Source |
| CVE-2017-9955 | suse_vex | SUSE CVE CVE-2017-9955 | known affected: 1 known not affected: 134 recommended: 54 | 2026-07-26T00:38:08+00:00 | Vulnerability · Source |
| 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-10053 | suse_vex | SUSE CVE CVE-2017-10053 | known affected: 15 known not affected: 109 recommended: 690 | 2026-07-26T00:38:04+00:00 | Vulnerability · Source |
| CVE-2017-10067 | suse_vex | SUSE CVE CVE-2017-10067 | known affected: 15 known not affected: 109 recommended: 690 | 2026-07-26T00:38:02+00:00 | Vulnerability · Source |
| CVE-2017-10087 | suse_vex | SUSE CVE CVE-2017-10087 | known affected: 15 known not affected: 109 recommended: 690 | 2026-07-26T00:38:01+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 |