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-18888 | suse_vex | SUSE CVE CVE-2017-18888 | No product status | 2026-08-01T23:35:31+00:00 | Vulnerability · Source |
| CVE-2017-18894 | suse_vex | SUSE CVE CVE-2017-18894 | No product status | 2026-08-01T23:35:28+00:00 | Vulnerability · Source |
| CVE-2017-18900 | suse_vex | SUSE CVE CVE-2017-18900 | No product status | 2026-08-01T23:35:26+00:00 | Vulnerability · Source |
| CVE-2018-2582 | suse_vex | SUSE CVE CVE-2018-2582 | known affected: 73 known not affected: 279 recommended: 669 | 2026-08-01T23:35:18+00:00 | Vulnerability · Source |
| CVE-2018-2641 | suse_vex | SUSE CVE CVE-2018-2641 | known affected: 73 known not affected: 263 recommended: 730 | 2026-08-01T23:35:15+00:00 | Vulnerability · Source |
| CVE-2018-3064 | suse_vex | SUSE CVE CVE-2018-3064 | known affected: 65 known not affected: 59 recommended: 590 | 2026-08-01T23:35:14+00:00 | Vulnerability · Source |
| CVE-2018-3180 | suse_vex | SUSE CVE CVE-2018-3180 | known affected: 411 known not affected: 55 recommended: 1133 | 2026-08-01T23:35:12+00:00 | Vulnerability · Source |
| CVE-2018-4127 | suse_vex | SUSE CVE CVE-2018-4127 | known affected: 116 known not affected: 169 recommended: 915 | 2026-08-01T23:35:07+00:00 | Vulnerability · Source |
| CVE-2018-4213 | suse_vex | SUSE CVE CVE-2018-4213 | known affected: 108 known not affected: 82 recommended: 959 | 2026-08-01T23:35:05+00:00 | Vulnerability · Source |
| CVE-2018-4265 | suse_vex | SUSE CVE CVE-2018-4265 | known affected: 108 known not affected: 82 recommended: 957 | 2026-08-01T23:35:03+00:00 | Vulnerability · Source |
| CVE-2018-4311 | suse_vex | SUSE CVE CVE-2018-4311 | known affected: 108 known not affected: 82 | 2026-08-01T23:35:02+00:00 | Vulnerability · Source |
| CVE-2018-5097 | suse_vex | SUSE CVE CVE-2018-5097 | known affected: 2 recommended: 408 | 2026-08-01T23:34:59+00:00 | Vulnerability · Source |
| CVE-2018-5130 | suse_vex | SUSE CVE CVE-2018-5130 | known affected: 2 recommended: 311 | 2026-08-01T23:34:58+00:00 | Vulnerability · Source |
| CVE-2018-5144 | suse_vex | SUSE CVE CVE-2018-5144 | known affected: 2 recommended: 384 | 2026-08-01T23:34:57+00:00 | Vulnerability · Source |
| CVE-2018-5163 | suse_vex | SUSE CVE CVE-2018-5163 | known affected: 26 recommended: 83 | 2026-08-01T23:34:56+00:00 | Vulnerability · Source |
| CVE-2018-5167 | suse_vex | SUSE CVE CVE-2018-5167 | known affected: 26 recommended: 83 | 2026-08-01T23:34:55+00:00 | Vulnerability · Source |
| CVE-2018-7544 | suse_vex | SUSE CVE CVE-2018-7544 | known affected: 43 known not affected: 42 recommended: 165 | 2026-08-01T23:34:51+00:00 | Vulnerability · Source |
| CVE-2018-7549 | suse_vex | SUSE CVE CVE-2018-7549 | known affected: 17 known not affected: 45 recommended: 16 | 2026-08-01T23:34:50+00:00 | Vulnerability · Source |
| CVE-2018-7730 | suse_vex | SUSE CVE CVE-2018-7730 | known affected: 5 known not affected: 60 recommended: 154 | 2026-08-01T23:34:49+00:00 | Vulnerability · Source |
| CVE-2018-8897 | suse_vex | SUSE CVE CVE-2018-8897 | known affected: 338 known not affected: 342 recommended: 930 | 2026-08-01T23:34:45+00:00 | Vulnerability · Source |
| CVE-2018-10903 | suse_vex | SUSE CVE CVE-2018-10903 | known affected: 382 recommended: 310 | 2026-08-01T23:34:43+00:00 | Vulnerability · Source |
| CVE-2018-10910 | suse_vex | SUSE CVE CVE-2018-10910 | known not affected: 123 recommended: 11 | 2026-08-01T23:34:42+00:00 | Vulnerability · Source |
| CVE-2018-11489 | suse_vex | SUSE CVE CVE-2018-11489 | known affected: 2 known not affected: 103 | 2026-08-01T23:34:40+00:00 | Vulnerability · Source |
| CVE-2018-12193 | suse_vex | SUSE CVE CVE-2018-12193 | known not affected: 111 | 2026-08-01T23:34:37+00:00 | Vulnerability · Source |
| CVE-2018-12207 | suse_vex | SUSE CVE CVE-2018-12207 | known affected: 633 known not affected: 238 recommended: 2940 | 2026-08-01T23:34:36+00:00 | Vulnerability · Source |
| CVE-2018-12364 | suse_vex | SUSE CVE CVE-2018-12364 | known affected: 21 recommended: 451 | 2026-08-01T23:34:35+00:00 | Vulnerability · Source |
| CVE-2018-12375 | suse_vex | SUSE CVE CVE-2018-12375 | known not affected: 200 recommended: 9 | 2026-08-01T23:34:34+00:00 | Vulnerability · Source |
| CVE-2018-13096 | suse_vex | SUSE CVE CVE-2018-13096 | known not affected: 206 | 2026-08-01T23:34:32+00:00 | Vulnerability · Source |
| CVE-2018-14610 | suse_vex | SUSE CVE CVE-2018-14610 | known affected: 7 known not affected: 408 | 2026-08-01T23:34:29+00:00 | Vulnerability · Source |
| CVE-2018-16749 | suse_vex | SUSE CVE CVE-2018-16749 | known affected: 95 known not affected: 46 recommended: 186 | 2026-08-01T23:34:25+00:00 | Vulnerability · Source |
| CVE-2018-18312 | suse_vex | SUSE CVE CVE-2018-18312 | known affected: 341 known not affected: 145 recommended: 372 | 2026-08-01T23:34:20+00:00 | Vulnerability · Source |
| CVE-2018-18397 | suse_vex | SUSE CVE CVE-2018-18397 | known affected: 49 known not affected: 438 recommended: 430 | 2026-08-01T23:34:19+00:00 | Vulnerability · Source |
| CVE-2018-18650 | suse_vex | SUSE CVE CVE-2018-18650 | known not affected: 573 | 2026-08-01T23:34:16+00:00 | Vulnerability · Source |
| CVE-2018-19622 | suse_vex | SUSE CVE CVE-2018-19622 | known affected: 111 known not affected: 37 recommended: 925 | 2026-08-01T23:34:14+00:00 | Vulnerability · Source |
| CVE-2018-20019 | suse_vex | SUSE CVE CVE-2018-20019 | known affected: 41 recommended: 129 | 2026-08-01T23:34:13+00:00 | Vulnerability · Source |
| CVE-2018-20467 | suse_vex | SUSE CVE CVE-2018-20467 | known affected: 46 recommended: 826 | 2026-08-01T23:34:11+00:00 | Vulnerability · Source |
| CVE-2018-20784 | suse_vex | SUSE CVE CVE-2018-20784 | known not affected: 491 recommended: 137 | 2026-08-01T23:34:09+00:00 | Vulnerability · Source |
| CVE-2018-21258 | suse_vex | SUSE CVE CVE-2018-21258 | No product status | 2026-08-01T23:34:08+00:00 | Vulnerability · Source |
| CVE-2018-25020 | suse_vex | SUSE CVE CVE-2018-25020 | known affected: 433 known not affected: 238 recommended: 438 | 2026-08-01T23:34:06+00:00 | Vulnerability · Source |
| CVE-2019-2981 | suse_vex | SUSE CVE CVE-2019-2981 | known affected: 525 recommended: 1129 | 2026-08-01T23:34:00+00:00 | Vulnerability · Source |
| CVE-2019-3018 | suse_vex | SUSE CVE CVE-2019-3018 | known affected: 13 known not affected: 121 recommended: 10 | 2026-08-01T23:33:59+00:00 | Vulnerability · Source |
| CVE-2019-3560 | suse_vex | SUSE CVE CVE-2019-3560 | recommended: 204 | 2026-08-01T23:33:58+00:00 | Vulnerability · Source |
| CVE-2019-4732 | suse_vex | SUSE CVE CVE-2019-4732 | known affected: 423 recommended: 311 | 2026-08-01T23:33:54+00:00 | Vulnerability · Source |
| CVE-2019-8587 | suse_vex | SUSE CVE CVE-2019-8587 | known affected: 153 known not affected: 82 recommended: 298 | 2026-08-01T23:33:50+00:00 | Vulnerability · Source |
| CVE-2019-8611 | suse_vex | SUSE CVE CVE-2019-8611 | known affected: 153 known not affected: 82 recommended: 298 | 2026-08-01T23:33:49+00:00 | Vulnerability · Source |
| CVE-2019-9457 | suse_vex | SUSE CVE CVE-2019-9457 | known affected: 6 known not affected: 256 | 2026-08-01T23:33:47+00:00 | Vulnerability · Source |
| CVE-2019-9495 | suse_vex | SUSE CVE CVE-2019-9495 | known affected: 8 known not affected: 10 recommended: 98 | 2026-08-01T23:33:46+00:00 | Vulnerability · Source |
| CVE-2019-9498 | suse_vex | SUSE CVE CVE-2019-9498 | known affected: 2 known not affected: 10 recommended: 95 | 2026-08-01T23:33:45+00:00 | Vulnerability · Source |
| CVE-2019-9788 | suse_vex | SUSE CVE CVE-2019-9788 | known affected: 20 known not affected: 76 recommended: 384 | 2026-08-01T23:33:43+00:00 | Vulnerability · Source |
| CVE-2019-9857 | suse_vex | SUSE CVE CVE-2019-9857 | known not affected: 335 | 2026-08-01T23:33:41+00:00 | Vulnerability · Source |