VEX records
Browse vendor VEX statements available in this Vulnerability-Lookup instance and pivot to the related vulnerability.
291935 VEX records
API response| Vulnerability | Source | Title | Product status | Imported | Links |
|---|---|---|---|---|---|
| CVE-2018-19876 | suse_vex | SUSE CVE CVE-2018-19876 | known not affected: 149 | 2026-07-25T18:11:13+00:00 | Vulnerability · Source |
| CVE-2018-19961 | suse_vex | SUSE CVE CVE-2018-19961 | known affected: 388 known not affected: 32 recommended: 539 | 2026-07-25T18:11:09+00:00 | Vulnerability · Source |
| CVE-2018-19965 | suse_vex | SUSE CVE CVE-2018-19965 | known affected: 388 known not affected: 84 recommended: 531 | 2026-07-25T18:11:07+00:00 | Vulnerability · Source |
| CVE-2018-20097 | suse_vex | SUSE CVE CVE-2018-20097 | known affected: 38 known not affected: 3 recommended: 114 | 2026-07-25T18:11:01+00:00 | Vulnerability · Source |
| CVE-2018-20106 | suse_vex | SUSE CVE CVE-2018-20106 | known affected: 3 known not affected: 47 | 2026-07-25T18:10:59+00:00 | Vulnerability · Source |
| CVE-2018-20125 | suse_vex | SUSE CVE CVE-2018-20125 | known affected: 394 known not affected: 544 recommended: 1486 | 2026-07-25T18:10:56+00:00 | Vulnerability · Source |
| CVE-2018-20126 | suse_vex | SUSE CVE CVE-2018-20126 | known affected: 486 known not affected: 450 recommended: 1725 | 2026-07-25T18:10:55+00:00 | Vulnerability · Source |
| CVE-2018-20169 | suse_vex | SUSE CVE CVE-2018-20169 | known affected: 66 known not affected: 194 recommended: 806 | 2026-07-25T18:10:53+00:00 | Vulnerability · Source |
| CVE-2018-20185 | suse_vex | SUSE CVE CVE-2018-20185 | known affected: 3 known not affected: 205 recommended: 14 | 2026-07-25T18:10:51+00:00 | Vulnerability · Source |
| CVE-2018-20509 | suse_vex | SUSE CVE CVE-2018-20509 | known not affected: 127 | 2026-07-25T18:10:44+00:00 | Vulnerability · Source |
| CVE-2018-20510 | suse_vex | SUSE CVE CVE-2018-20510 | known not affected: 134 | 2026-07-25T18:10:43+00:00 | Vulnerability · Source |
| CVE-2018-20511 | suse_vex | SUSE CVE CVE-2018-20511 | known not affected: 563 | 2026-07-25T18:10:42+00:00 | Vulnerability · Source |
| CVE-2018-20534 | suse_vex | SUSE CVE CVE-2018-20534 | known affected: 60 recommended: 928 | 2026-07-25T18:10:38+00:00 | Vulnerability · Source |
| CVE-2018-20584 | suse_vex | SUSE CVE CVE-2018-20584 | known not affected: 89 | 2026-07-25T18:10:37+00:00 | Vulnerability · Source |
| CVE-2018-20650 | suse_vex | SUSE CVE CVE-2018-20650 | known affected: 26 known not affected: 324 recommended: 179 | 2026-07-25T18:10:36+00:00 | Vulnerability · Source |
| CVE-2018-20651 | suse_vex | SUSE CVE CVE-2018-20651 | known affected: 449 recommended: 485 | 2026-07-25T18:10:34+00:00 | Vulnerability · Source |
| CVE-2018-20669 | suse_vex | SUSE CVE CVE-2018-20669 | known affected: 361 known not affected: 276 recommended: 1377 | 2026-07-25T18:10:32+00:00 | Vulnerability · Source |
| CVE-2018-20712 | suse_vex | SUSE CVE CVE-2018-20712 | known not affected: 318 | 2026-07-25T18:10:29+00:00 | Vulnerability · Source |
| CVE-2018-20781 | suse_vex | SUSE CVE CVE-2018-20781 | known affected: 106 known not affected: 309 | 2026-07-25T18:10:25+00:00 | Vulnerability · Source |
| CVE-2018-20843 | suse_vex | SUSE CVE CVE-2018-20843 | known affected: 372 recommended: 393 | 2026-07-25T18:10:21+00:00 | Vulnerability · Source |
| CVE-2018-20847 | suse_vex | SUSE CVE CVE-2018-20847 | known affected: 5 known not affected: 335 recommended: 4 | 2026-07-25T18:10:18+00:00 | Vulnerability · Source |
| CVE-2018-20852 | suse_vex | SUSE CVE CVE-2018-20852 | known affected: 459 recommended: 1884 | 2026-07-25T18:10:17+00:00 | Vulnerability · Source |
| CVE-2018-20976 | suse_vex | SUSE CVE CVE-2018-20976 | known not affected: 227 recommended: 903 | 2026-07-25T18:10:15+00:00 | Vulnerability · Source |
| CVE-2018-21035 | suse_vex | SUSE CVE CVE-2018-21035 | recommended: 26 | 2026-07-25T18:10:12+00:00 | Vulnerability · Source |
| CVE-2018-21232 | suse_vex | SUSE CVE CVE-2018-21232 | recommended: 29 | 2026-07-25T18:10:11+00:00 | Vulnerability · Source |
| CVE-2018-21247 | suse_vex | SUSE CVE CVE-2018-21247 | known affected: 24 known not affected: 3 recommended: 117 | 2026-07-25T18:10:10+00:00 | Vulnerability · Source |
| CVE-2018-25013 | suse_vex | SUSE CVE CVE-2018-25013 | known affected: 395 known not affected: 55 recommended: 227 | 2026-07-25T18:10:08+00:00 | Vulnerability · Source |
| CVE-2018-25015 | suse_vex | SUSE CVE CVE-2018-25015 | known not affected: 320 | 2026-07-25T18:10:07+00:00 | Vulnerability · Source |
| CVE-2018-25091 | suse_vex | SUSE CVE CVE-2018-25091 | known not affected: 147 recommended: 38 | 2026-07-25T18:10:06+00:00 | Vulnerability · Source |
| CVE-2018-1000028 | suse_vex | SUSE CVE CVE-2018-1000028 | known not affected: 142 recommended: 293 | 2026-07-25T18:10:01+00:00 | Vulnerability · Source |
| CVE-2018-1000032 | suse_vex | SUSE CVE CVE-2018-1000032 | known not affected: 14 | 2026-07-25T18:10:00+00:00 | Vulnerability · Source |
| CVE-2018-1000034 | suse_vex | SUSE CVE CVE-2018-1000034 | known not affected: 14 | 2026-07-25T18:09:58+00:00 | Vulnerability · Source |
| CVE-2018-1000035 | suse_vex | SUSE CVE CVE-2018-1000035 | known affected: 397 known not affected: 30 recommended: 92 | 2026-07-25T18:09:57+00:00 | Vulnerability · Source |
| CVE-2018-1000041 | suse_vex | SUSE CVE CVE-2018-1000041 | recommended: 72 | 2026-07-25T18:09:56+00:00 | Vulnerability · Source |
| CVE-2018-1000073 | suse_vex | SUSE CVE CVE-2018-1000073 | known affected: 324 known not affected: 53 recommended: 491 | 2026-07-25T18:09:54+00:00 | Vulnerability · Source |
| CVE-2018-1000074 | suse_vex | SUSE CVE CVE-2018-1000074 | known affected: 320 known not affected: 90 recommended: 491 | 2026-07-25T18:09:53+00:00 | Vulnerability · Source |
| CVE-2018-1000076 | suse_vex | SUSE CVE CVE-2018-1000076 | known affected: 320 known not affected: 90 recommended: 491 | 2026-07-25T18:09:51+00:00 | Vulnerability · Source |
| CVE-2018-1000079 | suse_vex | SUSE CVE CVE-2018-1000079 | known affected: 323 known not affected: 67 recommended: 491 | 2026-07-25T18:09:50+00:00 | Vulnerability · Source |
| CVE-2018-1000116 | suse_vex | SUSE CVE CVE-2018-1000116 | known affected: 2 known not affected: 52 | 2026-07-25T18:09:47+00:00 | Vulnerability · Source |
| CVE-2018-1000300 | suse_vex | SUSE CVE CVE-2018-1000300 | known affected: 320 known not affected: 130 recommended: 370 | 2026-07-25T18:09:43+00:00 | Vulnerability · Source |
| CVE-2018-1000654 | suse_vex | SUSE CVE CVE-2018-1000654 | known affected: 377 recommended: 406 | 2026-07-25T18:09:40+00:00 | Vulnerability · Source |
| CVE-2018-1000802 | suse_vex | SUSE CVE CVE-2018-1000802 | known affected: 438 known not affected: 2 recommended: 1387 | 2026-07-25T18:09:38+00:00 | Vulnerability · Source |
| CVE-2018-1000852 | suse_vex | SUSE CVE CVE-2018-1000852 | recommended: 221 | 2026-07-25T18:09:36+00:00 | Vulnerability · Source |
| CVE-2018-1000858 | suse_vex | SUSE CVE CVE-2018-1000858 | known affected: 331 known not affected: 40 recommended: 204 | 2026-07-25T18:09:34+00:00 | Vulnerability · Source |
| CVE-2018-1000876 | suse_vex | SUSE CVE CVE-2018-1000876 | known affected: 394 recommended: 487 | 2026-07-25T18:09:33+00:00 | Vulnerability · Source |
| CVE-2019-0154 | suse_vex | SUSE CVE CVE-2019-0154 | known affected: 323 known not affected: 108 recommended: 1549 | 2026-07-25T18:09:30+00:00 | Vulnerability · Source |
| CVE-2019-0155 | suse_vex | SUSE CVE CVE-2019-0155 | known affected: 261 known not affected: 303 recommended: 1275 | 2026-07-25T18:09:28+00:00 | Vulnerability · Source |
| CVE-2019-0190 | suse_vex | SUSE CVE CVE-2019-0190 | known not affected: 138 | 2026-07-25T18:09:27+00:00 | Vulnerability · Source |
| CVE-2019-0199 | suse_vex | SUSE CVE CVE-2019-0199 | known affected: 467 known not affected: 129 recommended: 226 | 2026-07-25T18:09:26+00:00 | Vulnerability · Source |
| CVE-2019-0211 | suse_vex | SUSE CVE CVE-2019-0211 | known affected: 111 known not affected: 65 recommended: 212 | 2026-07-25T18:09:24+00:00 | Vulnerability · Source |