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-2019-9948 | suse_vex | SUSE CVE CVE-2019-9948 | known affected: 458 known not affected: 289 recommended: 834 | 2026-08-01T23:33:40+00:00 | Vulnerability · Source |
| CVE-2019-11486 | suse_vex | SUSE CVE CVE-2019-11486 | known affected: 107 known not affected: 21 recommended: 841 | 2026-08-01T23:33:34+00:00 | Vulnerability · Source |
| CVE-2019-11757 | suse_vex | SUSE CVE CVE-2019-11757 | known not affected: 160 recommended: 450 | 2026-08-01T23:33:33+00:00 | Vulnerability · Source |
| CVE-2019-13111 | suse_vex | SUSE CVE CVE-2019-13111 | known affected: 60 known not affected: 131 recommended: 139 | 2026-08-01T23:33:31+00:00 | Vulnerability · Source |
| CVE-2019-13115 | suse_vex | SUSE CVE CVE-2019-13115 | known not affected: 233 | 2026-08-01T23:33:30+00:00 | Vulnerability · Source |
| CVE-2019-14899 | suse_vex | SUSE CVE CVE-2019-14899 | known not affected: 371 | 2026-08-01T23:33:27+00:00 | Vulnerability · Source |
| CVE-2019-15292 | suse_vex | SUSE CVE CVE-2019-15292 | known affected: 95 known not affected: 224 recommended: 698 | 2026-08-01T23:33:24+00:00 | Vulnerability · Source |
| CVE-2019-16714 | suse_vex | SUSE CVE CVE-2019-16714 | known not affected: 223 | 2026-08-01T23:33:21+00:00 | Vulnerability · Source |
| CVE-2019-17624 | suse_vex | SUSE CVE CVE-2019-17624 | known affected: 40 known not affected: 71 | 2026-08-01T23:33:20+00:00 | Vulnerability · Source |
| CVE-2019-18282 | suse_vex | SUSE CVE CVE-2019-18282 | known not affected: 426 recommended: 33 | 2026-08-01T23:33:18+00:00 | Vulnerability · Source |
| CVE-2019-18902 | suse_vex | SUSE CVE CVE-2019-18902 | known affected: 361 known not affected: 18 recommended: 245 | 2026-08-01T23:33:15+00:00 | Vulnerability · Source |
| CVE-2019-19071 | suse_vex | SUSE CVE CVE-2019-19071 | known affected: 320 known not affected: 376 recommended: 781 | 2026-08-01T23:33:14+00:00 | Vulnerability · Source |
| CVE-2019-19449 | suse_vex | SUSE CVE CVE-2019-19449 | known not affected: 459 | 2026-08-01T23:33:11+00:00 | Vulnerability · Source |
| CVE-2019-20382 | suse_vex | SUSE CVE CVE-2019-20382 | known affected: 196 known not affected: 180 recommended: 505 | 2026-08-01T23:33:09+00:00 | Vulnerability · Source |
| CVE-2020-0030 | suse_vex | SUSE CVE CVE-2020-0030 | known not affected: 204 | 2026-08-01T23:33:07+00:00 | Vulnerability · Source |
| CVE-2020-10134 | suse_vex | SUSE CVE CVE-2020-10134 | known affected: 3 | 2026-08-01T23:32:57+00:00 | Vulnerability · Source |
| CVE-2020-13249 | suse_vex | SUSE CVE CVE-2020-13249 | known affected: 75 known not affected: 69 recommended: 648 | 2026-08-01T23:32:51+00:00 | Vulnerability · Source |
| CVE-2020-13435 | suse_vex | SUSE CVE CVE-2020-13435 | known affected: 364 known not affected: 279 recommended: 459 | 2026-08-01T23:32:49+00:00 | Vulnerability · Source |
| CVE-2020-13791 | suse_vex | SUSE CVE CVE-2020-13791 | known not affected: 538 | 2026-08-01T23:32:48+00:00 | Vulnerability · Source |
| CVE-2020-13962 | suse_vex | SUSE CVE CVE-2020-13962 | known affected: 394 known not affected: 1364 recommended: 2088 | 2026-08-01T23:32:46+00:00 | Vulnerability · Source |
| CVE-2020-14303 | suse_vex | SUSE CVE CVE-2020-14303 | known affected: 675 known not affected: 822 recommended: 3070 | 2026-08-01T23:32:44+00:00 | Vulnerability · Source |
| CVE-2020-14579 | suse_vex | SUSE CVE CVE-2020-14579 | known affected: 170 recommended: 945 | 2026-08-01T23:32:41+00:00 | Vulnerability · Source |
| CVE-2020-16591 | suse_vex | SUSE CVE CVE-2020-16591 | known affected: 395 known not affected: 85 recommended: 540 | 2026-08-01T23:32:39+00:00 | Vulnerability · Source |
| CVE-2020-25624 | suse_vex | SUSE CVE CVE-2020-25624 | known affected: 388 known not affected: 587 recommended: 850 | 2026-08-01T23:32:36+00:00 | Vulnerability · Source |
| CVE-2020-25650 | suse_vex | SUSE CVE CVE-2020-25650 | known affected: 13 recommended: 67 | 2026-08-01T23:32:34+00:00 | Vulnerability · Source |
| CVE-2020-25684 | suse_vex | SUSE CVE CVE-2020-25684 | recommended: 113 | 2026-08-01T23:32:32+00:00 | Vulnerability · Source |
| CVE-2020-26141 | suse_vex | SUSE CVE CVE-2020-26141 | known affected: 318 known not affected: 158 recommended: 1522 | 2026-08-01T23:32:30+00:00 | Vulnerability · Source |
| CVE-2020-29443 | suse_vex | SUSE CVE CVE-2020-29443 | known affected: 388 known not affected: 146 recommended: 854 | 2026-08-01T23:32:27+00:00 | Vulnerability · Source |
| CVE-2020-36227 | suse_vex | SUSE CVE CVE-2020-36227 | known affected: 298 recommended: 854 | 2026-08-01T23:32:25+00:00 | Vulnerability · Source |
| CVE-2021-3347 | suse_vex | SUSE CVE CVE-2021-3347 | known affected: 441 known not affected: 124 recommended: 1704 | 2026-08-01T23:32:21+00:00 | Vulnerability · Source |
| CVE-2021-3621 | suse_vex | SUSE CVE CVE-2021-3621 | known affected: 1 known not affected: 171 recommended: 1721 | 2026-08-01T23:32:18+00:00 | Vulnerability · Source |
| CVE-2021-3770 | suse_vex | SUSE CVE CVE-2021-3770 | known not affected: 160 | 2026-08-01T23:32:16+00:00 | Vulnerability · Source |
| CVE-2021-38160 | suse_vex | SUSE CVE CVE-2021-38160 | known affected: 311 known not affected: 61 recommended: 1753 | 2026-08-01T23:32:02+00:00 | Vulnerability · Source |
| CVE-2021-46916 | suse_vex | SUSE CVE CVE-2021-46916 | known not affected: 312 | 2026-08-01T23:31:57+00:00 | Vulnerability · Source |
| CVE-2021-46970 | suse_vex | SUSE CVE CVE-2021-46970 | known not affected: 292 | 2026-08-01T23:31:56+00:00 | Vulnerability · Source |
| CVE-2021-47325 | suse_vex | SUSE CVE CVE-2021-47325 | known affected: 55 known not affected: 280 | 2026-08-01T23:31:50+00:00 | Vulnerability · Source |
| CVE-2021-47385 | suse_vex | SUSE CVE CVE-2021-47385 | known affected: 275 known not affected: 217 recommended: 501 | 2026-08-01T23:31:49+00:00 | Vulnerability · Source |
| CVE-2022-21553 | suse_vex | SUSE CVE CVE-2022-21553 | recommended: 17 | 2026-08-01T23:31:34+00:00 | Vulnerability · Source |
| CVE-2022-21724 | suse_vex | SUSE CVE CVE-2022-21724 | known not affected: 47 recommended: 1 | 2026-08-01T23:31:32+00:00 | Vulnerability · Source |
| CVE-2022-28199 | suse_vex | SUSE CVE CVE-2022-28199 | known not affected: 102 recommended: 276 | 2026-08-01T23:31:28+00:00 | Vulnerability · Source |
| CVE-2022-48866 | suse_vex | SUSE CVE CVE-2022-48866 | known affected: 295 known not affected: 205 recommended: 468 | 2026-08-01T23:31:15+00:00 | Vulnerability · Source |
| CVE-2022-49780 | suse_vex | SUSE CVE CVE-2022-49780 | known affected: 643 known not affected: 135 recommended: 37 | 2026-08-01T23:31:04+00:00 | Vulnerability · Source |
| CVE-2022-50745 | suse_vex | SUSE CVE CVE-2022-50745 | known affected: 354 known not affected: 341 recommended: 196 | 2026-08-01T23:30:55+00:00 | Vulnerability · Source |
| CVE-2023-51580 | suse_vex | SUSE CVE CVE-2023-51580 | known not affected: 85 recommended: 5 | 2026-08-01T23:30:32+00:00 | Vulnerability · Source |
| CVE-2024-11701 | suse_vex | SUSE CVE CVE-2024-11701 | known affected: 29 recommended: 9 | 2026-08-01T23:30:14+00:00 | Vulnerability · Source |
| CVE-2024-26652 | suse_vex | SUSE CVE CVE-2024-26652 | known not affected: 403 recommended: 264 | 2026-08-01T23:30:08+00:00 | Vulnerability · Source |
| CVE-2024-39133 | suse_vex | SUSE CVE CVE-2024-39133 | known not affected: 114 recommended: 14 | 2026-08-01T23:29:56+00:00 | Vulnerability · Source |
| CVE-2024-49975 | suse_vex | SUSE CVE CVE-2024-49975 | known affected: 582 known not affected: 42 recommended: 670 | 2026-08-01T23:29:43+00:00 | Vulnerability · Source |
| CVE-2025-47273 | suse_vex | SUSE CVE CVE-2025-47273 | known affected: 365 known not affected: 9 recommended: 350 | 2026-08-01T23:28:57+00:00 | Vulnerability · Source |
| CVE-2025-69418 | suse_vex | SUSE CVE CVE-2025-69418 | known affected: 406 known not affected: 250 recommended: 329 | 2026-08-01T23:28:48+00:00 | Vulnerability · Source |