VEX records
Browse vendor VEX statements available in this Vulnerability-Lookup instance and pivot to the related vulnerability.
286450 VEX records
API response| Vulnerability | Source | Title | Product status | Imported | Links |
|---|---|---|---|---|---|
| CVE-2025-58058 | suse_vex | SUSE CVE CVE-2025-58058 | known affected: 150 known not affected: 263 recommended: 85 | 2026-07-27T17:10:39+00:00 | Vulnerability · Source |
| CVE-2025-58185 | suse_vex | SUSE CVE CVE-2025-58185 | known affected: 24 known not affected: 67 recommended: 317 | 2026-07-27T17:10:37+00:00 | Vulnerability · Source |
| CVE-2025-58187 | suse_vex | SUSE CVE CVE-2025-58187 | first fixed: 14 known affected: 39 known not affected: 94 recommended: 302 | 2026-07-27T17:10:36+00:00 | Vulnerability · Source |
| CVE-2025-58188 | suse_vex | SUSE CVE CVE-2025-58188 | first fixed: 14 known affected: 24 known not affected: 67 recommended: 302 | 2026-07-27T17:10:35+00:00 | Vulnerability · Source |
| CVE-2025-59353 | suse_vex | SUSE CVE CVE-2025-59353 | recommended: 1 | 2026-07-27T17:10:30+00:00 | Vulnerability · Source |
| CVE-2025-59362 | suse_vex | SUSE CVE CVE-2025-59362 | known affected: 405 recommended: 34 | 2026-07-27T17:10:29+00:00 | Vulnerability · Source |
| CVE-2025-59800 | suse_vex | SUSE CVE CVE-2025-59800 | known affected: 1 known not affected: 123 recommended: 14 | 2026-07-27T17:10:25+00:00 | Vulnerability · Source |
| CVE-2025-61723 | suse_vex | SUSE CVE CVE-2025-61723 | first fixed: 14 known affected: 24 known not affected: 103 recommended: 301 | 2026-07-27T17:10:23+00:00 | Vulnerability · Source |
| CVE-2025-61725 | suse_vex | SUSE CVE CVE-2025-61725 | known affected: 156 known not affected: 67 recommended: 311 | 2026-07-27T17:10:22+00:00 | Vulnerability · Source |
| CVE-2025-61726 | suse_vex | SUSE CVE CVE-2025-61726 | known affected: 24 known not affected: 108 recommended: 384 | 2026-07-27T17:10:21+00:00 | Vulnerability · Source |
| CVE-2025-61727 | suse_vex | SUSE CVE CVE-2025-61727 | known not affected: 294 recommended: 319 | 2026-07-27T17:10:19+00:00 | Vulnerability · Source |
| CVE-2025-61728 | suse_vex | SUSE CVE CVE-2025-61728 | known affected: 24 known not affected: 54 recommended: 356 | 2026-07-27T17:10:18+00:00 | Vulnerability · Source |
| CVE-2025-61730 | suse_vex | SUSE CVE CVE-2025-61730 | known affected: 24 known not affected: 108 recommended: 268 | 2026-07-27T17:10:17+00:00 | Vulnerability · Source |
| CVE-2025-61731 | suse_vex | SUSE CVE CVE-2025-61731 | known affected: 24 known not affected: 108 recommended: 301 | 2026-07-27T17:10:16+00:00 | Vulnerability · Source |
| CVE-2025-61732 | suse_vex | SUSE CVE CVE-2025-61732 | known affected: 18 known not affected: 114 recommended: 293 | 2026-07-27T17:10:14+00:00 | Vulnerability · Source |
| CVE-2025-64433 | suse_vex | SUSE CVE CVE-2025-64433 | first fixed: 1 known not affected: 70 recommended: 71 | 2026-07-27T17:10:10+00:00 | Vulnerability · Source |
| CVE-2025-64435 | suse_vex | SUSE CVE CVE-2025-64435 | first fixed: 1 known not affected: 70 recommended: 27 | 2026-07-27T17:10:09+00:00 | Vulnerability · Source |
| CVE-2025-67030 | suse_vex | SUSE CVE CVE-2025-67030 | known affected: 4 recommended: 93 | 2026-07-27T17:10:03+00:00 | Vulnerability · Source |
| CVE-2025-67746 | suse_vex | SUSE CVE CVE-2025-67746 | known affected: 5 recommended: 19 | 2026-07-27T17:10:01+00:00 | Vulnerability · Source |
| CVE-2025-68119 | suse_vex | SUSE CVE CVE-2025-68119 | known affected: 24 known not affected: 108 recommended: 278 | 2026-07-27T17:09:59+00:00 | Vulnerability · Source |
| CVE-2025-68121 | suse_vex | SUSE CVE CVE-2025-68121 | known affected: 6 known not affected: 54 recommended: 424 | 2026-07-27T17:09:58+00:00 | Vulnerability · Source |
| CVE-2025-68741 | suse_vex | SUSE CVE CVE-2025-68741 | first fixed: 2 known affected: 172 known not affected: 264 recommended: 283 | 2026-07-27T17:09:54+00:00 | Vulnerability · Source |
| CVE-2025-68973 | suse_vex | SUSE CVE CVE-2025-68973 | known affected: 403 recommended: 142 | 2026-07-27T17:09:52+00:00 | Vulnerability · Source |
| CVE-2025-69420 | suse_vex | SUSE CVE CVE-2025-69420 | known affected: 406 known not affected: 143 recommended: 427 | 2026-07-27T17:09:50+00:00 | Vulnerability · Source |
| CVE-2025-71147 | suse_vex | SUSE CVE CVE-2025-71147 | first fixed: 2 known affected: 482 known not affected: 129 recommended: 444 | 2026-07-27T17:09:48+00:00 | Vulnerability · Source |
| CVE-2026-0716 | suse_vex | SUSE CVE CVE-2026-0716 | known affected: 104 recommended: 214 | 2026-07-27T17:09:45+00:00 | Vulnerability · Source |
| CVE-2026-0964 | suse_vex | SUSE CVE CVE-2026-0964 | known affected: 465 recommended: 109 | 2026-07-27T17:09:42+00:00 | Vulnerability · Source |
| CVE-2026-0965 | suse_vex | SUSE CVE CVE-2026-0965 | known affected: 465 recommended: 109 | 2026-07-27T17:09:40+00:00 | Vulnerability · Source |
| CVE-2026-0966 | suse_vex | SUSE CVE CVE-2026-0966 | known affected: 465 recommended: 109 | 2026-07-27T17:09:39+00:00 | Vulnerability · Source |
| CVE-2026-0967 | suse_vex | SUSE CVE CVE-2026-0967 | known affected: 465 recommended: 109 | 2026-07-27T17:09:38+00:00 | Vulnerability · Source |
| CVE-2026-3833 | suse_vex | SUSE CVE CVE-2026-3833 | known affected: 466 recommended: 242 | 2026-07-27T17:09:30+00:00 | Vulnerability · Source |
| CVE-2026-4111 | suse_vex | SUSE CVE CVE-2026-4111 | known affected: 443 known not affected: 29 recommended: 75 | 2026-07-27T17:09:28+00:00 | Vulnerability · Source |
| CVE-2026-4424 | suse_vex | SUSE CVE CVE-2026-4424 | known affected: 463 recommended: 84 | 2026-07-27T17:09:26+00:00 | Vulnerability · Source |
| CVE-2026-4437 | suse_vex | SUSE CVE CVE-2026-4437 | first fixed: 1 known affected: 430 known not affected: 278 recommended: 657 | 2026-07-27T17:09:25+00:00 | Vulnerability · Source |
| CVE-2026-4438 | suse_vex | SUSE CVE CVE-2026-4438 | first fixed: 1 known affected: 432 known not affected: 276 recommended: 657 | 2026-07-27T17:09:23+00:00 | Vulnerability · Source |
| CVE-2026-5201 | suse_vex | SUSE CVE CVE-2026-5201 | known affected: 501 known not affected: 281 recommended: 260 | 2026-07-27T17:09:20+00:00 | Vulnerability · Source |
| CVE-2026-5260 | suse_vex | SUSE CVE CVE-2026-5260 | known affected: 466 recommended: 242 | 2026-07-27T17:09:19+00:00 | Vulnerability · Source |
| CVE-2026-5419 | suse_vex | SUSE CVE CVE-2026-5419 | known affected: 567 recommended: 91 | 2026-07-27T17:09:17+00:00 | Vulnerability · Source |
| CVE-2026-5435 | suse_vex | SUSE CVE CVE-2026-5435 | first fixed: 1 known affected: 570 known not affected: 61 recommended: 912 | 2026-07-27T17:09:15+00:00 | Vulnerability · Source |
| CVE-2026-5450 | suse_vex | SUSE CVE CVE-2026-5450 | first fixed: 1 known affected: 532 recommended: 1100 | 2026-07-27T17:09:14+00:00 | Vulnerability · Source |
| CVE-2026-5928 | suse_vex | SUSE CVE CVE-2026-5928 | first fixed: 1 known affected: 532 recommended: 948 | 2026-07-27T17:09:12+00:00 | Vulnerability · Source |
| CVE-2026-6238 | suse_vex | SUSE CVE CVE-2026-6238 | first fixed: 1 known affected: 570 known not affected: 61 recommended: 912 | 2026-07-27T17:09:10+00:00 | Vulnerability · Source |
| CVE-2026-7383 | suse_vex | SUSE CVE CVE-2026-7383 | known affected: 503 known not affected: 84 recommended: 362 | 2026-07-27T17:09:07+00:00 | Vulnerability · Source |
| CVE-2026-8643 | suse_vex | SUSE CVE CVE-2026-8643 | known affected: 796 recommended: 43 | 2026-07-27T17:09:02+00:00 | Vulnerability · Source |
| CVE-2026-9076 | suse_vex | SUSE CVE CVE-2026-9076 | known affected: 503 known not affected: 84 recommended: 362 | 2026-07-27T17:08:58+00:00 | Vulnerability · Source |
| CVE-2026-10517 | suse_vex | SUSE CVE CVE-2026-10517 | No product status | 2026-07-27T17:08:53+00:00 | Vulnerability · Source |
| CVE-2026-11979 | suse_vex | SUSE CVE CVE-2026-11979 | known affected: 450 recommended: 168 | 2026-07-27T17:08:49+00:00 | Vulnerability · Source |
| CVE-2026-14241 | suse_vex | SUSE CVE CVE-2026-14241 | known not affected: 106 | 2026-07-27T17:08:40+00:00 | Vulnerability · Source |
| CVE-2026-14380 | suse_vex | SUSE CVE CVE-2026-14380 | first fixed: 7 known affected: 31 recommended: 5 | 2026-07-27T17:08:39+00:00 | Vulnerability · Source |
| CVE-2026-14740 | suse_vex | SUSE CVE CVE-2026-14740 | first fixed: 7 known affected: 31 recommended: 5 | 2026-07-27T17:08:35+00:00 | Vulnerability · Source |