VEX records
Browse vendor VEX statements available in this Vulnerability-Lookup instance and pivot to the related vulnerability.
104719 VEX records
API response| Vulnerability | Source | Title | Product status | Imported | Links |
|---|---|---|---|---|---|
| CVE-2024-7558 | suse_vex | SUSE CVE CVE-2024-7558 | recommended: 4 | 2026-10-16T02:25:01+00:00 | Vulnerability · Source |
| CVE-2024-7594 | suse_vex | SUSE CVE CVE-2024-7594 | recommended: 4 | 2026-10-16T02:24:57+00:00 | Vulnerability · Source |
| CVE-2024-7595 | suse_vex | SUSE CVE CVE-2024-7595 | No product status | 2026-10-16T02:24:56+00:00 | Vulnerability · Source |
| CVE-2024-7596 | suse_vex | SUSE CVE CVE-2024-7596 | known affected: 0 known not affected: 456 | 2026-10-16T02:24:54+00:00 | Vulnerability · Source |
| CVE-2024-7966 | suse_vex | SUSE CVE CVE-2024-7966 | known affected: 179 recommended: 14 | 2026-10-16T02:24:51+00:00 | Vulnerability · Source |
| CVE-2024-8006 | suse_vex | SUSE CVE CVE-2024-8006 | known affected: 387 known not affected: 1 recommended: 164 | 2026-10-16T02:24:48+00:00 | Vulnerability · Source |
| CVE-2024-8096 | suse_vex | SUSE CVE CVE-2024-8096 | first fixed: 5 known affected: 424 known not affected: 17 recommended: 221 | 2026-10-16T02:24:44+00:00 | Vulnerability · Source |
| CVE-2024-8235 | suse_vex | SUSE CVE CVE-2024-8235 | known not affected: 1453 recommended: 300 | 2026-10-16T02:24:38+00:00 | Vulnerability · Source |
| CVE-2024-8244 | suse_vex | SUSE CVE CVE-2024-8244 | known affected: 297 known not affected: 65 | 2026-10-16T02:24:36+00:00 | Vulnerability · Source |
| CVE-2024-8381 | suse_vex | SUSE CVE CVE-2024-8381 | known affected: 58 recommended: 220 | 2026-10-16T02:24:34+00:00 | Vulnerability · Source |
| CVE-2024-8382 | suse_vex | SUSE CVE CVE-2024-8382 | known affected: 58 recommended: 223 | 2026-10-16T02:24:32+00:00 | Vulnerability · Source |
| CVE-2024-8383 | suse_vex | SUSE CVE CVE-2024-8383 | known affected: 58 recommended: 163 | 2026-10-16T02:24:30+00:00 | Vulnerability · Source |
| CVE-2024-8384 | suse_vex | SUSE CVE CVE-2024-8384 | known affected: 58 recommended: 223 | 2026-10-16T02:24:28+00:00 | Vulnerability · Source |
| CVE-2024-8385 | suse_vex | SUSE CVE CVE-2024-8385 | known affected: 58 recommended: 219 | 2026-10-16T02:24:26+00:00 | Vulnerability · Source |
| CVE-2024-8418 | suse_vex | SUSE CVE CVE-2024-8418 | known not affected: 27 recommended: 6 | 2026-10-16T02:24:24+00:00 | Vulnerability · Source |
| CVE-2024-8612 | suse_vex | SUSE CVE CVE-2024-8612 | known affected: 844 recommended: 1402 | 2026-10-16T02:24:21+00:00 | Vulnerability · Source |
| CVE-2024-8676 | suse_vex | SUSE CVE CVE-2024-8676 | recommended: 4 | 2026-10-16T02:24:19+00:00 | Vulnerability · Source |
| CVE-2024-8900 | suse_vex | SUSE CVE CVE-2024-8900 | known affected: 46 recommended: 211 | 2026-10-16T02:24:18+00:00 | Vulnerability · Source |
| CVE-2024-8925 | suse_vex | SUSE CVE CVE-2024-8925 | known affected: 1562 recommended: 2069 | 2026-10-16T02:24:15+00:00 | Vulnerability · Source |
| CVE-2024-8927 | suse_vex | SUSE CVE CVE-2024-8927 | known affected: 1562 recommended: 2069 | 2026-10-16T02:24:13+00:00 | Vulnerability · Source |
| CVE-2024-8996 | suse_vex | SUSE CVE CVE-2024-8996 | recommended: 4 | 2026-10-16T02:24:11+00:00 | Vulnerability · Source |
| CVE-2024-9026 | suse_vex | SUSE CVE CVE-2024-9026 | known affected: 1133 known not affected: 2369 recommended: 2069 | 2026-10-16T02:24:09+00:00 | Vulnerability · Source |
| CVE-2024-9143 | suse_vex | SUSE CVE CVE-2024-9143 | known not affected: 831 recommended: 55 | 2026-10-16T02:24:05+00:00 | Vulnerability · Source |
| CVE-2024-9312 | suse_vex | SUSE CVE CVE-2024-9312 | recommended: 4 | 2026-10-16T02:24:01+00:00 | Vulnerability · Source |
| CVE-2024-9313 | suse_vex | SUSE CVE CVE-2024-9313 | recommended: 4 | 2026-10-16T02:23:59+00:00 | Vulnerability · Source |
| CVE-2024-9341 | suse_vex | SUSE CVE CVE-2024-9341 | known affected: 403 known not affected: 70 recommended: 187 | 2026-10-16T02:23:57+00:00 | Vulnerability · Source |
| CVE-2024-9355 | suse_vex | SUSE CVE CVE-2024-9355 | recommended: 37 | 2026-10-16T02:23:55+00:00 | Vulnerability · Source |
| CVE-2024-9392 | suse_vex | SUSE CVE CVE-2024-9392 | known affected: 57 recommended: 223 | 2026-10-16T02:23:53+00:00 | Vulnerability · Source |
| CVE-2024-9394 | suse_vex | SUSE CVE CVE-2024-9394 | known affected: 57 recommended: 223 | 2026-10-16T02:23:51+00:00 | Vulnerability · Source |
| CVE-2024-9398 | suse_vex | SUSE CVE CVE-2024-9398 | known affected: 57 recommended: 219 | 2026-10-16T02:23:49+00:00 | Vulnerability · Source |
| CVE-2024-9399 | suse_vex | SUSE CVE CVE-2024-9399 | known affected: 29 recommended: 225 | 2026-10-16T02:23:47+00:00 | Vulnerability · Source |
| CVE-2024-9402 | suse_vex | SUSE CVE CVE-2024-9402 | known affected: 57 recommended: 223 | 2026-10-16T02:23:45+00:00 | Vulnerability · Source |
| CVE-2024-9403 | suse_vex | SUSE CVE CVE-2024-9403 | known affected: 57 recommended: 12 | 2026-10-16T02:23:43+00:00 | Vulnerability · Source |
| CVE-2024-9407 | suse_vex | SUSE CVE CVE-2024-9407 | known affected: 394 known not affected: 9 recommended: 188 | 2026-10-16T02:23:41+00:00 | Vulnerability · Source |
| CVE-2024-9676 | suse_vex | SUSE CVE CVE-2024-9676 | known affected: 421 known not affected: 58 recommended: 200 | 2026-10-16T02:23:38+00:00 | Vulnerability · Source |
| CVE-2024-9779 | suse_vex | SUSE CVE CVE-2024-9779 | recommended: 4 | 2026-10-16T02:23:36+00:00 | Vulnerability · Source |
| CVE-2024-9781 | suse_vex | SUSE CVE CVE-2024-9781 | known not affected: 347 recommended: 196 | 2026-10-16T02:23:33+00:00 | Vulnerability · Source |
| CVE-2024-9900 | suse_vex | SUSE CVE CVE-2024-9900 | recommended: 5 | 2026-10-16T02:23:31+00:00 | Vulnerability · Source |
| CVE-2024-10005 | suse_vex | SUSE CVE CVE-2024-10005 | recommended: 5 | 2026-10-16T02:23:29+00:00 | Vulnerability · Source |
| CVE-2024-10006 | suse_vex | SUSE CVE CVE-2024-10006 | recommended: 5 | 2026-10-16T02:23:27+00:00 | Vulnerability · Source |
| CVE-2024-10086 | suse_vex | SUSE CVE CVE-2024-10086 | recommended: 4 | 2026-10-16T02:23:25+00:00 | Vulnerability · Source |
| CVE-2024-10214 | suse_vex | SUSE CVE CVE-2024-10214 | recommended: 4 | 2026-10-16T02:23:23+00:00 | Vulnerability · Source |
| CVE-2024-10220 | suse_vex | SUSE CVE CVE-2024-10220 | known not affected: 440 recommended: 4 | 2026-10-16T02:23:20+00:00 | Vulnerability · Source |
| CVE-2024-10241 | suse_vex | SUSE CVE CVE-2024-10241 | recommended: 5 | 2026-10-16T02:23:18+00:00 | Vulnerability · Source |
| CVE-2024-10389 | suse_vex | SUSE CVE CVE-2024-10389 | recommended: 5 | 2026-10-16T02:23:16+00:00 | Vulnerability · Source |
| CVE-2024-10452 | suse_vex | SUSE CVE CVE-2024-10452 | known not affected: 4 recommended: 4 | 2026-10-16T02:23:14+00:00 | Vulnerability · Source |
| CVE-2024-10460 | suse_vex | SUSE CVE CVE-2024-10460 | known affected: 67 recommended: 219 | 2026-10-16T02:23:12+00:00 | Vulnerability · Source |
| CVE-2024-10465 | suse_vex | SUSE CVE CVE-2024-10465 | known affected: 67 recommended: 219 | 2026-10-16T02:23:10+00:00 | Vulnerability · Source |
| CVE-2024-10466 | suse_vex | SUSE CVE CVE-2024-10466 | known affected: 67 recommended: 216 | 2026-10-16T02:23:08+00:00 | Vulnerability · Source |
| CVE-2024-10524 | suse_vex | SUSE CVE CVE-2024-10524 | known affected: 364 recommended: 106 | 2026-10-16T02:23:06+00:00 | Vulnerability · Source |