VEX records
Browse vendor VEX statements available in this Vulnerability-Lookup instance and pivot to the related vulnerability.
288000 VEX records
API response| Vulnerability | Source | Title | Product status | Imported | Links |
|---|---|---|---|---|---|
| CVE-2018-6555 | suse_vex | SUSE CVE CVE-2018-6555 | known affected: 63 known not affected: 274 recommended: 742 | 2026-07-31T01:42:31+00:00 | Vulnerability · Source |
| CVE-2018-6559 | suse_vex | SUSE CVE CVE-2018-6559 | known not affected: 407 | 2026-07-31T01:42:29+00:00 | Vulnerability · Source |
| CVE-2018-6927 | suse_vex | SUSE CVE CVE-2018-6927 | known affected: 14 known not affected: 442 recommended: 508 | 2026-07-31T01:42:27+00:00 | Vulnerability · Source |
| CVE-2018-7174 | suse_vex | SUSE CVE CVE-2018-7174 | known not affected: 381 | 2026-07-31T01:42:24+00:00 | Vulnerability · Source |
| CVE-2018-7208 | suse_vex | SUSE CVE CVE-2018-7208 | known affected: 394 known not affected: 244 recommended: 586 | 2026-07-31T01:42:22+00:00 | Vulnerability · Source |
| CVE-2018-7332 | suse_vex | SUSE CVE CVE-2018-7332 | known affected: 1 known not affected: 115 recommended: 583 | 2026-07-31T01:42:21+00:00 | Vulnerability · Source |
| CVE-2018-7542 | suse_vex | SUSE CVE CVE-2018-7542 | known affected: 320 known not affected: 107 recommended: 411 | 2026-07-31T01:42:19+00:00 | Vulnerability · Source |
| CVE-2018-8043 | suse_vex | SUSE CVE CVE-2018-8043 | known not affected: 124 recommended: 423 | 2026-07-31T01:42:16+00:00 | Vulnerability · Source |
| CVE-2018-8778 | suse_vex | SUSE CVE CVE-2018-8778 | known affected: 320 known not affected: 2 recommended: 491 | 2026-07-31T01:42:15+00:00 | Vulnerability · Source |
| CVE-2018-8822 | suse_vex | SUSE CVE CVE-2018-8822 | known not affected: 223 recommended: 658 | 2026-07-31T01:42:13+00:00 | Vulnerability · Source |
| CVE-2018-8956 | suse_vex | SUSE CVE CVE-2018-8956 | known affected: 18 recommended: 107 | 2026-07-31T01:42:09+00:00 | Vulnerability · Source |
| CVE-2018-9260 | suse_vex | SUSE CVE CVE-2018-9260 | known affected: 89 known not affected: 115 recommended: 555 | 2026-07-31T01:42:08+00:00 | Vulnerability · Source |
| CVE-2018-9306 | suse_vex | SUSE CVE CVE-2018-9306 | known affected: 4 known not affected: 53 recommended: 8 | 2026-07-31T01:42:06+00:00 | Vulnerability · Source |
| CVE-2018-10804 | suse_vex | SUSE CVE CVE-2018-10804 | known affected: 6 known not affected: 36 recommended: 134 | 2026-07-31T01:42:04+00:00 | Vulnerability · Source |
| CVE-2018-11251 | suse_vex | SUSE CVE CVE-2018-11251 | known not affected: 2 recommended: 136 | 2026-07-31T01:42:02+00:00 | Vulnerability · Source |
| CVE-2018-11684 | suse_vex | SUSE CVE CVE-2018-11684 | known affected: 44 known not affected: 128 recommended: 316 | 2026-07-31T01:42:00+00:00 | Vulnerability · Source |
| CVE-2018-12126 | suse_vex | SUSE CVE CVE-2018-12126 | known affected: 336 known not affected: 457 recommended: 5854 | 2026-07-31T01:41:58+00:00 | Vulnerability · Source |
| CVE-2018-12265 | suse_vex | SUSE CVE CVE-2018-12265 | known not affected: 24 recommended: 153 | 2026-07-31T01:41:56+00:00 | Vulnerability · Source |
| CVE-2018-12363 | suse_vex | SUSE CVE CVE-2018-12363 | known affected: 21 recommended: 451 | 2026-07-31T01:41:54+00:00 | Vulnerability · Source |
| CVE-2018-12383 | suse_vex | SUSE CVE CVE-2018-12383 | known not affected: 200 recommended: 819 | 2026-07-31T01:41:52+00:00 | Vulnerability · Source |
| CVE-2018-12386 | suse_vex | SUSE CVE CVE-2018-12386 | known affected: 1 recommended: 728 | 2026-07-31T01:41:51+00:00 | Vulnerability · Source |
| CVE-2018-12613 | suse_vex | SUSE CVE CVE-2018-12613 | known affected: 71 known not affected: 391 recommended: 5 | 2026-07-31T01:41:49+00:00 | Vulnerability · Source |
| CVE-2018-13419 | suse_vex | SUSE CVE CVE-2018-13419 | known not affected: 62 | 2026-07-31T01:41:47+00:00 | Vulnerability · Source |
| CVE-2018-14348 | suse_vex | SUSE CVE CVE-2018-14348 | known affected: 395 recommended: 171 | 2026-07-31T01:41:45+00:00 | Vulnerability · Source |
| CVE-2018-14567 | suse_vex | SUSE CVE CVE-2018-14567 | known affected: 418 known not affected: 6 recommended: 550 | 2026-07-31T01:41:43+00:00 | Vulnerability · Source |
| CVE-2018-14625 | suse_vex | SUSE CVE CVE-2018-14625 | known affected: 52 known not affected: 628 recommended: 430 | 2026-07-31T01:41:41+00:00 | Vulnerability · Source |
| CVE-2018-14628 | suse_vex | SUSE CVE CVE-2018-14628 | known not affected: 654 recommended: 286 | 2026-07-31T01:41:40+00:00 | Vulnerability · Source |
| CVE-2018-15594 | suse_vex | SUSE CVE CVE-2018-15594 | known affected: 38 known not affected: 329 recommended: 251 | 2026-07-31T01:41:38+00:00 | Vulnerability · Source |
| CVE-2018-15856 | suse_vex | SUSE CVE CVE-2018-15856 | known affected: 565 known not affected: 65 recommended: 402 | 2026-07-31T01:41:36+00:00 | Vulnerability · Source |
| CVE-2018-15864 | suse_vex | SUSE CVE CVE-2018-15864 | known affected: 565 known not affected: 65 recommended: 391 | 2026-07-31T01:41:34+00:00 | Vulnerability · Source |
| CVE-2018-16152 | suse_vex | SUSE CVE CVE-2018-16152 | known affected: 26 known not affected: 135 recommended: 440 | 2026-07-31T01:41:32+00:00 | Vulnerability · Source |
| CVE-2018-16230 | suse_vex | SUSE CVE CVE-2018-16230 | known affected: 333 recommended: 145 | 2026-07-31T01:41:30+00:00 | Vulnerability · Source |
| CVE-2018-16427 | suse_vex | SUSE CVE CVE-2018-16427 | known affected: 16 known not affected: 19 recommended: 106 | 2026-07-31T01:41:28+00:00 | Vulnerability · Source |
| CVE-2018-16470 | suse_vex | SUSE CVE CVE-2018-16470 | known not affected: 38 recommended: 114 | 2026-07-31T01:41:27+00:00 | Vulnerability · Source |
| CVE-2018-16540 | suse_vex | SUSE CVE CVE-2018-16540 | known affected: 16 recommended: 424 | 2026-07-31T01:41:25+00:00 | Vulnerability · Source |
| CVE-2018-16874 | suse_vex | SUSE CVE CVE-2018-16874 | known affected: 320 known not affected: 10 recommended: 1077 | 2026-07-31T01:41:23+00:00 | Vulnerability · Source |
| CVE-2018-16882 | suse_vex | SUSE CVE CVE-2018-16882 | known affected: 394 known not affected: 144 recommended: 103 | 2026-07-31T01:41:21+00:00 | Vulnerability · Source |
| CVE-2018-16885 | suse_vex | SUSE CVE CVE-2018-16885 | known not affected: 239 recommended: 26 | 2026-07-31T01:41:19+00:00 | Vulnerability · Source |
| CVE-2018-16888 | suse_vex | SUSE CVE CVE-2018-16888 | recommended: 10 | 2026-07-31T01:41:18+00:00 | Vulnerability · Source |
| CVE-2018-17000 | suse_vex | SUSE CVE CVE-2018-17000 | known affected: 394 known not affected: 20 recommended: 260 | 2026-07-31T01:41:16+00:00 | Vulnerability · Source |
| CVE-2018-17282 | suse_vex | SUSE CVE CVE-2018-17282 | known affected: 68 known not affected: 50 recommended: 161 | 2026-07-31T01:41:15+00:00 | Vulnerability · Source |
| CVE-2018-17795 | suse_vex | SUSE CVE CVE-2018-17795 | known affected: 464 recommended: 290 | 2026-07-31T01:41:13+00:00 | Vulnerability · Source |
| CVE-2018-17977 | suse_vex | SUSE CVE CVE-2018-17977 | known not affected: 138 | 2026-07-31T01:41:11+00:00 | Vulnerability · Source |
| CVE-2018-18023 | suse_vex | SUSE CVE CVE-2018-18023 | known not affected: 176 | 2026-07-31T01:41:09+00:00 | Vulnerability · Source |
| CVE-2018-18024 | suse_vex | SUSE CVE CVE-2018-18024 | known affected: 1 recommended: 736 | 2026-07-31T01:41:08+00:00 | Vulnerability · Source |
| CVE-2018-18313 | suse_vex | SUSE CVE CVE-2018-18313 | known affected: 341 known not affected: 84 recommended: 357 | 2026-07-31T01:41:06+00:00 | Vulnerability · Source |
| CVE-2018-18459 | suse_vex | SUSE CVE CVE-2018-18459 | known not affected: 381 | 2026-07-31T01:41:04+00:00 | Vulnerability · Source |
| CVE-2018-18510 | suse_vex | SUSE CVE CVE-2018-18510 | known not affected: 64 | 2026-07-31T01:41:02+00:00 | Vulnerability · Source |
| CVE-2018-18606 | suse_vex | SUSE CVE CVE-2018-18606 | known affected: 448 recommended: 485 | 2026-07-31T01:41:00+00:00 | Vulnerability · Source |
| CVE-2018-18661 | suse_vex | SUSE CVE CVE-2018-18661 | known affected: 459 recommended: 298 | 2026-07-31T01:40:58+00:00 | Vulnerability · Source |