VEX records
Browse vendor VEX statements available in this Vulnerability-Lookup instance and pivot to the related vulnerability.
291348 VEX records
API response| Vulnerability | Source | Title | Product status | Imported | Links |
|---|---|---|---|---|---|
| CVE-2017-5337 | suse_vex | SUSE CVE CVE-2017-5337 | known affected: 8 known not affected: 4 recommended: 176 | 2026-08-07T00:29:51+00:00 | Vulnerability · Source |
| CVE-2017-5841 | suse_vex | SUSE CVE CVE-2017-5841 | known not affected: 6 recommended: 448 | 2026-08-07T00:29:48+00:00 | Vulnerability · Source |
| CVE-2017-7479 | suse_vex | SUSE CVE CVE-2017-7479 | known affected: 30 recommended: 41 | 2026-08-07T00:29:42+00:00 | Vulnerability · Source |
| CVE-2017-7799 | suse_vex | SUSE CVE CVE-2017-7799 | known affected: 1 known not affected: 42 recommended: 12 | 2026-08-07T00:29:38+00:00 | Vulnerability · Source |
| CVE-2017-7816 | suse_vex | SUSE CVE CVE-2017-7816 | known not affected: 42 recommended: 12 | 2026-08-07T00:29:37+00:00 | Vulnerability · Source |
| CVE-2017-9612 | suse_vex | SUSE CVE CVE-2017-9612 | known affected: 1 recommended: 85 | 2026-08-07T00:29:31+00:00 | Vulnerability · Source |
| CVE-2017-9789 | suse_vex | SUSE CVE CVE-2017-9789 | known not affected: 63 recommended: 87 | 2026-08-07T00:29:29+00:00 | Vulnerability · Source |
| CVE-2017-11462 | suse_vex | SUSE CVE CVE-2017-11462 | known affected: 320 known not affected: 33 recommended: 690 | 2026-08-07T00:29:25+00:00 | Vulnerability · Source |
| CVE-2017-12424 | suse_vex | SUSE CVE CVE-2017-12424 | recommended: 15 | 2026-08-07T00:29:22+00:00 | Vulnerability · Source |
| CVE-2017-13079 | suse_vex | SUSE CVE CVE-2017-13079 | known affected: 6 known not affected: 354 recommended: 121 | 2026-08-07T00:29:19+00:00 | Vulnerability · Source |
| CVE-2017-13086 | suse_vex | SUSE CVE CVE-2017-13086 | known affected: 6 known not affected: 354 recommended: 95 | 2026-08-07T00:29:14+00:00 | Vulnerability · Source |
| CVE-2017-13729 | suse_vex | SUSE CVE CVE-2017-13729 | known affected: 157 recommended: 201 | 2026-08-07T00:29:10+00:00 | Vulnerability · Source |
| CVE-2017-13752 | suse_vex | SUSE CVE CVE-2017-13752 | known affected: 6 known not affected: 56 | 2026-08-07T00:29:08+00:00 | Vulnerability · Source |
| CVE-2017-14528 | suse_vex | SUSE CVE CVE-2017-14528 | known affected: 36 known not affected: 271 | 2026-08-07T00:29:06+00:00 | Vulnerability · Source |
| CVE-2017-16852 | suse_vex | SUSE CVE CVE-2017-16852 | known not affected: 74 recommended: 217 | 2026-08-07T00:29:02+00:00 | Vulnerability · Source |
| CVE-2017-17862 | suse_vex | SUSE CVE CVE-2017-17862 | known affected: 394 known not affected: 182 recommended: 502 | 2026-08-07T00:29:00+00:00 | Vulnerability · Source |
| CVE-2017-18202 | suse_vex | SUSE CVE CVE-2017-18202 | known affected: 12 known not affected: 102 recommended: 293 | 2026-08-07T00:28:58+00:00 | Vulnerability · Source |
| CVE-2017-1000363 | suse_vex | SUSE CVE CVE-2017-1000363 | known affected: 2 known not affected: 27 recommended: 242 | 2026-08-07T00:28:55+00:00 | Vulnerability · Source |
| CVE-2017-1000410 | suse_vex | SUSE CVE CVE-2017-1000410 | known affected: 36 known not affected: 108 recommended: 419 | 2026-08-07T00:28:52+00:00 | Vulnerability · Source |
| CVE-2018-2579 | suse_vex | SUSE CVE CVE-2018-2579 | known affected: 73 known not affected: 263 recommended: 730 | 2026-08-07T00:28:50+00:00 | Vulnerability · Source |
| CVE-2018-6068 | suse_vex | SUSE CVE CVE-2018-6068 | recommended: 10 | 2026-08-07T00:28:43+00:00 | Vulnerability · Source |
| CVE-2018-7333 | suse_vex | SUSE CVE CVE-2018-7333 | known affected: 1 known not affected: 115 recommended: 589 | 2026-08-07T00:28:40+00:00 | Vulnerability · Source |
| CVE-2018-7480 | suse_vex | SUSE CVE CVE-2018-7480 | known not affected: 297 recommended: 179 | 2026-08-07T00:28:36+00:00 | Vulnerability · Source |
| CVE-2018-9305 | suse_vex | SUSE CVE CVE-2018-9305 | known affected: 36 known not affected: 56 recommended: 161 | 2026-08-07T00:28:34+00:00 | Vulnerability · Source |
| CVE-2018-10981 | suse_vex | SUSE CVE CVE-2018-10981 | known affected: 358 known not affected: 63 recommended: 438 | 2026-08-07T00:28:30+00:00 | Vulnerability · Source |
| CVE-2018-13259 | suse_vex | SUSE CVE CVE-2018-13259 | known affected: 397 known not affected: 46 recommended: 91 | 2026-08-07T00:28:19+00:00 | Vulnerability · Source |
| CVE-2018-15855 | suse_vex | SUSE CVE CVE-2018-15855 | known affected: 565 known not affected: 65 recommended: 391 | 2026-08-07T00:28:13+00:00 | Vulnerability · Source |
| CVE-2018-17183 | suse_vex | SUSE CVE CVE-2018-17183 | known affected: 17 known not affected: 86 recommended: 403 | 2026-08-07T00:28:09+00:00 | Vulnerability · Source |
| CVE-2018-17985 | suse_vex | SUSE CVE CVE-2018-17985 | known affected: 448 recommended: 485 | 2026-08-07T00:28:05+00:00 | Vulnerability · Source |
| CVE-2018-18225 | suse_vex | SUSE CVE CVE-2018-18225 | known not affected: 266 recommended: 677 | 2026-08-07T00:28:04+00:00 | Vulnerability · Source |
| CVE-2018-18439 | suse_vex | SUSE CVE CVE-2018-18439 | known not affected: 27 recommended: 150 | 2026-08-07T00:28:02+00:00 | Vulnerability · Source |
| CVE-2018-18445 | suse_vex | SUSE CVE CVE-2018-18445 | known affected: 49 known not affected: 306 recommended: 425 | 2026-08-07T00:28:00+00:00 | Vulnerability · Source |
| CVE-2018-20544 | suse_vex | SUSE CVE CVE-2018-20544 | known not affected: 294 recommended: 214 | 2026-08-07T00:27:57+00:00 | Vulnerability · Source |
| CVE-2019-1547 | suse_vex | SUSE CVE CVE-2019-1547 | known affected: 435 known not affected: 179 recommended: 989 | 2026-08-07T00:27:54+00:00 | Vulnerability · Source |
| CVE-2019-2482 | suse_vex | SUSE CVE CVE-2019-2482 | known affected: 70 known not affected: 185 recommended: 10 | 2026-08-07T00:27:52+00:00 | Vulnerability · Source |
| CVE-2019-2762 | suse_vex | SUSE CVE CVE-2019-2762 | known affected: 500 known not affected: 9 recommended: 1149 | 2026-08-07T00:27:50+00:00 | Vulnerability · Source |
| CVE-2019-9077 | suse_vex | SUSE CVE CVE-2019-9077 | known affected: 428 recommended: 553 | 2026-08-07T00:27:40+00:00 | Vulnerability · Source |
| CVE-2019-9209 | suse_vex | SUSE CVE CVE-2019-9209 | known affected: 117 known not affected: 38 recommended: 922 | 2026-08-07T00:27:38+00:00 | Vulnerability · Source |
| CVE-2019-9636 | suse_vex | SUSE CVE CVE-2019-9636 | known affected: 449 recommended: 1772 | 2026-08-07T00:27:35+00:00 | Vulnerability · Source |
| CVE-2019-19553 | suse_vex | SUSE CVE CVE-2019-19553 | known not affected: 134 recommended: 677 | 2026-08-07T00:27:12+00:00 | Vulnerability · Source |
| CVE-2019-19924 | suse_vex | SUSE CVE CVE-2019-19924 | known affected: 368 known not affected: 268 recommended: 440 | 2026-08-07T00:27:08+00:00 | Vulnerability · Source |
| CVE-2019-19925 | suse_vex | SUSE CVE CVE-2019-19925 | known affected: 368 known not affected: 268 recommended: 453 | 2026-08-07T00:27:06+00:00 | Vulnerability · Source |
| CVE-2019-25161 | suse_vex | SUSE CVE CVE-2019-25161 | known affected: 51 known not affected: 496 | 2026-08-07T00:27:01+00:00 | Vulnerability · Source |
| CVE-2020-11501 | suse_vex | SUSE CVE CVE-2020-11501 | known affected: 320 known not affected: 170 recommended: 993 | 2026-08-07T00:26:48+00:00 | Vulnerability · Source |
| CVE-2020-11612 | suse_vex | SUSE CVE CVE-2020-11612 | known affected: 394 known not affected: 3 recommended: 6 | 2026-08-07T00:26:45+00:00 | Vulnerability · Source |
| CVE-2020-12393 | suse_vex | SUSE CVE CVE-2020-12393 | known affected: 21 recommended: 376 | 2026-08-07T00:26:43+00:00 | Vulnerability · Source |
| CVE-2020-12673 | suse_vex | SUSE CVE CVE-2020-12673 | known affected: 54 recommended: 589 | 2026-08-07T00:26:36+00:00 | Vulnerability · Source |
| CVE-2020-14155 | suse_vex | SUSE CVE CVE-2020-14155 | known affected: 320 recommended: 639 | 2026-08-07T00:26:32+00:00 | Vulnerability · Source |
| CVE-2020-25661 | suse_vex | SUSE CVE CVE-2020-25661 | known not affected: 327 recommended: 20 | 2026-08-07T00:26:25+00:00 | Vulnerability · Source |
| CVE-2020-26217 | suse_vex | SUSE CVE CVE-2020-26217 | known affected: 394 recommended: 188 | 2026-08-07T00:26:22+00:00 | Vulnerability · Source |