VEX records
Browse vendor VEX statements available in this Vulnerability-Lookup instance and pivot to the related vulnerability.
291911 VEX records
API response| Vulnerability | Source | Title | Product status | Imported | Links |
|---|---|---|---|---|---|
| CVE-2017-7542 | suse_vex | SUSE CVE CVE-2017-7542 | known affected: 26 known not affected: 406 recommended: 667 | 2026-08-02T16:54:10+00:00 | Vulnerability · Source |
| CVE-2017-7834 | suse_vex | SUSE CVE CVE-2017-7834 | known affected: 1 known not affected: 42 recommended: 12 | 2026-08-02T16:54:05+00:00 | Vulnerability · Source |
| CVE-2017-9043 | suse_vex | SUSE CVE CVE-2017-9043 | known not affected: 33 recommended: 54 | 2026-08-02T16:54:02+00:00 | Vulnerability · Source |
| CVE-2017-9106 | suse_vex | SUSE CVE CVE-2017-9106 | known affected: 18 recommended: 49 | 2026-08-02T16:54:00+00:00 | Vulnerability · Source |
| CVE-2017-9125 | suse_vex | SUSE CVE CVE-2017-9125 | known affected: 30 recommended: 208 | 2026-08-02T16:53:57+00:00 | Vulnerability · Source |
| CVE-2017-11499 | suse_vex | SUSE CVE CVE-2017-11499 | known not affected: 310 recommended: 495 | 2026-08-02T16:53:51+00:00 | Vulnerability · Source |
| CVE-2017-11523 | suse_vex | SUSE CVE CVE-2017-11523 | known affected: 94 known not affected: 50 recommended: 136 | 2026-08-02T16:53:50+00:00 | Vulnerability · Source |
| CVE-2017-11530 | suse_vex | SUSE CVE CVE-2017-11530 | known affected: 94 known not affected: 14 recommended: 172 | 2026-08-02T16:53:49+00:00 | Vulnerability · Source |
| CVE-2017-12185 | suse_vex | SUSE CVE CVE-2017-12185 | known affected: 2 known not affected: 51 recommended: 42 | 2026-08-02T16:53:46+00:00 | Vulnerability · Source |
| CVE-2017-13006 | suse_vex | SUSE CVE CVE-2017-13006 | known affected: 336 known not affected: 24 recommended: 151 | 2026-08-02T16:53:43+00:00 | Vulnerability · Source |
| CVE-2017-13747 | suse_vex | SUSE CVE CVE-2017-13747 | known affected: 6 known not affected: 56 | 2026-08-02T16:53:39+00:00 | Vulnerability · Source |
| CVE-2017-13758 | suse_vex | SUSE CVE CVE-2017-13758 | known not affected: 52 recommended: 150 | 2026-08-02T16:53:37+00:00 | Vulnerability · Source |
| CVE-2017-14061 | suse_vex | SUSE CVE CVE-2017-14061 | known affected: 8 known not affected: 272 | 2026-08-02T16:53:36+00:00 | Vulnerability · Source |
| CVE-2017-14989 | suse_vex | SUSE CVE CVE-2017-14989 | known affected: 94 known not affected: 50 recommended: 136 | 2026-08-02T16:53:33+00:00 | Vulnerability · Source |
| CVE-2017-15710 | suse_vex | SUSE CVE CVE-2017-15710 | known affected: 92 recommended: 168 | 2026-08-02T16:53:31+00:00 | Vulnerability · Source |
| CVE-2017-16527 | suse_vex | SUSE CVE CVE-2017-16527 | known not affected: 346 recommended: 496 | 2026-08-02T16:53:29+00:00 | Vulnerability · Source |
| CVE-2017-17052 | suse_vex | SUSE CVE CVE-2017-17052 | known not affected: 116 recommended: 293 | 2026-08-02T16:53:28+00:00 | Vulnerability · Source |
| CVE-2017-17500 | suse_vex | SUSE CVE CVE-2017-17500 | known affected: 3 known not affected: 128 recommended: 14 | 2026-08-02T16:53:25+00:00 | Vulnerability · Source |
| CVE-2017-1000377 | suse_vex | SUSE CVE CVE-2017-1000377 | known not affected: 298 | 2026-08-02T16:53:20+00:00 | Vulnerability · Source |
| CVE-2018-1111 | suse_vex | SUSE CVE CVE-2018-1111 | known not affected: 61 recommended: 5 | 2026-08-02T16:53:18+00:00 | Vulnerability · Source |
| CVE-2018-3630 | suse_vex | SUSE CVE CVE-2018-3630 | known affected: 50 recommended: 239 | 2026-08-02T16:53:15+00:00 | Vulnerability · Source |
| CVE-2018-10471 | suse_vex | SUSE CVE CVE-2018-10471 | known affected: 358 known not affected: 63 recommended: 535 | 2026-08-02T16:53:07+00:00 | Vulnerability · Source |
| CVE-2018-10938 | suse_vex | SUSE CVE CVE-2018-10938 | known affected: 140 known not affected: 273 recommended: 643 | 2026-08-02T16:53:05+00:00 | Vulnerability · Source |
| CVE-2018-12360 | suse_vex | SUSE CVE CVE-2018-12360 | known affected: 21 recommended: 451 | 2026-08-02T16:53:02+00:00 | Vulnerability · Source |
| CVE-2018-19409 | suse_vex | SUSE CVE CVE-2018-19409 | known affected: 17 known not affected: 87 recommended: 403 | 2026-08-02T16:52:50+00:00 | Vulnerability · Source |
| CVE-2018-19490 | suse_vex | SUSE CVE CVE-2018-19490 | known affected: 23 known not affected: 10 recommended: 91 | 2026-08-02T16:52:49+00:00 | Vulnerability · Source |
| CVE-2018-19638 | suse_vex | SUSE CVE CVE-2018-19638 | known affected: 320 recommended: 185 | 2026-08-02T16:52:47+00:00 | Vulnerability · Source |
| CVE-2018-20506 | suse_vex | SUSE CVE CVE-2018-20506 | known affected: 6 known not affected: 199 recommended: 72 | 2026-08-02T16:52:45+00:00 | Vulnerability · Source |
| CVE-2018-1000161 | suse_vex | SUSE CVE CVE-2018-1000161 | known not affected: 13 | 2026-08-02T16:52:42+00:00 | Vulnerability · Source |
| CVE-2019-2530 | suse_vex | SUSE CVE CVE-2019-2530 | known affected: 70 known not affected: 185 recommended: 10 | 2026-08-02T16:52:40+00:00 | Vulnerability · Source |
| CVE-2019-2964 | suse_vex | SUSE CVE CVE-2019-2964 | known affected: 525 recommended: 1129 | 2026-08-02T16:52:37+00:00 | Vulnerability · Source |
| CVE-2019-2975 | suse_vex | SUSE CVE CVE-2019-2975 | known affected: 525 recommended: 890 | 2026-08-02T16:52:36+00:00 | Vulnerability · Source |
| CVE-2019-2978 | suse_vex | SUSE CVE CVE-2019-2978 | known affected: 525 recommended: 1129 | 2026-08-02T16:52:34+00:00 | Vulnerability · Source |
| CVE-2019-2983 | suse_vex | SUSE CVE CVE-2019-2983 | known affected: 525 recommended: 1129 | 2026-08-02T16:52:32+00:00 | Vulnerability · Source |
| CVE-2019-8601 | suse_vex | SUSE CVE CVE-2019-8601 | known affected: 153 known not affected: 82 recommended: 298 | 2026-08-02T16:52:27+00:00 | Vulnerability · Source |
| CVE-2019-17594 | suse_vex | SUSE CVE CVE-2019-17594 | known affected: 544 known not affected: 107 recommended: 944 | 2026-08-02T16:52:08+00:00 | Vulnerability · Source |
| CVE-2019-19069 | suse_vex | SUSE CVE CVE-2019-19069 | known affected: 320 known not affected: 381 recommended: 781 | 2026-08-02T16:52:02+00:00 | Vulnerability · Source |
| CVE-2020-0110 | suse_vex | SUSE CVE CVE-2020-0110 | known affected: 320 known not affected: 277 recommended: 884 | 2026-08-02T16:51:59+00:00 | Vulnerability · Source |
| CVE-2020-8834 | suse_vex | SUSE CVE CVE-2020-8834 | known affected: 98 known not affected: 480 recommended: 492 | 2026-08-02T16:51:54+00:00 | Vulnerability · Source |
| CVE-2020-13844 | suse_vex | SUSE CVE CVE-2020-13844 | known affected: 401 known not affected: 1814 recommended: 5428 | 2026-08-02T16:51:46+00:00 | Vulnerability · Source |
| CVE-2020-14573 | suse_vex | SUSE CVE CVE-2020-14573 | known affected: 564 recommended: 308 | 2026-08-02T16:51:42+00:00 | Vulnerability · Source |
| CVE-2020-23793 | suse_vex | SUSE CVE CVE-2020-23793 | known not affected: 488 | 2026-08-02T16:51:39+00:00 | Vulnerability · Source |
| CVE-2020-25211 | suse_vex | SUSE CVE CVE-2020-25211 | known affected: 355 known not affected: 122 recommended: 1246 | 2026-08-02T16:51:37+00:00 | Vulnerability · Source |
| CVE-2020-25704 | suse_vex | SUSE CVE CVE-2020-25704 | known affected: 393 known not affected: 245 recommended: 1432 | 2026-08-02T16:51:34+00:00 | Vulnerability · Source |
| CVE-2021-29966 | suse_vex | SUSE CVE CVE-2021-29966 | known affected: 46 recommended: 9 | 2026-08-02T16:51:10+00:00 | Vulnerability · Source |
| CVE-2021-47579 | suse_vex | SUSE CVE CVE-2021-47579 | known affected: 80 known not affected: 66 recommended: 49 | 2026-08-02T16:50:48+00:00 | Vulnerability · Source |
| CVE-2022-2327 | suse_vex | SUSE CVE CVE-2022-2327 | known not affected: 566 | 2026-08-02T16:50:37+00:00 | Vulnerability · Source |
| CVE-2022-48765 | suse_vex | SUSE CVE CVE-2022-48765 | known affected: 330 known not affected: 205 recommended: 433 | 2026-08-02T16:50:09+00:00 | Vulnerability · Source |
| CVE-2022-48892 | suse_vex | SUSE CVE CVE-2022-48892 | known not affected: 310 | 2026-08-02T16:50:06+00:00 | Vulnerability · Source |
| CVE-2022-48961 | suse_vex | SUSE CVE CVE-2022-48961 | known affected: 324 known not affected: 395 recommended: 394 | 2026-08-02T16:50:04+00:00 | Vulnerability · Source |