VEX records
Browse vendor VEX statements available in this Vulnerability-Lookup instance and pivot to the related vulnerability.
292116 VEX records
API response| Vulnerability | Source | Title | Product status | Imported | Links |
|---|---|---|---|---|---|
| CVE-2024-38609 | suse_vex | SUSE CVE CVE-2024-38609 | known affected: 394 known not affected: 258 recommended: 360 | 2026-07-23T02:04:35+00:00 | Vulnerability · Source |
| CVE-2024-38624 | suse_vex | SUSE CVE CVE-2024-38624 | known affected: 4 known not affected: 436 | 2026-07-23T02:04:32+00:00 | Vulnerability · Source |
| CVE-2024-38626 | suse_vex | SUSE CVE CVE-2024-38626 | known not affected: 318 | 2026-07-23T02:04:30+00:00 | Vulnerability · Source |
| CVE-2024-38630 | suse_vex | SUSE CVE CVE-2024-38630 | known affected: 524 known not affected: 33 recommended: 740 | 2026-07-23T02:04:28+00:00 | Vulnerability · Source |
| CVE-2024-38631 | suse_vex | SUSE CVE CVE-2024-38631 | known not affected: 318 | 2026-07-23T02:04:26+00:00 | Vulnerability · Source |
| CVE-2024-38635 | suse_vex | SUSE CVE CVE-2024-38635 | known affected: 461 known not affected: 132 recommended: 656 | 2026-07-23T02:04:23+00:00 | Vulnerability · Source |
| CVE-2024-38659 | suse_vex | SUSE CVE CVE-2024-38659 | known affected: 538 recommended: 740 | 2026-07-23T02:04:22+00:00 | Vulnerability · Source |
| CVE-2024-39296 | suse_vex | SUSE CVE CVE-2024-39296 | known affected: 421 known not affected: 300 recommended: 358 | 2026-07-23T02:04:19+00:00 | Vulnerability · Source |
| CVE-2024-39483 | suse_vex | SUSE CVE CVE-2024-39483 | known affected: 394 known not affected: 261 recommended: 389 | 2026-07-23T02:04:14+00:00 | Vulnerability · Source |
| CVE-2024-39495 | suse_vex | SUSE CVE CVE-2024-39495 | known not affected: 318 | 2026-07-23T02:04:10+00:00 | Vulnerability · Source |
| CVE-2024-39920 | suse_vex | SUSE CVE CVE-2024-39920 | known not affected: 417 | 2026-07-23T02:04:07+00:00 | Vulnerability · Source |
| CVE-2024-40779 | suse_vex | SUSE CVE CVE-2024-40779 | known affected: 116 recommended: 722 | 2026-07-23T02:04:03+00:00 | Vulnerability · Source |
| CVE-2024-40794 | suse_vex | SUSE CVE CVE-2024-40794 | known not affected: 346 recommended: 648 | 2026-07-23T02:04:00+00:00 | Vulnerability · Source |
| CVE-2024-40907 | suse_vex | SUSE CVE CVE-2024-40907 | known not affected: 318 recommended: 59 | 2026-07-23T02:03:59+00:00 | Vulnerability · Source |
| CVE-2024-40911 | suse_vex | SUSE CVE CVE-2024-40911 | known affected: 560 known not affected: 6 recommended: 707 | 2026-07-23T02:03:56+00:00 | Vulnerability · Source |
| CVE-2024-40915 | suse_vex | SUSE CVE CVE-2024-40915 | known not affected: 318 | 2026-07-23T02:03:54+00:00 | Vulnerability · Source |
| CVE-2024-40917 | suse_vex | SUSE CVE CVE-2024-40917 | known not affected: 318 | 2026-07-23T02:03:53+00:00 | Vulnerability · Source |
| CVE-2024-40933 | suse_vex | SUSE CVE CVE-2024-40933 | known not affected: 318 | 2026-07-23T02:03:48+00:00 | Vulnerability · Source |
| CVE-2024-40952 | suse_vex | SUSE CVE CVE-2024-40952 | known not affected: 318 | 2026-07-23T02:03:43+00:00 | Vulnerability · Source |
| CVE-2024-40992 | suse_vex | SUSE CVE CVE-2024-40992 | known affected: 394 known not affected: 258 recommended: 360 | 2026-07-23T02:03:35+00:00 | Vulnerability · Source |
| CVE-2024-40995 | suse_vex | SUSE CVE CVE-2024-40995 | known affected: 542 known not affected: 46 recommended: 713 | 2026-07-23T02:03:33+00:00 | Vulnerability · Source |
| CVE-2024-41011 | suse_vex | SUSE CVE CVE-2024-41011 | known affected: 292 known not affected: 86 recommended: 931 | 2026-07-23T02:03:29+00:00 | Vulnerability · Source |
| CVE-2024-41017 | suse_vex | SUSE CVE CVE-2024-41017 | known affected: 434 known not affected: 168 recommended: 656 | 2026-07-23T02:03:25+00:00 | Vulnerability · Source |
| CVE-2024-41026 | suse_vex | SUSE CVE CVE-2024-41026 | known not affected: 324 | 2026-07-23T02:03:23+00:00 | Vulnerability · Source |
| CVE-2024-41029 | suse_vex | SUSE CVE CVE-2024-41029 | known not affected: 324 | 2026-07-23T02:03:21+00:00 | Vulnerability · Source |
| CVE-2024-41037 | suse_vex | SUSE CVE CVE-2024-41037 | known affected: 394 known not affected: 264 recommended: 360 | 2026-07-23T02:03:18+00:00 | Vulnerability · Source |
| CVE-2024-41044 | suse_vex | SUSE CVE CVE-2024-41044 | known affected: 524 recommended: 791 | 2026-07-23T02:03:11+00:00 | Vulnerability · Source |
| CVE-2024-41045 | suse_vex | SUSE CVE CVE-2024-41045 | known affected: 340 known not affected: 223 recommended: 648 | 2026-07-23T02:03:09+00:00 | Vulnerability · Source |
| CVE-2024-41052 | suse_vex | SUSE CVE CVE-2024-41052 | known not affected: 324 recommended: 59 | 2026-07-23T02:03:06+00:00 | Vulnerability · Source |
| CVE-2024-41058 | suse_vex | SUSE CVE CVE-2024-41058 | known affected: 330 known not affected: 223 recommended: 658 | 2026-07-23T02:03:05+00:00 | Vulnerability · Source |
| CVE-2024-41060 | suse_vex | SUSE CVE CVE-2024-41060 | known affected: 460 known not affected: 6 recommended: 752 | 2026-07-23T02:03:03+00:00 | Vulnerability · Source |
| CVE-2024-41082 | suse_vex | SUSE CVE CVE-2024-41082 | known affected: 344 known not affected: 246 recommended: 762 | 2026-07-23T02:02:57+00:00 | Vulnerability · Source |
| CVE-2024-41096 | suse_vex | SUSE CVE CVE-2024-41096 | known affected: 394 known not affected: 264 recommended: 389 | 2026-07-23T02:02:54+00:00 | Vulnerability · Source |
| CVE-2024-41123 | suse_vex | SUSE CVE CVE-2024-41123 | known affected: 394 known not affected: 161 recommended: 228 | 2026-07-23T02:02:53+00:00 | Vulnerability · Source |
| CVE-2024-41149 | suse_vex | SUSE CVE CVE-2024-41149 | known affected: 575 known not affected: 143 recommended: 362 | 2026-07-23T02:02:52+00:00 | Vulnerability · Source |
| CVE-2024-42040 | suse_vex | SUSE CVE CVE-2024-42040 | known affected: 75 | 2026-07-23T02:02:49+00:00 | Vulnerability · Source |
| CVE-2024-42066 | suse_vex | SUSE CVE CVE-2024-42066 | known not affected: 324 recommended: 59 | 2026-07-23T02:02:46+00:00 | Vulnerability · Source |
| CVE-2024-42072 | suse_vex | SUSE CVE CVE-2024-42072 | known not affected: 324 | 2026-07-23T02:02:45+00:00 | Vulnerability · Source |
| CVE-2024-42075 | suse_vex | SUSE CVE CVE-2024-42075 | known not affected: 324 | 2026-07-23T02:02:43+00:00 | Vulnerability · Source |
| CVE-2024-42086 | suse_vex | SUSE CVE CVE-2024-42086 | known affected: 395 known not affected: 92 recommended: 648 | 2026-07-23T02:02:42+00:00 | Vulnerability · Source |
| CVE-2024-42092 | suse_vex | SUSE CVE CVE-2024-42092 | known affected: 395 known not affected: 92 recommended: 648 | 2026-07-23T02:02:40+00:00 | Vulnerability · Source |
| CVE-2024-42099 | suse_vex | SUSE CVE CVE-2024-42099 | known not affected: 324 | 2026-07-23T02:02:38+00:00 | Vulnerability · Source |
| CVE-2024-42122 | suse_vex | SUSE CVE CVE-2024-42122 | known affected: 434 known not affected: 126 recommended: 658 | 2026-07-23T02:02:34+00:00 | Vulnerability · Source |
| CVE-2024-42123 | suse_vex | SUSE CVE CVE-2024-42123 | known not affected: 324 recommended: 59 | 2026-07-23T02:02:32+00:00 | Vulnerability · Source |
| CVE-2024-42129 | suse_vex | SUSE CVE CVE-2024-42129 | known not affected: 86 | 2026-07-23T02:02:31+00:00 | Vulnerability · Source |
| CVE-2024-42137 | suse_vex | SUSE CVE CVE-2024-42137 | known affected: 340 known not affected: 151 recommended: 648 | 2026-07-23T02:02:29+00:00 | Vulnerability · Source |
| CVE-2024-42144 | suse_vex | SUSE CVE CVE-2024-42144 | known affected: 394 known not affected: 264 recommended: 360 | 2026-07-23T02:02:28+00:00 | Vulnerability · Source |
| CVE-2024-42149 | suse_vex | SUSE CVE CVE-2024-42149 | known not affected: 324 | 2026-07-23T02:02:26+00:00 | Vulnerability · Source |
| CVE-2024-42150 | suse_vex | SUSE CVE CVE-2024-42150 | known not affected: 324 | 2026-07-23T02:02:25+00:00 | Vulnerability · Source |
| CVE-2024-42226 | suse_vex | SUSE CVE CVE-2024-42226 | known affected: 551 known not affected: 4 recommended: 721 | 2026-07-23T02:02:19+00:00 | Vulnerability · Source |