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-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 |
| CVE-2017-7486 | suse_vex | SUSE CVE CVE-2017-7486 | recommended: 154 | 2026-07-26T00:41:57+00:00 | Vulnerability · Source |
| CVE-2017-7501 | suse_vex | SUSE CVE CVE-2017-7501 | known affected: 54 known not affected: 147 recommended: 121 | 2026-07-26T00:41:52+00:00 | Vulnerability · Source |
| CVE-2017-7516 | suse_vex | SUSE CVE CVE-2017-7516 | known not affected: 27 | 2026-07-26T00:41:50+00:00 | Vulnerability · Source |
| CVE-2017-7519 | suse_vex | SUSE CVE CVE-2017-7519 | known not affected: 33 recommended: 42 | 2026-07-26T00:41:48+00:00 | Vulnerability · Source |
| CVE-2017-7522 | suse_vex | SUSE CVE CVE-2017-7522 | known affected: 31 known not affected: 60 recommended: 191 | 2026-07-26T00:41:46+00:00 | Vulnerability · Source |
| CVE-2017-7548 | suse_vex | SUSE CVE CVE-2017-7548 | known affected: 98 known not affected: 45 recommended: 252 | 2026-07-26T00:41:42+00:00 | Vulnerability · Source |
| CVE-2017-7592 | suse_vex | SUSE CVE CVE-2017-7592 | known affected: 438 known not affected: 99 recommended: 264 | 2026-07-26T00:41:40+00:00 | Vulnerability · Source |
| CVE-2017-7594 | suse_vex | SUSE CVE CVE-2017-7594 | known affected: 438 known not affected: 99 recommended: 264 | 2026-07-26T00:41:38+00:00 | Vulnerability · Source |
| CVE-2017-7600 | suse_vex | SUSE CVE CVE-2017-7600 | known affected: 45 known not affected: 80 recommended: 281 | 2026-07-26T00:41:35+00:00 | Vulnerability · Source |
| CVE-2017-7607 | suse_vex | SUSE CVE CVE-2017-7607 | known affected: 522 recommended: 834 | 2026-07-26T00:41:33+00:00 | Vulnerability · Source |
| CVE-2017-7610 | suse_vex | SUSE CVE CVE-2017-7610 | known affected: 522 recommended: 834 | 2026-07-26T00:41:31+00:00 | Vulnerability · Source |
| CVE-2017-7611 | suse_vex | SUSE CVE CVE-2017-7611 | known affected: 522 recommended: 834 | 2026-07-26T00:41:29+00:00 | Vulnerability · Source |
| CVE-2017-7612 | suse_vex | SUSE CVE CVE-2017-7612 | known affected: 522 recommended: 834 | 2026-07-26T00:41:28+00:00 | Vulnerability · Source |
| CVE-2017-7613 | suse_vex | SUSE CVE CVE-2017-7613 | known affected: 522 known not affected: 1 recommended: 825 | 2026-07-26T00:41:26+00:00 | Vulnerability · Source |
| CVE-2017-7616 | suse_vex | SUSE CVE CVE-2017-7616 | known affected: 14 known not affected: 343 recommended: 346 | 2026-07-26T00:41:25+00:00 | Vulnerability · Source |
| CVE-2017-7618 | suse_vex | SUSE CVE CVE-2017-7618 | known affected: 12 known not affected: 425 recommended: 101 | 2026-07-26T00:41:24+00:00 | Vulnerability · Source |
| CVE-2017-7659 | suse_vex | SUSE CVE CVE-2017-7659 | known not affected: 63 recommended: 87 | 2026-07-26T00:41:22+00:00 | Vulnerability · Source |
| CVE-2017-7674 | suse_vex | SUSE CVE CVE-2017-7674 | known affected: 46 known not affected: 19 recommended: 154 | 2026-07-26T00:41:21+00:00 | Vulnerability · Source |
| CVE-2017-7701 | suse_vex | SUSE CVE CVE-2017-7701 | known affected: 1 recommended: 588 | 2026-07-26T00:41:17+00:00 | Vulnerability · Source |
| CVE-2017-7702 | suse_vex | SUSE CVE CVE-2017-7702 | known affected: 1 known not affected: 115 recommended: 588 | 2026-07-26T00:41:15+00:00 | Vulnerability · Source |
| CVE-2017-7741 | suse_vex | SUSE CVE CVE-2017-7741 | known affected: 1 recommended: 68 | 2026-07-26T00:41:11+00:00 | Vulnerability · Source |
| CVE-2017-7747 | suse_vex | SUSE CVE CVE-2017-7747 | known affected: 1 recommended: 588 | 2026-07-26T00:41:06+00:00 | Vulnerability · Source |
| CVE-2017-7751 | suse_vex | SUSE CVE CVE-2017-7751 | known affected: 2 known not affected: 42 recommended: 462 | 2026-07-26T00:41:02+00:00 | Vulnerability · Source |
| CVE-2017-7752 | suse_vex | SUSE CVE CVE-2017-7752 | known affected: 2 known not affected: 42 recommended: 462 | 2026-07-26T00:41:00+00:00 | Vulnerability · Source |
| CVE-2017-7754 | suse_vex | SUSE CVE CVE-2017-7754 | known affected: 2 known not affected: 42 recommended: 462 | 2026-07-26T00:40:58+00:00 | Vulnerability · Source |
| CVE-2017-7764 | suse_vex | SUSE CVE CVE-2017-7764 | known affected: 2 known not affected: 42 recommended: 462 | 2026-07-26T00:40:53+00:00 | Vulnerability · Source |