VEX records
Browse vendor VEX statements available in this Vulnerability-Lookup instance and pivot to the related vulnerability.
292098 VEX records
API response| Vulnerability | Source | Title | Product status | Imported | Links |
|---|---|---|---|---|---|
| CVE-2024-41021 | suse_vex | SUSE CVE CVE-2024-41021 | known not affected: 324 | 2026-07-25T01:44:36+00:00 | Vulnerability · Source |
| CVE-2024-41027 | suse_vex | SUSE CVE CVE-2024-41027 | known affected: 155 known not affected: 192 | 2026-07-25T01:44:31+00:00 | Vulnerability · Source |
| CVE-2024-41034 | suse_vex | SUSE CVE CVE-2024-41034 | known not affected: 217 | 2026-07-25T01:44:27+00:00 | Vulnerability · Source |
| CVE-2024-41043 | suse_vex | SUSE CVE CVE-2024-41043 | known not affected: 324 | 2026-07-25T01:44:24+00:00 | Vulnerability · Source |
| CVE-2024-41046 | suse_vex | SUSE CVE CVE-2024-41046 | known not affected: 324 | 2026-07-25T01:44:21+00:00 | Vulnerability · Source |
| CVE-2024-41050 | suse_vex | SUSE CVE CVE-2024-41050 | known affected: 471 known not affected: 237 recommended: 360 | 2026-07-25T01:44:16+00:00 | Vulnerability · Source |
| CVE-2024-41055 | suse_vex | SUSE CVE CVE-2024-41055 | known affected: 394 known not affected: 258 recommended: 359 | 2026-07-25T01:44:14+00:00 | Vulnerability · Source |
| CVE-2024-41063 | suse_vex | SUSE CVE CVE-2024-41063 | known affected: 450 known not affected: 6 recommended: 742 | 2026-07-25T01:44:09+00:00 | Vulnerability · Source |
| CVE-2024-41066 | suse_vex | SUSE CVE CVE-2024-41066 | known affected: 453 known not affected: 6 recommended: 762 | 2026-07-25T01:44:06+00:00 | Vulnerability · Source |
| CVE-2024-41067 | suse_vex | SUSE CVE CVE-2024-41067 | known not affected: 324 | 2026-07-25T01:44:04+00:00 | Vulnerability · Source |
| CVE-2024-41077 | suse_vex | SUSE CVE CVE-2024-41077 | known affected: 394 known not affected: 46 recommended: 309 | 2026-07-25T01:43:59+00:00 | Vulnerability · Source |
| CVE-2024-41081 | suse_vex | SUSE CVE CVE-2024-41081 | known affected: 514 known not affected: 10 recommended: 728 | 2026-07-25T01:43:54+00:00 | Vulnerability · Source |
| CVE-2024-41085 | suse_vex | SUSE CVE CVE-2024-41085 | known affected: 404 known not affected: 550 recommended: 111 | 2026-07-25T01:43:50+00:00 | Vulnerability · Source |
| CVE-2024-41087 | suse_vex | SUSE CVE CVE-2024-41087 | known affected: 353 known not affected: 30 recommended: 988 | 2026-07-25T01:43:47+00:00 | Vulnerability · Source |
| CVE-2024-41817 | suse_vex | SUSE CVE CVE-2024-41817 | known not affected: 393 | 2026-07-25T01:43:38+00:00 | Vulnerability · Source |
| CVE-2024-41957 | suse_vex | SUSE CVE CVE-2024-41957 | known not affected: 251 | 2026-07-25T01:43:36+00:00 | Vulnerability · Source |
| CVE-2024-42065 | suse_vex | SUSE CVE CVE-2024-42065 | known not affected: 324 recommended: 59 | 2026-07-25T01:43:31+00:00 | Vulnerability · Source |
| CVE-2024-42071 | suse_vex | SUSE CVE CVE-2024-42071 | known not affected: 324 recommended: 59 | 2026-07-25T01:43:27+00:00 | Vulnerability · Source |
| CVE-2024-42093 | suse_vex | SUSE CVE CVE-2024-42093 | known affected: 365 known not affected: 65 recommended: 856 | 2026-07-25T01:43:23+00:00 | Vulnerability · Source |
| CVE-2024-42096 | suse_vex | SUSE CVE CVE-2024-42096 | known affected: 524 recommended: 791 | 2026-07-25T01:43:21+00:00 | Vulnerability · Source |
| CVE-2024-42100 | suse_vex | SUSE CVE CVE-2024-42100 | known not affected: 324 | 2026-07-25T01:43:17+00:00 | Vulnerability · Source |
| CVE-2024-42103 | suse_vex | SUSE CVE CVE-2024-42103 | known affected: 394 known not affected: 301 recommended: 230 | 2026-07-25T01:43:13+00:00 | Vulnerability · Source |
| CVE-2024-42114 | suse_vex | SUSE CVE CVE-2024-42114 | known affected: 524 known not affected: 58 recommended: 694 | 2026-07-25T01:43:08+00:00 | Vulnerability · Source |
| CVE-2024-42116 | suse_vex | SUSE CVE CVE-2024-42116 | known not affected: 324 | 2026-07-25T01:43:06+00:00 | Vulnerability · Source |
| CVE-2024-42127 | suse_vex | SUSE CVE CVE-2024-42127 | known affected: 340 known not affected: 204 recommended: 648 | 2026-07-25T01:43:01+00:00 | Vulnerability · Source |
| CVE-2024-42132 | suse_vex | SUSE CVE CVE-2024-42132 | known affected: 394 known not affected: 264 recommended: 360 | 2026-07-25T01:43:00+00:00 | Vulnerability · Source |
| CVE-2024-42133 | suse_vex | SUSE CVE CVE-2024-42133 | known affected: 394 known not affected: 264 recommended: 410 | 2026-07-25T01:42:58+00:00 | Vulnerability · Source |
| CVE-2024-42135 | suse_vex | SUSE CVE CVE-2024-42135 | known not affected: 324 | 2026-07-25T01:42:56+00:00 | Vulnerability · Source |
| CVE-2024-42140 | suse_vex | SUSE CVE CVE-2024-42140 | known not affected: 327 | 2026-07-25T01:42:53+00:00 | Vulnerability · Source |
| CVE-2024-42141 | suse_vex | SUSE CVE CVE-2024-42141 | known affected: 394 known not affected: 264 recommended: 360 | 2026-07-25T01:42:51+00:00 | Vulnerability · Source |
| CVE-2024-42154 | suse_vex | SUSE CVE CVE-2024-42154 | known affected: 543 known not affected: 38 recommended: 749 | 2026-07-25T01:42:45+00:00 | Vulnerability · Source |
| CVE-2024-42225 | suse_vex | SUSE CVE CVE-2024-42225 | known affected: 372 known not affected: 115 recommended: 697 | 2026-07-25T01:42:42+00:00 | Vulnerability · Source |
| CVE-2024-42229 | suse_vex | SUSE CVE CVE-2024-42229 | known affected: 542 recommended: 811 | 2026-07-25T01:42:39+00:00 | Vulnerability · Source |
| CVE-2024-42231 | suse_vex | SUSE CVE CVE-2024-42231 | known not affected: 324 | 2026-07-25T01:42:36+00:00 | Vulnerability · Source |
| CVE-2024-42234 | suse_vex | SUSE CVE CVE-2024-42234 | known not affected: 311 | 2026-07-25T01:42:34+00:00 | Vulnerability · Source |
| CVE-2024-42249 | suse_vex | SUSE CVE CVE-2024-42249 | known not affected: 310 | 2026-07-25T01:42:30+00:00 | Vulnerability · Source |
| CVE-2024-42268 | suse_vex | SUSE CVE CVE-2024-42268 | known affected: 340 known not affected: 211 recommended: 648 | 2026-07-25T01:42:28+00:00 | Vulnerability · Source |
| CVE-2024-42275 | suse_vex | SUSE CVE CVE-2024-42275 | known not affected: 311 recommended: 59 | 2026-07-25T01:42:22+00:00 | Vulnerability · Source |
| CVE-2024-42294 | suse_vex | SUSE CVE CVE-2024-42294 | known affected: 394 known not affected: 339 recommended: 392 | 2026-07-25T01:42:17+00:00 | Vulnerability · Source |
| CVE-2024-42299 | suse_vex | SUSE CVE CVE-2024-42299 | known not affected: 513 | 2026-07-25T01:42:15+00:00 | Vulnerability · Source |
| CVE-2024-42305 | suse_vex | SUSE CVE CVE-2024-42305 | known affected: 537 known not affected: 32 recommended: 764 | 2026-07-25T01:42:14+00:00 | Vulnerability · Source |
| CVE-2024-42307 | suse_vex | SUSE CVE CVE-2024-42307 | known affected: 369 known not affected: 227 recommended: 404 | 2026-07-25T01:42:10+00:00 | Vulnerability · Source |
| CVE-2024-42312 | suse_vex | SUSE CVE CVE-2024-42312 | known affected: 465 known not affected: 57 recommended: 761 | 2026-07-25T01:42:09+00:00 | Vulnerability · Source |
| CVE-2024-42316 | suse_vex | SUSE CVE CVE-2024-42316 | known affected: 394 known not affected: 280 recommended: 403 | 2026-07-25T01:42:05+00:00 | Vulnerability · Source |
| CVE-2024-42322 | suse_vex | SUSE CVE CVE-2024-42322 | known affected: 512 known not affected: 10 recommended: 782 | 2026-07-25T01:42:02+00:00 | Vulnerability · Source |
| CVE-2024-42326 | suse_vex | SUSE CVE CVE-2024-42326 | known not affected: 12 | 2026-07-25T01:42:01+00:00 | Vulnerability · Source |
| CVE-2024-42330 | suse_vex | SUSE CVE CVE-2024-42330 | known not affected: 12 | 2026-07-25T01:42:00+00:00 | Vulnerability · Source |
| CVE-2024-42331 | suse_vex | SUSE CVE CVE-2024-42331 | known not affected: 12 | 2026-07-25T01:41:59+00:00 | Vulnerability · Source |
| CVE-2024-42333 | suse_vex | SUSE CVE CVE-2024-42333 | known affected: 10 recommended: 3 | 2026-07-25T01:41:57+00:00 | Vulnerability · Source |
| CVE-2024-42415 | suse_vex | SUSE CVE CVE-2024-42415 | known affected: 37 recommended: 94 | 2026-07-25T01:41:56+00:00 | Vulnerability · Source |