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-6311 | suse_vex | SUSE CVE CVE-2017-6311 | known affected: 14 known not affected: 60 | 2026-07-26T00:44:35+00:00 | Vulnerability · Source |
| CVE-2017-6312 | suse_vex | SUSE CVE CVE-2017-6312 | known affected: 397 known not affected: 828 recommended: 672 | 2026-07-26T00:44:33+00:00 | Vulnerability · Source |
| CVE-2017-6317 | suse_vex | SUSE CVE CVE-2017-6317 | recommended: 29 | 2026-07-26T00:44:32+00:00 | Vulnerability · Source |
| CVE-2017-6348 | suse_vex | SUSE CVE CVE-2017-6348 | known affected: 2 known not affected: 319 recommended: 233 | 2026-07-26T00:44:31+00:00 | Vulnerability · Source |
| CVE-2017-6353 | suse_vex | SUSE CVE CVE-2017-6353 | known affected: 14 known not affected: 345 recommended: 423 | 2026-07-26T00:44:29+00:00 | Vulnerability · Source |
| CVE-2017-6439 | suse_vex | SUSE CVE CVE-2017-6439 | recommended: 338 | 2026-07-26T00:44:18+00:00 | Vulnerability · Source |
| CVE-2017-6462 | suse_vex | SUSE CVE CVE-2017-6462 | known affected: 31 recommended: 103 | 2026-07-26T00:44:16+00:00 | Vulnerability · Source |
| CVE-2017-6508 | suse_vex | SUSE CVE CVE-2017-6508 | known affected: 337 known not affected: 24 recommended: 169 | 2026-07-26T00:44:11+00:00 | Vulnerability · Source |
| CVE-2017-6590 | suse_vex | SUSE CVE CVE-2017-6590 | known not affected: 172 recommended: 253 | 2026-07-26T00:44:09+00:00 | Vulnerability · Source |
| CVE-2017-6828 | suse_vex | SUSE CVE CVE-2017-6828 | known affected: 45 recommended: 202 | 2026-07-26T00:44:07+00:00 | Vulnerability · Source |
| CVE-2017-6830 | suse_vex | SUSE CVE CVE-2017-6830 | known affected: 45 recommended: 202 | 2026-07-26T00:44:05+00:00 | Vulnerability · Source |
| CVE-2017-6833 | suse_vex | SUSE CVE CVE-2017-6833 | known affected: 45 recommended: 196 | 2026-07-26T00:44:04+00:00 | Vulnerability · Source |
| CVE-2017-6834 | suse_vex | SUSE CVE CVE-2017-6834 | known affected: 45 recommended: 202 | 2026-07-26T00:44:02+00:00 | Vulnerability · Source |
| CVE-2017-6835 | suse_vex | SUSE CVE CVE-2017-6835 | known affected: 45 recommended: 202 | 2026-07-26T00:44:00+00:00 | Vulnerability · Source |
| CVE-2017-6852 | suse_vex | SUSE CVE CVE-2017-6852 | known not affected: 100 | 2026-07-26T00:43:58+00:00 | Vulnerability · Source |
| CVE-2017-6874 | suse_vex | SUSE CVE CVE-2017-6874 | known not affected: 343 | 2026-07-26T00:43:56+00:00 | Vulnerability · Source |
| CVE-2017-6892 | suse_vex | SUSE CVE CVE-2017-6892 | known affected: 394 known not affected: 14 recommended: 165 | 2026-07-26T00:43:53+00:00 | Vulnerability · Source |
| CVE-2017-6965 | suse_vex | SUSE CVE CVE-2017-6965 | known affected: 394 known not affected: 158 recommended: 340 | 2026-07-26T00:43:51+00:00 | Vulnerability · Source |
| CVE-2017-7006 | suse_vex | SUSE CVE CVE-2017-7006 | known affected: 12 known not affected: 329 recommended: 939 | 2026-07-26T00:43:49+00:00 | Vulnerability · Source |
| CVE-2017-7018 | suse_vex | SUSE CVE CVE-2017-7018 | known affected: 12 known not affected: 329 recommended: 927 | 2026-07-26T00:43:46+00:00 | Vulnerability · Source |
| CVE-2017-7019 | suse_vex | SUSE CVE CVE-2017-7019 | known affected: 12 known not affected: 329 recommended: 939 | 2026-07-26T00:43:44+00:00 | Vulnerability · Source |
| CVE-2017-7043 | suse_vex | SUSE CVE CVE-2017-7043 | known affected: 12 known not affected: 329 recommended: 939 | 2026-07-26T00:43:33+00:00 | Vulnerability · Source |
| CVE-2017-7059 | suse_vex | SUSE CVE CVE-2017-7059 | known affected: 12 known not affected: 329 recommended: 927 | 2026-07-26T00:43:26+00:00 | Vulnerability · Source |
| CVE-2017-7061 | suse_vex | SUSE CVE CVE-2017-7061 | known affected: 12 known not affected: 329 recommended: 927 | 2026-07-26T00:43:24+00:00 | Vulnerability · Source |
| CVE-2017-7087 | suse_vex | SUSE CVE CVE-2017-7087 | known not affected: 87 recommended: 927 | 2026-07-26T00:43:21+00:00 | Vulnerability · Source |
| CVE-2017-7090 | suse_vex | SUSE CVE CVE-2017-7090 | known not affected: 87 recommended: 927 | 2026-07-26T00:43:19+00:00 | Vulnerability · Source |
| CVE-2017-7096 | suse_vex | SUSE CVE CVE-2017-7096 | known not affected: 87 recommended: 927 | 2026-07-26T00:43:11+00:00 | Vulnerability · Source |
| CVE-2017-7111 | suse_vex | SUSE CVE CVE-2017-7111 | known not affected: 87 recommended: 927 | 2026-07-26T00:43:09+00:00 | Vulnerability · Source |
| CVE-2017-7184 | suse_vex | SUSE CVE CVE-2017-7184 | known not affected: 394 recommended: 478 | 2026-07-26T00:43:00+00:00 | Vulnerability · Source |
| CVE-2017-7187 | suse_vex | SUSE CVE CVE-2017-7187 | known affected: 14 known not affected: 345 recommended: 435 | 2026-07-26T00:42:58+00:00 | Vulnerability · Source |
| CVE-2017-7209 | suse_vex | SUSE CVE CVE-2017-7209 | known affected: 442 known not affected: 21 recommended: 340 | 2026-07-26T00:42:56+00:00 | Vulnerability · Source |
| CVE-2017-7227 | suse_vex | SUSE CVE CVE-2017-7227 | known affected: 2 known not affected: 163 recommended: 54 | 2026-07-26T00:42:48+00:00 | Vulnerability · Source |
| CVE-2017-7228 | suse_vex | SUSE CVE CVE-2017-7228 | known affected: 13 recommended: 111 | 2026-07-26T00:42:46+00:00 | Vulnerability · Source |
| CVE-2017-7244 | suse_vex | SUSE CVE CVE-2017-7244 | known affected: 415 known not affected: 537 recommended: 644 | 2026-07-26T00:42:43+00:00 | Vulnerability · Source |
| CVE-2017-7261 | suse_vex | SUSE CVE CVE-2017-7261 | known not affected: 377 recommended: 416 | 2026-07-26T00:42:41+00:00 | Vulnerability · Source |
| CVE-2017-7273 | suse_vex | SUSE CVE CVE-2017-7273 | known affected: 55 known not affected: 336 recommended: 195 | 2026-07-26T00:42:39+00:00 | Vulnerability · Source |
| CVE-2017-7277 | suse_vex | SUSE CVE CVE-2017-7277 | known not affected: 136 recommended: 89 | 2026-07-26T00:42:37+00:00 | Vulnerability · Source |
| CVE-2017-7302 | suse_vex | SUSE CVE CVE-2017-7302 | known affected: 442 known not affected: 21 recommended: 340 | 2026-07-26T00:42:32+00:00 | Vulnerability · Source |
| CVE-2017-7319 | suse_vex | SUSE CVE CVE-2017-7319 | known not affected: 64 | 2026-07-26T00:42:28+00:00 | Vulnerability · Source |
| CVE-2017-7374 | suse_vex | SUSE CVE CVE-2017-7374 | known not affected: 773 recommended: 101 | 2026-07-26T00:42:25+00:00 | Vulnerability · Source |
| CVE-2017-7375 | suse_vex | SUSE CVE CVE-2017-7375 | known affected: 1 recommended: 108 | 2026-07-26T00:42:23+00:00 | Vulnerability · Source |
| CVE-2017-7392 | suse_vex | SUSE CVE CVE-2017-7392 | recommended: 34 | 2026-07-26T00:42:21+00:00 | Vulnerability · Source |
| CVE-2017-7393 | suse_vex | SUSE CVE CVE-2017-7393 | recommended: 34 | 2026-07-26T00:42:19+00:00 | Vulnerability · Source |
| CVE-2017-7395 | suse_vex | SUSE CVE CVE-2017-7395 | recommended: 34 | 2026-07-26T00:42:17+00:00 | Vulnerability · Source |
| CVE-2017-7435 | suse_vex | SUSE CVE CVE-2017-7435 | known affected: 354 known not affected: 30 recommended: 287 | 2026-07-26T00:42:15+00:00 | Vulnerability · Source |
| CVE-2017-7467 | suse_vex | SUSE CVE CVE-2017-7467 | known affected: 1 known not affected: 42 recommended: 134 | 2026-07-26T00:42:13+00:00 | Vulnerability · Source |
| CVE-2017-7471 | suse_vex | SUSE CVE CVE-2017-7471 | known affected: 420 known not affected: 137 recommended: 1812 | 2026-07-26T00:42:08+00:00 | Vulnerability · Source |
| CVE-2017-7472 | suse_vex | SUSE CVE CVE-2017-7472 | known affected: 23 known not affected: 319 recommended: 221 | 2026-07-26T00:42:06+00:00 | Vulnerability · Source |
| CVE-2017-7476 | suse_vex | SUSE CVE CVE-2017-7476 | known affected: 320 known not affected: 444 recommended: 606 | 2026-07-26T00:42:04+00:00 | Vulnerability · Source |
| CVE-2017-7484 | suse_vex | SUSE CVE CVE-2017-7484 | recommended: 154 | 2026-07-26T00:41:59+00:00 | Vulnerability · Source |