VEX records
Browse vendor VEX statements available in this Vulnerability-Lookup instance and pivot to the related vulnerability.
291890 VEX records
API response| Vulnerability | Source | Title | Product status | Imported | Links |
|---|---|---|---|---|---|
| CVE-2017-12563 | suse_vex | SUSE CVE CVE-2017-12563 | known affected: 95 recommended: 186 | 2026-08-05T01:28:48+00:00 | Vulnerability · Source |
| CVE-2017-12989 | suse_vex | SUSE CVE CVE-2017-12989 | known affected: 336 known not affected: 24 recommended: 147 | 2026-08-05T01:28:46+00:00 | Vulnerability · Source |
| CVE-2017-13003 | suse_vex | SUSE CVE CVE-2017-13003 | known affected: 336 known not affected: 24 recommended: 151 | 2026-08-05T01:28:44+00:00 | Vulnerability · Source |
| CVE-2017-13051 | suse_vex | SUSE CVE CVE-2017-13051 | known affected: 336 known not affected: 24 recommended: 151 | 2026-08-05T01:28:42+00:00 | Vulnerability · Source |
| CVE-2017-13084 | suse_vex | SUSE CVE CVE-2017-13084 | known affected: 6 known not affected: 354 | 2026-08-05T01:28:40+00:00 | Vulnerability · Source |
| CVE-2017-13147 | suse_vex | SUSE CVE CVE-2017-13147 | known affected: 94 recommended: 186 | 2026-08-05T01:28:38+00:00 | Vulnerability · Source |
| CVE-2017-13673 | suse_vex | SUSE CVE CVE-2017-13673 | known affected: 394 known not affected: 163 recommended: 1738 | 2026-08-05T01:28:34+00:00 | Vulnerability · Source |
| CVE-2017-13721 | suse_vex | SUSE CVE CVE-2017-13721 | known affected: 394 known not affected: 29 recommended: 262 | 2026-08-05T01:28:32+00:00 | Vulnerability · Source |
| CVE-2017-14245 | suse_vex | SUSE CVE CVE-2017-14245 | known affected: 394 known not affected: 68 recommended: 179 | 2026-08-05T01:28:29+00:00 | Vulnerability · Source |
| CVE-2017-14248 | suse_vex | SUSE CVE CVE-2017-14248 | known not affected: 301 | 2026-08-05T01:28:27+00:00 | Vulnerability · Source |
| CVE-2017-14952 | suse_vex | SUSE CVE CVE-2017-14952 | recommended: 136 | 2026-08-05T01:28:25+00:00 | Vulnerability · Source |
| CVE-2017-14994 | suse_vex | SUSE CVE CVE-2017-14994 | known affected: 3 known not affected: 128 recommended: 14 | 2026-08-05T01:28:24+00:00 | Vulnerability · Source |
| CVE-2017-15275 | suse_vex | SUSE CVE CVE-2017-15275 | known affected: 854 known not affected: 475 recommended: 3972 | 2026-08-05T01:28:21+00:00 | Vulnerability · Source |
| CVE-2017-15281 | suse_vex | SUSE CVE CVE-2017-15281 | known affected: 95 known not affected: 14 recommended: 172 | 2026-08-05T01:28:20+00:00 | Vulnerability · Source |
| CVE-2017-15400 | suse_vex | SUSE CVE CVE-2017-15400 | known not affected: 123 | 2026-08-05T01:28:18+00:00 | Vulnerability · Source |
| CVE-2017-15412 | suse_vex | SUSE CVE CVE-2017-15412 | known affected: 394 known not affected: 6 recommended: 161 | 2026-08-05T01:28:17+00:00 | Vulnerability · Source |
| CVE-2017-16526 | suse_vex | SUSE CVE CVE-2017-16526 | known not affected: 570 | 2026-08-05T01:28:15+00:00 | Vulnerability · Source |
| CVE-2017-18237 | suse_vex | SUSE CVE CVE-2017-18237 | known not affected: 178 | 2026-08-05T01:28:10+00:00 | Vulnerability · Source |
| CVE-2017-1000158 | suse_vex | SUSE CVE CVE-2017-1000158 | known affected: 480 known not affected: 16 recommended: 777 | 2026-08-05T01:28:08+00:00 | Vulnerability · Source |
| CVE-2017-1000409 | suse_vex | SUSE CVE CVE-2017-1000409 | known affected: 61 known not affected: 266 recommended: 1108 | 2026-08-05T01:28:06+00:00 | Vulnerability · Source |
| CVE-2018-1053 | suse_vex | SUSE CVE CVE-2018-1053 | known not affected: 46 recommended: 433 | 2026-08-05T01:28:04+00:00 | Vulnerability · Source |
| CVE-2018-1066 | suse_vex | SUSE CVE CVE-2018-1066 | known not affected: 77 recommended: 80 | 2026-08-05T01:28:02+00:00 | Vulnerability · Source |
| CVE-2018-5147 | suse_vex | SUSE CVE CVE-2018-5147 | known affected: 27 known not affected: 229 recommended: 310 | 2026-08-05T01:27:52+00:00 | Vulnerability · Source |
| CVE-2018-5745 | suse_vex | SUSE CVE CVE-2018-5745 | known affected: 428 known not affected: 1 recommended: 1076 | 2026-08-05T01:27:48+00:00 | Vulnerability · Source |
| CVE-2018-6081 | suse_vex | SUSE CVE CVE-2018-6081 | recommended: 10 | 2026-08-05T01:27:47+00:00 | Vulnerability · Source |
| CVE-2018-7419 | suse_vex | SUSE CVE CVE-2018-7419 | known affected: 1 known not affected: 115 recommended: 589 | 2026-08-05T01:27:44+00:00 | Vulnerability · Source |
| CVE-2018-10675 | suse_vex | SUSE CVE CVE-2018-10675 | known affected: 2 known not affected: 158 recommended: 203 | 2026-08-05T01:27:39+00:00 | Vulnerability · Source |
| CVE-2018-12120 | suse_vex | SUSE CVE CVE-2018-12120 | known affected: 40 known not affected: 76 recommended: 84 | 2026-08-05T01:27:36+00:00 | Vulnerability · Source |
| CVE-2018-13153 | suse_vex | SUSE CVE CVE-2018-13153 | recommended: 34 | 2026-08-05T01:27:32+00:00 | Vulnerability · Source |
| CVE-2018-14665 | suse_vex | SUSE CVE CVE-2018-14665 | known affected: 394 known not affected: 58 recommended: 269 | 2026-08-05T01:27:29+00:00 | Vulnerability · Source |
| CVE-2018-15862 | suse_vex | SUSE CVE CVE-2018-15862 | known affected: 565 known not affected: 65 recommended: 391 | 2026-08-05T01:27:26+00:00 | Vulnerability · Source |
| CVE-2018-16869 | suse_vex | SUSE CVE CVE-2018-16869 | known affected: 320 recommended: 425 | 2026-08-05T01:27:23+00:00 | Vulnerability · Source |
| CVE-2018-19134 | suse_vex | SUSE CVE CVE-2018-19134 | known affected: 1 known not affected: 189 recommended: 5 | 2026-08-05T01:27:17+00:00 | Vulnerability · Source |
| CVE-2018-19539 | suse_vex | SUSE CVE CVE-2018-19539 | known affected: 60 recommended: 176 | 2026-08-05T01:27:16+00:00 | Vulnerability · Source |
| CVE-2018-19543 | suse_vex | SUSE CVE CVE-2018-19543 | known affected: 46 recommended: 154 | 2026-08-05T01:27:14+00:00 | Vulnerability · Source |
| CVE-2018-20449 | suse_vex | SUSE CVE CVE-2018-20449 | known not affected: 83 | 2026-08-05T01:27:12+00:00 | Vulnerability · Source |
| CVE-2018-21010 | suse_vex | SUSE CVE CVE-2018-21010 | known affected: 1 known not affected: 365 recommended: 314 | 2026-08-05T01:27:08+00:00 | Vulnerability · Source |
| CVE-2019-0217 | suse_vex | SUSE CVE CVE-2019-0217 | known affected: 111 known not affected: 4 recommended: 291 | 2026-08-05T01:27:03+00:00 | Vulnerability · Source |
| CVE-2019-2455 | suse_vex | SUSE CVE CVE-2019-2455 | known affected: 70 known not affected: 185 recommended: 10 | 2026-08-05T01:27:02+00:00 | Vulnerability · Source |
| CVE-2019-7283 | suse_vex | SUSE CVE CVE-2019-7283 | known affected: 6 | 2026-08-05T01:26:56+00:00 | Vulnerability · Source |
| CVE-2019-9448 | suse_vex | SUSE CVE CVE-2019-9448 | known not affected: 215 | 2026-08-05T01:26:51+00:00 | Vulnerability · Source |
| CVE-2019-9514 | suse_vex | SUSE CVE CVE-2019-9514 | known affected: 82 known not affected: 262 recommended: 563 | 2026-08-05T01:26:50+00:00 | Vulnerability · Source |
| CVE-2019-9674 | suse_vex | SUSE CVE CVE-2019-9674 | known affected: 402 known not affected: 233 recommended: 1602 | 2026-08-05T01:26:48+00:00 | Vulnerability · Source |
| CVE-2019-9704 | suse_vex | SUSE CVE CVE-2019-9704 | known affected: 405 recommended: 155 | 2026-08-05T01:26:46+00:00 | Vulnerability · Source |
| CVE-2019-9717 | suse_vex | SUSE CVE CVE-2019-9717 | No product status | 2026-08-05T01:26:45+00:00 | Vulnerability · Source |
| CVE-2019-9720 | suse_vex | SUSE CVE CVE-2019-9720 | No product status | 2026-08-05T01:26:43+00:00 | Vulnerability · Source |
| CVE-2019-10098 | suse_vex | SUSE CVE CVE-2019-10098 | known affected: 510 known not affected: 52 recommended: 402 | 2026-08-05T01:26:41+00:00 | Vulnerability · Source |
| CVE-2019-11085 | suse_vex | SUSE CVE CVE-2019-11085 | known affected: 87 known not affected: 85 recommended: 666 | 2026-08-05T01:26:38+00:00 | Vulnerability · Source |
| CVE-2019-11692 | suse_vex | SUSE CVE CVE-2019-11692 | known affected: 20 known not affected: 8 recommended: 412 | 2026-08-05T01:26:36+00:00 | Vulnerability · Source |
| CVE-2019-11707 | suse_vex | SUSE CVE CVE-2019-11707 | recommended: 429 | 2026-08-05T01:26:34+00:00 | Vulnerability · Source |