VEX records
Browse vendor VEX statements available in this Vulnerability-Lookup instance and pivot to the related vulnerability.
291911 VEX records
API response| Vulnerability | Source | Title | Product status | Imported | Links |
|---|---|---|---|---|---|
| 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 |
| CVE-2019-9948 | suse_vex | SUSE CVE CVE-2019-9948 | known affected: 458 known not affected: 289 recommended: 834 | 2026-08-01T23:33:40+00:00 | Vulnerability · Source |
| CVE-2019-11486 | suse_vex | SUSE CVE CVE-2019-11486 | known affected: 107 known not affected: 21 recommended: 841 | 2026-08-01T23:33:34+00:00 | Vulnerability · Source |
| CVE-2019-11757 | suse_vex | SUSE CVE CVE-2019-11757 | known not affected: 160 recommended: 450 | 2026-08-01T23:33:33+00:00 | Vulnerability · Source |
| CVE-2019-13111 | suse_vex | SUSE CVE CVE-2019-13111 | known affected: 60 known not affected: 131 recommended: 139 | 2026-08-01T23:33:31+00:00 | Vulnerability · Source |
| CVE-2019-13115 | suse_vex | SUSE CVE CVE-2019-13115 | known not affected: 233 | 2026-08-01T23:33:30+00:00 | Vulnerability · Source |
| CVE-2019-14899 | suse_vex | SUSE CVE CVE-2019-14899 | known not affected: 371 | 2026-08-01T23:33:27+00:00 | Vulnerability · Source |
| CVE-2019-15292 | suse_vex | SUSE CVE CVE-2019-15292 | known affected: 95 known not affected: 224 recommended: 698 | 2026-08-01T23:33:24+00:00 | Vulnerability · Source |
| CVE-2019-16714 | suse_vex | SUSE CVE CVE-2019-16714 | known not affected: 223 | 2026-08-01T23:33:21+00:00 | Vulnerability · Source |
| CVE-2019-17624 | suse_vex | SUSE CVE CVE-2019-17624 | known affected: 40 known not affected: 71 | 2026-08-01T23:33:20+00:00 | Vulnerability · Source |
| CVE-2019-18282 | suse_vex | SUSE CVE CVE-2019-18282 | known not affected: 426 recommended: 33 | 2026-08-01T23:33:18+00:00 | Vulnerability · Source |
| CVE-2019-18902 | suse_vex | SUSE CVE CVE-2019-18902 | known affected: 361 known not affected: 18 recommended: 245 | 2026-08-01T23:33:15+00:00 | Vulnerability · Source |
| CVE-2019-19071 | suse_vex | SUSE CVE CVE-2019-19071 | known affected: 320 known not affected: 376 recommended: 781 | 2026-08-01T23:33:14+00:00 | Vulnerability · Source |
| CVE-2019-19449 | suse_vex | SUSE CVE CVE-2019-19449 | known not affected: 459 | 2026-08-01T23:33:11+00:00 | Vulnerability · Source |
| CVE-2019-20382 | suse_vex | SUSE CVE CVE-2019-20382 | known affected: 196 known not affected: 180 recommended: 505 | 2026-08-01T23:33:09+00:00 | Vulnerability · Source |
| CVE-2020-0030 | suse_vex | SUSE CVE CVE-2020-0030 | known not affected: 204 | 2026-08-01T23:33:07+00:00 | Vulnerability · Source |
| CVE-2020-10134 | suse_vex | SUSE CVE CVE-2020-10134 | known affected: 3 | 2026-08-01T23:32:57+00:00 | Vulnerability · Source |
| CVE-2020-13249 | suse_vex | SUSE CVE CVE-2020-13249 | known affected: 75 known not affected: 69 recommended: 648 | 2026-08-01T23:32:51+00:00 | Vulnerability · Source |
| CVE-2020-13435 | suse_vex | SUSE CVE CVE-2020-13435 | known affected: 364 known not affected: 279 recommended: 459 | 2026-08-01T23:32:49+00:00 | Vulnerability · Source |
| CVE-2020-13791 | suse_vex | SUSE CVE CVE-2020-13791 | known not affected: 538 | 2026-08-01T23:32:48+00:00 | Vulnerability · Source |
| CVE-2020-13962 | suse_vex | SUSE CVE CVE-2020-13962 | known affected: 394 known not affected: 1364 recommended: 2088 | 2026-08-01T23:32:46+00:00 | Vulnerability · Source |
| CVE-2020-14303 | suse_vex | SUSE CVE CVE-2020-14303 | known affected: 675 known not affected: 822 recommended: 3070 | 2026-08-01T23:32:44+00:00 | Vulnerability · Source |
| CVE-2020-14579 | suse_vex | SUSE CVE CVE-2020-14579 | known affected: 170 recommended: 945 | 2026-08-01T23:32:41+00:00 | Vulnerability · Source |
| CVE-2020-16591 | suse_vex | SUSE CVE CVE-2020-16591 | known affected: 395 known not affected: 85 recommended: 540 | 2026-08-01T23:32:39+00:00 | Vulnerability · Source |
| CVE-2020-25624 | suse_vex | SUSE CVE CVE-2020-25624 | known affected: 388 known not affected: 587 recommended: 850 | 2026-08-01T23:32:36+00:00 | Vulnerability · Source |
| CVE-2020-25650 | suse_vex | SUSE CVE CVE-2020-25650 | known affected: 13 recommended: 67 | 2026-08-01T23:32:34+00:00 | Vulnerability · Source |
| CVE-2020-25684 | suse_vex | SUSE CVE CVE-2020-25684 | recommended: 113 | 2026-08-01T23:32:32+00:00 | Vulnerability · Source |