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-31951 | suse_vex | SUSE CVE CVE-2024-31951 | known not affected: 476 recommended: 164 | 2026-10-16T02:07:37+00:00 | Vulnerability · Source |
| CVE-2024-32002 | suse_vex | SUSE CVE CVE-2024-32002 | known affected: 206 known not affected: 137 recommended: 460 | 2026-10-16T02:07:35+00:00 | Vulnerability · Source |
| CVE-2024-32004 | suse_vex | SUSE CVE CVE-2024-32004 | known affected: 206 known not affected: 137 recommended: 475 | 2026-10-16T02:07:34+00:00 | Vulnerability · Source |
| CVE-2024-32021 | suse_vex | SUSE CVE CVE-2024-32021 | known affected: 206 known not affected: 137 recommended: 460 | 2026-10-16T02:07:32+00:00 | Vulnerability · Source |
| CVE-2024-32039 | suse_vex | SUSE CVE CVE-2024-32039 | known not affected: 48 recommended: 150 | 2026-10-16T02:07:30+00:00 | Vulnerability · Source |
| CVE-2024-32040 | suse_vex | SUSE CVE CVE-2024-32040 | known not affected: 48 recommended: 155 | 2026-10-16T02:07:28+00:00 | Vulnerability · Source |
| CVE-2024-32229 | suse_vex | SUSE CVE CVE-2024-32229 | known not affected: 827 recommended: 44 | 2026-10-16T02:07:26+00:00 | Vulnerability · Source |
| CVE-2024-32459 | suse_vex | SUSE CVE CVE-2024-32459 | known not affected: 48 recommended: 155 | 2026-10-16T02:07:24+00:00 | Vulnerability · Source |
| CVE-2024-32465 | suse_vex | SUSE CVE CVE-2024-32465 | known affected: 206 known not affected: 137 recommended: 460 | 2026-10-16T02:07:23+00:00 | Vulnerability · Source |
| CVE-2024-32650 | suse_vex | SUSE CVE CVE-2024-32650 | known affected: 31 known not affected: 70 recommended: 63 | 2026-10-16T02:07:21+00:00 | Vulnerability · Source |
| CVE-2024-33394 | suse_vex | SUSE CVE CVE-2024-33394 | known not affected: 9 recommended: 97 | 2026-10-16T02:07:17+00:00 | Vulnerability · Source |
| CVE-2024-33599 | suse_vex | SUSE CVE CVE-2024-33599 | known affected: 264 known not affected: 252 recommended: 1404 | 2026-10-16T02:07:15+00:00 | Vulnerability · Source |
| CVE-2024-33600 | suse_vex | SUSE CVE CVE-2024-33600 | known affected: 442 known not affected: 70 recommended: 1189 | 2026-10-16T02:07:12+00:00 | Vulnerability · Source |
| CVE-2024-33601 | suse_vex | SUSE CVE CVE-2024-33601 | known affected: 337 known not affected: 75 recommended: 1404 | 2026-10-16T02:07:10+00:00 | Vulnerability · Source |
| CVE-2024-33602 | suse_vex | SUSE CVE CVE-2024-33602 | known affected: 441 known not affected: 75 recommended: 1404 | 2026-10-16T02:07:08+00:00 | Vulnerability · Source |
| CVE-2024-33619 | suse_vex | SUSE CVE CVE-2024-33619 | known affected: 352 known not affected: 293 recommended: 651 | 2026-10-16T02:07:06+00:00 | Vulnerability · Source |
| CVE-2024-33621 | suse_vex | SUSE CVE CVE-2024-33621 | known affected: 340 known not affected: 6 recommended: 49 | 2026-10-16T02:07:04+00:00 | Vulnerability · Source |
| CVE-2024-33663 | suse_vex | SUSE CVE CVE-2024-33663 | known not affected: 3 recommended: 14 | 2026-10-16T02:07:03+00:00 | Vulnerability · Source |
| CVE-2024-33664 | suse_vex | SUSE CVE CVE-2024-33664 | known not affected: 3 recommended: 14 | 2026-10-16T02:07:01+00:00 | Vulnerability · Source |
| CVE-2024-33847 | suse_vex | SUSE CVE CVE-2024-33847 | known not affected: 568 | 2026-10-16T02:06:59+00:00 | Vulnerability · Source |
| CVE-2024-33871 | suse_vex | SUSE CVE CVE-2024-33871 | known affected: 44 recommended: 144 | 2026-10-16T02:06:55+00:00 | Vulnerability · Source |
| CVE-2024-34027 | suse_vex | SUSE CVE CVE-2024-34027 | known not affected: 316 | 2026-10-16T02:06:53+00:00 | Vulnerability · Source |
| CVE-2024-34030 | suse_vex | SUSE CVE CVE-2024-34030 | known not affected: 373 | 2026-10-16T02:06:51+00:00 | Vulnerability · Source |
| CVE-2024-34062 | suse_vex | SUSE CVE CVE-2024-34062 | recommended: 56 | 2026-10-16T02:06:50+00:00 | Vulnerability · Source |
| CVE-2024-34088 | suse_vex | SUSE CVE CVE-2024-34088 | known not affected: 476 recommended: 164 | 2026-10-16T02:06:48+00:00 | Vulnerability · Source |
| CVE-2024-34397 | suse_vex | SUSE CVE CVE-2024-34397 | known affected: 707 known not affected: 1 recommended: 579 | 2026-10-16T02:06:46+00:00 | Vulnerability · Source |
| CVE-2024-34403 | suse_vex | SUSE CVE CVE-2024-34403 | recommended: 37 | 2026-10-16T02:06:44+00:00 | Vulnerability · Source |
| CVE-2024-34459 | suse_vex | SUSE CVE CVE-2024-34459 | known affected: 470 known not affected: 63 recommended: 304 | 2026-10-16T02:06:43+00:00 | Vulnerability · Source |
| CVE-2024-34750 | suse_vex | SUSE CVE CVE-2024-34750 | known affected: 487 known not affected: 5 recommended: 439 | 2026-10-16T02:06:41+00:00 | Vulnerability · Source |
| CVE-2024-34777 | suse_vex | SUSE CVE CVE-2024-34777 | known affected: 394 known not affected: 285 recommended: 353 | 2026-10-16T02:06:39+00:00 | Vulnerability · Source |
| CVE-2024-35176 | suse_vex | SUSE CVE CVE-2024-35176 | known affected: 439 known not affected: 154 recommended: 192 | 2026-10-16T02:06:37+00:00 | Vulnerability · Source |
| CVE-2024-35177 | suse_vex | SUSE CVE CVE-2024-35177 | recommended: 5 | 2026-10-16T02:06:35+00:00 | Vulnerability · Source |
| CVE-2024-35195 | suse_vex | SUSE CVE CVE-2024-35195 | known affected: 314 recommended: 288 | 2026-10-16T02:06:34+00:00 | Vulnerability · Source |
| CVE-2024-35242 | suse_vex | SUSE CVE CVE-2024-35242 | recommended: 29 | 2026-10-16T02:06:32+00:00 | Vulnerability · Source |
| CVE-2024-35326 | suse_vex | SUSE CVE CVE-2024-35326 | known not affected: 376 | 2026-10-16T02:06:29+00:00 | Vulnerability · Source |
| CVE-2024-35328 | suse_vex | SUSE CVE CVE-2024-35328 | known not affected: 376 | 2026-10-16T02:06:27+00:00 | Vulnerability · Source |
| CVE-2024-35368 | suse_vex | SUSE CVE CVE-2024-35368 | known affected: 467 recommended: 558 | 2026-10-16T02:06:25+00:00 | Vulnerability · Source |
| CVE-2024-35369 | suse_vex | SUSE CVE CVE-2024-35369 | known not affected: 962 | 2026-10-16T02:06:23+00:00 | Vulnerability · Source |
| CVE-2024-35784 | suse_vex | SUSE CVE CVE-2024-35784 | known affected: 394 known not affected: 332 recommended: 357 | 2026-10-16T02:06:21+00:00 | Vulnerability · Source |
| CVE-2024-35785 | suse_vex | SUSE CVE CVE-2024-35785 | known not affected: 385 | 2026-10-16T02:06:19+00:00 | Vulnerability · Source |
| CVE-2024-35786 | suse_vex | SUSE CVE CVE-2024-35786 | known affected: 394 known not affected: 332 recommended: 357 | 2026-10-16T02:06:18+00:00 | Vulnerability · Source |
| CVE-2024-35787 | suse_vex | SUSE CVE CVE-2024-35787 | known not affected: 628 | 2026-10-16T02:06:16+00:00 | Vulnerability · Source |
| CVE-2024-35791 | suse_vex | SUSE CVE CVE-2024-35791 | known affected: 315 known not affected: 201 recommended: 794 | 2026-10-16T02:06:09+00:00 | Vulnerability · Source |
| CVE-2024-35792 | suse_vex | SUSE CVE CVE-2024-35792 | known not affected: 385 | 2026-10-16T02:06:08+00:00 | Vulnerability · Source |
| CVE-2024-35793 | suse_vex | SUSE CVE CVE-2024-35793 | known not affected: 385 | 2026-10-16T02:06:06+00:00 | Vulnerability · Source |
| CVE-2024-35794 | suse_vex | SUSE CVE CVE-2024-35794 | known affected: 781 known not affected: 44 recommended: 357 | 2026-10-16T02:06:04+00:00 | Vulnerability · Source |
| CVE-2024-35798 | suse_vex | SUSE CVE CVE-2024-35798 | known not affected: 385 | 2026-10-16T02:06:00+00:00 | Vulnerability · Source |
| CVE-2024-35799 | suse_vex | SUSE CVE CVE-2024-35799 | known affected: 315 known not affected: 270 recommended: 670 | 2026-10-16T02:05:58+00:00 | Vulnerability · Source |
| CVE-2024-35804 | suse_vex | SUSE CVE CVE-2024-35804 | known affected: 382 known not affected: 237 recommended: 666 | 2026-10-16T02:05:56+00:00 | Vulnerability · Source |
| CVE-2024-35805 | suse_vex | SUSE CVE CVE-2024-35805 | known affected: 604 recommended: 735 | 2026-10-16T02:05:54+00:00 | Vulnerability · Source |