VEX records
Browse vendor VEX statements available in this Vulnerability-Lookup instance and pivot to the related vulnerability.
292114 VEX records
API response| Vulnerability | Source | Title | Product status | Imported | Links |
|---|---|---|---|---|---|
| CVE-2023-53609 | suse_vex | SUSE CVE CVE-2023-53609 | known not affected: 416 recommended: 29 | 2026-07-25T16:58:48+00:00 | Vulnerability · Source |
| CVE-2023-53610 | suse_vex | SUSE CVE CVE-2023-53610 | known affected: 55 known not affected: 361 | 2026-07-25T16:58:47+00:00 | Vulnerability · Source |
| CVE-2023-53641 | suse_vex | SUSE CVE CVE-2023-53641 | known affected: 478 known not affected: 176 recommended: 268 | 2026-07-25T16:58:45+00:00 | Vulnerability · Source |
| CVE-2023-53643 | suse_vex | SUSE CVE CVE-2023-53643 | known not affected: 416 recommended: 29 | 2026-07-25T16:58:44+00:00 | Vulnerability · Source |
| CVE-2023-53692 | suse_vex | SUSE CVE CVE-2023-53692 | known affected: 354 known not affected: 295 recommended: 196 | 2026-07-25T16:58:42+00:00 | Vulnerability · Source |
| CVE-2023-53745 | suse_vex | SUSE CVE CVE-2023-53745 | known affected: 161 known not affected: 247 | 2026-07-25T16:58:40+00:00 | Vulnerability · Source |
| CVE-2023-53749 | suse_vex | SUSE CVE CVE-2023-53749 | known not affected: 453 | 2026-07-25T16:58:39+00:00 | Vulnerability · Source |
| CVE-2023-53755 | suse_vex | SUSE CVE CVE-2023-53755 | known affected: 354 known not affected: 296 recommended: 245 | 2026-07-25T16:58:37+00:00 | Vulnerability · Source |
| CVE-2023-53789 | suse_vex | SUSE CVE CVE-2023-53789 | known affected: 57 known not affected: 357 recommended: 29 | 2026-07-25T16:58:35+00:00 | Vulnerability · Source |
| CVE-2023-53811 | suse_vex | SUSE CVE CVE-2023-53811 | known affected: 354 known not affected: 296 recommended: 243 | 2026-07-25T16:58:34+00:00 | Vulnerability · Source |
| CVE-2023-53814 | suse_vex | SUSE CVE CVE-2023-53814 | known affected: 354 known not affected: 296 recommended: 225 | 2026-07-25T16:58:32+00:00 | Vulnerability · Source |
| CVE-2023-53830 | suse_vex | SUSE CVE CVE-2023-53830 | known affected: 354 known not affected: 296 recommended: 196 | 2026-07-25T16:58:31+00:00 | Vulnerability · Source |
| CVE-2023-53987 | suse_vex | SUSE CVE CVE-2023-53987 | known not affected: 453 | 2026-07-25T16:58:29+00:00 | Vulnerability · Source |
| CVE-2023-54007 | suse_vex | SUSE CVE CVE-2023-54007 | known affected: 502 known not affected: 195 recommended: 196 | 2026-07-25T16:58:27+00:00 | Vulnerability · Source |
| CVE-2023-54056 | suse_vex | SUSE CVE CVE-2023-54056 | known affected: 167 known not affected: 286 | 2026-07-25T16:58:26+00:00 | Vulnerability · Source |
| CVE-2023-54098 | suse_vex | SUSE CVE CVE-2023-54098 | known affected: 453 known not affected: 209 recommended: 245 | 2026-07-25T16:58:24+00:00 | Vulnerability · Source |
| CVE-2023-54123 | suse_vex | SUSE CVE CVE-2023-54123 | known affected: 456 known not affected: 209 recommended: 268 | 2026-07-25T16:58:22+00:00 | Vulnerability · Source |
| CVE-2023-54132 | suse_vex | SUSE CVE CVE-2023-54132 | known affected: 484 known not affected: 286 recommended: 87 | 2026-07-25T16:58:21+00:00 | Vulnerability · Source |
| CVE-2023-54160 | suse_vex | SUSE CVE CVE-2023-54160 | known affected: 184 known not affected: 239 recommended: 29 | 2026-07-25T16:58:19+00:00 | Vulnerability · Source |
| CVE-2023-54199 | suse_vex | SUSE CVE CVE-2023-54199 | known affected: 354 known not affected: 341 recommended: 196 | 2026-07-25T16:58:17+00:00 | Vulnerability · Source |
| CVE-2023-54233 | suse_vex | SUSE CVE CVE-2023-54233 | known affected: 57 known not affected: 396 recommended: 49 | 2026-07-25T16:58:16+00:00 | Vulnerability · Source |
| CVE-2023-54237 | suse_vex | SUSE CVE CVE-2023-54237 | known affected: 153 known not affected: 300 recommended: 41 | 2026-07-25T16:58:14+00:00 | Vulnerability · Source |
| CVE-2023-54260 | suse_vex | SUSE CVE CVE-2023-54260 | known affected: 456 known not affected: 209 recommended: 248 | 2026-07-25T16:58:12+00:00 | Vulnerability · Source |
| CVE-2023-54262 | suse_vex | SUSE CVE CVE-2023-54262 | known affected: 374 known not affected: 396 recommended: 136 | 2026-07-25T16:58:11+00:00 | Vulnerability · Source |
| CVE-2024-0562 | suse_vex | SUSE CVE CVE-2024-0562 | known not affected: 458 | 2026-07-25T16:58:09+00:00 | Vulnerability · Source |
| CVE-2024-0749 | suse_vex | SUSE CVE CVE-2024-0749 | known affected: 93 recommended: 219 | 2026-07-25T16:58:06+00:00 | Vulnerability · Source |
| CVE-2024-2201 | suse_vex | SUSE CVE CVE-2024-2201 | known affected: 801 known not affected: 42 recommended: 832 | 2026-07-25T16:57:59+00:00 | Vulnerability · Source |
| CVE-2024-2616 | suse_vex | SUSE CVE CVE-2024-2616 | known affected: 41 recommended: 192 | 2026-07-25T16:57:56+00:00 | Vulnerability · Source |
| CVE-2024-3220 | suse_vex | SUSE CVE CVE-2024-3220 | known not affected: 440 | 2026-07-25T16:57:55+00:00 | Vulnerability · Source |
| CVE-2024-6655 | suse_vex | SUSE CVE CVE-2024-6655 | known affected: 528 known not affected: 157 recommended: 942 | 2026-07-25T16:57:38+00:00 | Vulnerability · Source |
| CVE-2024-21217 | suse_vex | SUSE CVE CVE-2024-21217 | known affected: 517 recommended: 884 | 2026-07-25T16:57:24+00:00 | Vulnerability · Source |
| CVE-2024-22116 | suse_vex | SUSE CVE CVE-2024-22116 | known not affected: 11 | 2026-07-25T16:57:21+00:00 | Vulnerability · Source |
| CVE-2024-22119 | suse_vex | SUSE CVE CVE-2024-22119 | known affected: 13 recommended: 25 | 2026-07-25T16:57:20+00:00 | Vulnerability · Source |
| CVE-2024-22123 | suse_vex | SUSE CVE CVE-2024-22123 | known not affected: 11 | 2026-07-25T16:57:18+00:00 | Vulnerability · Source |
| CVE-2024-23307 | suse_vex | SUSE CVE CVE-2024-23307 | known affected: 310 known not affected: 70 recommended: 1105 | 2026-07-25T16:57:16+00:00 | Vulnerability · Source |
| CVE-2024-24246 | suse_vex | SUSE CVE CVE-2024-24246 | known not affected: 123 | 2026-07-25T16:57:14+00:00 | Vulnerability · Source |
| CVE-2024-24479 | suse_vex | SUSE CVE CVE-2024-24479 | known not affected: 316 | 2026-07-25T16:57:12+00:00 | Vulnerability · Source |
| CVE-2024-24986 | suse_vex | SUSE CVE CVE-2024-24986 | known not affected: 311 | 2026-07-25T16:57:10+00:00 | Vulnerability · Source |
| CVE-2024-25629 | suse_vex | SUSE CVE CVE-2024-25629 | known affected: 326 recommended: 230 | 2026-07-25T16:57:09+00:00 | Vulnerability · Source |
| CVE-2024-26630 | suse_vex | SUSE CVE CVE-2024-26630 | known not affected: 292 recommended: 29 | 2026-07-25T16:57:02+00:00 | Vulnerability · Source |
| CVE-2024-26675 | suse_vex | SUSE CVE CVE-2024-26675 | known affected: 528 known not affected: 60 recommended: 644 | 2026-07-25T16:56:57+00:00 | Vulnerability · Source |
| CVE-2024-26687 | suse_vex | SUSE CVE CVE-2024-26687 | known affected: 381 known not affected: 64 recommended: 752 | 2026-07-25T16:56:54+00:00 | Vulnerability · Source |
| CVE-2024-26692 | suse_vex | SUSE CVE CVE-2024-26692 | known affected: 315 known not affected: 266 recommended: 629 | 2026-07-25T16:56:52+00:00 | Vulnerability · Source |
| CVE-2024-26731 | suse_vex | SUSE CVE CVE-2024-26731 | known not affected: 296 recommended: 356 | 2026-07-25T16:56:49+00:00 | Vulnerability · Source |
| CVE-2024-26748 | suse_vex | SUSE CVE CVE-2024-26748 | known affected: 362 known not affected: 233 recommended: 519 | 2026-07-25T16:56:46+00:00 | Vulnerability · Source |
| CVE-2024-26752 | suse_vex | SUSE CVE CVE-2024-26752 | known affected: 394 known not affected: 371 recommended: 276 | 2026-07-25T16:56:44+00:00 | Vulnerability · Source |
| CVE-2024-26766 | suse_vex | SUSE CVE CVE-2024-26766 | known affected: 356 known not affected: 335 recommended: 666 | 2026-07-25T16:56:43+00:00 | Vulnerability · Source |
| CVE-2024-26802 | suse_vex | SUSE CVE CVE-2024-26802 | known affected: 391 known not affected: 203 recommended: 674 | 2026-07-25T16:56:41+00:00 | Vulnerability · Source |
| CVE-2024-26823 | suse_vex | SUSE CVE CVE-2024-26823 | known not affected: 311 | 2026-07-25T16:56:36+00:00 | Vulnerability · Source |
| CVE-2024-26827 | suse_vex | SUSE CVE CVE-2024-26827 | known not affected: 311 | 2026-07-25T16:56:34+00:00 | Vulnerability · Source |