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-2020-25969 | suse_vex | SUSE CVE CVE-2020-25969 | known affected: 15 known not affected: 54 recommended: 5 | 2026-08-01T00:17:49+00:00 | Vulnerability · Source |
| CVE-2020-36228 | suse_vex | SUSE CVE CVE-2020-36228 | known affected: 298 recommended: 854 | 2026-08-01T00:17:46+00:00 | Vulnerability · Source |
| CVE-2021-3996 | suse_vex | SUSE CVE CVE-2021-3996 | known affected: 347 known not affected: 753 recommended: 863 | 2026-08-01T00:17:38+00:00 | Vulnerability · Source |
| CVE-2021-4442 | suse_vex | SUSE CVE CVE-2021-4442 | known affected: 458 known not affected: 308 recommended: 32 | 2026-08-01T00:17:36+00:00 | Vulnerability · Source |
| CVE-2021-21996 | suse_vex | SUSE CVE CVE-2021-21996 | known affected: 396 known not affected: 108 recommended: 900 | 2026-08-01T00:17:33+00:00 | Vulnerability · Source |
| CVE-2021-22897 | suse_vex | SUSE CVE CVE-2021-22897 | known not affected: 144 | 2026-08-01T00:17:31+00:00 | Vulnerability · Source |
| CVE-2021-47167 | suse_vex | SUSE CVE CVE-2021-47167 | known affected: 477 known not affected: 204 recommended: 221 | 2026-08-01T00:17:16+00:00 | Vulnerability · Source |
| CVE-2022-3550 | suse_vex | SUSE CVE CVE-2022-3550 | known affected: 394 recommended: 288 | 2026-08-01T00:17:06+00:00 | Vulnerability · Source |
| CVE-2022-22942 | suse_vex | SUSE CVE CVE-2022-22942 | known affected: 276 known not affected: 225 recommended: 1564 | 2026-08-01T00:16:59+00:00 | Vulnerability · Source |
| CVE-2022-49079 | suse_vex | SUSE CVE CVE-2022-49079 | known not affected: 352 | 2026-08-01T00:16:38+00:00 | Vulnerability · Source |
| CVE-2022-49271 | suse_vex | SUSE CVE CVE-2022-49271 | known affected: 441 known not affected: 195 recommended: 271 | 2026-08-01T00:16:33+00:00 | Vulnerability · Source |
| CVE-2022-49862 | suse_vex | SUSE CVE CVE-2022-49862 | known affected: 551 known not affected: 214 recommended: 70 | 2026-08-01T00:16:26+00:00 | Vulnerability · Source |
| CVE-2022-50883 | suse_vex | SUSE CVE CVE-2022-50883 | known affected: 374 known not affected: 396 recommended: 116 | 2026-08-01T00:16:16+00:00 | Vulnerability · Source |
| CVE-2023-6507 | suse_vex | SUSE CVE CVE-2023-6507 | known not affected: 519 recommended: 51 | 2026-08-01T00:16:03+00:00 | Vulnerability · Source |
| CVE-2023-50229 | suse_vex | SUSE CVE CVE-2023-50229 | known affected: 65 known not affected: 32 recommended: 112 | 2026-08-01T00:15:51+00:00 | Vulnerability · Source |
| CVE-2024-46823 | suse_vex | SUSE CVE CVE-2024-46823 | known not affected: 518 | 2026-08-01T00:14:56+00:00 | Vulnerability · Source |
| CVE-2024-47615 | suse_vex | SUSE CVE CVE-2024-47615 | known affected: 412 recommended: 1051 | 2026-08-01T00:14:53+00:00 | Vulnerability · Source |
| CVE-2024-53222 | suse_vex | SUSE CVE CVE-2024-53222 | known affected: 398 known not affected: 399 recommended: 448 | 2026-08-01T00:14:40+00:00 | Vulnerability · Source |
| CVE-2025-13018 | suse_vex | SUSE CVE CVE-2025-13018 | known affected: 14 recommended: 187 | 2026-08-01T00:14:20+00:00 | Vulnerability · Source |
| CVE-2025-27516 | suse_vex | SUSE CVE CVE-2025-27516 | known affected: 387 recommended: 150 | 2026-08-01T00:14:07+00:00 | Vulnerability · Source |
| CVE-2025-39797 | suse_vex | SUSE CVE CVE-2025-39797 | first fixed: 2 known affected: 352 known not affected: 150 recommended: 744 | 2026-08-01T00:13:25+00:00 | Vulnerability · Source |
| CVE-2026-0861 | suse_vex | SUSE CVE CVE-2026-0861 | first fixed: 1 known affected: 380 known not affected: 198 recommended: 892 | 2026-08-01T00:12:24+00:00 | Vulnerability · Source |
| CVE-2026-0915 | suse_vex | SUSE CVE CVE-2026-0915 | first fixed: 1 known affected: 492 recommended: 999 | 2026-08-01T00:12:22+00:00 | Vulnerability · Source |
| CVE-2026-0968 | suse_vex | SUSE CVE CVE-2026-0968 | known affected: 366 known not affected: 99 recommended: 109 | 2026-08-01T00:12:19+00:00 | Vulnerability · Source |
| CVE-2026-4046 | suse_vex | SUSE CVE CVE-2026-4046 | first fixed: 1 known affected: 516 known not affected: 56 recommended: 1114 | 2026-08-01T00:12:12+00:00 | Vulnerability · Source |
| CVE-2026-5958 | suse_vex | SUSE CVE CVE-2026-5958 | known affected: 396 recommended: 75 | 2026-08-01T00:12:03+00:00 | Vulnerability · Source |
| CVE-2026-9079 | suse_vex | SUSE CVE CVE-2026-9079 | first fixed: 13 known affected: 422 known not affected: 39 recommended: 124 | 2026-08-01T00:11:51+00:00 | Vulnerability · Source |
| CVE-2026-9080 | suse_vex | SUSE CVE CVE-2026-9080 | first fixed: 13 known affected: 422 known not affected: 39 recommended: 124 | 2026-08-01T00:11:49+00:00 | Vulnerability · Source |
| CVE-2026-9149 | suse_vex | SUSE CVE CVE-2026-9149 | first fixed: 36 known affected: 447 known not affected: 25 recommended: 135 | 2026-08-01T00:11:47+00:00 | Vulnerability · Source |
| CVE-2026-9150 | suse_vex | SUSE CVE CVE-2026-9150 | first fixed: 36 known affected: 447 known not affected: 25 recommended: 135 | 2026-08-01T00:11:45+00:00 | Vulnerability · Source |
| CVE-2026-9545 | suse_vex | SUSE CVE CVE-2026-9545 | first fixed: 13 known affected: 422 known not affected: 39 recommended: 124 | 2026-08-01T00:11:43+00:00 | Vulnerability · Source |
| CVE-2026-12912 | suse_vex | SUSE CVE CVE-2026-12912 | known affected: 433 recommended: 118 | 2026-08-01T00:11:37+00:00 | Vulnerability · Source |
| CVE-2026-14355 | suse_vex | SUSE CVE CVE-2026-14355 | first fixed: 104 known affected: 1104 recommended: 650 | 2026-08-01T00:11:30+00:00 | Vulnerability · Source |
| CVE-2026-22795 | suse_vex | SUSE CVE CVE-2026-22795 | known affected: 406 known not affected: 251 recommended: 329 | 2026-08-01T00:10:27+00:00 | Vulnerability · Source |
| CVE-2026-22796 | suse_vex | SUSE CVE CVE-2026-22796 | known affected: 494 known not affected: 96 recommended: 391 | 2026-08-01T00:10:26+00:00 | Vulnerability · Source |
| CVE-2026-31790 | suse_vex | SUSE CVE CVE-2026-31790 | known affected: 394 known not affected: 373 recommended: 314 | 2026-08-01T00:08:57+00:00 | Vulnerability · Source |
| CVE-2026-34181 | suse_vex | SUSE CVE CVE-2026-34181 | known affected: 413 known not affected: 443 recommended: 38 | 2026-08-01T00:08:47+00:00 | Vulnerability · Source |
| CVE-2026-34183 | suse_vex | SUSE CVE CVE-2026-34183 | known affected: 413 known not affected: 443 recommended: 80 | 2026-08-01T00:08:46+00:00 | Vulnerability · Source |
| CVE-2026-42768 | suse_vex | SUSE CVE CVE-2026-42768 | known affected: 431 known not affected: 425 recommended: 80 | 2026-08-01T00:08:18+00:00 | Vulnerability · Source |
| CVE-2026-42769 | suse_vex | SUSE CVE CVE-2026-42769 | known affected: 413 known not affected: 443 recommended: 80 | 2026-08-01T00:08:16+00:00 | Vulnerability · Source |
| CVE-2026-51235 | suse_vex | SUSE CVE CVE-2026-51235 | No product status | 2026-08-01T00:06:43+00:00 | Vulnerability · Source |
| CVE-2026-51296 | suse_vex | SUSE CVE CVE-2026-51296 | No product status | 2026-08-01T00:06:41+00:00 | Vulnerability · Source |
| CVE-2026-51297 | suse_vex | SUSE CVE CVE-2026-51297 | No product status | 2026-08-01T00:06:40+00:00 | Vulnerability · Source |
| CVE-2026-51298 | suse_vex | SUSE CVE CVE-2026-51298 | No product status | 2026-08-01T00:06:38+00:00 | Vulnerability · Source |
| CVE-2026-51300 | suse_vex | SUSE CVE CVE-2026-51300 | No product status | 2026-08-01T00:06:36+00:00 | Vulnerability · Source |
| CVE-2026-51302 | suse_vex | SUSE CVE CVE-2026-51302 | No product status | 2026-08-01T00:06:34+00:00 | Vulnerability · Source |
| CVE-2026-51303 | suse_vex | SUSE CVE CVE-2026-51303 | No product status | 2026-08-01T00:06:32+00:00 | Vulnerability · Source |
| CVE-2026-51304 | suse_vex | SUSE CVE CVE-2026-51304 | No product status | 2026-08-01T00:06:31+00:00 | Vulnerability · Source |
| CVE-2026-54706 | suse_vex | SUSE CVE CVE-2026-54706 | recommended: 1 | 2026-08-01T00:06:08+00:00 | Vulnerability · Source |
| CVE-2026-54707 | suse_vex | SUSE CVE CVE-2026-54707 | recommended: 1 | 2026-08-01T00:06:07+00:00 | Vulnerability · Source |