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-2024-56624 | suse_vex | SUSE CVE CVE-2024-56624 | known not affected: 425 recommended: 112 | 2026-07-26T23:34:35+00:00 | Vulnerability · Source |
| CVE-2024-56662 | suse_vex | SUSE CVE CVE-2024-56662 | known affected: 693 known not affected: 40 recommended: 472 | 2026-07-26T23:34:30+00:00 | Vulnerability · Source |
| CVE-2025-1939 | suse_vex | SUSE CVE CVE-2025-1939 | recommended: 9 | 2026-07-26T23:34:18+00:00 | Vulnerability · Source |
| CVE-2025-1942 | suse_vex | SUSE CVE CVE-2025-1942 | recommended: 9 | 2026-07-26T23:34:16+00:00 | Vulnerability · Source |
| CVE-2025-3031 | suse_vex | SUSE CVE CVE-2025-3031 | known affected: 37 recommended: 9 | 2026-07-26T23:34:15+00:00 | Vulnerability · Source |
| CVE-2025-3035 | suse_vex | SUSE CVE CVE-2025-3035 | known affected: 37 recommended: 9 | 2026-07-26T23:34:13+00:00 | Vulnerability · Source |
| CVE-2025-4085 | suse_vex | SUSE CVE CVE-2025-4085 | known affected: 69 recommended: 9 | 2026-07-26T23:34:12+00:00 | Vulnerability · Source |
| CVE-2025-5245 | suse_vex | SUSE CVE CVE-2025-5245 | known affected: 480 recommended: 521 | 2026-07-26T23:34:10+00:00 | Vulnerability · Source |
| CVE-2025-5270 | suse_vex | SUSE CVE CVE-2025-5270 | known affected: 37 recommended: 9 | 2026-07-26T23:34:09+00:00 | Vulnerability · Source |
| CVE-2025-9230 | suse_vex | SUSE CVE CVE-2025-9230 | known affected: 455 known not affected: 106 recommended: 582 | 2026-07-26T23:34:02+00:00 | Vulnerability · Source |
| CVE-2025-10531 | suse_vex | SUSE CVE CVE-2025-10531 | known affected: 37 recommended: 9 | 2026-07-26T23:34:00+00:00 | Vulnerability · Source |
| CVE-2025-11153 | suse_vex | SUSE CVE CVE-2025-11153 | known not affected: 151 recommended: 9 | 2026-07-26T23:33:58+00:00 | Vulnerability · Source |
| CVE-2025-13021 | suse_vex | SUSE CVE CVE-2025-13021 | known affected: 14 recommended: 9 | 2026-07-26T23:33:54+00:00 | Vulnerability · Source |
| CVE-2025-14087 | suse_vex | SUSE CVE CVE-2025-14087 | known affected: 549 known not affected: 1 recommended: 534 | 2026-07-26T23:33:50+00:00 | Vulnerability · Source |
| CVE-2025-15467 | suse_vex | SUSE CVE CVE-2025-15467 | known affected: 396 known not affected: 427 recommended: 156 | 2026-07-26T23:33:49+00:00 | Vulnerability · Source |
| CVE-2025-21900 | suse_vex | SUSE CVE CVE-2025-21900 | known not affected: 344 recommended: 53 | 2026-07-26T23:33:44+00:00 | Vulnerability · Source |
| CVE-2025-32053 | suse_vex | SUSE CVE CVE-2025-32053 | known affected: 55 recommended: 244 | 2026-07-26T23:33:37+00:00 | Vulnerability · Source |
| CVE-2025-32909 | suse_vex | SUSE CVE CVE-2025-32909 | known affected: 54 known not affected: 7 recommended: 240 | 2026-07-26T23:33:36+00:00 | Vulnerability · Source |
| CVE-2025-38070 | suse_vex | SUSE CVE CVE-2025-38070 | known not affected: 401 recommended: 27 | 2026-07-26T23:33:32+00:00 | Vulnerability · Source |
| CVE-2025-39720 | suse_vex | SUSE CVE CVE-2025-39720 | known not affected: 416 | 2026-07-26T23:33:25+00:00 | Vulnerability · Source |
| CVE-2025-47153 | suse_vex | SUSE CVE CVE-2025-47153 | known not affected: 373 | 2026-07-26T23:33:17+00:00 | Vulnerability · Source |
| CVE-2025-61594 | suse_vex | SUSE CVE CVE-2025-61594 | known affected: 179 recommended: 119 | 2026-07-26T23:33:13+00:00 | Vulnerability · Source |
| CVE-2025-62813 | suse_vex | SUSE CVE CVE-2025-62813 | recommended: 14 | 2026-07-26T23:33:07+00:00 | Vulnerability · Source |
| CVE-2025-68821 | suse_vex | SUSE CVE CVE-2025-68821 | first fixed: 2 known affected: 5 known not affected: 331 recommended: 172 | 2026-07-26T23:33:01+00:00 | Vulnerability · Source |
| CVE-2025-69421 | suse_vex | SUSE CVE CVE-2025-69421 | known affected: 454 known not affected: 96 recommended: 441 | 2026-07-26T23:33:00+00:00 | Vulnerability · Source |
| CVE-2026-47300 | suse_vex | SUSE CVE CVE-2026-47300 | recommended: 121 | 2026-07-26T23:32:04+00:00 | Vulnerability · Source |
| CVE-2026-47302 | suse_vex | SUSE CVE CVE-2026-47302 | recommended: 121 | 2026-07-26T23:32:03+00:00 | Vulnerability · Source |
| CVE-2026-47303 | suse_vex | SUSE CVE CVE-2026-47303 | recommended: 121 | 2026-07-26T23:32:01+00:00 | Vulnerability · Source |
| CVE-2026-47304 | suse_vex | SUSE CVE CVE-2026-47304 | recommended: 121 | 2026-07-26T23:31:59+00:00 | Vulnerability · Source |
| CVE-2026-50524 | suse_vex | SUSE CVE CVE-2026-50524 | recommended: 121 | 2026-07-26T23:31:49+00:00 | Vulnerability · Source |
| CVE-2026-50525 | suse_vex | SUSE CVE CVE-2026-50525 | recommended: 93 | 2026-07-26T23:31:48+00:00 | Vulnerability · Source |
| CVE-2026-50527 | suse_vex | SUSE CVE CVE-2026-50527 | recommended: 121 | 2026-07-26T23:31:45+00:00 | Vulnerability · Source |
| CVE-2026-50528 | suse_vex | SUSE CVE CVE-2026-50528 | recommended: 121 | 2026-07-26T23:31:44+00:00 | Vulnerability · Source |
| CVE-2026-50646 | suse_vex | SUSE CVE CVE-2026-50646 | recommended: 121 | 2026-07-26T23:31:43+00:00 | Vulnerability · Source |
| CVE-2026-50648 | suse_vex | SUSE CVE CVE-2026-50648 | recommended: 121 | 2026-07-26T23:31:41+00:00 | Vulnerability · Source |
| CVE-2026-50649 | suse_vex | SUSE CVE CVE-2026-50649 | recommended: 121 | 2026-07-26T23:31:40+00:00 | Vulnerability · Source |
| CVE-2026-50650 | suse_vex | SUSE CVE CVE-2026-50650 | recommended: 121 | 2026-07-26T23:31:39+00:00 | Vulnerability · Source |
| CVE-2026-50651 | suse_vex | SUSE CVE CVE-2026-50651 | recommended: 121 | 2026-07-26T23:31:37+00:00 | Vulnerability · Source |
| CVE-2026-50659 | suse_vex | SUSE CVE CVE-2026-50659 | recommended: 121 | 2026-07-26T23:31:36+00:00 | Vulnerability · Source |
| CVE-2026-56170 | suse_vex | SUSE CVE CVE-2026-56170 | recommended: 121 | 2026-07-26T23:31:19+00:00 | Vulnerability · Source |
| CVE-2026-57108 | suse_vex | SUSE CVE CVE-2026-57108 | recommended: 121 | 2026-07-26T23:31:15+00:00 | Vulnerability · Source |
| CVE-2026-60311 | redhat_vex | mysql: Optimizer unspecified vulnerability (CPU Jul 2026) | known not affected: 41 | 2026-07-26T18:29:48+00:00 | Vulnerability · Source |
| CVE-2026-60194 | redhat_vex | mysql: JSON Duality unspecified vulnerability (CPU Jul 2026) | known not affected: 41 | 2026-07-26T18:29:46+00:00 | Vulnerability · Source |
| CVE-2026-61128 | redhat_vex | mysql: Optimizer unspecified vulnerability (CPU Jul 2026) | known not affected: 41 | 2026-07-26T18:29:37+00:00 | Vulnerability · Source |
| CVE-2026-60324 | redhat_vex | mysql: Optimizer unspecified vulnerability (CPU Jul 2026) | known not affected: 41 | 2026-07-26T18:29:20+00:00 | Vulnerability · Source |
| CVE-2026-61144 | redhat_vex | mysql: Optimizer unspecified vulnerability (CPU Jul 2026) | known not affected: 41 | 2026-07-26T18:28:34+00:00 | Vulnerability · Source |
| CVE-2026-61108 | redhat_vex | mysql: GIS unspecified vulnerability (CPU Jul 2026) | known not affected: 41 | 2026-07-26T18:28:15+00:00 | Vulnerability · Source |
| CVE-2026-61093 | redhat_vex | mysql: Optimizer unspecified vulnerability (CPU Jul 2026) | known not affected: 41 | 2026-07-26T18:28:12+00:00 | Vulnerability · Source |
| CVE-2026-47008 | redhat_vex | mysql: InnoDB unspecified vulnerability (CPU Jul 2026) | known not affected: 41 | 2026-07-26T18:23:00+00:00 | Vulnerability · Source |
| CVE-2026-60174 | redhat_vex | mysql: Optimizer unspecified vulnerability (CPU Jul 2026) | known not affected: 41 | 2026-07-26T18:22:43+00:00 | Vulnerability · Source |