VEX records
Browse vendor VEX statements available in this Vulnerability-Lookup instance and pivot to the related vulnerability.
289480 VEX records
API response| Vulnerability | Source | Title | Product status | Imported | Links |
|---|---|---|---|---|---|
| CVE-2017-8345 | suse_vex | SUSE CVE CVE-2017-8345 | recommended: 184 | 2026-08-06T02:13:59+00:00 | Vulnerability · Source |
| CVE-2017-8386 | suse_vex | SUSE CVE CVE-2017-8386 | known affected: 130 recommended: 954 | 2026-08-06T02:13:58+00:00 | Vulnerability · Source |
| CVE-2017-9077 | suse_vex | SUSE CVE CVE-2017-9077 | known affected: 14 known not affected: 476 recommended: 454 | 2026-08-06T02:13:56+00:00 | Vulnerability · Source |
| CVE-2017-9432 | suse_vex | SUSE CVE CVE-2017-9432 | recommended: 1580 | 2026-08-06T02:13:54+00:00 | Vulnerability · Source |
| CVE-2017-11339 | suse_vex | SUSE CVE CVE-2017-11339 | known affected: 96 known not affected: 41 recommended: 157 | 2026-08-06T02:13:51+00:00 | Vulnerability · Source |
| CVE-2017-11408 | suse_vex | SUSE CVE CVE-2017-11408 | known affected: 86 known not affected: 115 recommended: 565 | 2026-08-06T02:13:49+00:00 | Vulnerability · Source |
| CVE-2017-11509 | suse_vex | SUSE CVE CVE-2017-11509 | known not affected: 5 recommended: 27 | 2026-08-06T02:13:48+00:00 | Vulnerability · Source |
| CVE-2017-11755 | suse_vex | SUSE CVE CVE-2017-11755 | known not affected: 91 | 2026-08-06T02:13:46+00:00 | Vulnerability · Source |
| CVE-2017-13775 | suse_vex | SUSE CVE CVE-2017-13775 | known affected: 10 known not affected: 144 | 2026-08-06T02:13:42+00:00 | Vulnerability · Source |
| CVE-2017-14120 | suse_vex | SUSE CVE CVE-2017-14120 | known not affected: 37 | 2026-08-06T02:13:40+00:00 | Vulnerability · Source |
| CVE-2017-14152 | suse_vex | SUSE CVE CVE-2017-14152 | known not affected: 110 recommended: 184 | 2026-08-06T02:13:38+00:00 | Vulnerability · Source |
| CVE-2017-14324 | suse_vex | SUSE CVE CVE-2017-14324 | known affected: 7 known not affected: 316 | 2026-08-06T02:13:36+00:00 | Vulnerability · Source |
| CVE-2017-15017 | suse_vex | SUSE CVE CVE-2017-15017 | known affected: 94 recommended: 186 | 2026-08-06T02:13:34+00:00 | Vulnerability · Source |
| CVE-2017-15033 | suse_vex | SUSE CVE CVE-2017-15033 | recommended: 186 | 2026-08-06T02:13:33+00:00 | Vulnerability · Source |
| CVE-2017-15595 | suse_vex | SUSE CVE CVE-2017-15595 | known affected: 32 known not affected: 63 recommended: 166 | 2026-08-06T02:13:30+00:00 | Vulnerability · Source |
| CVE-2017-16536 | suse_vex | SUSE CVE CVE-2017-16536 | known affected: 323 known not affected: 225 recommended: 1365 | 2026-08-06T02:13:26+00:00 | Vulnerability · Source |
| CVE-2017-16939 | suse_vex | SUSE CVE CVE-2017-16939 | known affected: 132 known not affected: 221 recommended: 766 | 2026-08-06T02:13:24+00:00 | Vulnerability · Source |
| CVE-2017-17724 | suse_vex | SUSE CVE CVE-2017-17724 | recommended: 4 | 2026-08-06T02:13:22+00:00 | Vulnerability · Source |
| CVE-2017-18030 | suse_vex | SUSE CVE CVE-2017-18030 | known not affected: 505 recommended: 237 | 2026-08-06T02:13:20+00:00 | Vulnerability · Source |
| CVE-2017-1000099 | suse_vex | SUSE CVE CVE-2017-1000099 | known affected: 320 known not affected: 122 recommended: 365 | 2026-08-06T02:13:16+00:00 | Vulnerability · Source |
| CVE-2017-1000366 | suse_vex | SUSE CVE CVE-2017-1000366 | known affected: 382 known not affected: 230 recommended: 1358 | 2026-08-06T02:13:13+00:00 | Vulnerability · Source |
| CVE-2018-4284 | suse_vex | SUSE CVE CVE-2018-4284 | known affected: 108 known not affected: 82 recommended: 969 | 2026-08-06T02:13:06+00:00 | Vulnerability · Source |
| CVE-2018-4700 | suse_vex | SUSE CVE CVE-2018-4700 | known affected: 376 known not affected: 21 recommended: 870 | 2026-08-06T02:13:04+00:00 | Vulnerability · Source |
| CVE-2018-5140 | suse_vex | SUSE CVE CVE-2018-5140 | known affected: 1 known not affected: 54 recommended: 12 | 2026-08-06T02:13:02+00:00 | Vulnerability · Source |
| CVE-2018-5333 | suse_vex | SUSE CVE CVE-2018-5333 | known affected: 57 known not affected: 352 recommended: 655 | 2026-08-06T02:12:59+00:00 | Vulnerability · Source |
| CVE-2018-5735 | suse_vex | SUSE CVE CVE-2018-5735 | known not affected: 105 | 2026-08-06T02:12:57+00:00 | Vulnerability · Source |
| CVE-2018-5738 | suse_vex | SUSE CVE CVE-2018-5738 | known affected: 27 known not affected: 378 recommended: 306 | 2026-08-06T02:12:56+00:00 | Vulnerability · Source |
| CVE-2018-6798 | suse_vex | SUSE CVE CVE-2018-6798 | known affected: 312 recommended: 428 | 2026-08-06T02:12:52+00:00 | Vulnerability · Source |
| CVE-2018-6872 | suse_vex | SUSE CVE CVE-2018-6872 | known affected: 452 known not affected: 62 recommended: 507 | 2026-08-06T02:12:51+00:00 | Vulnerability · Source |
| CVE-2018-6952 | suse_vex | SUSE CVE CVE-2018-6952 | known affected: 416 recommended: 47 | 2026-08-06T02:12:49+00:00 | Vulnerability · Source |
| CVE-2018-11235 | suse_vex | SUSE CVE CVE-2018-11235 | known affected: 128 known not affected: 38 recommended: 1099 | 2026-08-06T02:12:45+00:00 | Vulnerability · Source |
| CVE-2018-12130 | suse_vex | SUSE CVE CVE-2018-12130 | known affected: 1012 known not affected: 1993 recommended: 5738 | 2026-08-06T02:12:41+00:00 | Vulnerability · Source |
| CVE-2018-12376 | suse_vex | SUSE CVE CVE-2018-12376 | known not affected: 200 recommended: 819 | 2026-08-06T02:12:40+00:00 | Vulnerability · Source |
| CVE-2018-14437 | suse_vex | SUSE CVE CVE-2018-14437 | known not affected: 14 recommended: 739 | 2026-08-06T02:12:37+00:00 | Vulnerability · Source |
| CVE-2018-14629 | suse_vex | SUSE CVE CVE-2018-14629 | known affected: 320 known not affected: 1309 recommended: 2983 | 2026-08-06T02:12:35+00:00 | Vulnerability · Source |
| CVE-2018-16597 | suse_vex | SUSE CVE CVE-2018-16597 | known affected: 44 known not affected: 329 recommended: 91 | 2026-08-06T02:12:30+00:00 | Vulnerability · Source |
| CVE-2018-16841 | suse_vex | SUSE CVE CVE-2018-16841 | known affected: 320 known not affected: 1217 recommended: 2983 | 2026-08-06T02:12:28+00:00 | Vulnerability · Source |
| CVE-2018-16890 | suse_vex | SUSE CVE CVE-2018-16890 | known affected: 341 known not affected: 55 recommended: 435 | 2026-08-06T02:12:26+00:00 | Vulnerability · Source |
| CVE-2018-18559 | suse_vex | SUSE CVE CVE-2018-18559 | known not affected: 642 recommended: 13 | 2026-08-06T02:12:22+00:00 | Vulnerability · Source |
| CVE-2018-18897 | suse_vex | SUSE CVE CVE-2018-18897 | known affected: 16 known not affected: 386 recommended: 179 | 2026-08-06T02:12:21+00:00 | Vulnerability · Source |
| CVE-2018-19625 | suse_vex | SUSE CVE CVE-2018-19625 | known affected: 111 known not affected: 37 recommended: 922 | 2026-08-06T02:12:19+00:00 | Vulnerability · Source |
| CVE-2018-20855 | suse_vex | SUSE CVE CVE-2018-20855 | known not affected: 79 recommended: 883 | 2026-08-06T02:12:16+00:00 | Vulnerability · Source |
| CVE-2018-1000075 | suse_vex | SUSE CVE CVE-2018-1000075 | known affected: 320 known not affected: 90 recommended: 491 | 2026-08-06T02:12:14+00:00 | Vulnerability · Source |
| CVE-2019-0196 | suse_vex | SUSE CVE CVE-2019-0196 | known affected: 111 known not affected: 65 recommended: 212 | 2026-08-06T02:12:12+00:00 | Vulnerability · Source |
| CVE-2019-1563 | suse_vex | SUSE CVE CVE-2019-1563 | known affected: 404 known not affected: 271 recommended: 984 | 2026-08-06T02:12:10+00:00 | Vulnerability · Source |
| CVE-2019-3892 | suse_vex | SUSE CVE CVE-2019-3892 | known not affected: 78 | 2026-08-06T02:12:07+00:00 | Vulnerability · Source |
| CVE-2019-6502 | suse_vex | SUSE CVE CVE-2019-6502 | known affected: 17 known not affected: 9 recommended: 64 | 2026-08-06T02:12:04+00:00 | Vulnerability · Source |
| CVE-2019-8763 | suse_vex | SUSE CVE CVE-2019-8763 | known not affected: 10 recommended: 983 | 2026-08-06T02:12:01+00:00 | Vulnerability · Source |
| CVE-2019-11026 | suse_vex | SUSE CVE CVE-2019-11026 | known affected: 10 known not affected: 223 | 2026-08-06T02:11:53+00:00 | Vulnerability · Source |
| CVE-2019-11360 | suse_vex | SUSE CVE CVE-2019-11360 | known not affected: 248 | 2026-08-06T02:11:51+00:00 | Vulnerability · Source |