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-21886 | suse_vex | SUSE CVE CVE-2024-21886 | known affected: 438 known not affected: 22 recommended: 196 | 2026-10-16T02:21:23+00:00 | Vulnerability · Source |
| CVE-2024-21980 | suse_vex | SUSE CVE CVE-2024-21980 | No product status | 2026-10-16T02:21:21+00:00 | Vulnerability · Source |
| CVE-2024-22018 | suse_vex | SUSE CVE CVE-2024-22018 | known affected: 28 known not affected: 635 recommended: 93 | 2026-10-16T02:21:19+00:00 | Vulnerability · Source |
| CVE-2024-22020 | suse_vex | SUSE CVE CVE-2024-22020 | known affected: 341 known not affected: 12 recommended: 179 | 2026-10-16T02:21:17+00:00 | Vulnerability · Source |
| CVE-2024-22030 | suse_vex | SUSE CVE CVE-2024-22030 | recommended: 4 | 2026-10-16T02:21:15+00:00 | Vulnerability · Source |
| CVE-2024-22038 | suse_vex | SUSE CVE CVE-2024-22038 | first fixed: 1 known affected: 4 recommended: 96 | 2026-10-16T02:21:12+00:00 | Vulnerability · Source |
| CVE-2024-22099 | suse_vex | SUSE CVE CVE-2024-22099 | known affected: 455 known not affected: 6 recommended: 1072 | 2026-10-16T02:21:10+00:00 | Vulnerability · Source |
| CVE-2024-22211 | suse_vex | SUSE CVE CVE-2024-22211 | known affected: 30 recommended: 210 | 2026-10-16T02:21:08+00:00 | Vulnerability · Source |
| CVE-2024-22231 | suse_vex | SUSE CVE CVE-2024-22231 | known affected: 675 recommended: 439 | 2026-10-16T02:21:06+00:00 | Vulnerability · Source |
| CVE-2024-22232 | suse_vex | SUSE CVE CVE-2024-22232 | known affected: 675 recommended: 439 | 2026-10-16T02:21:04+00:00 | Vulnerability · Source |
| CVE-2024-22365 | suse_vex | SUSE CVE CVE-2024-22365 | known affected: 150 recommended: 304 | 2026-10-16T02:21:02+00:00 | Vulnerability · Source |
| CVE-2024-23184 | suse_vex | SUSE CVE CVE-2024-23184 | known affected: 72 known not affected: 45 recommended: 350 | 2026-10-16T02:21:00+00:00 | Vulnerability · Source |
| CVE-2024-23185 | suse_vex | SUSE CVE CVE-2024-23185 | known affected: 72 known not affected: 55 recommended: 350 | 2026-10-16T02:20:59+00:00 | Vulnerability · Source |
| CVE-2024-23222 | suse_vex | SUSE CVE CVE-2024-23222 | known affected: 43 known not affected: 131 recommended: 663 | 2026-10-16T02:20:57+00:00 | Vulnerability · Source |
| CVE-2024-23252 | suse_vex | SUSE CVE CVE-2024-23252 | known affected: 108 recommended: 663 | 2026-10-16T02:20:55+00:00 | Vulnerability · Source |
| CVE-2024-23254 | suse_vex | SUSE CVE CVE-2024-23254 | known affected: 63 recommended: 711 | 2026-10-16T02:20:53+00:00 | Vulnerability · Source |
| CVE-2024-23284 | suse_vex | SUSE CVE CVE-2024-23284 | known affected: 108 recommended: 663 | 2026-10-16T02:20:51+00:00 | Vulnerability · Source |
| CVE-2024-23307 | suse_vex | SUSE CVE CVE-2024-23307 | known affected: 342 known not affected: 63 recommended: 1101 | 2026-10-16T02:20:49+00:00 | Vulnerability · Source |
| CVE-2024-23331 | suse_vex | SUSE CVE CVE-2024-23331 | recommended: 22 | 2026-10-16T02:20:47+00:00 | Vulnerability · Source |
| CVE-2024-23334 | suse_vex | SUSE CVE CVE-2024-23334 | recommended: 29 | 2026-10-16T02:20:45+00:00 | Vulnerability · Source |
| CVE-2024-23337 | suse_vex | SUSE CVE CVE-2024-23337 | known affected: 430 recommended: 126 | 2026-10-16T02:20:44+00:00 | Vulnerability · Source |
| CVE-2024-23651 | suse_vex | SUSE CVE CVE-2024-23651 | known affected: 262 recommended: 375 | 2026-10-16T02:20:42+00:00 | Vulnerability · Source |
| CVE-2024-23653 | suse_vex | SUSE CVE CVE-2024-23653 | known affected: 259 recommended: 407 | 2026-10-16T02:20:40+00:00 | Vulnerability · Source |
| CVE-2024-23672 | suse_vex | SUSE CVE CVE-2024-23672 | known affected: 562 known not affected: 5 recommended: 745 | 2026-10-16T02:20:38+00:00 | Vulnerability · Source |
| CVE-2024-23829 | suse_vex | SUSE CVE CVE-2024-23829 | known affected: 16 recommended: 24 | 2026-10-16T02:20:36+00:00 | Vulnerability · Source |
| CVE-2024-23848 | suse_vex | SUSE CVE CVE-2024-23848 | known affected: 526 known not affected: 42 recommended: 905 | 2026-10-16T02:20:34+00:00 | Vulnerability · Source |
| CVE-2024-23849 | suse_vex | SUSE CVE CVE-2024-23849 | known affected: 424 known not affected: 95 recommended: 901 | 2026-10-16T02:20:32+00:00 | Vulnerability · Source |
| CVE-2024-23850 | suse_vex | SUSE CVE CVE-2024-23850 | known affected: 306 known not affected: 330 recommended: 685 | 2026-10-16T02:20:30+00:00 | Vulnerability · Source |
| CVE-2024-23851 | suse_vex | SUSE CVE CVE-2024-23851 | known affected: 563 known not affected: 83 recommended: 810 | 2026-10-16T02:20:28+00:00 | Vulnerability · Source |
| CVE-2024-23918 | suse_vex | SUSE CVE CVE-2024-23918 | known affected: 19 recommended: 48 | 2026-10-16T02:20:26+00:00 | Vulnerability · Source |
| CVE-2024-23981 | suse_vex | SUSE CVE CVE-2024-23981 | known not affected: 372 | 2026-10-16T02:20:24+00:00 | Vulnerability · Source |
| CVE-2024-24425 | suse_vex | SUSE CVE CVE-2024-24425 | recommended: 4 | 2026-10-16T02:20:23+00:00 | Vulnerability · Source |
| CVE-2024-24557 | suse_vex | SUSE CVE CVE-2024-24557 | known not affected: 185 recommended: 4 | 2026-10-16T02:20:21+00:00 | Vulnerability · Source |
| CVE-2024-24575 | suse_vex | SUSE CVE CVE-2024-24575 | known affected: 16 known not affected: 743 recommended: 36 | 2026-10-16T02:20:19+00:00 | Vulnerability · Source |
| CVE-2024-24784 | suse_vex | SUSE CVE CVE-2024-24784 | recommended: 237 | 2026-10-16T02:20:17+00:00 | Vulnerability · Source |
| CVE-2024-24787 | suse_vex | SUSE CVE CVE-2024-24787 | known not affected: 163 recommended: 170 | 2026-10-16T02:20:15+00:00 | Vulnerability · Source |
| CVE-2024-24788 | suse_vex | SUSE CVE CVE-2024-24788 | known not affected: 57 recommended: 134 | 2026-10-16T02:20:13+00:00 | Vulnerability · Source |
| CVE-2024-24790 | suse_vex | SUSE CVE CVE-2024-24790 | known affected: 386 known not affected: 62 recommended: 313 | 2026-10-16T02:20:11+00:00 | Vulnerability · Source |
| CVE-2024-24795 | suse_vex | SUSE CVE CVE-2024-24795 | known affected: 480 recommended: 459 | 2026-10-16T02:20:08+00:00 | Vulnerability · Source |
| CVE-2024-24826 | suse_vex | SUSE CVE CVE-2024-24826 | known not affected: 159 recommended: 16 | 2026-10-16T02:20:06+00:00 | Vulnerability · Source |
| CVE-2024-24853 | suse_vex | SUSE CVE CVE-2024-24853 | known affected: 17 recommended: 63 | 2026-10-16T02:20:05+00:00 | Vulnerability · Source |
| CVE-2024-24855 | suse_vex | SUSE CVE CVE-2024-24855 | known affected: 394 known not affected: 588 recommended: 70 | 2026-10-16T02:20:03+00:00 | Vulnerability · Source |
| CVE-2024-24857 | suse_vex | SUSE CVE CVE-2024-24857 | known not affected: 313 recommended: 20 | 2026-10-16T02:20:01+00:00 | Vulnerability · Source |
| CVE-2024-24858 | suse_vex | SUSE CVE CVE-2024-24858 | known not affected: 426 | 2026-10-16T02:19:59+00:00 | Vulnerability · Source |
| CVE-2024-24859 | suse_vex | SUSE CVE CVE-2024-24859 | known not affected: 458 | 2026-10-16T02:19:58+00:00 | Vulnerability · Source |
| CVE-2024-24860 | suse_vex | SUSE CVE CVE-2024-24860 | known affected: 330 known not affected: 224 recommended: 701 | 2026-10-16T02:19:56+00:00 | Vulnerability · Source |
| CVE-2024-24864 | suse_vex | SUSE CVE CVE-2024-24864 | known affected: 101 | 2026-10-16T02:19:54+00:00 | Vulnerability · Source |
| CVE-2024-24986 | suse_vex | SUSE CVE CVE-2024-24986 | known not affected: 372 | 2026-10-16T02:19:52+00:00 | Vulnerability · Source |
| CVE-2024-24990 | suse_vex | SUSE CVE CVE-2024-24990 | known not affected: 66 recommended: 6 | 2026-10-16T02:19:50+00:00 | Vulnerability · Source |
| CVE-2024-25062 | suse_vex | SUSE CVE CVE-2024-25062 | known affected: 474 known not affected: 87 recommended: 419 | 2026-10-16T02:19:48+00:00 | Vulnerability · Source |