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-42232 | suse_vex | SUSE CVE CVE-2024-42232 | known affected: 373 known not affected: 10 recommended: 1089 | 2026-07-23T02:02:16+00:00 | Vulnerability · Source |
| CVE-2024-42242 | suse_vex | SUSE CVE CVE-2024-42242 | known not affected: 310 | 2026-07-23T02:02:13+00:00 | Vulnerability · Source |
| CVE-2024-42243 | suse_vex | SUSE CVE CVE-2024-42243 | known affected: 394 known not affected: 340 recommended: 349 | 2026-07-23T02:02:12+00:00 | Vulnerability · Source |
| CVE-2024-42252 | suse_vex | SUSE CVE CVE-2024-42252 | known affected: 394 known not affected: 38 recommended: 357 | 2026-07-23T02:02:10+00:00 | Vulnerability · Source |
| CVE-2024-42261 | suse_vex | SUSE CVE CVE-2024-42261 | known not affected: 310 recommended: 59 | 2026-07-23T02:02:09+00:00 | Vulnerability · Source |
| CVE-2024-42263 | suse_vex | SUSE CVE CVE-2024-42263 | known not affected: 310 recommended: 59 | 2026-07-23T02:02:07+00:00 | Vulnerability · Source |
| CVE-2024-42266 | suse_vex | SUSE CVE CVE-2024-42266 | known not affected: 310 | 2026-07-23T02:02:06+00:00 | Vulnerability · Source |
| CVE-2024-42267 | suse_vex | SUSE CVE CVE-2024-42267 | known not affected: 311 | 2026-07-23T02:02:05+00:00 | Vulnerability · Source |
| CVE-2024-42274 | suse_vex | SUSE CVE CVE-2024-42274 | known affected: 340 known not affected: 139 recommended: 648 | 2026-07-23T02:02:03+00:00 | Vulnerability · Source |
| CVE-2024-42284 | suse_vex | SUSE CVE CVE-2024-42284 | known affected: 516 known not affected: 6 recommended: 781 | 2026-07-23T02:02:00+00:00 | Vulnerability · Source |
| CVE-2024-42293 | suse_vex | SUSE CVE CVE-2024-42293 | known not affected: 310 | 2026-07-23T02:01:56+00:00 | Vulnerability · Source |
| CVE-2024-42297 | suse_vex | SUSE CVE CVE-2024-42297 | known not affected: 514 | 2026-07-23T02:01:54+00:00 | Vulnerability · Source |
| CVE-2024-42311 | suse_vex | SUSE CVE CVE-2024-42311 | known affected: 550 known not affected: 84 recommended: 648 | 2026-07-23T02:01:47+00:00 | Vulnerability · Source |
| CVE-2024-42328 | suse_vex | SUSE CVE CVE-2024-42328 | known not affected: 12 | 2026-07-23T02:01:45+00:00 | Vulnerability · Source |
| CVE-2024-42332 | suse_vex | SUSE CVE CVE-2024-42332 | known not affected: 12 | 2026-07-23T02:01:44+00:00 | Vulnerability · Source |
| CVE-2024-42472 | suse_vex | SUSE CVE CVE-2024-42472 | known affected: 24 recommended: 338 | 2026-07-23T02:01:41+00:00 | Vulnerability · Source |
| CVE-2024-42934 | suse_vex | SUSE CVE CVE-2024-42934 | known affected: 454 recommended: 89 | 2026-07-23T02:01:40+00:00 | Vulnerability · Source |
| CVE-2024-43398 | suse_vex | SUSE CVE CVE-2024-43398 | known affected: 394 known not affected: 130 recommended: 228 | 2026-07-23T02:01:39+00:00 | Vulnerability · Source |
| CVE-2024-43827 | suse_vex | SUSE CVE CVE-2024-43827 | known not affected: 310 recommended: 59 | 2026-07-23T02:01:33+00:00 | Vulnerability · Source |
| CVE-2024-43843 | suse_vex | SUSE CVE CVE-2024-43843 | known not affected: 310 | 2026-07-23T02:01:28+00:00 | Vulnerability · Source |
| CVE-2024-43845 | suse_vex | SUSE CVE CVE-2024-43845 | known affected: 394 known not affected: 339 recommended: 349 | 2026-07-23T02:01:27+00:00 | Vulnerability · Source |
| CVE-2024-43855 | suse_vex | SUSE CVE CVE-2024-43855 | known affected: 394 known not affected: 280 recommended: 404 | 2026-07-23T02:01:24+00:00 | Vulnerability · Source |
| CVE-2024-43860 | suse_vex | SUSE CVE CVE-2024-43860 | known affected: 465 known not affected: 105 recommended: 648 | 2026-07-23T02:01:21+00:00 | Vulnerability · Source |
| CVE-2024-43862 | suse_vex | SUSE CVE CVE-2024-43862 | known not affected: 310 | 2026-07-23T02:01:20+00:00 | Vulnerability · Source |
| CVE-2024-43865 | suse_vex | SUSE CVE CVE-2024-43865 | known not affected: 310 | 2026-07-23T02:01:18+00:00 | Vulnerability · Source |
| CVE-2024-43869 | suse_vex | SUSE CVE CVE-2024-43869 | known affected: 416 known not affected: 341 recommended: 354 | 2026-07-23T02:01:17+00:00 | Vulnerability · Source |
| CVE-2024-43878 | suse_vex | SUSE CVE CVE-2024-43878 | known not affected: 310 | 2026-07-23T02:01:15+00:00 | Vulnerability · Source |
| CVE-2024-43888 | suse_vex | SUSE CVE CVE-2024-43888 | known not affected: 311 | 2026-07-23T02:01:13+00:00 | Vulnerability · Source |
| CVE-2024-43900 | suse_vex | SUSE CVE CVE-2024-43900 | known affected: 516 known not affected: 18 recommended: 732 | 2026-07-23T02:01:07+00:00 | Vulnerability · Source |
| CVE-2024-44936 | suse_vex | SUSE CVE CVE-2024-44936 | known not affected: 310 | 2026-07-23T02:00:59+00:00 | Vulnerability · Source |
| CVE-2024-44941 | suse_vex | SUSE CVE CVE-2024-44941 | known not affected: 325 | 2026-07-23T02:00:58+00:00 | Vulnerability · Source |
| CVE-2024-44949 | suse_vex | SUSE CVE CVE-2024-44949 | known not affected: 324 | 2026-07-23T02:00:57+00:00 | Vulnerability · Source |
| CVE-2024-44955 | suse_vex | SUSE CVE CVE-2024-44955 | known not affected: 518 recommended: 59 | 2026-07-23T02:00:55+00:00 | Vulnerability · Source |
| CVE-2024-44957 | suse_vex | SUSE CVE CVE-2024-44957 | known not affected: 324 | 2026-07-23T02:00:54+00:00 | Vulnerability · Source |
| CVE-2024-44969 | suse_vex | SUSE CVE CVE-2024-44969 | known affected: 465 known not affected: 92 recommended: 715 | 2026-07-23T02:00:49+00:00 | Vulnerability · Source |
| CVE-2024-44973 | suse_vex | SUSE CVE CVE-2024-44973 | known not affected: 324 | 2026-07-23T02:00:47+00:00 | Vulnerability · Source |
| CVE-2024-44975 | suse_vex | SUSE CVE CVE-2024-44975 | known not affected: 324 recommended: 102 | 2026-07-23T02:00:45+00:00 | Vulnerability · Source |
| CVE-2024-44978 | suse_vex | SUSE CVE CVE-2024-44978 | known not affected: 325 recommended: 59 | 2026-07-23T02:00:44+00:00 | Vulnerability · Source |
| CVE-2024-44983 | suse_vex | SUSE CVE CVE-2024-44983 | known affected: 57 known not affected: 188 | 2026-07-23T02:00:43+00:00 | Vulnerability · Source |
| CVE-2024-44991 | suse_vex | SUSE CVE CVE-2024-44991 | known affected: 394 known not affected: 353 recommended: 357 | 2026-07-23T02:00:41+00:00 | Vulnerability · Source |
| CVE-2024-44993 | suse_vex | SUSE CVE CVE-2024-44993 | known not affected: 324 recommended: 59 | 2026-07-23T02:00:40+00:00 | Vulnerability · Source |
| CVE-2024-45010 | suse_vex | SUSE CVE CVE-2024-45010 | known affected: 569 known not affected: 213 recommended: 353 | 2026-07-23T02:00:34+00:00 | Vulnerability · Source |
| CVE-2024-45023 | suse_vex | SUSE CVE CVE-2024-45023 | known affected: 394 known not affected: 353 recommended: 357 | 2026-07-23T02:00:31+00:00 | Vulnerability · Source |
| CVE-2024-45310 | suse_vex | SUSE CVE CVE-2024-45310 | first fixed: 1 known affected: 301 known not affected: 665 recommended: 213 | 2026-07-23T02:00:30+00:00 | Vulnerability · Source |
| CVE-2024-45492 | suse_vex | SUSE CVE CVE-2024-45492 | known affected: 489 known not affected: 7 recommended: 311 | 2026-07-23T02:00:28+00:00 | Vulnerability · Source |
| CVE-2024-45619 | suse_vex | SUSE CVE CVE-2024-45619 | known affected: 422 recommended: 39 | 2026-07-23T02:00:27+00:00 | Vulnerability · Source |
| CVE-2024-45699 | suse_vex | SUSE CVE CVE-2024-45699 | known not affected: 11 | 2026-07-23T02:00:25+00:00 | Vulnerability · Source |
| CVE-2024-46544 | suse_vex | SUSE CVE CVE-2024-46544 | known affected: 35 recommended: 13 | 2026-07-23T02:00:20+00:00 | Vulnerability · Source |
| CVE-2024-46697 | suse_vex | SUSE CVE CVE-2024-46697 | known not affected: 324 | 2026-07-23T02:00:13+00:00 | Vulnerability · Source |
| CVE-2024-46702 | suse_vex | SUSE CVE CVE-2024-46702 | known affected: 537 known not affected: 12 recommended: 715 | 2026-07-23T02:00:11+00:00 | Vulnerability · Source |