VEX records
Browse vendor VEX statements available in this Vulnerability-Lookup instance and pivot to the related vulnerability.
291513 VEX records
API response| Vulnerability | Source | Title | Product status | Imported | Links |
|---|---|---|---|---|---|
| CVE-2024-35951 | suse_vex | SUSE CVE CVE-2024-35951 | known affected: 394 known not affected: 121 recommended: 675 | 2026-08-05T00:58:19+00:00 | Vulnerability · Source |
| CVE-2024-35967 | suse_vex | SUSE CVE CVE-2024-35967 | known affected: 515 known not affected: 12 recommended: 802 | 2026-08-05T00:58:14+00:00 | Vulnerability · Source |
| CVE-2024-35968 | suse_vex | SUSE CVE CVE-2024-35968 | known not affected: 330 | 2026-08-05T00:58:13+00:00 | Vulnerability · Source |
| CVE-2024-35993 | suse_vex | SUSE CVE CVE-2024-35993 | known not affected: 330 | 2026-08-05T00:58:06+00:00 | Vulnerability · Source |
| CVE-2024-35994 | suse_vex | SUSE CVE CVE-2024-35994 | known not affected: 330 | 2026-08-05T00:58:04+00:00 | Vulnerability · Source |
| CVE-2024-36016 | suse_vex | SUSE CVE CVE-2024-36016 | known affected: 431 recommended: 804 | 2026-08-05T00:57:59+00:00 | Vulnerability · Source |
| CVE-2024-36018 | suse_vex | SUSE CVE CVE-2024-36018 | known affected: 394 known not affected: 270 recommended: 362 | 2026-08-05T00:57:57+00:00 | Vulnerability · Source |
| CVE-2024-36288 | suse_vex | SUSE CVE CVE-2024-36288 | known affected: 330 known not affected: 175 recommended: 728 | 2026-08-05T00:57:53+00:00 | Vulnerability · Source |
| CVE-2024-36884 | suse_vex | SUSE CVE CVE-2024-36884 | known not affected: 330 recommended: 59 | 2026-08-05T00:57:50+00:00 | Vulnerability · Source |
| CVE-2024-36894 | suse_vex | SUSE CVE CVE-2024-36894 | known affected: 365 known not affected: 6 recommended: 1026 | 2026-08-05T00:57:47+00:00 | Vulnerability · Source |
| CVE-2024-36958 | suse_vex | SUSE CVE CVE-2024-36958 | known not affected: 330 | 2026-08-05T00:57:35+00:00 | Vulnerability · Source |
| CVE-2024-36960 | suse_vex | SUSE CVE CVE-2024-36960 | known affected: 550 known not affected: 33 recommended: 760 | 2026-08-05T00:57:33+00:00 | Vulnerability · Source |
| CVE-2024-36962 | suse_vex | SUSE CVE CVE-2024-36962 | known affected: 394 known not affected: 235 recommended: 592 | 2026-08-05T00:57:32+00:00 | Vulnerability · Source |
| CVE-2024-38544 | suse_vex | SUSE CVE CVE-2024-38544 | known affected: 501 known not affected: 37 recommended: 755 | 2026-08-05T00:57:17+00:00 | Vulnerability · Source |
| CVE-2024-38564 | suse_vex | SUSE CVE CVE-2024-38564 | known affected: 317 known not affected: 169 recommended: 809 | 2026-08-05T00:57:14+00:00 | Vulnerability · Source |
| CVE-2024-38568 | suse_vex | SUSE CVE CVE-2024-38568 | known affected: 357 known not affected: 230 recommended: 656 | 2026-08-05T00:57:12+00:00 | Vulnerability · Source |
| CVE-2024-38599 | suse_vex | SUSE CVE CVE-2024-38599 | known affected: 397 known not affected: 142 recommended: 752 | 2026-08-05T00:56:58+00:00 | Vulnerability · Source |
| CVE-2024-38614 | suse_vex | SUSE CVE CVE-2024-38614 | known not affected: 318 | 2026-08-05T00:56:53+00:00 | Vulnerability · Source |
| CVE-2024-38620 | suse_vex | SUSE CVE CVE-2024-38620 | known not affected: 523 recommended: 59 | 2026-08-05T00:56:52+00:00 | Vulnerability · Source |
| CVE-2024-39292 | suse_vex | SUSE CVE CVE-2024-39292 | known not affected: 318 | 2026-08-05T00:56:47+00:00 | Vulnerability · Source |
| CVE-2024-39463 | suse_vex | SUSE CVE CVE-2024-39463 | known affected: 295 known not affected: 185 recommended: 784 | 2026-08-05T00:56:45+00:00 | Vulnerability · Source |
| CVE-2024-39467 | suse_vex | SUSE CVE CVE-2024-39467 | known not affected: 318 | 2026-08-05T00:56:43+00:00 | Vulnerability · Source |
| CVE-2024-39477 | suse_vex | SUSE CVE CVE-2024-39477 | known not affected: 318 | 2026-08-05T00:56:39+00:00 | Vulnerability · Source |
| CVE-2024-39478 | suse_vex | SUSE CVE CVE-2024-39478 | known not affected: 318 | 2026-08-05T00:56:37+00:00 | Vulnerability · Source |
| CVE-2024-39482 | suse_vex | SUSE CVE CVE-2024-39482 | known affected: 442 known not affected: 6 recommended: 656 | 2026-08-05T00:56:32+00:00 | Vulnerability · Source |
| CVE-2024-39496 | suse_vex | SUSE CVE CVE-2024-39496 | known affected: 394 known not affected: 230 recommended: 358 | 2026-08-05T00:56:23+00:00 | Vulnerability · Source |
| CVE-2024-40923 | suse_vex | SUSE CVE CVE-2024-40923 | known affected: 330 known not affected: 195 recommended: 726 | 2026-08-05T00:56:12+00:00 | Vulnerability · Source |
| CVE-2024-40925 | suse_vex | SUSE CVE CVE-2024-40925 | known affected: 394 known not affected: 300 recommended: 358 | 2026-08-05T00:56:08+00:00 | Vulnerability · Source |
| CVE-2024-40971 | suse_vex | SUSE CVE CVE-2024-40971 | known not affected: 318 | 2026-08-05T00:55:58+00:00 | Vulnerability · Source |
| CVE-2024-40974 | suse_vex | SUSE CVE CVE-2024-40974 | recommended: 20 | 2026-08-05T00:55:56+00:00 | Vulnerability · Source |
| CVE-2024-40986 | suse_vex | SUSE CVE CVE-2024-40986 | known not affected: 318 | 2026-08-05T00:55:51+00:00 | Vulnerability · Source |
| CVE-2024-40989 | suse_vex | SUSE CVE CVE-2024-40989 | known affected: 295 known not affected: 169 recommended: 806 | 2026-08-05T00:55:50+00:00 | Vulnerability · Source |
| CVE-2024-40991 | suse_vex | SUSE CVE CVE-2024-40991 | known not affected: 318 | 2026-08-05T00:55:48+00:00 | Vulnerability · Source |
| CVE-2024-41008 | suse_vex | SUSE CVE CVE-2024-41008 | recommended: 79 | 2026-08-05T00:55:46+00:00 | Vulnerability · Source |
| CVE-2024-41018 | suse_vex | SUSE CVE CVE-2024-41018 | known not affected: 324 | 2026-08-05T00:55:38+00:00 | Vulnerability · Source |
| CVE-2024-41038 | suse_vex | SUSE CVE CVE-2024-41038 | known affected: 387 known not affected: 151 recommended: 668 | 2026-08-05T00:55:31+00:00 | Vulnerability · Source |
| CVE-2024-41056 | suse_vex | SUSE CVE CVE-2024-41056 | known affected: 401 known not affected: 181 recommended: 668 | 2026-08-05T00:55:24+00:00 | Vulnerability · Source |
| CVE-2024-41073 | suse_vex | SUSE CVE CVE-2024-41073 | known affected: 534 known not affected: 6 recommended: 781 | 2026-08-05T00:55:18+00:00 | Vulnerability · Source |
| CVE-2024-41075 | suse_vex | SUSE CVE CVE-2024-41075 | known affected: 394 known not affected: 261 recommended: 360 | 2026-08-05T00:55:16+00:00 | Vulnerability · Source |
| CVE-2024-41086 | suse_vex | SUSE CVE CVE-2024-41086 | known not affected: 324 | 2026-08-05T00:55:13+00:00 | Vulnerability · Source |
| CVE-2024-42067 | suse_vex | SUSE CVE CVE-2024-42067 | known not affected: 324 | 2026-08-05T00:55:07+00:00 | Vulnerability · Source |
| CVE-2024-42104 | suse_vex | SUSE CVE CVE-2024-42104 | known affected: 501 known not affected: 31 recommended: 662 | 2026-08-05T00:55:00+00:00 | Vulnerability · Source |
| CVE-2024-42108 | suse_vex | SUSE CVE CVE-2024-42108 | known not affected: 324 | 2026-08-05T00:54:56+00:00 | Vulnerability · Source |
| CVE-2024-42110 | suse_vex | SUSE CVE CVE-2024-42110 | known affected: 528 known not affected: 6 recommended: 761 | 2026-08-05T00:54:54+00:00 | Vulnerability · Source |
| CVE-2024-42111 | suse_vex | SUSE CVE CVE-2024-42111 | known not affected: 324 | 2026-08-05T00:54:52+00:00 | Vulnerability · Source |
| CVE-2024-42120 | suse_vex | SUSE CVE CVE-2024-42120 | known affected: 504 known not affected: 42 recommended: 732 | 2026-08-05T00:54:47+00:00 | Vulnerability · Source |
| CVE-2024-42233 | suse_vex | SUSE CVE CVE-2024-42233 | known not affected: 311 | 2026-08-05T00:54:39+00:00 | Vulnerability · Source |
| CVE-2024-42235 | suse_vex | SUSE CVE CVE-2024-42235 | known not affected: 311 | 2026-08-05T00:54:38+00:00 | Vulnerability · Source |
| CVE-2024-42256 | suse_vex | SUSE CVE CVE-2024-42256 | known not affected: 310 | 2026-08-05T00:54:29+00:00 | Vulnerability · Source |
| CVE-2024-42258 | suse_vex | SUSE CVE CVE-2024-42258 | known not affected: 311 | 2026-08-05T00:54:28+00:00 | Vulnerability · Source |