VEX records
Browse vendor VEX statements available in this Vulnerability-Lookup instance and pivot to the related vulnerability.
284520 VEX records
API response| Vulnerability | Source | Title | Product status | Imported | Links |
|---|---|---|---|---|---|
| CVE-2018-9144 | suse_vex | SUSE CVE CVE-2018-9144 | known affected: 4 known not affected: 53 | 2026-07-26T00:19:51+00:00 | Vulnerability · Source |
| CVE-2018-9145 | suse_vex | SUSE CVE CVE-2018-9145 | known affected: 4 known not affected: 53 | 2026-07-26T00:19:49+00:00 | Vulnerability · Source |
| CVE-2018-9146 | suse_vex | SUSE CVE CVE-2018-9146 | known affected: 4 known not affected: 53 | 2026-07-26T00:19:47+00:00 | Vulnerability · Source |
| CVE-2018-9154 | suse_vex | SUSE CVE CVE-2018-9154 | known affected: 46 recommended: 153 | 2026-07-26T00:19:44+00:00 | Vulnerability · Source |
| CVE-2018-9259 | suse_vex | SUSE CVE CVE-2018-9259 | known affected: 89 known not affected: 115 recommended: 111 | 2026-07-26T00:19:42+00:00 | Vulnerability · Source |
| CVE-2018-9262 | suse_vex | SUSE CVE CVE-2018-9262 | known affected: 89 known not affected: 115 recommended: 555 | 2026-07-26T00:19:40+00:00 | Vulnerability · Source |
| CVE-2018-9263 | suse_vex | SUSE CVE CVE-2018-9263 | known affected: 89 known not affected: 115 recommended: 555 | 2026-07-26T00:19:38+00:00 | Vulnerability · Source |
| CVE-2018-9266 | suse_vex | SUSE CVE CVE-2018-9266 | known affected: 89 known not affected: 115 recommended: 549 | 2026-07-26T00:19:35+00:00 | Vulnerability · Source |
| CVE-2018-9267 | suse_vex | SUSE CVE CVE-2018-9267 | known affected: 89 known not affected: 115 recommended: 549 | 2026-07-26T00:19:33+00:00 | Vulnerability · Source |
| CVE-2018-9268 | suse_vex | SUSE CVE CVE-2018-9268 | known affected: 89 known not affected: 115 recommended: 549 | 2026-07-26T00:19:31+00:00 | Vulnerability · Source |
| CVE-2018-9270 | suse_vex | SUSE CVE CVE-2018-9270 | known affected: 89 known not affected: 115 recommended: 549 | 2026-07-26T00:19:29+00:00 | Vulnerability · Source |
| CVE-2018-9272 | suse_vex | SUSE CVE CVE-2018-9272 | known affected: 89 known not affected: 115 recommended: 549 | 2026-07-26T00:19:27+00:00 | Vulnerability · Source |
| CVE-2018-9273 | suse_vex | SUSE CVE CVE-2018-9273 | known affected: 89 known not affected: 115 recommended: 555 | 2026-07-26T00:19:25+00:00 | Vulnerability · Source |
| CVE-2018-9274 | suse_vex | SUSE CVE CVE-2018-9274 | known affected: 89 known not affected: 115 recommended: 549 | 2026-07-26T00:19:22+00:00 | Vulnerability · Source |
| CVE-2018-9304 | suse_vex | SUSE CVE CVE-2018-9304 | recommended: 8 | 2026-07-26T00:19:20+00:00 | Vulnerability · Source |
| CVE-2018-9415 | suse_vex | SUSE CVE CVE-2018-9415 | known not affected: 113 | 2026-07-26T00:19:18+00:00 | Vulnerability · Source |
| CVE-2018-9422 | suse_vex | SUSE CVE CVE-2018-9422 | known not affected: 71 | 2026-07-26T00:19:16+00:00 | Vulnerability · Source |
| CVE-2018-9465 | suse_vex | SUSE CVE CVE-2018-9465 | known not affected: 71 | 2026-07-26T00:19:14+00:00 | Vulnerability · Source |
| CVE-2018-9516 | suse_vex | SUSE CVE CVE-2018-9516 | known affected: 15 known not affected: 37 recommended: 379 | 2026-07-26T00:19:12+00:00 | Vulnerability · Source |
| CVE-2018-9518 | suse_vex | SUSE CVE CVE-2018-9518 | known not affected: 71 | 2026-07-26T00:19:10+00:00 | Vulnerability · Source |
| CVE-2018-9918 | suse_vex | SUSE CVE CVE-2018-9918 | known affected: 46 known not affected: 153 recommended: 13 | 2026-07-26T00:19:08+00:00 | Vulnerability · Source |
| CVE-2018-9996 | suse_vex | SUSE CVE CVE-2018-9996 | known affected: 16 | 2026-07-26T00:19:05+00:00 | Vulnerability · Source |
| CVE-2018-10021 | suse_vex | SUSE CVE CVE-2018-10021 | known not affected: 55 | 2026-07-26T00:19:03+00:00 | Vulnerability · Source |
| CVE-2018-10074 | suse_vex | SUSE CVE CVE-2018-10074 | known not affected: 14 | 2026-07-26T00:19:01+00:00 | Vulnerability · Source |
| CVE-2018-10115 | suse_vex | SUSE CVE CVE-2018-10115 | known not affected: 32 | 2026-07-26T00:19:00+00:00 | Vulnerability · Source |
| CVE-2018-10126 | suse_vex | SUSE CVE CVE-2018-10126 | known affected: 6 known not affected: 63 | 2026-07-26T00:18:58+00:00 | Vulnerability · Source |
| CVE-2018-10194 | suse_vex | SUSE CVE CVE-2018-10194 | known affected: 46 recommended: 274 | 2026-07-26T00:18:55+00:00 | Vulnerability · Source |
| CVE-2018-10196 | suse_vex | SUSE CVE CVE-2018-10196 | known affected: 414 recommended: 358 | 2026-07-26T00:18:53+00:00 | Vulnerability · Source |
| CVE-2018-10323 | suse_vex | SUSE CVE CVE-2018-10323 | known affected: 320 known not affected: 376 recommended: 1067 | 2026-07-26T00:18:51+00:00 | Vulnerability · Source |
| CVE-2018-10372 | suse_vex | SUSE CVE CVE-2018-10372 | known affected: 457 known not affected: 264 recommended: 345 | 2026-07-26T00:18:48+00:00 | Vulnerability · Source |
| CVE-2018-10534 | suse_vex | SUSE CVE CVE-2018-10534 | known affected: 453 known not affected: 95 recommended: 345 | 2026-07-26T00:18:46+00:00 | Vulnerability · Source |
| CVE-2018-10538 | suse_vex | SUSE CVE CVE-2018-10538 | known not affected: 92 recommended: 172 | 2026-07-26T00:18:44+00:00 | Vulnerability · Source |
| CVE-2018-10675 | suse_vex | SUSE CVE CVE-2018-10675 | known affected: 2 known not affected: 158 recommended: 203 | 2026-07-26T00:18:41+00:00 | Vulnerability · Source |
| CVE-2018-10754 | suse_vex | SUSE CVE CVE-2018-10754 | known affected: 132 known not affected: 69 recommended: 116 | 2026-07-26T00:18:39+00:00 | Vulnerability · Source |
| CVE-2018-10767 | suse_vex | SUSE CVE CVE-2018-10767 | known affected: 281 recommended: 848 | 2026-07-26T00:18:37+00:00 | Vulnerability · Source |
| CVE-2018-10768 | suse_vex | SUSE CVE CVE-2018-10768 | known not affected: 76 recommended: 855 | 2026-07-26T00:18:34+00:00 | Vulnerability · Source |
| CVE-2018-10780 | suse_vex | SUSE CVE CVE-2018-10780 | known affected: 4 known not affected: 55 | 2026-07-26T00:18:32+00:00 | Vulnerability · Source |
| CVE-2018-10840 | suse_vex | SUSE CVE CVE-2018-10840 | known not affected: 304 | 2026-07-26T00:18:29+00:00 | Vulnerability · Source |
| CVE-2018-10852 | suse_vex | SUSE CVE CVE-2018-10852 | known affected: 220 known not affected: 75 recommended: 1717 | 2026-07-26T00:18:27+00:00 | Vulnerability · Source |
| CVE-2018-10853 | suse_vex | SUSE CVE CVE-2018-10853 | known affected: 112 known not affected: 346 recommended: 771 | 2026-07-26T00:18:25+00:00 | Vulnerability · Source |
| CVE-2018-10873 | suse_vex | SUSE CVE CVE-2018-10873 | known affected: 143 known not affected: 182 recommended: 598 | 2026-07-26T00:18:22+00:00 | Vulnerability · Source |
| CVE-2018-10876 | suse_vex | SUSE CVE CVE-2018-10876 | known affected: 48 known not affected: 401 recommended: 429 | 2026-07-26T00:18:20+00:00 | Vulnerability · Source |
| CVE-2018-10877 | suse_vex | SUSE CVE CVE-2018-10877 | known affected: 48 known not affected: 124 recommended: 429 | 2026-07-26T00:18:18+00:00 | Vulnerability · Source |
| CVE-2018-10878 | suse_vex | SUSE CVE CVE-2018-10878 | known affected: 48 known not affected: 272 recommended: 442 | 2026-07-26T00:18:15+00:00 | Vulnerability · Source |
| CVE-2018-10879 | suse_vex | SUSE CVE CVE-2018-10879 | known affected: 48 known not affected: 257 recommended: 442 | 2026-07-26T00:18:13+00:00 | Vulnerability · Source |
| CVE-2018-10880 | suse_vex | SUSE CVE CVE-2018-10880 | known affected: 71 known not affected: 128 recommended: 429 | 2026-07-26T00:18:10+00:00 | Vulnerability · Source |
| CVE-2018-10882 | suse_vex | SUSE CVE CVE-2018-10882 | known affected: 15 known not affected: 466 recommended: 429 | 2026-07-26T00:18:08+00:00 | Vulnerability · Source |
| CVE-2018-10883 | suse_vex | SUSE CVE CVE-2018-10883 | known affected: 48 known not affected: 229 recommended: 442 | 2026-07-26T00:18:05+00:00 | Vulnerability · Source |
| CVE-2018-10893 | suse_vex | SUSE CVE CVE-2018-10893 | known affected: 110 known not affected: 239 recommended: 610 | 2026-07-26T00:18:03+00:00 | Vulnerability · Source |
| CVE-2018-10902 | suse_vex | SUSE CVE CVE-2018-10902 | known affected: 427 known not affected: 509 recommended: 962 | 2026-07-26T00:18:00+00:00 | Vulnerability · Source |