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-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 |
| CVE-2022-49020 | suse_vex | SUSE CVE CVE-2022-49020 | known affected: 579 known not affected: 55 recommended: 311 | 2026-08-02T16:50:00+00:00 | Vulnerability · Source |
| CVE-2022-49970 | suse_vex | SUSE CVE CVE-2022-49970 | known not affected: 401 recommended: 27 | 2026-08-02T16:49:47+00:00 | Vulnerability · Source |
| CVE-2022-50119 | suse_vex | SUSE CVE CVE-2022-50119 | known not affected: 401 | 2026-08-02T16:49:44+00:00 | Vulnerability · Source |
| CVE-2022-50723 | suse_vex | SUSE CVE CVE-2022-50723 | known affected: 374 known not affected: 396 recommended: 134 | 2026-08-02T16:49:38+00:00 | Vulnerability · Source |
| CVE-2023-28879 | suse_vex | SUSE CVE CVE-2023-28879 | known affected: 16 known not affected: 374 recommended: 206 | 2026-08-02T16:49:12+00:00 | Vulnerability · Source |
| CVE-2023-40267 | suse_vex | SUSE CVE CVE-2023-40267 | known not affected: 3 recommended: 12 | 2026-08-02T16:49:05+00:00 | Vulnerability · Source |
| CVE-2023-40476 | suse_vex | SUSE CVE CVE-2023-40476 | known affected: 312 recommended: 1483 | 2026-08-02T16:49:02+00:00 | Vulnerability · Source |
| CVE-2023-51780 | suse_vex | SUSE CVE CVE-2023-51780 | known affected: 333 recommended: 1380 | 2026-08-02T16:48:54+00:00 | Vulnerability · Source |
| CVE-2023-53022 | suse_vex | SUSE CVE CVE-2023-53022 | known affected: 55 known not affected: 289 | 2026-08-02T16:48:48+00:00 | Vulnerability · Source |
| CVE-2024-35946 | suse_vex | SUSE CVE CVE-2024-35946 | known affected: 394 known not affected: 270 recommended: 382 | 2026-08-02T16:48:16+00:00 | Vulnerability · Source |
| CVE-2024-40647 | suse_vex | SUSE CVE CVE-2024-40647 | recommended: 9 | 2026-08-02T16:48:11+00:00 | Vulnerability · Source |
| CVE-2024-49865 | suse_vex | SUSE CVE CVE-2024-49865 | known not affected: 379 recommended: 65 | 2026-08-02T16:47:58+00:00 | Vulnerability · Source |
| CVE-2024-56597 | suse_vex | SUSE CVE CVE-2024-56597 | known affected: 595 known not affected: 213 recommended: 411 | 2026-08-02T16:47:47+00:00 | Vulnerability · Source |
| CVE-2024-56627 | suse_vex | SUSE CVE CVE-2024-56627 | known not affected: 534 | 2026-08-02T16:47:45+00:00 | Vulnerability · Source |
| CVE-2025-11563 | suse_vex | SUSE CVE CVE-2025-11563 | known affected: 441 known not affected: 41 recommended: 137 | 2026-08-02T16:47:29+00:00 | Vulnerability · Source |
| CVE-2025-22039 | suse_vex | SUSE CVE CVE-2025-22039 | known not affected: 453 | 2026-08-02T16:47:22+00:00 | Vulnerability · Source |
| CVE-2025-22040 | suse_vex | SUSE CVE CVE-2025-22040 | known not affected: 453 | 2026-08-02T16:47:21+00:00 | Vulnerability · Source |
| CVE-2025-22041 | suse_vex | SUSE CVE CVE-2025-22041 | known not affected: 453 | 2026-08-02T16:47:19+00:00 | Vulnerability · Source |
| CVE-2025-49178 | suse_vex | SUSE CVE CVE-2025-49178 | known affected: 420 known not affected: 1 recommended: 184 | 2026-08-02T16:46:55+00:00 | Vulnerability · Source |
| CVE-2026-3184 | suse_vex | SUSE CVE CVE-2026-3184 | known affected: 715 recommended: 416 | 2026-08-02T16:46:43+00:00 | Vulnerability · Source |
| CVE-2026-5745 | suse_vex | SUSE CVE CVE-2026-5745 | known affected: 154 known not affected: 7 | 2026-08-02T16:46:39+00:00 | Vulnerability · Source |
| CVE-2026-23427 | suse_vex | SUSE CVE CVE-2026-23427 | known not affected: 338 | 2026-08-02T16:38:02+00:00 | Vulnerability · Source |
| CVE-2026-23428 | suse_vex | SUSE CVE CVE-2026-23428 | known not affected: 338 | 2026-08-02T16:38:00+00:00 | Vulnerability · Source |
| CVE-2026-31409 | suse_vex | SUSE CVE CVE-2026-31409 | known not affected: 338 | 2026-08-02T16:37:54+00:00 | Vulnerability · Source |