VEX records
Browse vendor VEX statements available in this Vulnerability-Lookup instance and pivot to the related vulnerability.
290275 VEX records
API response| Vulnerability | Source | Title | Product status | Imported | Links |
|---|---|---|---|---|---|
| CVE-2017-17887 | suse_vex | SUSE CVE CVE-2017-17887 | known affected: 97 known not affected: 36 recommended: 100 | 2026-08-01T00:20:25+00:00 | Vulnerability · Source |
| CVE-2017-18022 | suse_vex | SUSE CVE CVE-2017-18022 | recommended: 186 | 2026-08-01T00:20:23+00:00 | Vulnerability · Source |
| CVE-2017-18186 | suse_vex | SUSE CVE CVE-2017-18186 | known not affected: 157 | 2026-08-01T00:20:22+00:00 | Vulnerability · Source |
| CVE-2017-18238 | suse_vex | SUSE CVE CVE-2017-18238 | known affected: 4 known not affected: 14 recommended: 26 | 2026-08-01T00:20:20+00:00 | Vulnerability · Source |
| CVE-2017-1000408 | suse_vex | SUSE CVE CVE-2017-1000408 | known affected: 381 known not affected: 266 recommended: 1194 | 2026-08-01T00:20:18+00:00 | Vulnerability · Source |
| CVE-2018-2633 | suse_vex | SUSE CVE CVE-2018-2633 | known affected: 73 known not affected: 263 recommended: 730 | 2026-08-01T00:20:15+00:00 | Vulnerability · Source |
| CVE-2018-2795 | suse_vex | SUSE CVE CVE-2018-2795 | known affected: 527 known not affected: 179 recommended: 1098 | 2026-08-01T00:20:13+00:00 | Vulnerability · Source |
| CVE-2018-3214 | suse_vex | SUSE CVE CVE-2018-3214 | known affected: 411 known not affected: 94 recommended: 841 | 2026-08-01T00:20:11+00:00 | Vulnerability · Source |
| CVE-2018-4119 | suse_vex | SUSE CVE CVE-2018-4119 | known affected: 116 known not affected: 169 recommended: 903 | 2026-08-01T00:20:09+00:00 | Vulnerability · Source |
| CVE-2018-5114 | suse_vex | SUSE CVE CVE-2018-5114 | known affected: 1 known not affected: 42 recommended: 12 | 2026-08-01T00:20:07+00:00 | Vulnerability · Source |
| CVE-2018-5182 | suse_vex | SUSE CVE CVE-2018-5182 | known affected: 26 recommended: 83 | 2026-08-01T00:20:05+00:00 | Vulnerability · Source |
| CVE-2018-5407 | suse_vex | SUSE CVE CVE-2018-5407 | known affected: 430 known not affected: 304 recommended: 598 | 2026-08-01T00:20:04+00:00 | Vulnerability · Source |
| CVE-2018-5736 | suse_vex | SUSE CVE CVE-2018-5736 | known not affected: 495 recommended: 306 | 2026-08-01T00:20:02+00:00 | Vulnerability · Source |
| CVE-2018-7456 | suse_vex | SUSE CVE CVE-2018-7456 | known affected: 441 recommended: 302 | 2026-08-01T00:19:59+00:00 | Vulnerability · Source |
| CVE-2018-8011 | suse_vex | SUSE CVE CVE-2018-8011 | known affected: 31 known not affected: 233 recommended: 82 | 2026-08-01T00:19:57+00:00 | Vulnerability · Source |
| CVE-2018-8781 | suse_vex | SUSE CVE CVE-2018-8781 | known affected: 101 known not affected: 272 recommended: 660 | 2026-08-01T00:19:55+00:00 | Vulnerability · Source |
| CVE-2018-8785 | suse_vex | SUSE CVE CVE-2018-8785 | recommended: 215 | 2026-08-01T00:19:54+00:00 | Vulnerability · Source |
| CVE-2018-9252 | suse_vex | SUSE CVE CVE-2018-9252 | known affected: 46 recommended: 154 | 2026-08-01T00:19:53+00:00 | Vulnerability · Source |
| CVE-2018-9257 | suse_vex | SUSE CVE CVE-2018-9257 | known affected: 89 known not affected: 115 recommended: 444 | 2026-08-01T00:19:51+00:00 | Vulnerability · Source |
| CVE-2018-9261 | suse_vex | SUSE CVE CVE-2018-9261 | known affected: 89 known not affected: 115 recommended: 555 | 2026-08-01T00:19:49+00:00 | Vulnerability · Source |
| CVE-2018-10124 | suse_vex | SUSE CVE CVE-2018-10124 | known affected: 28 known not affected: 221 recommended: 662 | 2026-08-01T00:19:48+00:00 | Vulnerability · Source |
| CVE-2018-10537 | suse_vex | SUSE CVE CVE-2018-10537 | known affected: 394 known not affected: 92 recommended: 172 | 2026-08-01T00:19:46+00:00 | Vulnerability · Source |
| CVE-2018-10932 | suse_vex | SUSE CVE CVE-2018-10932 | known not affected: 154 recommended: 15 | 2026-08-01T00:19:44+00:00 | Vulnerability · Source |
| CVE-2018-11508 | suse_vex | SUSE CVE CVE-2018-11508 | known not affected: 144 | 2026-08-01T00:19:42+00:00 | Vulnerability · Source |
| CVE-2018-13033 | suse_vex | SUSE CVE CVE-2018-13033 | recommended: 2 | 2026-08-01T00:19:39+00:00 | Vulnerability · Source |
| CVE-2018-13053 | suse_vex | SUSE CVE CVE-2018-13053 | known affected: 362 known not affected: 239 recommended: 1481 | 2026-08-01T00:19:38+00:00 | Vulnerability · Source |
| CVE-2018-13405 | suse_vex | SUSE CVE CVE-2018-13405 | known affected: 394 known not affected: 83 recommended: 988 | 2026-08-01T00:19:36+00:00 | Vulnerability · Source |
| CVE-2018-14680 | suse_vex | SUSE CVE CVE-2018-14680 | known affected: 41 recommended: 329 | 2026-08-01T00:19:34+00:00 | Vulnerability · Source |
| CVE-2018-15861 | suse_vex | SUSE CVE CVE-2018-15861 | known affected: 565 known not affected: 65 recommended: 440 | 2026-08-01T00:19:32+00:00 | Vulnerability · Source |
| CVE-2018-16057 | suse_vex | SUSE CVE CVE-2018-16057 | known affected: 118 recommended: 1025 | 2026-08-01T00:19:30+00:00 | Vulnerability · Source |
| CVE-2018-18066 | suse_vex | SUSE CVE CVE-2018-18066 | known not affected: 297 recommended: 9 | 2026-08-01T00:19:27+00:00 | Vulnerability · Source |
| CVE-2018-18310 | suse_vex | SUSE CVE CVE-2018-18310 | known affected: 522 recommended: 1131 | 2026-08-01T00:19:25+00:00 | Vulnerability · Source |
| CVE-2018-18751 | suse_vex | SUSE CVE CVE-2018-18751 | known affected: 433 known not affected: 139 recommended: 98 | 2026-08-01T00:19:23+00:00 | Vulnerability · Source |
| CVE-2018-19491 | suse_vex | SUSE CVE CVE-2018-19491 | known affected: 24 recommended: 90 | 2026-08-01T00:19:21+00:00 | Vulnerability · Source |
| CVE-2018-19591 | suse_vex | SUSE CVE CVE-2018-19591 | known not affected: 498 recommended: 216 | 2026-08-01T00:19:19+00:00 | Vulnerability · Source |
| CVE-2018-19636 | suse_vex | SUSE CVE CVE-2018-19636 | known not affected: 5 recommended: 43 | 2026-08-01T00:19:17+00:00 | Vulnerability · Source |
| CVE-2018-19870 | suse_vex | SUSE CVE CVE-2018-19870 | known affected: 36 known not affected: 1727 recommended: 1076 | 2026-08-01T00:19:15+00:00 | Vulnerability · Source |
| CVE-2018-19964 | suse_vex | SUSE CVE CVE-2018-19964 | known affected: 320 known not affected: 176 recommended: 369 | 2026-08-01T00:19:13+00:00 | Vulnerability · Source |
| CVE-2018-20216 | suse_vex | SUSE CVE CVE-2018-20216 | known affected: 394 known not affected: 679 recommended: 1486 | 2026-08-01T00:19:10+00:00 | Vulnerability · Source |
| CVE-2018-20346 | suse_vex | SUSE CVE CVE-2018-20346 | known affected: 415 known not affected: 44 recommended: 496 | 2026-08-01T00:19:08+00:00 | Vulnerability · Source |
| CVE-2018-1000030 | suse_vex | SUSE CVE CVE-2018-1000030 | known affected: 465 known not affected: 123 recommended: 537 | 2026-08-01T00:19:04+00:00 | Vulnerability · Source |
| CVE-2019-1798 | suse_vex | SUSE CVE CVE-2019-1798 | known affected: 21 known not affected: 40 recommended: 242 | 2026-08-01T00:19:01+00:00 | Vulnerability · Source |
| CVE-2019-2213 | suse_vex | SUSE CVE CVE-2019-2213 | known not affected: 208 | 2026-08-01T00:18:59+00:00 | Vulnerability · Source |
| CVE-2019-2946 | suse_vex | SUSE CVE CVE-2019-2946 | known affected: 13 known not affected: 121 recommended: 10 | 2026-08-01T00:18:56+00:00 | Vulnerability · Source |
| CVE-2019-2988 | suse_vex | SUSE CVE CVE-2019-2988 | known affected: 525 recommended: 1008 | 2026-08-01T00:18:54+00:00 | Vulnerability · Source |
| CVE-2019-2989 | suse_vex | SUSE CVE CVE-2019-2989 | known affected: 525 recommended: 1129 | 2026-08-01T00:18:53+00:00 | Vulnerability · Source |
| CVE-2019-3815 | suse_vex | SUSE CVE CVE-2019-3815 | known not affected: 242 recommended: 10 | 2026-08-01T00:18:51+00:00 | Vulnerability · Source |
| CVE-2019-3829 | suse_vex | SUSE CVE CVE-2019-3829 | known affected: 361 known not affected: 118 recommended: 535 | 2026-08-01T00:18:49+00:00 | Vulnerability · Source |
| CVE-2019-3882 | suse_vex | SUSE CVE CVE-2019-3882 | known not affected: 102 recommended: 835 | 2026-08-01T00:18:47+00:00 | Vulnerability · Source |
| CVE-2019-5953 | suse_vex | SUSE CVE CVE-2019-5953 | known affected: 326 known not affected: 7 recommended: 170 | 2026-08-01T00:18:45+00:00 | Vulnerability · Source |