VEX records
Browse vendor VEX statements available in this Vulnerability-Lookup instance and pivot to the related vulnerability.
103255 VEX records
API response| Vulnerability | Source | Title | Product status | Imported | Links |
|---|---|---|---|---|---|
| CVE-2023-20941 | suse_vex | SUSE CVE CVE-2023-20941 | known affected: 0 known not affected: 350 | 2026-10-17T01:17:38+00:00 | Vulnerability · Source |
| CVE-2023-22045 | suse_vex | SUSE CVE CVE-2023-22045 | known affected: 543 recommended: 950 | 2026-10-17T01:17:36+00:00 | Vulnerability · Source |
| CVE-2023-22067 | suse_vex | SUSE CVE CVE-2023-22067 | known affected: 450 known not affected: 390 recommended: 435 | 2026-10-17T01:17:34+00:00 | Vulnerability · Source |
| CVE-2023-22655 | suse_vex | SUSE CVE CVE-2023-22655 | known affected: 18 known not affected: 54 recommended: 52 | 2026-10-17T01:17:32+00:00 | Vulnerability · Source |
| CVE-2023-23006 | suse_vex | SUSE CVE CVE-2023-23006 | known affected: 290 known not affected: 141 recommended: 978 | 2026-10-17T01:17:31+00:00 | Vulnerability · Source |
| CVE-2023-23931 | suse_vex | SUSE CVE CVE-2023-23931 | known affected: 384 recommended: 224 | 2026-10-17T01:17:29+00:00 | Vulnerability · Source |
| CVE-2023-25433 | suse_vex | SUSE CVE CVE-2023-25433 | known affected: 394 known not affected: 143 recommended: 98 | 2026-10-17T01:17:27+00:00 | Vulnerability · Source |
| CVE-2023-25587 | suse_vex | SUSE CVE CVE-2023-25587 | known affected: 436 known not affected: 1 recommended: 327 | 2026-10-17T01:17:26+00:00 | Vulnerability · Source |
| CVE-2023-25690 | suse_vex | SUSE CVE CVE-2023-25690 | known affected: 425 recommended: 456 | 2026-10-17T01:17:24+00:00 | Vulnerability · Source |
| CVE-2023-25815 | suse_vex | SUSE CVE CVE-2023-25815 | known affected: 1 known not affected: 112 recommended: 712 | 2026-10-17T01:17:23+00:00 | Vulnerability · Source |
| CVE-2023-26248 | suse_vex | SUSE CVE CVE-2023-26248 | recommended: 4 | 2026-10-17T01:17:21+00:00 | Vulnerability · Source |
| CVE-2023-26484 | suse_vex | SUSE CVE CVE-2023-26484 | known affected: 6 known not affected: 21 recommended: 104 | 2026-10-17T01:17:20+00:00 | Vulnerability · Source |
| CVE-2023-27561 | suse_vex | SUSE CVE CVE-2023-27561 | known affected: 290 known not affected: 46 recommended: 181 | 2026-10-17T01:17:18+00:00 | Vulnerability · Source |
| CVE-2023-27586 | suse_vex | SUSE CVE CVE-2023-27586 | recommended: 17 | 2026-10-17T01:17:17+00:00 | Vulnerability · Source |
| CVE-2023-28163 | suse_vex | SUSE CVE CVE-2023-28163 | known affected: 1 recommended: 297 | 2026-10-17T01:17:15+00:00 | Vulnerability · Source |
| CVE-2023-28204 | suse_vex | SUSE CVE CVE-2023-28204 | known affected: 57 recommended: 861 | 2026-10-17T01:17:14+00:00 | Vulnerability · Source |
| CVE-2023-31122 | suse_vex | SUSE CVE CVE-2023-31122 | known affected: 486 recommended: 407 | 2026-10-17T01:17:10+00:00 | Vulnerability · Source |
| CVE-2023-32253 | suse_vex | SUSE CVE CVE-2023-32253 | known affected: 0 known not affected: 458 | 2026-10-17T01:17:08+00:00 | Vulnerability · Source |
| CVE-2023-32255 | suse_vex | SUSE CVE CVE-2023-32255 | known affected: 0 known not affected: 458 | 2026-10-17T01:17:07+00:00 | Vulnerability · Source |
| CVE-2023-32258 | suse_vex | SUSE CVE CVE-2023-32258 | known affected: 0 known not affected: 458 | 2026-10-17T01:17:06+00:00 | Vulnerability · Source |
| CVE-2023-32803 | suse_vex | SUSE CVE CVE-2023-32803 | known affected: 0 known not affected: 96 | 2026-10-17T01:17:04+00:00 | Vulnerability · Source |
| CVE-2023-35828 | suse_vex | SUSE CVE CVE-2023-35828 | known affected: 197 known not affected: 193 recommended: 1050 | 2026-10-17T01:17:02+00:00 | Vulnerability · Source |
| CVE-2023-37209 | suse_vex | SUSE CVE CVE-2023-37209 | recommended: 268 | 2026-10-17T01:17:00+00:00 | Vulnerability · Source |
| CVE-2023-38201 | suse_vex | SUSE CVE CVE-2023-38201 | recommended: 247 | 2026-10-17T01:16:59+00:00 | Vulnerability · Source |
| CVE-2023-38289 | suse_vex | SUSE CVE CVE-2023-38289 | known affected: 537 recommended: 95 | 2026-10-17T01:16:57+00:00 | Vulnerability · Source |
| CVE-2023-39180 | suse_vex | SUSE CVE CVE-2023-39180 | known not affected: 593 | 2026-10-17T01:16:55+00:00 | Vulnerability · Source |
| CVE-2023-39354 | suse_vex | SUSE CVE CVE-2023-39354 | recommended: 185 | 2026-10-17T01:16:53+00:00 | Vulnerability · Source |
| CVE-2023-39434 | suse_vex | SUSE CVE CVE-2023-39434 | known affected: 130 known not affected: 101 recommended: 791 | 2026-10-17T01:16:52+00:00 | Vulnerability · Source |
| CVE-2023-40397 | suse_vex | SUSE CVE CVE-2023-40397 | known affected: 35 known not affected: 98 recommended: 590 | 2026-10-17T01:16:50+00:00 | Vulnerability · Source |
| CVE-2023-40477 | suse_vex | SUSE CVE CVE-2023-40477 | known affected: 32 recommended: 210 | 2026-10-17T01:16:49+00:00 | Vulnerability · Source |
| CVE-2023-40551 | suse_vex | SUSE CVE CVE-2023-40551 | known affected: 435 recommended: 56 | 2026-10-17T01:16:47+00:00 | Vulnerability · Source |
| CVE-2023-40589 | suse_vex | SUSE CVE CVE-2023-40589 | recommended: 185 | 2026-10-17T01:16:46+00:00 | Vulnerability · Source |
| CVE-2023-41080 | suse_vex | SUSE CVE CVE-2023-41080 | known affected: 537 recommended: 436 | 2026-10-17T01:16:44+00:00 | Vulnerability · Source |
| CVE-2023-42467 | suse_vex | SUSE CVE CVE-2023-42467 | known affected: 394 known not affected: 1245 recommended: 492 | 2026-10-17T01:16:42+00:00 | Vulnerability · Source |
| CVE-2023-43635 | suse_vex | SUSE CVE CVE-2023-43635 | recommended: 2 | 2026-10-17T01:16:40+00:00 | Vulnerability · Source |
| CVE-2023-45229 | suse_vex | SUSE CVE CVE-2023-45229 | known affected: 178 known not affected: 17 recommended: 149 | 2026-10-17T01:16:38+00:00 | Vulnerability · Source |
| CVE-2023-45919 | suse_vex | SUSE CVE CVE-2023-45919 | known affected: 1116 known not affected: 91 recommended: 1063 | 2026-10-17T01:16:35+00:00 | Vulnerability · Source |
| CVE-2023-45929 | suse_vex | SUSE CVE CVE-2023-45929 | No product status | 2026-10-17T01:16:34+00:00 | Vulnerability · Source |
| CVE-2023-46137 | suse_vex | SUSE CVE CVE-2023-46137 | known affected: 42 recommended: 285 | 2026-10-17T01:16:32+00:00 | Vulnerability · Source |
| CVE-2023-49460 | suse_vex | SUSE CVE CVE-2023-49460 | known affected: 0 known not affected: 37 recommended: 53 | 2026-10-17T01:16:29+00:00 | Vulnerability · Source |
| CVE-2023-51780 | suse_vex | SUSE CVE CVE-2023-51780 | known affected: 365 recommended: 1404 | 2026-10-17T01:16:26+00:00 | Vulnerability · Source |
| CVE-2023-52438 | suse_vex | SUSE CVE CVE-2023-52438 | known not affected: 365 | 2026-10-17T01:16:24+00:00 | Vulnerability · Source |
| CVE-2023-52448 | suse_vex | SUSE CVE CVE-2023-52448 | known affected: 249 known not affected: 236 recommended: 909 | 2026-10-17T01:16:23+00:00 | Vulnerability · Source |
| CVE-2023-52469 | suse_vex | SUSE CVE CVE-2023-52469 | known affected: 347 known not affected: 95 recommended: 929 | 2026-10-17T01:16:20+00:00 | Vulnerability · Source |
| CVE-2023-52477 | suse_vex | SUSE CVE CVE-2023-52477 | known affected: 388 known not affected: 66 recommended: 928 | 2026-10-17T01:16:18+00:00 | Vulnerability · Source |
| CVE-2023-52485 | suse_vex | SUSE CVE CVE-2023-52485 | known not affected: 362 recommended: 202 | 2026-10-17T01:16:17+00:00 | Vulnerability · Source |
| CVE-2023-52489 | suse_vex | SUSE CVE CVE-2023-52489 | known affected: 359 known not affected: 189 recommended: 854 | 2026-10-17T01:16:15+00:00 | Vulnerability · Source |
| CVE-2023-52493 | suse_vex | SUSE CVE CVE-2023-52493 | known affected: 358 known not affected: 310 recommended: 528 | 2026-10-17T01:16:13+00:00 | Vulnerability · Source |
| CVE-2023-52496 | suse_vex | SUSE CVE CVE-2023-52496 | known not affected: 362 | 2026-10-17T01:16:12+00:00 | Vulnerability · Source |
| CVE-2023-52528 | suse_vex | SUSE CVE CVE-2023-52528 | known affected: 474 known not affected: 61 recommended: 777 | 2026-10-17T01:16:09+00:00 | Vulnerability · Source |