VEX records
Browse vendor VEX statements available in this Vulnerability-Lookup instance and pivot to the related vulnerability.
306858 VEX records
API response| Vulnerability | Source | Title | Product status | Imported | Links |
|---|---|---|---|---|---|
| CVE-2024-2955 | suse_vex | SUSE CVE CVE-2024-2955 | known not affected: 303 recommended: 78 | 2026-10-11T00:49:03+00:00 | Vulnerability · Source |
| CVE-2024-2961 | suse_vex | SUSE CVE CVE-2024-2961 | known affected: 432 known not affected: 70 recommended: 1439 | 2026-10-11T00:49:01+00:00 | Vulnerability · Source |
| CVE-2024-3183 | suse_vex | SUSE CVE CVE-2024-3183 | recommended: 39 | 2026-10-11T00:48:59+00:00 | Vulnerability · Source |
| CVE-2024-3596 | suse_vex | SUSE CVE CVE-2024-3596 | known affected: 156 recommended: 456 | 2026-10-11T00:48:55+00:00 | Vulnerability · Source |
| CVE-2024-3657 | suse_vex | SUSE CVE CVE-2024-3657 | known affected: 52 recommended: 138 | 2026-10-11T00:48:53+00:00 | Vulnerability · Source |
| CVE-2024-3727 | suse_vex | SUSE CVE CVE-2024-3727 | known affected: 429 recommended: 493 | 2026-10-11T00:48:50+00:00 | Vulnerability · Source |
| CVE-2024-3772 | suse_vex | SUSE CVE CVE-2024-3772 | known affected: 25 recommended: 25 | 2026-10-11T00:48:48+00:00 | Vulnerability · Source |
| CVE-2024-3852 | suse_vex | SUSE CVE CVE-2024-3852 | known affected: 48 recommended: 211 | 2026-10-11T00:48:46+00:00 | Vulnerability · Source |
| CVE-2024-3853 | suse_vex | SUSE CVE CVE-2024-3853 | known affected: 48 recommended: 9 | 2026-10-11T00:48:44+00:00 | Vulnerability · Source |
| CVE-2024-3857 | suse_vex | SUSE CVE CVE-2024-3857 | known affected: 48 recommended: 211 | 2026-10-11T00:48:41+00:00 | Vulnerability · Source |
| CVE-2024-3859 | suse_vex | SUSE CVE CVE-2024-3859 | known affected: 48 recommended: 211 | 2026-10-11T00:48:39+00:00 | Vulnerability · Source |
| CVE-2024-3860 | suse_vex | SUSE CVE CVE-2024-3860 | known affected: 48 recommended: 9 | 2026-10-11T00:48:37+00:00 | Vulnerability · Source |
| CVE-2024-4141 | suse_vex | SUSE CVE CVE-2024-4141 | known affected: 263 known not affected: 16 recommended: 126 | 2026-10-11T00:48:33+00:00 | Vulnerability · Source |
| CVE-2024-4317 | suse_vex | SUSE CVE CVE-2024-4317 | known affected: 847 known not affected: 669 recommended: 738 | 2026-10-11T00:48:31+00:00 | Vulnerability · Source |
| CVE-2024-4367 | suse_vex | SUSE CVE CVE-2024-4367 | known affected: 52 recommended: 658 | 2026-10-11T00:48:28+00:00 | Vulnerability · Source |
| CVE-2024-4577 | suse_vex | SUSE CVE CVE-2024-4577 | known not affected: 5024 recommended: 206 | 2026-10-11T00:48:24+00:00 | Vulnerability · Source |
| CVE-2024-4741 | suse_vex | SUSE CVE CVE-2024-4741 | known affected: 351 known not affected: 418 recommended: 534 | 2026-10-11T00:48:22+00:00 | Vulnerability · Source |
| CVE-2024-4765 | suse_vex | SUSE CVE CVE-2024-4765 | known affected: 52 recommended: 9 | 2026-10-11T00:48:19+00:00 | Vulnerability · Source |
| CVE-2024-4767 | suse_vex | SUSE CVE CVE-2024-4767 | known affected: 52 recommended: 214 | 2026-10-11T00:48:16+00:00 | Vulnerability · Source |
| CVE-2024-4768 | suse_vex | SUSE CVE CVE-2024-4768 | known affected: 52 recommended: 214 | 2026-10-11T00:48:13+00:00 | Vulnerability · Source |
| CVE-2024-4771 | suse_vex | SUSE CVE CVE-2024-4771 | known affected: 52 recommended: 9 | 2026-10-11T00:48:11+00:00 | Vulnerability · Source |
| CVE-2024-4772 | suse_vex | SUSE CVE CVE-2024-4772 | known affected: 52 recommended: 9 | 2026-10-11T00:48:08+00:00 | Vulnerability · Source |
| CVE-2024-4775 | suse_vex | SUSE CVE CVE-2024-4775 | known affected: 52 recommended: 9 | 2026-10-11T00:48:06+00:00 | Vulnerability · Source |
| CVE-2024-4778 | suse_vex | SUSE CVE CVE-2024-4778 | known affected: 52 recommended: 9 | 2026-10-11T00:48:04+00:00 | Vulnerability · Source |
| CVE-2024-5321 | suse_vex | SUSE CVE CVE-2024-5321 | known not affected: 415 recommended: 4 | 2026-10-11T00:48:01+00:00 | Vulnerability · Source |
| CVE-2024-5458 | suse_vex | SUSE CVE CVE-2024-5458 | known affected: 1 known not affected: 189 recommended: 2740 | 2026-10-11T00:47:58+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-11T00:47:55+00:00 | Vulnerability · Source |
| CVE-2024-5585 | suse_vex | SUSE CVE CVE-2024-5585 | known not affected: 5024 recommended: 158 | 2026-10-11T00:47:52+00:00 | Vulnerability · Source |
| CVE-2024-5688 | suse_vex | SUSE CVE CVE-2024-5688 | known affected: 52 recommended: 214 | 2026-10-11T00:47:49+00:00 | Vulnerability · Source |
| CVE-2024-5690 | suse_vex | SUSE CVE CVE-2024-5690 | known affected: 52 recommended: 214 | 2026-10-11T00:47:47+00:00 | Vulnerability · Source |
| CVE-2024-5691 | suse_vex | SUSE CVE CVE-2024-5691 | known affected: 52 recommended: 214 | 2026-10-11T00:47:45+00:00 | Vulnerability · Source |
| CVE-2024-5692 | suse_vex | SUSE CVE CVE-2024-5692 | known affected: 52 recommended: 204 | 2026-10-11T00:47:43+00:00 | Vulnerability · Source |
| CVE-2024-5698 | suse_vex | SUSE CVE CVE-2024-5698 | known affected: 52 recommended: 9 | 2026-10-11T00:47:41+00:00 | Vulnerability · Source |
| CVE-2024-5702 | suse_vex | SUSE CVE CVE-2024-5702 | known affected: 52 recommended: 205 | 2026-10-11T00:47:39+00:00 | Vulnerability · Source |
| CVE-2024-6174 | suse_vex | SUSE CVE CVE-2024-6174 | known affected: 402 recommended: 156 | 2026-10-11T00:47:37+00:00 | Vulnerability · Source |
| CVE-2024-6232 | suse_vex | SUSE CVE CVE-2024-6232 | known affected: 393 recommended: 1168 | 2026-10-11T00:47:35+00:00 | Vulnerability · Source |
| CVE-2024-6237 | suse_vex | SUSE CVE CVE-2024-6237 | known not affected: 150 recommended: 40 | 2026-10-11T00:47:33+00:00 | Vulnerability · Source |
| CVE-2024-6239 | suse_vex | SUSE CVE CVE-2024-6239 | known affected: 233 known not affected: 67 recommended: 148 | 2026-10-11T00:47:30+00:00 | Vulnerability · Source |
| CVE-2024-6345 | suse_vex | SUSE CVE CVE-2024-6345 | known affected: 334 recommended: 482 | 2026-10-11T00:47:28+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-11T00:47:25+00:00 | Vulnerability · Source |
| CVE-2024-6505 | suse_vex | SUSE CVE CVE-2024-6505 | known affected: 1125 known not affected: 868 recommended: 503 | 2026-10-11T00:47:23+00:00 | Vulnerability · Source |
| CVE-2024-6600 | suse_vex | SUSE CVE CVE-2024-6600 | known affected: 52 recommended: 237 | 2026-10-11T00:47:20+00:00 | Vulnerability · Source |
| CVE-2024-6604 | suse_vex | SUSE CVE CVE-2024-6604 | known affected: 52 recommended: 245 | 2026-10-11T00:47:18+00:00 | Vulnerability · Source |
| CVE-2024-6605 | suse_vex | SUSE CVE CVE-2024-6605 | known affected: 52 recommended: 180 | 2026-10-11T00:47:15+00:00 | Vulnerability · Source |
| CVE-2024-6606 | suse_vex | SUSE CVE CVE-2024-6606 | known affected: 52 recommended: 233 | 2026-10-11T00:47:13+00:00 | Vulnerability · Source |
| CVE-2024-6607 | suse_vex | SUSE CVE CVE-2024-6607 | known affected: 52 recommended: 233 | 2026-10-11T00:47:11+00:00 | Vulnerability · Source |
| CVE-2024-6614 | suse_vex | SUSE CVE CVE-2024-6614 | known affected: 52 recommended: 233 | 2026-10-11T00:47:09+00:00 | Vulnerability · Source |
| CVE-2024-7254 | suse_vex | SUSE CVE CVE-2024-7254 | known affected: 407 known not affected: 2 recommended: 150 | 2026-10-11T00:47:06+00:00 | Vulnerability · Source |
| CVE-2024-7409 | suse_vex | SUSE CVE CVE-2024-7409 | known affected: 644 known not affected: 239 recommended: 1505 | 2026-10-11T00:47:03+00:00 | Vulnerability · Source |
| CVE-2024-7528 | suse_vex | SUSE CVE CVE-2024-7528 | known affected: 46 recommended: 241 | 2026-10-11T00:47:00+00:00 | Vulnerability · Source |