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-4770 | suse_vex | SUSE CVE CVE-2024-4770 | known affected: 52 recommended: 211 | 2026-10-16T02:26:38+00:00 | Vulnerability · Source |
| CVE-2024-4774 | suse_vex | SUSE CVE CVE-2024-4774 | known affected: 52 recommended: 9 | 2026-10-16T02:26:36+00:00 | Vulnerability · Source |
| CVE-2024-4776 | suse_vex | SUSE CVE CVE-2024-4776 | known affected: 52 recommended: 9 | 2026-10-16T02:26:34+00:00 | Vulnerability · Source |
| CVE-2024-4854 | suse_vex | SUSE CVE CVE-2024-4854 | known affected: 180 known not affected: 58 recommended: 123 | 2026-10-16T02:26:32+00:00 | Vulnerability · Source |
| CVE-2024-5321 | suse_vex | SUSE CVE CVE-2024-5321 | known affected: 0 known not affected: 415 recommended: 5 | 2026-10-16T02:26:30+00:00 | Vulnerability · Source |
| CVE-2024-5458 | suse_vex | SUSE CVE CVE-2024-5458 | known affected: 1 known not affected: 189 recommended: 2792 | 2026-10-16T02:26:28+00:00 | Vulnerability · Source |
| CVE-2024-5535 | suse_vex | SUSE CVE CVE-2024-5535 | known affected: 430 known not affected: 168 recommended: 710 | 2026-10-16T02:26:26+00:00 | Vulnerability · Source |
| CVE-2024-5564 | suse_vex | SUSE CVE CVE-2024-5564 | known affected: 422 recommended: 84 | 2026-10-16T02:26:24+00:00 | Vulnerability · Source |
| CVE-2024-5569 | suse_vex | SUSE CVE CVE-2024-5569 | known affected: 4 known not affected: 98 recommended: 37 | 2026-10-16T02:26:23+00:00 | Vulnerability · Source |
| CVE-2024-5594 | suse_vex | SUSE CVE CVE-2024-5594 | known affected: 84 recommended: 112 | 2026-10-16T02:26:21+00:00 | Vulnerability · Source |
| CVE-2024-5690 | suse_vex | SUSE CVE CVE-2024-5690 | known affected: 52 recommended: 214 | 2026-10-16T02:26:18+00:00 | Vulnerability · Source |
| CVE-2024-5693 | suse_vex | SUSE CVE CVE-2024-5693 | known affected: 52 recommended: 214 | 2026-10-16T02:26:17+00:00 | Vulnerability · Source |
| CVE-2024-5742 | suse_vex | SUSE CVE CVE-2024-5742 | recommended: 13 | 2026-10-16T02:26:15+00:00 | Vulnerability · Source |
| CVE-2024-6104 | suse_vex | SUSE CVE CVE-2024-6104 | known affected: 467 known not affected: 3 recommended: 373 | 2026-10-16T02:26:13+00:00 | Vulnerability · Source |
| CVE-2024-6119 | suse_vex | SUSE CVE CVE-2024-6119 | known affected: 394 known not affected: 668 recommended: 154 | 2026-10-16T02:26:11+00:00 | Vulnerability · Source |
| CVE-2024-6126 | suse_vex | SUSE CVE CVE-2024-6126 | known affected: 394 recommended: 128 | 2026-10-16T02:26:09+00:00 | Vulnerability · Source |
| CVE-2024-6174 | suse_vex | SUSE CVE CVE-2024-6174 | known affected: 402 recommended: 159 | 2026-10-16T02:26:07+00:00 | Vulnerability · Source |
| CVE-2024-6197 | suse_vex | SUSE CVE CVE-2024-6197 | known affected: 394 known not affected: 176 recommended: 69 | 2026-10-16T02:26:05+00:00 | Vulnerability · Source |
| CVE-2024-6232 | suse_vex | SUSE CVE CVE-2024-6232 | known affected: 393 recommended: 1168 | 2026-10-16T02:26:03+00:00 | Vulnerability · Source |
| CVE-2024-6237 | suse_vex | SUSE CVE CVE-2024-6237 | known not affected: 150 recommended: 40 | 2026-10-16T02:26:02+00:00 | Vulnerability · Source |
| CVE-2024-6285 | suse_vex | SUSE CVE CVE-2024-6285 | known not affected: 34 | 2026-10-16T02:26:00+00:00 | Vulnerability · Source |
| CVE-2024-6345 | suse_vex | SUSE CVE CVE-2024-6345 | known affected: 334 recommended: 482 | 2026-10-16T02:25:58+00:00 | Vulnerability · Source |
| CVE-2024-6387 | suse_vex | SUSE CVE CVE-2024-6387 | known affected: 394 known not affected: 422 recommended: 127 | 2026-10-16T02:25:56+00:00 | Vulnerability · Source |
| CVE-2024-6409 | suse_vex | SUSE CVE CVE-2024-6409 | known not affected: 251 recommended: 12 | 2026-10-16T02:25:54+00:00 | Vulnerability · Source |
| CVE-2024-6501 | suse_vex | SUSE CVE CVE-2024-6501 | known not affected: 427 recommended: 32 | 2026-10-16T02:25:52+00:00 | Vulnerability · Source |
| CVE-2024-6538 | suse_vex | SUSE CVE CVE-2024-6538 | recommended: 4 | 2026-10-16T02:25:51+00:00 | Vulnerability · Source |
| CVE-2024-6564 | suse_vex | SUSE CVE CVE-2024-6564 | known not affected: 34 | 2026-10-16T02:25:49+00:00 | Vulnerability · Source |
| CVE-2024-6601 | suse_vex | SUSE CVE CVE-2024-6601 | known affected: 52 recommended: 245 | 2026-10-16T02:25:47+00:00 | Vulnerability · Source |
| CVE-2024-6606 | suse_vex | SUSE CVE CVE-2024-6606 | known affected: 52 recommended: 233 | 2026-10-16T02:25:45+00:00 | Vulnerability · Source |
| CVE-2024-6607 | suse_vex | SUSE CVE CVE-2024-6607 | known affected: 52 recommended: 233 | 2026-10-16T02:25:43+00:00 | Vulnerability · Source |
| CVE-2024-6609 | suse_vex | SUSE CVE CVE-2024-6609 | known affected: 52 recommended: 233 | 2026-10-16T02:25:41+00:00 | Vulnerability · Source |
| CVE-2024-6611 | suse_vex | SUSE CVE CVE-2024-6611 | known affected: 52 recommended: 233 | 2026-10-16T02:25:39+00:00 | Vulnerability · Source |
| CVE-2024-6612 | suse_vex | SUSE CVE CVE-2024-6612 | known affected: 52 recommended: 233 | 2026-10-16T02:25:38+00:00 | Vulnerability · Source |
| CVE-2024-6613 | suse_vex | SUSE CVE CVE-2024-6613 | known affected: 52 recommended: 233 | 2026-10-16T02:25:36+00:00 | Vulnerability · Source |
| CVE-2024-6614 | suse_vex | SUSE CVE CVE-2024-6614 | known affected: 52 recommended: 233 | 2026-10-16T02:25:34+00:00 | Vulnerability · Source |
| CVE-2024-6615 | suse_vex | SUSE CVE CVE-2024-6615 | known affected: 52 recommended: 233 | 2026-10-16T02:25:32+00:00 | Vulnerability · Source |
| CVE-2024-6717 | suse_vex | SUSE CVE CVE-2024-6717 | recommended: 2 | 2026-10-16T02:25:30+00:00 | Vulnerability · Source |
| CVE-2024-6874 | suse_vex | SUSE CVE CVE-2024-6874 | known not affected: 176 recommended: 66 | 2026-10-16T02:25:28+00:00 | Vulnerability · Source |
| CVE-2024-7055 | suse_vex | SUSE CVE CVE-2024-7055 | known not affected: 726 recommended: 359 | 2026-10-16T02:25:24+00:00 | Vulnerability · Source |
| CVE-2024-7246 | suse_vex | SUSE CVE CVE-2024-7246 | known affected: 394 known not affected: 90 recommended: 133 | 2026-10-16T02:25:22+00:00 | Vulnerability · Source |
| CVE-2024-7264 | suse_vex | SUSE CVE CVE-2024-7264 | first fixed: 13 known affected: 398 recommended: 279 | 2026-10-16T02:25:20+00:00 | Vulnerability · Source |
| CVE-2024-7348 | suse_vex | SUSE CVE CVE-2024-7348 | known affected: 464 known not affected: 462 recommended: 1564 | 2026-10-16T02:25:18+00:00 | Vulnerability · Source |
| CVE-2024-7383 | suse_vex | SUSE CVE CVE-2024-7383 | recommended: 65 | 2026-10-16T02:25:16+00:00 | Vulnerability · Source |
| CVE-2024-7518 | suse_vex | SUSE CVE CVE-2024-7518 | known affected: 46 recommended: 238 | 2026-10-16T02:25:14+00:00 | Vulnerability · Source |
| CVE-2024-7520 | suse_vex | SUSE CVE CVE-2024-7520 | known affected: 46 recommended: 238 | 2026-10-16T02:25:12+00:00 | Vulnerability · Source |
| CVE-2024-7521 | suse_vex | SUSE CVE CVE-2024-7521 | known affected: 46 recommended: 242 | 2026-10-16T02:25:10+00:00 | Vulnerability · Source |
| CVE-2024-7522 | suse_vex | SUSE CVE CVE-2024-7522 | known affected: 46 recommended: 242 | 2026-10-16T02:25:09+00:00 | Vulnerability · Source |
| CVE-2024-7527 | suse_vex | SUSE CVE CVE-2024-7527 | known affected: 46 recommended: 242 | 2026-10-16T02:25:07+00:00 | Vulnerability · Source |
| CVE-2024-7528 | suse_vex | SUSE CVE CVE-2024-7528 | known affected: 46 recommended: 241 | 2026-10-16T02:25:05+00:00 | Vulnerability · Source |
| CVE-2024-7531 | suse_vex | SUSE CVE CVE-2024-7531 | known affected: 46 recommended: 180 | 2026-10-16T02:25:03+00:00 | Vulnerability · Source |