VEX records
Browse vendor VEX statements available in this Vulnerability-Lookup instance and pivot to the related vulnerability.
286603 VEX records
API response| Vulnerability | Source | Title | Product status | Imported | Links |
|---|---|---|---|---|---|
| CVE-2018-5732 | suse_vex | SUSE CVE CVE-2018-5732 | known affected: 391 known not affected: 96 recommended: 399 | 2026-07-28T00:04:58+00:00 | Vulnerability · Source |
| CVE-2018-6003 | suse_vex | SUSE CVE CVE-2018-6003 | known affected: 320 known not affected: 117 recommended: 365 | 2026-07-28T00:04:57+00:00 | Vulnerability · Source |
| CVE-2018-6063 | suse_vex | SUSE CVE CVE-2018-6063 | recommended: 10 | 2026-07-28T00:04:55+00:00 | Vulnerability · Source |
| CVE-2018-6836 | suse_vex | SUSE CVE CVE-2018-6836 | known not affected: 395 | 2026-07-28T00:04:52+00:00 | Vulnerability · Source |
| CVE-2018-6871 | suse_vex | SUSE CVE CVE-2018-6871 | known not affected: 196 recommended: 3958 | 2026-07-28T00:04:50+00:00 | Vulnerability · Source |
| CVE-2018-6913 | suse_vex | SUSE CVE CVE-2018-6913 | known affected: 322 recommended: 416 | 2026-07-28T00:04:49+00:00 | Vulnerability · Source |
| CVE-2018-6969 | suse_vex | SUSE CVE CVE-2018-6969 | known not affected: 3 | 2026-07-28T00:04:47+00:00 | Vulnerability · Source |
| CVE-2018-7254 | suse_vex | SUSE CVE CVE-2018-7254 | known affected: 394 known not affected: 85 recommended: 227 | 2026-07-28T00:04:45+00:00 | Vulnerability · Source |
| 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-8977 | suse_vex | SUSE CVE CVE-2018-8977 | known not affected: 20 recommended: 95 | 2026-07-28T00:04:38+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-9264 | suse_vex | SUSE CVE CVE-2018-9264 | known affected: 72 known not affected: 115 recommended: 543 | 2026-07-28T00:04:35+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-10805 | suse_vex | SUSE CVE CVE-2018-10805 | known not affected: 53 recommended: 757 | 2026-07-28T00:04:29+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-10875 | suse_vex | SUSE CVE CVE-2018-10875 | known affected: 1 known not affected: 7 recommended: 250 | 2026-07-28T00:04:24+00:00 | Vulnerability · Source |
| CVE-2018-10925 | suse_vex | SUSE CVE CVE-2018-10925 | known affected: 142 known not affected: 153 recommended: 419 | 2026-07-28T00:04:22+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-11237 | suse_vex | SUSE CVE CVE-2018-11237 | known affected: 438 known not affected: 122 recommended: 1226 | 2026-07-28T00:04:17+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-12181 | suse_vex | SUSE CVE CVE-2018-12181 | known affected: 43 recommended: 234 | 2026-07-28T00:04:12+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-14036 | suse_vex | SUSE CVE CVE-2018-14036 | known not affected: 45 recommended: 766 | 2026-07-28T00:04:08+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-15126 | suse_vex | SUSE CVE CVE-2018-15126 | known affected: 33 recommended: 123 | 2026-07-28T00:03:56+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-16329 | suse_vex | SUSE CVE CVE-2018-16329 | recommended: 651 | 2026-07-28T00:03:48+00:00 | Vulnerability · Source |
| CVE-2018-16375 | suse_vex | SUSE CVE CVE-2018-16375 | recommended: 201 | 2026-07-28T00:03:47+00:00 | Vulnerability · Source |
| CVE-2018-16418 | suse_vex | SUSE CVE CVE-2018-16418 | known affected: 14 known not affected: 19 recommended: 104 | 2026-07-28T00:03:46+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-16511 | suse_vex | SUSE CVE CVE-2018-16511 | known affected: 16 recommended: 418 | 2026-07-28T00:03:42+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-16847 | suse_vex | SUSE CVE CVE-2018-16847 | known affected: 60 known not affected: 267 recommended: 1581 | 2026-07-28T00:03:39+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-17958 | suse_vex | SUSE CVE CVE-2018-17958 | known affected: 135 known not affected: 1207 recommended: 1871 | 2026-07-28T00:03:33+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 |