VEX records
Browse vendor VEX statements available in this Vulnerability-Lookup instance and pivot to the related vulnerability.
283044 VEX records
API response| Vulnerability | Source | Title | Product status | Imported | Links |
|---|---|---|---|---|---|
| CVE-2018-9267 | suse_vex | SUSE CVE CVE-2018-9267 | known affected: 72 known not affected: 115 recommended: 537 | 2026-07-19T18:28:49+00:00 | Vulnerability · Source |
| CVE-2018-9274 | suse_vex | SUSE CVE CVE-2018-9274 | known affected: 72 known not affected: 115 recommended: 537 | 2026-07-19T18:28:47+00:00 | Vulnerability · Source |
| CVE-2018-9305 | suse_vex | SUSE CVE CVE-2018-9305 | known affected: 36 known not affected: 52 recommended: 161 | 2026-07-19T18:28:46+00:00 | Vulnerability · Source |
| CVE-2018-10194 | suse_vex | SUSE CVE CVE-2018-10194 | known affected: 38 recommended: 270 | 2026-07-19T18:28:45+00:00 | Vulnerability · Source |
| CVE-2018-10392 | suse_vex | SUSE CVE CVE-2018-10392 | known affected: 494 recommended: 409 | 2026-07-19T18:28:43+00:00 | Vulnerability · Source |
| CVE-2018-10534 | suse_vex | SUSE CVE CVE-2018-10534 | known affected: 442 known not affected: 95 recommended: 342 | 2026-07-19T18:28:42+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-19T18:28:40+00:00 | Vulnerability · Source |
| CVE-2018-10871 | suse_vex | SUSE CVE CVE-2018-10871 | recommended: 153 | 2026-07-19T18:28:38+00:00 | Vulnerability · Source |
| CVE-2018-10888 | suse_vex | SUSE CVE CVE-2018-10888 | known affected: 16 known not affected: 38 recommended: 163 | 2026-07-19T18:28:37+00:00 | Vulnerability · Source |
| CVE-2018-10916 | suse_vex | SUSE CVE CVE-2018-10916 | known affected: 12 known not affected: 19 recommended: 71 | 2026-07-19T18:28:36+00:00 | Vulnerability · Source |
| CVE-2018-11235 | suse_vex | SUSE CVE CVE-2018-11235 | known affected: 101 known not affected: 38 recommended: 1095 | 2026-07-19T18:28:34+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-19T18:28:33+00:00 | Vulnerability · Source |
| CVE-2018-11357 | suse_vex | SUSE CVE CVE-2018-11357 | known affected: 70 recommended: 1004 | 2026-07-19T18:28:31+00:00 | Vulnerability · Source |
| CVE-2018-11358 | suse_vex | SUSE CVE CVE-2018-11358 | known affected: 70 recommended: 1004 | 2026-07-19T18:28:30+00:00 | Vulnerability · Source |
| CVE-2018-11685 | suse_vex | SUSE CVE CVE-2018-11685 | known affected: 36 known not affected: 128 recommended: 314 | 2026-07-19T18:28:29+00:00 | Vulnerability · Source |
| CVE-2018-11712 | suse_vex | SUSE CVE CVE-2018-11712 | known affected: 93 known not affected: 100 recommended: 1271 | 2026-07-19T18:28:27+00:00 | Vulnerability · Source |
| CVE-2018-11797 | suse_vex | SUSE CVE CVE-2018-11797 | known affected: 6 known not affected: 9 recommended: 75 | 2026-07-19T18:28:26+00:00 | Vulnerability · Source |
| CVE-2018-11813 | suse_vex | SUSE CVE CVE-2018-11813 | known affected: 429 recommended: 527 | 2026-07-19T18:28:25+00:00 | Vulnerability · Source |
| CVE-2018-12020 | suse_vex | SUSE CVE CVE-2018-12020 | known affected: 356 recommended: 368 | 2026-07-19T18:28:23+00:00 | Vulnerability · Source |
| CVE-2018-12022 | suse_vex | SUSE CVE CVE-2018-12022 | recommended: 47 | 2026-07-19T18:28:22+00:00 | Vulnerability · Source |
| CVE-2018-12086 | suse_vex | SUSE CVE CVE-2018-12086 | known not affected: 243 recommended: 970 | 2026-07-19T18:28:21+00:00 | Vulnerability · Source |
| CVE-2018-12126 | suse_vex | SUSE CVE CVE-2018-12126 | known affected: 335 known not affected: 394 recommended: 5642 | 2026-07-19T18:28:19+00:00 | Vulnerability · Source |
| CVE-2018-12360 | suse_vex | SUSE CVE CVE-2018-12360 | known affected: 21 recommended: 445 | 2026-07-19T18:28:17+00:00 | Vulnerability · Source |
| CVE-2018-12367 | suse_vex | SUSE CVE CVE-2018-12367 | known affected: 21 recommended: 105 | 2026-07-19T18:28:16+00:00 | Vulnerability · Source |
| CVE-2018-12371 | suse_vex | SUSE CVE CVE-2018-12371 | known affected: 21 recommended: 105 | 2026-07-19T18:28:15+00:00 | Vulnerability · Source |
| CVE-2018-12379 | suse_vex | SUSE CVE CVE-2018-12379 | known not affected: 200 recommended: 659 | 2026-07-19T18:28:14+00:00 | Vulnerability · Source |
| CVE-2018-12385 | suse_vex | SUSE CVE CVE-2018-12385 | known affected: 1 recommended: 755 | 2026-07-19T18:28:12+00:00 | Vulnerability · Source |
| CVE-2018-12404 | suse_vex | SUSE CVE CVE-2018-12404 | known affected: 321 known not affected: 209 recommended: 1555 | 2026-07-19T18:28:10+00:00 | Vulnerability · Source |
| CVE-2018-12405 | suse_vex | SUSE CVE CVE-2018-12405 | known affected: 20 known not affected: 168 recommended: 1185 | 2026-07-19T18:28:09+00:00 | Vulnerability · Source |
| CVE-2018-13139 | suse_vex | SUSE CVE CVE-2018-13139 | known affected: 403 known not affected: 17 recommended: 231 | 2026-07-19T18:28:07+00:00 | Vulnerability · Source |
| CVE-2018-13259 | suse_vex | SUSE CVE CVE-2018-13259 | known affected: 397 known not affected: 46 recommended: 87 | 2026-07-19T18:28:06+00:00 | Vulnerability · Source |
| CVE-2018-14340 | suse_vex | SUSE CVE CVE-2018-14340 | known affected: 101 recommended: 1007 | 2026-07-19T18:28:05+00:00 | Vulnerability · Source |
| CVE-2018-14351 | suse_vex | SUSE CVE CVE-2018-14351 | known affected: 26 known not affected: 5 recommended: 192 | 2026-07-19T18:28:03+00:00 | Vulnerability · Source |
| CVE-2018-14354 | suse_vex | SUSE CVE CVE-2018-14354 | known affected: 27 recommended: 199 | 2026-07-19T18:28:02+00:00 | Vulnerability · Source |
| CVE-2018-14357 | suse_vex | SUSE CVE CVE-2018-14357 | known affected: 27 recommended: 199 | 2026-07-19T18:28:01+00:00 | Vulnerability · Source |
| CVE-2018-14362 | suse_vex | SUSE CVE CVE-2018-14362 | known affected: 27 recommended: 199 | 2026-07-19T18:28:00+00:00 | Vulnerability · Source |
| CVE-2018-14436 | suse_vex | SUSE CVE CVE-2018-14436 | known not affected: 14 recommended: 735 | 2026-07-19T18:27:59+00:00 | Vulnerability · Source |
| CVE-2018-14447 | suse_vex | SUSE CVE CVE-2018-14447 | known not affected: 52 recommended: 9 | 2026-07-19T18:27:58+00:00 | Vulnerability · Source |
| CVE-2018-14465 | suse_vex | SUSE CVE CVE-2018-14465 | known affected: 332 recommended: 143 | 2026-07-19T18:27:56+00:00 | Vulnerability · Source |
| CVE-2018-14470 | suse_vex | SUSE CVE CVE-2018-14470 | known affected: 332 recommended: 139 | 2026-07-19T18:27:55+00:00 | Vulnerability · Source |
| CVE-2018-14526 | suse_vex | SUSE CVE CVE-2018-14526 | known affected: 394 known not affected: 15 recommended: 116 | 2026-07-19T18:27:54+00:00 | Vulnerability · Source |
| CVE-2018-14553 | suse_vex | SUSE CVE CVE-2018-14553 | known affected: 410 known not affected: 3 recommended: 191 | 2026-07-19T18:27:52+00:00 | Vulnerability · Source |
| CVE-2018-14600 | suse_vex | SUSE CVE CVE-2018-14600 | known affected: 394 recommended: 712 | 2026-07-19T18:27:51+00:00 | Vulnerability · Source |
| CVE-2018-14680 | suse_vex | SUSE CVE CVE-2018-14680 | known affected: 37 recommended: 326 | 2026-07-19T18:27:50+00:00 | Vulnerability · Source |
| CVE-2018-14721 | suse_vex | SUSE CVE CVE-2018-14721 | known affected: 29 recommended: 47 | 2026-07-19T18:27:48+00:00 | Vulnerability · Source |
| CVE-2018-14722 | suse_vex | SUSE CVE CVE-2018-14722 | known not affected: 75 recommended: 64 | 2026-07-19T18:27:47+00:00 | Vulnerability · Source |
| CVE-2018-15173 | suse_vex | SUSE CVE CVE-2018-15173 | known affected: 14 known not affected: 8 recommended: 102 | 2026-07-19T18:27:46+00:00 | Vulnerability · Source |
| CVE-2018-15855 | suse_vex | SUSE CVE CVE-2018-15855 | known affected: 557 known not affected: 65 recommended: 383 | 2026-07-19T18:27:44+00:00 | Vulnerability · Source |
| CVE-2018-15856 | suse_vex | SUSE CVE CVE-2018-15856 | known affected: 557 known not affected: 65 recommended: 394 | 2026-07-19T18:27:43+00:00 | Vulnerability · Source |
| CVE-2018-15857 | suse_vex | SUSE CVE CVE-2018-15857 | known affected: 557 known not affected: 65 recommended: 383 | 2026-07-19T18:27:42+00:00 | Vulnerability · Source |