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-2018-15473 | suse_vex | SUSE CVE CVE-2018-15473 | known affected: 2 known not affected: 40 recommended: 162 | 2026-07-28T00:03:54+00:00 | Vulnerability · Source |
| CVE-2018-16062 | suse_vex | SUSE CVE CVE-2018-16062 | known affected: 485 recommended: 823 | 2026-07-28T00:03:52+00:00 | Vulnerability · Source |
| CVE-2018-16227 | suse_vex | SUSE CVE CVE-2018-16227 | known affected: 320 recommended: 138 | 2026-07-28T00:03:50+00:00 | Vulnerability · Source |
| CVE-2018-16510 | suse_vex | SUSE CVE CVE-2018-16510 | known affected: 13 known not affected: 27 recommended: 357 | 2026-07-28T00:03:44+00:00 | Vulnerability · Source |
| CVE-2018-16588 | suse_vex | SUSE CVE CVE-2018-16588 | known affected: 10 known not affected: 18 recommended: 1 | 2026-07-28T00:03:41+00:00 | Vulnerability · Source |
| CVE-2018-16881 | suse_vex | SUSE CVE CVE-2018-16881 | known affected: 412 known not affected: 107 recommended: 104 | 2026-07-28T00:03:37+00:00 | Vulnerability · Source |
| CVE-2018-17182 | suse_vex | SUSE CVE CVE-2018-17182 | known affected: 108 known not affected: 199 recommended: 774 | 2026-07-28T00:03:36+00:00 | Vulnerability · Source |
| CVE-2018-17965 | suse_vex | SUSE CVE CVE-2018-17965 | known affected: 1 known not affected: 46 recommended: 148 | 2026-07-28T00:03:32+00:00 | Vulnerability · Source |
| CVE-2018-18016 | suse_vex | SUSE CVE CVE-2018-18016 | known affected: 1 recommended: 284 | 2026-07-28T00:03:29+00:00 | Vulnerability · Source |
| CVE-2018-18335 | suse_vex | SUSE CVE CVE-2018-18335 | known affected: 20 recommended: 407 | 2026-07-28T00:03:22+00:00 | Vulnerability · Source |
| CVE-2018-18511 | suse_vex | SUSE CVE CVE-2018-18511 | known not affected: 70 recommended: 104 | 2026-07-28T00:03:20+00:00 | Vulnerability · Source |
| CVE-2018-19406 | suse_vex | SUSE CVE CVE-2018-19406 | known not affected: 132 | 2026-07-28T00:03:16+00:00 | Vulnerability · Source |
| CVE-2018-20099 | suse_vex | SUSE CVE CVE-2018-20099 | known not affected: 100 recommended: 96 | 2026-07-28T00:03:12+00:00 | Vulnerability · Source |
| CVE-2018-20623 | suse_vex | SUSE CVE CVE-2018-20623 | known affected: 394 recommended: 481 | 2026-07-28T00:03:09+00:00 | Vulnerability · Source |
| CVE-2018-20839 | suse_vex | SUSE CVE CVE-2018-20839 | known affected: 11 known not affected: 186 | 2026-07-28T00:03:07+00:00 | Vulnerability · Source |
| CVE-2018-20846 | suse_vex | SUSE CVE CVE-2018-20846 | known affected: 31 known not affected: 46 recommended: 315 | 2026-07-28T00:03:06+00:00 | Vulnerability · Source |
| CVE-2018-25018 | suse_vex | SUSE CVE CVE-2018-25018 | known not affected: 21 | 2026-07-28T00:03:04+00:00 | Vulnerability · Source |
| CVE-2018-25282 | suse_vex | SUSE CVE CVE-2018-25282 | known not affected: 31 | 2026-07-28T00:03:02+00:00 | Vulnerability · Source |
| CVE-2018-1000077 | suse_vex | SUSE CVE CVE-2018-1000077 | known affected: 323 known not affected: 68 recommended: 478 | 2026-07-28T00:02:59+00:00 | Vulnerability · Source |
| CVE-2018-1000121 | suse_vex | SUSE CVE CVE-2018-1000121 | known affected: 13 known not affected: 51 recommended: 341 | 2026-07-28T00:02:57+00:00 | Vulnerability · Source |
| CVE-2018-1000122 | suse_vex | SUSE CVE CVE-2018-1000122 | known affected: 321 known not affected: 51 recommended: 420 | 2026-07-28T00:02:55+00:00 | Vulnerability · Source |
| CVE-2019-2024 | suse_vex | SUSE CVE CVE-2019-2024 | known affected: 74 known not affected: 69 recommended: 523 | 2026-07-28T00:02:52+00:00 | Vulnerability · Source |
| CVE-2019-2529 | suse_vex | SUSE CVE CVE-2019-2529 | known affected: 53 known not affected: 173 recommended: 134 | 2026-07-28T00:02:48+00:00 | Vulnerability · Source |
| CVE-2019-2531 | suse_vex | SUSE CVE CVE-2019-2531 | known affected: 53 known not affected: 173 recommended: 10 | 2026-07-28T00:02:46+00:00 | Vulnerability · Source |
| CVE-2019-2816 | suse_vex | SUSE CVE CVE-2019-2816 | known affected: 402 known not affected: 6 recommended: 1106 | 2026-07-28T00:02:43+00:00 | Vulnerability · Source |
| CVE-2019-2910 | suse_vex | SUSE CVE CVE-2019-2910 | known affected: 7 known not affected: 98 | 2026-07-28T00:02:42+00:00 | Vulnerability · Source |
| CVE-2019-2922 | suse_vex | SUSE CVE CVE-2019-2922 | known affected: 7 known not affected: 98 | 2026-07-28T00:02:40+00:00 | Vulnerability · Source |
| CVE-2019-2923 | suse_vex | SUSE CVE CVE-2019-2923 | known affected: 7 known not affected: 98 | 2026-07-28T00:02:39+00:00 | Vulnerability · Source |
| CVE-2019-2945 | suse_vex | SUSE CVE CVE-2019-2945 | known affected: 482 recommended: 1067 | 2026-07-28T00:02:37+00:00 | Vulnerability · Source |
| CVE-2019-2950 | suse_vex | SUSE CVE CVE-2019-2950 | known affected: 7 known not affected: 98 recommended: 10 | 2026-07-28T00:02:36+00:00 | Vulnerability · Source |
| CVE-2019-3009 | suse_vex | SUSE CVE CVE-2019-3009 | known affected: 7 known not affected: 98 recommended: 10 | 2026-07-28T00:02:34+00:00 | Vulnerability · Source |
| CVE-2019-3835 | suse_vex | SUSE CVE CVE-2019-3835 | known affected: 33 recommended: 269 | 2026-07-28T00:02:31+00:00 | Vulnerability · Source |
| CVE-2019-3858 | suse_vex | SUSE CVE CVE-2019-3858 | known affected: 452 known not affected: 74 recommended: 255 | 2026-07-28T00:02:29+00:00 | Vulnerability · Source |
| CVE-2019-3900 | suse_vex | SUSE CVE CVE-2019-3900 | known affected: 384 known not affected: 159 recommended: 368 | 2026-07-28T00:02:27+00:00 | Vulnerability · Source |
| CVE-2019-3901 | suse_vex | SUSE CVE CVE-2019-3901 | known not affected: 232 recommended: 13 | 2026-07-28T00:02:26+00:00 | Vulnerability · Source |
| CVE-2019-5785 | suse_vex | SUSE CVE CVE-2019-5785 | known affected: 20 recommended: 407 | 2026-07-28T00:02:21+00:00 | Vulnerability · Source |
| CVE-2019-6488 | suse_vex | SUSE CVE CVE-2019-6488 | known not affected: 245 | 2026-07-28T00:02:18+00:00 | Vulnerability · Source |
| CVE-2019-6501 | suse_vex | SUSE CVE CVE-2019-6501 | known not affected: 301 | 2026-07-28T00:02:17+00:00 | Vulnerability · Source |
| CVE-2019-7282 | suse_vex | SUSE CVE CVE-2019-7282 | known affected: 4 | 2026-07-28T00:02:15+00:00 | Vulnerability · Source |
| CVE-2019-7577 | suse_vex | SUSE CVE CVE-2019-7577 | known affected: 60 recommended: 319 | 2026-07-28T00:02:12+00:00 | Vulnerability · Source |
| CVE-2019-8320 | suse_vex | SUSE CVE CVE-2019-8320 | known affected: 308 known not affected: 2 recommended: 495 | 2026-07-28T00:02:10+00:00 | Vulnerability · Source |
| CVE-2019-8622 | suse_vex | SUSE CVE CVE-2019-8622 | known affected: 112 known not affected: 82 recommended: 288 | 2026-07-28T00:02:07+00:00 | Vulnerability · Source |
| CVE-2019-8696 | suse_vex | SUSE CVE CVE-2019-8696 | known affected: 92 recommended: 862 | 2026-07-28T00:02:02+00:00 | Vulnerability · Source |
| CVE-2019-8816 | suse_vex | SUSE CVE CVE-2019-8816 | known not affected: 10 recommended: 1075 | 2026-07-28T00:02:00+00:00 | Vulnerability · Source |
| CVE-2019-8846 | suse_vex | SUSE CVE CVE-2019-8846 | known affected: 46 known not affected: 82 recommended: 1063 | 2026-07-28T00:01:57+00:00 | Vulnerability · Source |
| CVE-2019-8922 | suse_vex | SUSE CVE CVE-2019-8922 | known affected: 7 known not affected: 80 recommended: 90 | 2026-07-28T00:01:55+00:00 | Vulnerability · Source |
| CVE-2019-9455 | suse_vex | SUSE CVE CVE-2019-9455 | known affected: 15 known not affected: 19 recommended: 592 | 2026-07-28T00:01:53+00:00 | Vulnerability · Source |
| CVE-2019-9458 | suse_vex | SUSE CVE CVE-2019-9458 | known affected: 164 known not affected: 56 recommended: 717 | 2026-07-28T00:01:52+00:00 | Vulnerability · Source |
| CVE-2019-9641 | suse_vex | SUSE CVE CVE-2019-9641 | known not affected: 1681 recommended: 3868 | 2026-07-28T00:01:49+00:00 | Vulnerability · Source |
| CVE-2019-9740 | suse_vex | SUSE CVE CVE-2019-9740 | known affected: 367 known not affected: 649 recommended: 685 | 2026-07-28T00:01:48+00:00 | Vulnerability · Source |