VEX records
Browse vendor VEX statements available in this Vulnerability-Lookup instance and pivot to the related vulnerability.
294033 VEX records
API response| Vulnerability | Source | Title | Product status | Imported | Links |
|---|---|---|---|---|---|
| CVE-2023-52906 | suse_vex | SUSE CVE CVE-2023-52906 | known affected: 465 known not affected: 169 recommended: 288 | 2026-07-23T02:17:27+00:00 | Vulnerability · Source |
| CVE-2023-53178 | suse_vex | SUSE CVE CVE-2023-53178 | known affected: 417 known not affected: 187 recommended: 355 | 2026-07-23T02:15:53+00:00 | Vulnerability · Source |
| CVE-2023-53299 | suse_vex | SUSE CVE CVE-2023-53299 | known affected: 462 known not affected: 187 recommended: 292 | 2026-07-23T02:15:25+00:00 | Vulnerability · Source |
| CVE-2023-53308 | suse_vex | SUSE CVE CVE-2023-53308 | known affected: 500 known not affected: 280 recommended: 23 | 2026-07-23T02:15:22+00:00 | Vulnerability · Source |
| CVE-2023-53459 | suse_vex | SUSE CVE CVE-2023-53459 | known not affected: 416 | 2026-07-23T02:15:00+00:00 | Vulnerability · Source |
| CVE-2023-53463 | suse_vex | SUSE CVE CVE-2023-53463 | known affected: 395 known not affected: 108 recommended: 552 | 2026-07-23T02:14:58+00:00 | Vulnerability · Source |
| CVE-2023-53581 | suse_vex | SUSE CVE CVE-2023-53581 | known affected: 480 known not affected: 108 recommended: 483 | 2026-07-23T02:14:26+00:00 | Vulnerability · Source |
| CVE-2023-53727 | suse_vex | SUSE CVE CVE-2023-53727 | known affected: 543 known not affected: 113 recommended: 346 | 2026-07-23T02:13:49+00:00 | Vulnerability · Source |
| CVE-2023-53801 | suse_vex | SUSE CVE CVE-2023-53801 | known affected: 429 known not affected: 296 recommended: 87 | 2026-07-23T02:13:38+00:00 | Vulnerability · Source |
| CVE-2023-54047 | suse_vex | SUSE CVE CVE-2023-54047 | known affected: 531 known not affected: 209 recommended: 110 | 2026-07-23T02:13:15+00:00 | Vulnerability · Source |
| CVE-2023-54063 | suse_vex | SUSE CVE CVE-2023-54063 | known not affected: 453 | 2026-07-23T02:13:13+00:00 | Vulnerability · Source |
| CVE-2023-54190 | suse_vex | SUSE CVE CVE-2023-54190 | known affected: 354 known not affected: 309 recommended: 196 | 2026-07-23T02:12:48+00:00 | Vulnerability · Source |
| CVE-2023-54198 | suse_vex | SUSE CVE CVE-2023-54198 | known affected: 476 known not affected: 187 recommended: 233 | 2026-07-23T02:12:47+00:00 | Vulnerability · Source |
| CVE-2023-54305 | suse_vex | SUSE CVE CVE-2023-54305 | known affected: 409 known not affected: 286 recommended: 196 | 2026-07-23T02:12:23+00:00 | Vulnerability · Source |
| CVE-2023-54310 | suse_vex | SUSE CVE CVE-2023-54310 | known affected: 234 known not affected: 187 | 2026-07-23T02:12:20+00:00 | Vulnerability · Source |
| CVE-2024-1305 | suse_vex | SUSE CVE CVE-2024-1305 | known not affected: 115 | 2026-07-23T02:11:59+00:00 | Vulnerability · Source |
| CVE-2024-3205 | suse_vex | SUSE CVE CVE-2024-3205 | known not affected: 160 | 2026-07-23T02:11:52+00:00 | Vulnerability · Source |
| CVE-2024-20328 | suse_vex | SUSE CVE CVE-2024-20328 | known not affected: 178 | 2026-07-23T02:10:43+00:00 | Vulnerability · Source |
| CVE-2024-21002 | suse_vex | SUSE CVE CVE-2024-21002 | known not affected: 563 recommended: 2 | 2026-07-23T02:10:38+00:00 | Vulnerability · Source |
| CVE-2024-22122 | suse_vex | SUSE CVE CVE-2024-22122 | known not affected: 11 | 2026-07-23T02:10:26+00:00 | Vulnerability · Source |
| CVE-2024-25740 | suse_vex | SUSE CVE CVE-2024-25740 | known not affected: 321 | 2026-07-23T02:10:14+00:00 | Vulnerability · Source |
| CVE-2024-26592 | suse_vex | SUSE CVE CVE-2024-26592 | known not affected: 312 | 2026-07-23T02:10:06+00:00 | Vulnerability · Source |
| CVE-2024-26678 | suse_vex | SUSE CVE CVE-2024-26678 | known not affected: 272 recommended: 59 | 2026-07-23T02:09:48+00:00 | Vulnerability · Source |
| CVE-2024-26760 | suse_vex | SUSE CVE CVE-2024-26760 | known not affected: 231 recommended: 527 | 2026-07-23T02:09:22+00:00 | Vulnerability · Source |
| CVE-2024-26903 | suse_vex | SUSE CVE CVE-2024-26903 | known affected: 65 known not affected: 39 recommended: 922 | 2026-07-23T02:08:47+00:00 | Vulnerability · Source |
| CVE-2024-29508 | suse_vex | SUSE CVE CVE-2024-29508 | known affected: 85 recommended: 72 | 2026-07-23T02:07:24+00:00 | Vulnerability · Source |
| CVE-2024-35894 | suse_vex | SUSE CVE CVE-2024-35894 | known not affected: 330 | 2026-07-23T02:06:31+00:00 | Vulnerability · Source |
| CVE-2024-35983 | suse_vex | SUSE CVE CVE-2024-35983 | known not affected: 330 | 2026-07-23T02:06:03+00:00 | Vulnerability · Source |
| CVE-2024-36461 | suse_vex | SUSE CVE CVE-2024-36461 | known not affected: 11 recommended: 33 | 2026-07-23T02:05:46+00:00 | Vulnerability · Source |
| CVE-2024-36926 | suse_vex | SUSE CVE CVE-2024-36926 | known affected: 345 known not affected: 138 recommended: 814 | 2026-07-23T02:05:18+00:00 | Vulnerability · Source |
| CVE-2024-38624 | suse_vex | SUSE CVE CVE-2024-38624 | known affected: 4 known not affected: 436 | 2026-07-23T02:04:32+00:00 | Vulnerability · Source |
| CVE-2024-41026 | suse_vex | SUSE CVE CVE-2024-41026 | known not affected: 324 | 2026-07-23T02:03:23+00:00 | Vulnerability · Source |
| CVE-2024-41052 | suse_vex | SUSE CVE CVE-2024-41052 | known not affected: 324 recommended: 59 | 2026-07-23T02:03:06+00:00 | Vulnerability · Source |
| CVE-2024-42123 | suse_vex | SUSE CVE CVE-2024-42123 | known not affected: 324 recommended: 59 | 2026-07-23T02:02:32+00:00 | Vulnerability · Source |
| CVE-2024-42242 | suse_vex | SUSE CVE CVE-2024-42242 | known not affected: 310 | 2026-07-23T02:02:13+00:00 | Vulnerability · Source |
| CVE-2024-43862 | suse_vex | SUSE CVE CVE-2024-43862 | known not affected: 310 | 2026-07-23T02:01:20+00:00 | Vulnerability · Source |
| CVE-2024-45010 | suse_vex | SUSE CVE CVE-2024-45010 | known affected: 569 known not affected: 213 recommended: 353 | 2026-07-23T02:00:34+00:00 | Vulnerability · Source |
| CVE-2024-46544 | suse_vex | SUSE CVE CVE-2024-46544 | known affected: 35 recommended: 13 | 2026-07-23T02:00:20+00:00 | Vulnerability · Source |
| CVE-2024-46703 | suse_vex | SUSE CVE CVE-2024-46703 | known not affected: 324 recommended: 59 | 2026-07-23T02:00:10+00:00 | Vulnerability · Source |
| CVE-2024-46715 | suse_vex | SUSE CVE CVE-2024-46715 | known affected: 505 known not affected: 52 recommended: 729 | 2026-07-23T02:00:05+00:00 | Vulnerability · Source |
| CVE-2024-46793 | suse_vex | SUSE CVE CVE-2024-46793 | known not affected: 324 recommended: 59 | 2026-07-23T01:59:34+00:00 | Vulnerability · Source |
| CVE-2024-47700 | suse_vex | SUSE CVE CVE-2024-47700 | known not affected: 402 recommended: 49 | 2026-07-23T01:58:40+00:00 | Vulnerability · Source |
| CVE-2024-49869 | suse_vex | SUSE CVE CVE-2024-49869 | known not affected: 379 recommended: 6 | 2026-07-23T01:58:09+00:00 | Vulnerability · Source |
| CVE-2024-50098 | suse_vex | SUSE CVE CVE-2024-50098 | known affected: 450 known not affected: 224 recommended: 585 | 2026-07-23T01:56:54+00:00 | Vulnerability · Source |
| CVE-2024-50145 | suse_vex | SUSE CVE CVE-2024-50145 | known affected: 398 known not affected: 396 recommended: 316 | 2026-07-23T01:56:43+00:00 | Vulnerability · Source |
| CVE-2024-50157 | suse_vex | SUSE CVE CVE-2024-50157 | known affected: 394 known not affected: 298 recommended: 316 | 2026-07-23T01:56:40+00:00 | Vulnerability · Source |
| CVE-2024-50195 | suse_vex | SUSE CVE CVE-2024-50195 | known affected: 593 known not affected: 36 recommended: 730 | 2026-07-23T01:56:30+00:00 | Vulnerability · Source |
| CVE-2024-50233 | suse_vex | SUSE CVE CVE-2024-50233 | known affected: 354 known not affected: 249 recommended: 585 | 2026-07-23T01:56:14+00:00 | Vulnerability · Source |
| CVE-2024-50247 | suse_vex | SUSE CVE CVE-2024-50247 | known not affected: 321 recommended: 6 | 2026-07-23T01:56:13+00:00 | Vulnerability · Source |
| CVE-2024-50283 | suse_vex | SUSE CVE CVE-2024-50283 | known not affected: 370 | 2026-07-23T01:56:01+00:00 | Vulnerability · Source |