VEX records
Browse vendor VEX statements available in this Vulnerability-Lookup instance and pivot to the related vulnerability.
286510 VEX records
API response| Vulnerability | Source | Title | Product status | Imported | Links |
|---|---|---|---|---|---|
| CVE-2023-53671 | suse_vex | SUSE CVE CVE-2023-53671 | known not affected: 345 recommended: 29 | 2026-07-27T23:46:52+00:00 | Vulnerability · Source |
| CVE-2023-53678 | suse_vex | SUSE CVE CVE-2023-53678 | known not affected: 345 recommended: 49 | 2026-07-27T23:46:51+00:00 | Vulnerability · Source |
| CVE-2023-53712 | suse_vex | SUSE CVE CVE-2023-53712 | known affected: 60 known not affected: 263 | 2026-07-27T23:46:50+00:00 | Vulnerability · Source |
| CVE-2023-53756 | suse_vex | SUSE CVE CVE-2023-53756 | known affected: 165 known not affected: 210 recommended: 29 | 2026-07-27T23:46:48+00:00 | Vulnerability · Source |
| CVE-2023-53758 | suse_vex | SUSE CVE CVE-2023-53758 | known not affected: 337 | 2026-07-27T23:46:46+00:00 | Vulnerability · Source |
| CVE-2023-53993 | suse_vex | SUSE CVE CVE-2023-53993 | known not affected: 378 recommended: 29 | 2026-07-27T23:46:44+00:00 | Vulnerability · Source |
| CVE-2023-54062 | suse_vex | SUSE CVE CVE-2023-54062 | known not affected: 354 recommended: 29 | 2026-07-27T23:46:42+00:00 | Vulnerability · Source |
| CVE-2023-54068 | suse_vex | SUSE CVE CVE-2023-54068 | known affected: 96 known not affected: 258 | 2026-07-27T23:46:40+00:00 | Vulnerability · Source |
| CVE-2023-54119 | suse_vex | SUSE CVE CVE-2023-54119 | known affected: 354 known not affected: 309 recommended: 262 | 2026-07-27T23:46:38+00:00 | Vulnerability · Source |
| CVE-2023-54124 | suse_vex | SUSE CVE CVE-2023-54124 | known affected: 139 known not affected: 239 | 2026-07-27T23:46:37+00:00 | Vulnerability · Source |
| CVE-2024-1048 | suse_vex | SUSE CVE CVE-2024-1048 | known not affected: 378 recommended: 23 | 2026-07-27T23:46:34+00:00 | Vulnerability · Source |
| CVE-2024-1682 | suse_vex | SUSE CVE CVE-2024-1682 | known not affected: 108 | 2026-07-27T23:46:32+00:00 | Vulnerability · Source |
| CVE-2024-3596 | suse_vex | SUSE CVE CVE-2024-3596 | known affected: 68 recommended: 436 | 2026-07-27T23:46:30+00:00 | Vulnerability · Source |
| CVE-2024-6197 | suse_vex | SUSE CVE CVE-2024-6197 | known affected: 394 known not affected: 142 recommended: 71 | 2026-07-27T23:46:27+00:00 | Vulnerability · Source |
| CVE-2024-6608 | suse_vex | SUSE CVE CVE-2024-6608 | known affected: 33 recommended: 226 | 2026-07-27T23:46:25+00:00 | Vulnerability · Source |
| CVE-2024-8389 | suse_vex | SUSE CVE CVE-2024-8389 | known affected: 30 recommended: 5 | 2026-07-27T23:46:23+00:00 | Vulnerability · Source |
| CVE-2024-9399 | suse_vex | SUSE CVE CVE-2024-9399 | known affected: 29 recommended: 212 | 2026-07-27T23:46:19+00:00 | Vulnerability · Source |
| CVE-2024-9780 | suse_vex | SUSE CVE CVE-2024-9780 | known not affected: 272 recommended: 183 | 2026-07-27T23:46:18+00:00 | Vulnerability · Source |
| CVE-2024-10458 | suse_vex | SUSE CVE CVE-2024-10458 | known affected: 37 recommended: 207 | 2026-07-27T23:46:16+00:00 | Vulnerability · Source |
| CVE-2024-11700 | suse_vex | SUSE CVE CVE-2024-11700 | known affected: 29 recommended: 5 | 2026-07-27T23:46:14+00:00 | Vulnerability · Source |
| CVE-2024-11703 | suse_vex | SUSE CVE CVE-2024-11703 | known affected: 29 recommended: 5 | 2026-07-27T23:46:12+00:00 | Vulnerability · Source |
| CVE-2024-11708 | suse_vex | SUSE CVE CVE-2024-11708 | known affected: 29 recommended: 5 | 2026-07-27T23:46:11+00:00 | Vulnerability · Source |
| CVE-2024-12224 | suse_vex | SUSE CVE CVE-2024-12224 | known affected: 656 known not affected: 1106 recommended: 236 | 2026-07-27T23:46:08+00:00 | Vulnerability · Source |
| CVE-2024-12705 | suse_vex | SUSE CVE CVE-2024-12705 | known affected: 394 known not affected: 281 recommended: 46 | 2026-07-27T23:46:07+00:00 | Vulnerability · Source |
| CVE-2024-12886 | suse_vex | SUSE CVE CVE-2024-12886 | recommended: 2 | 2026-07-27T23:46:04+00:00 | Vulnerability · Source |
| CVE-2024-21208 | suse_vex | SUSE CVE CVE-2024-21208 | known affected: 508 known not affected: 91 recommended: 876 | 2026-07-27T23:46:01+00:00 | Vulnerability · Source |
| CVE-2024-23206 | suse_vex | SUSE CVE CVE-2024-23206 | known affected: 69 known not affected: 53 recommended: 675 | 2026-07-27T23:45:59+00:00 | Vulnerability · Source |
| CVE-2024-26976 | suse_vex | SUSE CVE CVE-2024-26976 | known affected: 476 recommended: 839 | 2026-07-27T23:45:53+00:00 | Vulnerability · Source |
| CVE-2024-36972 | suse_vex | SUSE CVE CVE-2024-36972 | known not affected: 291 recommended: 332 | 2026-07-27T23:45:45+00:00 | Vulnerability · Source |
| CVE-2024-40900 | suse_vex | SUSE CVE CVE-2024-40900 | known affected: 330 known not affected: 190 recommended: 658 | 2026-07-27T23:45:41+00:00 | Vulnerability · Source |
| CVE-2024-40918 | suse_vex | SUSE CVE CVE-2024-40918 | known not affected: 271 | 2026-07-27T23:45:40+00:00 | Vulnerability · Source |
| CVE-2024-41069 | suse_vex | SUSE CVE CVE-2024-41069 | known affected: 325 known not affected: 60 recommended: 922 | 2026-07-27T23:45:37+00:00 | Vulnerability · Source |
| CVE-2024-53186 | suse_vex | SUSE CVE CVE-2024-53186 | known not affected: 358 | 2026-07-27T23:45:20+00:00 | Vulnerability · Source |
| CVE-2024-54031 | suse_vex | SUSE CVE CVE-2024-54031 | first fixed: 2 known not affected: 241 recommended: 332 | 2026-07-27T23:45:14+00:00 | Vulnerability · Source |
| CVE-2024-56689 | suse_vex | SUSE CVE CVE-2024-56689 | known not affected: 423 recommended: 26 | 2026-07-27T23:45:10+00:00 | Vulnerability · Source |
| CVE-2025-3416 | suse_vex | SUSE CVE CVE-2025-3416 | known affected: 718 known not affected: 1181 recommended: 371 | 2026-07-27T23:44:59+00:00 | Vulnerability · Source |
| CVE-2025-4575 | suse_vex | SUSE CVE CVE-2025-4575 | first fixed: 45 known not affected: 691 recommended: 24 | 2026-07-27T23:44:57+00:00 | Vulnerability · Source |
| CVE-2025-5791 | suse_vex | SUSE CVE CVE-2025-5791 | known affected: 394 known not affected: 4 recommended: 63 | 2026-07-27T23:44:56+00:00 | Vulnerability · Source |
| CVE-2025-6170 | suse_vex | SUSE CVE CVE-2025-6170 | known affected: 423 known not affected: 63 recommended: 285 | 2026-07-27T23:44:54+00:00 | Vulnerability · Source |
| CVE-2025-8835 | suse_vex | SUSE CVE CVE-2025-8835 | known affected: 485 recommended: 54 | 2026-07-27T23:44:50+00:00 | Vulnerability · Source |
| CVE-2025-10535 | suse_vex | SUSE CVE CVE-2025-10535 | known affected: 37 recommended: 5 | 2026-07-27T23:44:48+00:00 | Vulnerability · Source |
| CVE-2025-11717 | suse_vex | SUSE CVE CVE-2025-11717 | known affected: 70 recommended: 5 | 2026-07-27T23:44:44+00:00 | Vulnerability · Source |
| CVE-2025-11721 | suse_vex | SUSE CVE CVE-2025-11721 | known affected: 70 recommended: 5 | 2026-07-27T23:44:43+00:00 | Vulnerability · Source |
| CVE-2025-13017 | suse_vex | SUSE CVE CVE-2025-13017 | known affected: 14 recommended: 183 | 2026-07-27T23:44:40+00:00 | Vulnerability · Source |
| CVE-2025-13026 | suse_vex | SUSE CVE CVE-2025-13026 | known affected: 14 recommended: 5 | 2026-07-27T23:44:38+00:00 | Vulnerability · Source |
| CVE-2025-13465 | suse_vex | SUSE CVE CVE-2025-13465 | first fixed: 36 known affected: 512 known not affected: 248 recommended: 228 | 2026-07-27T23:44:36+00:00 | Vulnerability · Source |
| CVE-2025-21797 | suse_vex | SUSE CVE CVE-2025-21797 | known affected: 47 known not affected: 232 | 2026-07-27T23:44:31+00:00 | Vulnerability · Source |
| CVE-2025-32914 | suse_vex | SUSE CVE CVE-2025-32914 | known affected: 55 recommended: 259 | 2026-07-27T23:44:17+00:00 | Vulnerability · Source |
| CVE-2025-38349 | suse_vex | SUSE CVE CVE-2025-38349 | first fixed: 2 known affected: 445 known not affected: 283 recommended: 591 | 2026-07-27T23:44:04+00:00 | Vulnerability · Source |
| CVE-2025-38653 | suse_vex | SUSE CVE CVE-2025-38653 | first fixed: 2 known affected: 399 known not affected: 283 recommended: 583 | 2026-07-27T23:43:47+00:00 | Vulnerability · Source |