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-43893 | suse_vex | SUSE CVE CVE-2024-43893 | known affected: 519 known not affected: 6 recommended: 727 | 2026-10-16T01:44:45+00:00 | Vulnerability · Source |
| CVE-2024-43895 | suse_vex | SUSE CVE CVE-2024-43895 | known affected: 340 known not affected: 261 recommended: 643 | 2026-10-16T01:44:43+00:00 | Vulnerability · Source |
| CVE-2024-43897 | suse_vex | SUSE CVE CVE-2024-43897 | known affected: 354 known not affected: 260 recommended: 624 | 2026-10-16T01:44:41+00:00 | Vulnerability · Source |
| CVE-2024-43898 | suse_vex | SUSE CVE CVE-2024-43898 | known affected: 340 known not affected: 239 recommended: 802 | 2026-10-16T01:44:39+00:00 | Vulnerability · Source |
| CVE-2024-43900 | suse_vex | SUSE CVE CVE-2024-43900 | known affected: 584 known not affected: 18 recommended: 727 | 2026-10-16T01:44:36+00:00 | Vulnerability · Source |
| CVE-2024-43902 | suse_vex | SUSE CVE CVE-2024-43902 | known affected: 468 known not affected: 48 recommended: 713 | 2026-10-16T01:44:34+00:00 | Vulnerability · Source |
| CVE-2024-43903 | suse_vex | SUSE CVE CVE-2024-43903 | known affected: 340 known not affected: 212 recommended: 643 | 2026-10-16T01:44:32+00:00 | Vulnerability · Source |
| CVE-2024-43907 | suse_vex | SUSE CVE CVE-2024-43907 | known affected: 496 known not affected: 20 recommended: 713 | 2026-10-16T01:44:30+00:00 | Vulnerability · Source |
| CVE-2024-43908 | suse_vex | SUSE CVE CVE-2024-43908 | known affected: 401 known not affected: 136 recommended: 643 | 2026-10-16T01:44:28+00:00 | Vulnerability · Source |
| CVE-2024-43909 | suse_vex | SUSE CVE CVE-2024-43909 | known affected: 612 known not affected: 26 recommended: 643 | 2026-10-16T01:44:27+00:00 | Vulnerability · Source |
| CVE-2024-43910 | suse_vex | SUSE CVE CVE-2024-43910 | known not affected: 400 recommended: 86 | 2026-10-16T01:44:25+00:00 | Vulnerability · Source |
| CVE-2024-43911 | suse_vex | SUSE CVE CVE-2024-43911 | known affected: 394 known not affected: 376 recommended: 355 | 2026-10-16T01:44:23+00:00 | Vulnerability · Source |
| CVE-2024-43912 | suse_vex | SUSE CVE CVE-2024-43912 | known affected: 528 known not affected: 6 recommended: 727 | 2026-10-16T01:44:21+00:00 | Vulnerability · Source |
| CVE-2024-44070 | suse_vex | SUSE CVE CVE-2024-44070 | known affected: 21 recommended: 504 | 2026-10-16T01:44:19+00:00 | Vulnerability · Source |
| CVE-2024-44187 | suse_vex | SUSE CVE CVE-2024-44187 | known affected: 167 recommended: 741 | 2026-10-16T01:44:17+00:00 | Vulnerability · Source |
| CVE-2024-44296 | suse_vex | SUSE CVE CVE-2024-44296 | known affected: 201 known not affected: 113 recommended: 650 | 2026-10-16T01:44:15+00:00 | Vulnerability · Source |
| CVE-2024-44309 | suse_vex | SUSE CVE CVE-2024-44309 | known affected: 200 recommended: 741 | 2026-10-16T01:44:13+00:00 | Vulnerability · Source |
| CVE-2024-44625 | suse_vex | SUSE CVE CVE-2024-44625 | recommended: 4 | 2026-10-16T01:44:11+00:00 | Vulnerability · Source |
| CVE-2024-44905 | suse_vex | SUSE CVE CVE-2024-44905 | recommended: 5 | 2026-10-16T01:44:10+00:00 | Vulnerability · Source |
| CVE-2024-44906 | suse_vex | SUSE CVE CVE-2024-44906 | recommended: 5 | 2026-10-16T01:44:08+00:00 | Vulnerability · Source |
| CVE-2024-44934 | suse_vex | SUSE CVE CVE-2024-44934 | known affected: 498 known not affected: 257 recommended: 476 | 2026-10-16T01:44:06+00:00 | Vulnerability · Source |
| CVE-2024-44935 | suse_vex | SUSE CVE CVE-2024-44935 | known affected: 492 known not affected: 172 recommended: 652 | 2026-10-16T01:44:04+00:00 | Vulnerability · Source |
| CVE-2024-44939 | suse_vex | SUSE CVE CVE-2024-44939 | known affected: 456 known not affected: 218 recommended: 643 | 2026-10-16T01:44:02+00:00 | Vulnerability · Source |
| CVE-2024-44940 | suse_vex | SUSE CVE CVE-2024-44940 | known not affected: 6 | 2026-10-16T01:44:00+00:00 | Vulnerability · Source |
| CVE-2024-44941 | suse_vex | SUSE CVE CVE-2024-44941 | known not affected: 400 | 2026-10-16T01:43:59+00:00 | Vulnerability · Source |
| CVE-2024-44944 | suse_vex | SUSE CVE CVE-2024-44944 | known affected: 486 known not affected: 183 recommended: 632 | 2026-10-16T01:43:57+00:00 | Vulnerability · Source |
| CVE-2024-44947 | suse_vex | SUSE CVE CVE-2024-44947 | known affected: 439 known not affected: 6 recommended: 1016 | 2026-10-16T01:43:55+00:00 | Vulnerability · Source |
| CVE-2024-44948 | suse_vex | SUSE CVE CVE-2024-44948 | known affected: 624 known not affected: 15 recommended: 724 | 2026-10-16T01:43:53+00:00 | Vulnerability · Source |
| CVE-2024-44950 | suse_vex | SUSE CVE CVE-2024-44950 | known affected: 627 known not affected: 35 recommended: 716 | 2026-10-16T01:43:51+00:00 | Vulnerability · Source |
| CVE-2024-44956 | suse_vex | SUSE CVE CVE-2024-44956 | known not affected: 399 recommended: 47 | 2026-10-16T01:43:49+00:00 | Vulnerability · Source |
| CVE-2024-44960 | suse_vex | SUSE CVE CVE-2024-44960 | known affected: 394 recommended: 352 | 2026-10-16T01:43:47+00:00 | Vulnerability · Source |
| CVE-2024-44961 | suse_vex | SUSE CVE CVE-2024-44961 | known affected: 394 known not affected: 350 recommended: 352 | 2026-10-16T01:43:45+00:00 | Vulnerability · Source |
| CVE-2024-44963 | suse_vex | SUSE CVE CVE-2024-44963 | known affected: 823 recommended: 355 | 2026-10-16T01:43:44+00:00 | Vulnerability · Source |
| CVE-2024-44964 | suse_vex | SUSE CVE CVE-2024-44964 | known affected: 344 known not affected: 285 recommended: 839 | 2026-10-16T01:43:41+00:00 | Vulnerability · Source |
| CVE-2024-44965 | suse_vex | SUSE CVE CVE-2024-44965 | known affected: 394 known not affected: 350 recommended: 352 | 2026-10-16T01:43:39+00:00 | Vulnerability · Source |
| CVE-2024-44966 | suse_vex | SUSE CVE CVE-2024-44966 | known not affected: 399 | 2026-10-16T01:43:38+00:00 | Vulnerability · Source |
| CVE-2024-44967 | suse_vex | SUSE CVE CVE-2024-44967 | known affected: 340 known not affected: 288 recommended: 640 | 2026-10-16T01:43:36+00:00 | Vulnerability · Source |
| CVE-2024-44968 | suse_vex | SUSE CVE CVE-2024-44968 | known not affected: 399 | 2026-10-16T01:43:34+00:00 | Vulnerability · Source |
| CVE-2024-44969 | suse_vex | SUSE CVE CVE-2024-44969 | known affected: 483 known not affected: 156 recommended: 710 | 2026-10-16T01:43:32+00:00 | Vulnerability · Source |
| CVE-2024-44970 | suse_vex | SUSE CVE CVE-2024-44970 | known affected: 340 known not affected: 353 recommended: 660 | 2026-10-16T01:43:30+00:00 | Vulnerability · Source |
| CVE-2024-44971 | suse_vex | SUSE CVE CVE-2024-44971 | known affected: 410 known not affected: 282 recommended: 640 | 2026-10-16T01:43:28+00:00 | Vulnerability · Source |
| CVE-2024-44977 | suse_vex | SUSE CVE CVE-2024-44977 | known affected: 340 known not affected: 289 recommended: 640 | 2026-10-16T01:43:26+00:00 | Vulnerability · Source |
| CVE-2024-44978 | suse_vex | SUSE CVE CVE-2024-44978 | known not affected: 400 recommended: 47 | 2026-10-16T01:43:24+00:00 | Vulnerability · Source |
| CVE-2024-44979 | suse_vex | SUSE CVE CVE-2024-44979 | known not affected: 399 recommended: 47 | 2026-10-16T01:43:22+00:00 | Vulnerability · Source |
| CVE-2024-44981 | suse_vex | SUSE CVE CVE-2024-44981 | known affected: 394 known not affected: 376 recommended: 138 | 2026-10-16T01:43:20+00:00 | Vulnerability · Source |
| CVE-2024-44982 | suse_vex | SUSE CVE CVE-2024-44982 | known affected: 522 known not affected: 117 recommended: 710 | 2026-10-16T01:43:18+00:00 | Vulnerability · Source |
| CVE-2024-44983 | suse_vex | SUSE CVE CVE-2024-44983 | known affected: 63 known not affected: 264 | 2026-10-16T01:43:17+00:00 | Vulnerability · Source |
| CVE-2024-44985 | suse_vex | SUSE CVE CVE-2024-44985 | known affected: 394 known not affected: 432 recommended: 344 | 2026-10-16T01:43:15+00:00 | Vulnerability · Source |
| CVE-2024-44987 | suse_vex | SUSE CVE CVE-2024-44987 | known affected: 540 known not affected: 87 recommended: 899 | 2026-10-16T01:43:12+00:00 | Vulnerability · Source |
| CVE-2024-44989 | suse_vex | SUSE CVE CVE-2024-44989 | known affected: 453 known not affected: 239 recommended: 746 | 2026-10-16T01:43:10+00:00 | Vulnerability · Source |