VEX records
Browse vendor VEX statements available in this Vulnerability-Lookup instance and pivot to the related vulnerability.
293915 VEX records
API response| Vulnerability | Source | Title | Product status | Imported | Links |
|---|---|---|---|---|---|
| CVE-2019-13454 | suse_vex | SUSE CVE CVE-2019-13454 | known affected: 142 recommended: 712 | 2026-07-26T16:55:43+00:00 | Vulnerability · Source |
| CVE-2019-14196 | suse_vex | SUSE CVE CVE-2019-14196 | known affected: 19 recommended: 46 | 2026-07-26T16:55:40+00:00 | Vulnerability · Source |
| CVE-2019-14607 | suse_vex | SUSE CVE CVE-2019-14607 | known not affected: 28 | 2026-07-26T16:55:34+00:00 | Vulnerability · Source |
| CVE-2019-14444 | suse_vex | SUSE CVE CVE-2019-14444 | known affected: 428 recommended: 553 | 2026-07-26T16:55:34+00:00 | Vulnerability · Source |
| CVE-2019-15791 | suse_vex | SUSE CVE CVE-2019-15791 | known not affected: 208 | 2026-07-26T16:55:31+00:00 | Vulnerability · Source |
| CVE-2019-17040 | suse_vex | SUSE CVE CVE-2019-17040 | known affected: 22 known not affected: 241 | 2026-07-26T16:55:27+00:00 | Vulnerability · Source |
| CVE-2019-17347 | suse_vex | SUSE CVE CVE-2019-17347 | known affected: 18 known not affected: 166 recommended: 207 | 2026-07-26T16:55:26+00:00 | Vulnerability · Source |
| CVE-2019-17582 | suse_vex | SUSE CVE CVE-2019-17582 | known not affected: 131 | 2026-07-26T16:55:23+00:00 | Vulnerability · Source |
| CVE-2019-19242 | suse_vex | SUSE CVE CVE-2019-19242 | known not affected: 358 | 2026-07-26T16:55:19+00:00 | Vulnerability · Source |
| CVE-2019-19815 | suse_vex | SUSE CVE CVE-2019-19815 | known not affected: 257 | 2026-07-26T16:55:17+00:00 | Vulnerability · Source |
| CVE-2019-20808 | suse_vex | SUSE CVE CVE-2019-20808 | known not affected: 715 | 2026-07-26T16:55:07+00:00 | Vulnerability · Source |
| CVE-2019-1010238 | suse_vex | SUSE CVE CVE-2019-1010238 | known not affected: 156 recommended: 8 | 2026-07-26T16:55:02+00:00 | Vulnerability · Source |
| CVE-2020-1699 | suse_vex | SUSE CVE CVE-2020-1699 | known affected: 85 known not affected: 317 recommended: 214 | 2026-07-26T16:54:59+00:00 | Vulnerability · Source |
| CVE-2020-10135 | suse_vex | SUSE CVE CVE-2020-10135 | known affected: 407 known not affected: 21 recommended: 1647 | 2026-07-26T16:54:49+00:00 | Vulnerability · Source |
| CVE-2020-11931 | suse_vex | SUSE CVE CVE-2020-11931 | known not affected: 428 | 2026-07-26T16:54:43+00:00 | Vulnerability · Source |
| CVE-2020-13379 | suse_vex | SUSE CVE CVE-2020-13379 | known affected: 1 recommended: 886 | 2026-07-26T16:54:37+00:00 | Vulnerability · Source |
| CVE-2020-15802 | suse_vex | SUSE CVE CVE-2020-15802 | known affected: 2 | 2026-07-26T16:54:29+00:00 | Vulnerability · Source |
| CVE-2020-21678 | suse_vex | SUSE CVE CVE-2020-21678 | known not affected: 30 | 2026-07-26T16:54:19+00:00 | Vulnerability · Source |
| CVE-2020-25743 | suse_vex | SUSE CVE CVE-2020-25743 | known affected: 42 known not affected: 729 | 2026-07-26T16:54:07+00:00 | Vulnerability · Source |
| CVE-2020-26952 | suse_vex | SUSE CVE CVE-2020-26952 | known affected: 59 recommended: 9 | 2026-07-26T16:53:59+00:00 | Vulnerability · Source |
| CVE-2020-35513 | suse_vex | SUSE CVE CVE-2020-35513 | known not affected: 409 recommended: 13 | 2026-07-26T16:53:48+00:00 | Vulnerability · Source |
| CVE-2020-35517 | suse_vex | SUSE CVE CVE-2020-35517 | known not affected: 1180 | 2026-07-26T16:53:47+00:00 | Vulnerability · Source |
| CVE-2020-36775 | suse_vex | SUSE CVE CVE-2020-36775 | known not affected: 304 | 2026-07-26T16:53:43+00:00 | Vulnerability · Source |
| CVE-2021-0938 | suse_vex | SUSE CVE CVE-2021-0938 | known not affected: 316 | 2026-07-26T16:53:39+00:00 | Vulnerability · Source |
| CVE-2021-3658 | suse_vex | SUSE CVE CVE-2021-3658 | known affected: 6 known not affected: 42 recommended: 109 | 2026-07-26T16:53:31+00:00 | Vulnerability · Source |
| CVE-2021-28662 | suse_vex | SUSE CVE CVE-2021-28662 | known affected: 394 known not affected: 72 recommended: 52 | 2026-07-26T16:53:14+00:00 | Vulnerability · Source |
| CVE-2021-35604 | suse_vex | SUSE CVE CVE-2021-35604 | known not affected: 86 recommended: 446 | 2026-07-26T16:52:54+00:00 | Vulnerability · Source |
| CVE-2021-38604 | suse_vex | SUSE CVE CVE-2021-38604 | known not affected: 651 | 2026-07-26T16:52:52+00:00 | Vulnerability · Source |
| CVE-2021-46101 | suse_vex | SUSE CVE CVE-2021-46101 | known not affected: 573 | 2026-07-26T16:52:42+00:00 | Vulnerability · Source |
| CVE-2021-46935 | suse_vex | SUSE CVE CVE-2021-46935 | known not affected: 312 | 2026-07-26T16:52:39+00:00 | Vulnerability · Source |
| CVE-2022-2526 | suse_vex | SUSE CVE CVE-2022-2526 | known not affected: 598 recommended: 18 | 2026-07-26T16:51:52+00:00 | Vulnerability · Source |
| CVE-2022-49675 | suse_vex | SUSE CVE CVE-2022-49675 | known affected: 334 known not affected: 298 recommended: 243 | 2026-07-26T16:50:06+00:00 | Vulnerability · Source |
| CVE-2022-50033 | suse_vex | SUSE CVE CVE-2022-50033 | known affected: 429 known not affected: 196 recommended: 337 | 2026-07-26T16:49:51+00:00 | Vulnerability · Source |
| CVE-2022-50296 | suse_vex | SUSE CVE CVE-2022-50296 | known affected: 10 known not affected: 406 | 2026-07-26T16:49:41+00:00 | Vulnerability · Source |
| CVE-2022-50437 | suse_vex | SUSE CVE CVE-2022-50437 | known affected: 344 known not affected: 267 recommended: 273 | 2026-07-26T16:49:30+00:00 | Vulnerability · Source |
| CVE-2022-50518 | suse_vex | SUSE CVE CVE-2022-50518 | known not affected: 416 | 2026-07-26T16:49:22+00:00 | Vulnerability · Source |
| CVE-2022-50638 | suse_vex | SUSE CVE CVE-2022-50638 | known affected: 470 known not affected: 188 recommended: 282 | 2026-07-26T16:49:17+00:00 | Vulnerability · Source |
| CVE-2023-3326 | suse_vex | SUSE CVE CVE-2023-3326 | known not affected: 1172 | 2026-07-26T16:49:06+00:00 | Vulnerability · Source |
| CVE-2023-4156 | suse_vex | SUSE CVE CVE-2023-4156 | known affected: 184 recommended: 251 | 2026-07-26T16:49:00+00:00 | Vulnerability · Source |
| CVE-2023-29451 | suse_vex | SUSE CVE CVE-2023-29451 | known not affected: 21 | 2026-07-26T16:48:39+00:00 | Vulnerability · Source |
| CVE-2023-44431 | suse_vex | SUSE CVE CVE-2023-44431 | known not affected: 196 recommended: 5 | 2026-07-26T16:48:25+00:00 | Vulnerability · Source |
| CVE-2023-45872 | suse_vex | SUSE CVE CVE-2023-45872 | known not affected: 165 | 2026-07-26T16:48:19+00:00 | Vulnerability · Source |
| CVE-2023-52466 | suse_vex | SUSE CVE CVE-2023-52466 | known not affected: 312 | 2026-07-26T16:48:06+00:00 | Vulnerability · Source |
| CVE-2023-53378 | suse_vex | SUSE CVE CVE-2023-53378 | known affected: 369 known not affected: 359 recommended: 92 | 2026-07-26T16:47:23+00:00 | Vulnerability · Source |
| CVE-2023-53761 | suse_vex | SUSE CVE CVE-2023-53761 | known affected: 402 known not affected: 283 recommended: 229 | 2026-07-26T16:47:10+00:00 | Vulnerability · Source |
| CVE-2023-54180 | suse_vex | SUSE CVE CVE-2023-54180 | known affected: 260 known not affected: 195 | 2026-07-26T16:47:02+00:00 | Vulnerability · Source |
| CVE-2024-22121 | suse_vex | SUSE CVE CVE-2024-22121 | known not affected: 11 | 2026-07-26T16:46:27+00:00 | Vulnerability · Source |
| CVE-2025-0246 | suse_vex | SUSE CVE CVE-2025-0246 | known affected: 57 recommended: 9 | 2026-07-26T16:44:11+00:00 | Vulnerability · Source |
| CVE-2025-1941 | suse_vex | SUSE CVE CVE-2025-1941 | recommended: 9 | 2026-07-26T16:44:06+00:00 | Vulnerability · Source |
| CVE-2025-1943 | suse_vex | SUSE CVE CVE-2025-1943 | recommended: 9 | 2026-07-26T16:44:05+00:00 | Vulnerability · Source |