VEX records
Browse vendor VEX statements available in this Vulnerability-Lookup instance and pivot to the related vulnerability.
291949 VEX records
API response| Vulnerability | Source | Title | Product status | Imported | Links |
|---|---|---|---|---|---|
| CVE-2024-56697 | suse_vex | SUSE CVE CVE-2024-56697 | known not affected: 423 recommended: 112 | 2026-07-27T17:12:44+00:00 | Vulnerability · Source |
| CVE-2025-0244 | suse_vex | SUSE CVE CVE-2025-0244 | known affected: 57 recommended: 5 | 2026-07-27T17:12:33+00:00 | Vulnerability · Source |
| CVE-2025-0247 | suse_vex | SUSE CVE CVE-2025-0247 | known affected: 57 recommended: 5 | 2026-07-27T17:12:32+00:00 | Vulnerability · Source |
| CVE-2025-1019 | suse_vex | SUSE CVE CVE-2025-1019 | known affected: 110 recommended: 5 | 2026-07-27T17:12:30+00:00 | Vulnerability · Source |
| CVE-2025-1020 | suse_vex | SUSE CVE CVE-2025-1020 | known not affected: 179 recommended: 5 | 2026-07-27T17:12:29+00:00 | Vulnerability · Source |
| CVE-2025-3034 | suse_vex | SUSE CVE CVE-2025-3034 | known affected: 37 recommended: 5 | 2026-07-27T17:12:27+00:00 | Vulnerability · Source |
| CVE-2025-4083 | suse_vex | SUSE CVE CVE-2025-4083 | known affected: 69 recommended: 113 | 2026-07-27T17:12:23+00:00 | Vulnerability · Source |
| CVE-2025-4090 | suse_vex | SUSE CVE CVE-2025-4090 | known affected: 69 recommended: 5 | 2026-07-27T17:12:22+00:00 | Vulnerability · Source |
| CVE-2025-5272 | suse_vex | SUSE CVE CVE-2025-5272 | known affected: 37 recommended: 5 | 2026-07-27T17:12:20+00:00 | Vulnerability · Source |
| CVE-2025-8177 | suse_vex | SUSE CVE CVE-2025-8177 | known affected: 443 known not affected: 7 recommended: 142 | 2026-07-27T17:12:14+00:00 | Vulnerability · Source |
| CVE-2025-9566 | suse_vex | SUSE CVE CVE-2025-9566 | known affected: 394 recommended: 162 | 2026-07-27T17:12:11+00:00 | Vulnerability · Source |
| CVE-2025-9615 | suse_vex | SUSE CVE CVE-2025-9615 | known affected: 547 recommended: 216 | 2026-07-27T17:12:09+00:00 | Vulnerability · Source |
| CVE-2025-11152 | suse_vex | SUSE CVE CVE-2025-11152 | known not affected: 151 recommended: 5 | 2026-07-27T17:12:05+00:00 | Vulnerability · Source |
| CVE-2025-11621 | suse_vex | SUSE CVE CVE-2025-11621 | recommended: 1 | 2026-07-27T17:12:01+00:00 | Vulnerability · Source |
| CVE-2025-11712 | suse_vex | SUSE CVE CVE-2025-11712 | known affected: 70 recommended: 182 | 2026-07-27T17:12:00+00:00 | Vulnerability · Source |
| CVE-2025-11716 | suse_vex | SUSE CVE CVE-2025-11716 | known affected: 70 recommended: 5 | 2026-07-27T17:11:59+00:00 | Vulnerability · Source |
| CVE-2025-11719 | suse_vex | SUSE CVE CVE-2025-11719 | known affected: 70 recommended: 5 | 2026-07-27T17:11:58+00:00 | Vulnerability · Source |
| CVE-2025-12044 | suse_vex | SUSE CVE CVE-2025-12044 | recommended: 1 | 2026-07-27T17:11:56+00:00 | Vulnerability · Source |
| CVE-2025-13014 | suse_vex | SUSE CVE CVE-2025-13014 | known affected: 14 recommended: 176 | 2026-07-27T17:11:55+00:00 | Vulnerability · Source |
| CVE-2025-13015 | suse_vex | SUSE CVE CVE-2025-13015 | known affected: 14 recommended: 176 | 2026-07-27T17:11:54+00:00 | Vulnerability · Source |
| CVE-2025-13019 | suse_vex | SUSE CVE CVE-2025-13019 | known affected: 14 recommended: 183 | 2026-07-27T17:11:52+00:00 | Vulnerability · Source |
| CVE-2025-13023 | suse_vex | SUSE CVE CVE-2025-13023 | known affected: 14 recommended: 5 | 2026-07-27T17:11:51+00:00 | Vulnerability · Source |
| CVE-2025-14831 | suse_vex | SUSE CVE CVE-2025-14831 | known affected: 537 recommended: 148 | 2026-07-27T17:11:44+00:00 | Vulnerability · Source |
| CVE-2025-21921 | suse_vex | SUSE CVE CVE-2025-21921 | known not affected: 346 recommended: 26 | 2026-07-27T17:11:33+00:00 | Vulnerability · Source |
| CVE-2025-37828 | suse_vex | SUSE CVE CVE-2025-37828 | known affected: 57 known not affected: 338 recommended: 26 | 2026-07-27T17:11:16+00:00 | Vulnerability · Source |
| CVE-2025-38096 | suse_vex | SUSE CVE CVE-2025-38096 | first fixed: 2 known affected: 239 known not affected: 63 recommended: 127 | 2026-07-27T17:11:12+00:00 | Vulnerability · Source |
| CVE-2025-38330 | suse_vex | SUSE CVE CVE-2025-38330 | known not affected: 416 recommended: 69 | 2026-07-27T17:11:09+00:00 | Vulnerability · Source |
| CVE-2025-38658 | suse_vex | SUSE CVE CVE-2025-38658 | first fixed: 2 known not affected: 414 recommended: 154 | 2026-07-27T17:11:04+00:00 | Vulnerability · Source |
| CVE-2025-39723 | suse_vex | SUSE CVE CVE-2025-39723 | first fixed: 2 known affected: 62 known not affected: 376 recommended: 127 | 2026-07-27T17:11:02+00:00 | Vulnerability · Source |
| CVE-2025-49709 | suse_vex | SUSE CVE CVE-2025-49709 | known affected: 15 known not affected: 97 recommended: 5 | 2026-07-27T17:10:48+00:00 | Vulnerability · Source |
| CVE-2025-53905 | suse_vex | SUSE CVE CVE-2025-53905 | known affected: 515 recommended: 153 | 2026-07-27T17:10:46+00:00 | Vulnerability · Source |
| CVE-2025-53906 | suse_vex | SUSE CVE CVE-2025-53906 | first fixed: 2 known affected: 427 recommended: 245 | 2026-07-27T17:10:45+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-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-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-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 |