VEX records
Browse vendor VEX statements available in this Vulnerability-Lookup instance and pivot to the related vulnerability.
291942 VEX records
API response| Vulnerability | Source | Title | Product status | Imported | Links |
|---|---|---|---|---|---|
| CVE-2018-7327 | suse_vex | SUSE CVE CVE-2018-7327 | known affected: 1 known not affected: 103 recommended: 559 | 2026-07-28T00:04:44+00:00 | Vulnerability · Source |
| CVE-2018-7328 | suse_vex | SUSE CVE CVE-2018-7328 | known affected: 1 known not affected: 115 recommended: 565 | 2026-07-28T00:04:43+00:00 | Vulnerability · Source |
| CVE-2018-8105 | suse_vex | SUSE CVE CVE-2018-8105 | known not affected: 328 | 2026-07-28T00:04:41+00:00 | Vulnerability · Source |
| CVE-2018-8106 | suse_vex | SUSE CVE CVE-2018-8106 | known not affected: 328 | 2026-07-28T00:04:39+00:00 | Vulnerability · Source |
| CVE-2018-9056 | suse_vex | SUSE CVE CVE-2018-9056 | known not affected: 209 | 2026-07-28T00:04:36+00:00 | Vulnerability · Source |
| CVE-2018-10536 | suse_vex | SUSE CVE CVE-2018-10536 | known not affected: 78 recommended: 172 | 2026-07-28T00:04:31+00:00 | Vulnerability · Source |
| CVE-2018-10846 | suse_vex | SUSE CVE CVE-2018-10846 | known affected: 386 known not affected: 21 recommended: 654 | 2026-07-28T00:04:28+00:00 | Vulnerability · Source |
| CVE-2018-10858 | suse_vex | SUSE CVE CVE-2018-10858 | known affected: 411 known not affected: 651 recommended: 4105 | 2026-07-28T00:04:25+00:00 | Vulnerability · Source |
| CVE-2018-10940 | suse_vex | SUSE CVE CVE-2018-10940 | known affected: 34 known not affected: 198 recommended: 665 | 2026-07-28T00:04:21+00:00 | Vulnerability · Source |
| CVE-2018-11037 | suse_vex | SUSE CVE CVE-2018-11037 | known affected: 2 known not affected: 46 recommended: 12 | 2026-07-28T00:04:19+00:00 | Vulnerability · Source |
| CVE-2018-11355 | suse_vex | SUSE CVE CVE-2018-11355 | known affected: 70 recommended: 842 | 2026-07-28T00:04:15+00:00 | Vulnerability · Source |
| CVE-2018-11655 | suse_vex | SUSE CVE CVE-2018-11655 | known not affected: 48 recommended: 96 | 2026-07-28T00:04:14+00:00 | Vulnerability · Source |
| CVE-2018-12362 | suse_vex | SUSE CVE CVE-2018-12362 | known affected: 21 recommended: 445 | 2026-07-28T00:04:10+00:00 | Vulnerability · Source |
| CVE-2018-14044 | suse_vex | SUSE CVE CVE-2018-14044 | known not affected: 21 | 2026-07-28T00:04:06+00:00 | Vulnerability · Source |
| CVE-2018-14362 | suse_vex | SUSE CVE CVE-2018-14362 | known affected: 27 recommended: 199 | 2026-07-28T00:04:05+00:00 | Vulnerability · Source |
| CVE-2018-14367 | suse_vex | SUSE CVE CVE-2018-14367 | known affected: 101 recommended: 998 | 2026-07-28T00:04:03+00:00 | Vulnerability · Source |
| CVE-2018-14423 | suse_vex | SUSE CVE CVE-2018-14423 | recommended: 325 | 2026-07-28T00:04:01+00:00 | Vulnerability · Source |
| CVE-2018-14599 | suse_vex | SUSE CVE CVE-2018-14599 | known affected: 374 recommended: 707 | 2026-07-28T00:03:59+00:00 | Vulnerability · Source |
| CVE-2018-14600 | suse_vex | SUSE CVE CVE-2018-14600 | known affected: 394 recommended: 712 | 2026-07-28T00:03:58+00:00 | Vulnerability · Source |
| 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 |