VEX records
Browse vendor VEX statements available in this Vulnerability-Lookup instance and pivot to the related vulnerability.
292102 VEX records
API response| Vulnerability | Source | Title | Product status | Imported | Links |
|---|---|---|---|---|---|
| CVE-2024-49997 | suse_vex | SUSE CVE CVE-2024-49997 | known not affected: 462 recommended: 6 | 2026-07-25T01:30:29+00:00 | Vulnerability · Source |
| CVE-2024-49998 | suse_vex | SUSE CVE CVE-2024-49998 | known affected: 489 known not affected: 294 recommended: 316 | 2026-07-25T01:30:28+00:00 | Vulnerability · Source |
| CVE-2024-50003 | suse_vex | SUSE CVE CVE-2024-50003 | known affected: 365 known not affected: 309 recommended: 638 | 2026-07-25T01:30:19+00:00 | Vulnerability · Source |
| CVE-2024-50011 | suse_vex | SUSE CVE CVE-2024-50011 | known not affected: 379 recommended: 65 | 2026-07-25T01:30:08+00:00 | Vulnerability · Source |
| CVE-2024-50016 | suse_vex | SUSE CVE CVE-2024-50016 | known affected: 398 known not affected: 394 recommended: 316 | 2026-07-25T01:29:57+00:00 | Vulnerability · Source |
| CVE-2024-50018 | suse_vex | SUSE CVE CVE-2024-50018 | known affected: 354 recommended: 469 | 2026-07-25T01:29:53+00:00 | Vulnerability · Source |
| CVE-2024-50021 | suse_vex | SUSE CVE CVE-2024-50021 | known affected: 398 known not affected: 373 recommended: 372 | 2026-07-25T01:29:47+00:00 | Vulnerability · Source |
| CVE-2024-50023 | suse_vex | SUSE CVE CVE-2024-50023 | known affected: 394 known not affected: 321 recommended: 415 | 2026-07-25T01:29:43+00:00 | Vulnerability · Source |
| CVE-2024-50025 | suse_vex | SUSE CVE CVE-2024-50025 | known affected: 354 known not affected: 263 recommended: 641 | 2026-07-25T01:29:39+00:00 | Vulnerability · Source |
| CVE-2024-50026 | suse_vex | SUSE CVE CVE-2024-50026 | known affected: 365 known not affected: 294 recommended: 585 | 2026-07-25T01:29:36+00:00 | Vulnerability · Source |
| CVE-2024-50027 | suse_vex | SUSE CVE CVE-2024-50027 | known affected: 398 known not affected: 373 recommended: 415 | 2026-07-25T01:29:34+00:00 | Vulnerability · Source |
| CVE-2024-50029 | suse_vex | SUSE CVE CVE-2024-50029 | known affected: 410 known not affected: 373 recommended: 359 | 2026-07-25T01:29:32+00:00 | Vulnerability · Source |
| CVE-2024-50035 | suse_vex | SUSE CVE CVE-2024-50035 | known affected: 602 known not affected: 36 recommended: 726 | 2026-07-25T01:29:28+00:00 | Vulnerability · Source |
| CVE-2024-50039 | suse_vex | SUSE CVE CVE-2024-50039 | known affected: 671 known not affected: 36 recommended: 399 | 2026-07-25T01:29:25+00:00 | Vulnerability · Source |
| CVE-2024-50044 | suse_vex | SUSE CVE CVE-2024-50044 | known affected: 577 known not affected: 11 recommended: 724 | 2026-07-25T01:29:20+00:00 | Vulnerability · Source |
| CVE-2024-50049 | suse_vex | SUSE CVE CVE-2024-50049 | known affected: 459 known not affected: 158 recommended: 643 | 2026-07-25T01:29:12+00:00 | Vulnerability · Source |
| CVE-2024-50056 | suse_vex | SUSE CVE CVE-2024-50056 | known affected: 410 known not affected: 360 recommended: 348 | 2026-07-25T01:29:08+00:00 | Vulnerability · Source |
| CVE-2024-50064 | suse_vex | SUSE CVE CVE-2024-50064 | known affected: 398 known not affected: 373 recommended: 415 | 2026-07-25T01:28:59+00:00 | Vulnerability · Source |
| CVE-2024-50068 | suse_vex | SUSE CVE CVE-2024-50068 | known not affected: 379 recommended: 6 | 2026-07-25T01:28:57+00:00 | Vulnerability · Source |
| CVE-2024-50074 | suse_vex | SUSE CVE CVE-2024-50074 | known affected: 453 known not affected: 152 recommended: 724 | 2026-07-25T01:28:55+00:00 | Vulnerability · Source |
| CVE-2024-50079 | suse_vex | SUSE CVE CVE-2024-50079 | known not affected: 402 recommended: 65 | 2026-07-25T01:28:48+00:00 | Vulnerability · Source |
| CVE-2024-50084 | suse_vex | SUSE CVE CVE-2024-50084 | known affected: 394 known not affected: 336 recommended: 369 | 2026-07-25T01:28:42+00:00 | Vulnerability · Source |
| CVE-2024-50085 | suse_vex | SUSE CVE CVE-2024-50085 | known affected: 394 known not affected: 321 recommended: 316 | 2026-07-25T01:28:41+00:00 | Vulnerability · Source |
| CVE-2024-50087 | suse_vex | SUSE CVE CVE-2024-50087 | known affected: 398 known not affected: 373 recommended: 369 | 2026-07-25T01:28:39+00:00 | Vulnerability · Source |
| CVE-2024-50090 | suse_vex | SUSE CVE CVE-2024-50090 | known not affected: 370 recommended: 65 | 2026-07-25T01:28:35+00:00 | Vulnerability · Source |
| CVE-2024-50091 | suse_vex | SUSE CVE CVE-2024-50091 | known not affected: 370 recommended: 6 | 2026-07-25T01:28:34+00:00 | Vulnerability · Source |
| CVE-2024-50095 | suse_vex | SUSE CVE CVE-2024-50095 | known affected: 583 known not affected: 56 recommended: 625 | 2026-07-25T01:28:32+00:00 | Vulnerability · Source |
| CVE-2024-50096 | suse_vex | SUSE CVE CVE-2024-50096 | known affected: 479 known not affected: 129 recommended: 585 | 2026-07-25T01:28:31+00:00 | Vulnerability · Source |
| CVE-2024-50099 | suse_vex | SUSE CVE CVE-2024-50099 | known affected: 509 known not affected: 65 recommended: 631 | 2026-07-25T01:28:28+00:00 | Vulnerability · Source |
| CVE-2024-50100 | suse_vex | SUSE CVE CVE-2024-50100 | known affected: 394 known not affected: 312 recommended: 316 | 2026-07-25T01:28:27+00:00 | Vulnerability · Source |
| CVE-2024-50101 | suse_vex | SUSE CVE CVE-2024-50101 | known affected: 394 known not affected: 312 recommended: 359 | 2026-07-25T01:28:25+00:00 | Vulnerability · Source |
| CVE-2024-50102 | suse_vex | SUSE CVE CVE-2024-50102 | known affected: 394 known not affected: 312 recommended: 359 | 2026-07-25T01:28:24+00:00 | Vulnerability · Source |
| CVE-2024-50103 | suse_vex | SUSE CVE CVE-2024-50103 | known affected: 415 known not affected: 193 recommended: 585 | 2026-07-25T01:28:22+00:00 | Vulnerability · Source |
| CVE-2024-50105 | suse_vex | SUSE CVE CVE-2024-50105 | known not affected: 370 recommended: 65 | 2026-07-25T01:28:21+00:00 | Vulnerability · Source |
| CVE-2024-50108 | suse_vex | SUSE CVE CVE-2024-50108 | known affected: 354 known not affected: 254 recommended: 585 | 2026-07-25T01:28:19+00:00 | Vulnerability · Source |
| CVE-2024-50110 | suse_vex | SUSE CVE CVE-2024-50110 | known affected: 450 known not affected: 224 recommended: 605 | 2026-07-25T01:28:18+00:00 | Vulnerability · Source |
| CVE-2024-50114 | suse_vex | SUSE CVE CVE-2024-50114 | known not affected: 370 recommended: 6 | 2026-07-25T01:28:16+00:00 | Vulnerability · Source |
| CVE-2024-50116 | suse_vex | SUSE CVE CVE-2024-50116 | known affected: 354 known not affected: 156 recommended: 585 | 2026-07-25T01:28:13+00:00 | Vulnerability · Source |
| CVE-2024-50117 | suse_vex | SUSE CVE CVE-2024-50117 | known affected: 577 known not affected: 62 recommended: 668 | 2026-07-25T01:28:11+00:00 | Vulnerability · Source |
| CVE-2024-50119 | suse_vex | SUSE CVE CVE-2024-50119 | known not affected: 370 recommended: 6 | 2026-07-25T01:28:10+00:00 | Vulnerability · Source |
| CVE-2024-50123 | suse_vex | SUSE CVE CVE-2024-50123 | known not affected: 370 recommended: 6 | 2026-07-25T01:28:07+00:00 | Vulnerability · Source |
| CVE-2024-50124 | suse_vex | SUSE CVE CVE-2024-50124 | known affected: 374 known not affected: 300 recommended: 609 | 2026-07-25T01:28:05+00:00 | Vulnerability · Source |
| CVE-2024-50125 | suse_vex | SUSE CVE CVE-2024-50125 | known affected: 437 known not affected: 42 recommended: 921 | 2026-07-25T01:28:04+00:00 | Vulnerability · Source |
| CVE-2024-50131 | suse_vex | SUSE CVE CVE-2024-50131 | known affected: 479 known not affected: 129 recommended: 585 | 2026-07-25T01:27:58+00:00 | Vulnerability · Source |
| CVE-2024-50132 | suse_vex | SUSE CVE CVE-2024-50132 | known not affected: 370 recommended: 6 | 2026-07-25T01:27:56+00:00 | Vulnerability · Source |
| CVE-2024-50134 | suse_vex | SUSE CVE CVE-2024-50134 | known affected: 486 known not affected: 122 recommended: 585 | 2026-07-25T01:27:55+00:00 | Vulnerability · Source |
| CVE-2024-50135 | suse_vex | SUSE CVE CVE-2024-50135 | known affected: 584 known not affected: 55 recommended: 625 | 2026-07-25T01:27:53+00:00 | Vulnerability · Source |
| CVE-2024-50138 | suse_vex | SUSE CVE CVE-2024-50138 | known affected: 504 known not affected: 187 recommended: 585 | 2026-07-25T01:27:51+00:00 | Vulnerability · Source |
| CVE-2024-50139 | suse_vex | SUSE CVE CVE-2024-50139 | known affected: 398 known not affected: 369 recommended: 369 | 2026-07-25T01:27:49+00:00 | Vulnerability · Source |
| CVE-2024-50140 | suse_vex | SUSE CVE CVE-2024-50140 | known affected: 410 known not affected: 337 recommended: 348 | 2026-07-25T01:27:48+00:00 | Vulnerability · Source |