VEX records
Browse vendor VEX statements available in this Vulnerability-Lookup instance and pivot to the related vulnerability.
291994 VEX records
API response| Vulnerability | Source | Title | Product status | Imported | Links |
|---|---|---|---|---|---|
| CVE-2023-31356 | suse_vex | SUSE CVE CVE-2023-31356 | known not affected: 325 recommended: 38 | 2026-07-25T02:37:57+00:00 | Vulnerability · Source |
| CVE-2023-32206 | suse_vex | SUSE CVE CVE-2023-32206 | known affected: 65 recommended: 308 | 2026-07-25T02:37:49+00:00 | Vulnerability · Source |
| CVE-2023-32212 | suse_vex | SUSE CVE CVE-2023-32212 | known affected: 65 recommended: 308 | 2026-07-25T02:37:44+00:00 | Vulnerability · Source |
| CVE-2023-32215 | suse_vex | SUSE CVE CVE-2023-32215 | known affected: 65 recommended: 308 | 2026-07-25T02:37:39+00:00 | Vulnerability · Source |
| CVE-2023-32246 | suse_vex | SUSE CVE CVE-2023-32246 | known not affected: 416 | 2026-07-25T02:37:37+00:00 | Vulnerability · Source |
| CVE-2023-32247 | suse_vex | SUSE CVE CVE-2023-32247 | known not affected: 416 | 2026-07-25T02:37:35+00:00 | Vulnerability · Source |
| CVE-2023-32253 | suse_vex | SUSE CVE CVE-2023-32253 | known not affected: 416 | 2026-07-25T02:37:30+00:00 | Vulnerability · Source |
| CVE-2023-32256 | suse_vex | SUSE CVE CVE-2023-32256 | known not affected: 416 | 2026-07-25T02:37:28+00:00 | Vulnerability · Source |
| CVE-2023-32269 | suse_vex | SUSE CVE CVE-2023-32269 | known affected: 441 known not affected: 96 recommended: 483 | 2026-07-25T02:37:26+00:00 | Vulnerability · Source |
| CVE-2023-32373 | suse_vex | SUSE CVE CVE-2023-32373 | known affected: 48 recommended: 869 | 2026-07-25T02:37:21+00:00 | Vulnerability · Source |
| CVE-2023-32409 | suse_vex | SUSE CVE CVE-2023-32409 | known not affected: 341 | 2026-07-25T02:37:19+00:00 | Vulnerability · Source |
| CVE-2023-32762 | suse_vex | SUSE CVE CVE-2023-32762 | known affected: 394 known not affected: 684 recommended: 2335 | 2026-07-25T02:37:14+00:00 | Vulnerability · Source |
| CVE-2023-33203 | suse_vex | SUSE CVE CVE-2023-33203 | known affected: 14 known not affected: 6 recommended: 49 | 2026-07-25T02:37:11+00:00 | Vulnerability · Source |
| CVE-2023-33250 | suse_vex | SUSE CVE CVE-2023-33250 | known not affected: 416 | 2026-07-25T02:37:09+00:00 | Vulnerability · Source |
| CVE-2023-34256 | suse_vex | SUSE CVE CVE-2023-34256 | known not affected: 389 | 2026-07-25T02:37:02+00:00 | Vulnerability · Source |
| CVE-2023-34872 | suse_vex | SUSE CVE CVE-2023-34872 | known affected: 19 recommended: 152 | 2026-07-25T02:36:59+00:00 | Vulnerability · Source |
| CVE-2023-34969 | suse_vex | SUSE CVE CVE-2023-34969 | known affected: 284 known not affected: 1 recommended: 443 | 2026-07-25T02:36:54+00:00 | Vulnerability · Source |
| CVE-2023-35826 | suse_vex | SUSE CVE CVE-2023-35826 | known not affected: 361 recommended: 138 | 2026-07-25T02:36:47+00:00 | Vulnerability · Source |
| CVE-2023-36191 | suse_vex | SUSE CVE CVE-2023-36191 | known not affected: 12 | 2026-07-25T02:36:42+00:00 | Vulnerability · Source |
| CVE-2023-36478 | suse_vex | SUSE CVE CVE-2023-36478 | known affected: 8 recommended: 357 | 2026-07-25T02:36:39+00:00 | Vulnerability · Source |
| CVE-2023-36617 | suse_vex | SUSE CVE CVE-2023-36617 | known not affected: 310 recommended: 66 | 2026-07-25T02:36:37+00:00 | Vulnerability · Source |
| CVE-2023-37369 | suse_vex | SUSE CVE CVE-2023-37369 | known affected: 1097 known not affected: 608 recommended: 2160 | 2026-07-25T02:36:27+00:00 | Vulnerability · Source |
| CVE-2023-37536 | suse_vex | SUSE CVE CVE-2023-37536 | known affected: 25 recommended: 120 | 2026-07-25T02:36:23+00:00 | Vulnerability · Source |
| CVE-2023-38253 | suse_vex | SUSE CVE CVE-2023-38253 | known not affected: 39 recommended: 34 | 2026-07-25T02:36:16+00:00 | Vulnerability · Source |
| CVE-2023-38407 | suse_vex | SUSE CVE CVE-2023-38407 | known not affected: 359 recommended: 312 | 2026-07-25T02:36:11+00:00 | Vulnerability · Source |
| CVE-2023-38430 | suse_vex | SUSE CVE CVE-2023-38430 | known not affected: 361 | 2026-07-25T02:36:07+00:00 | Vulnerability · Source |
| CVE-2023-38432 | suse_vex | SUSE CVE CVE-2023-38432 | known not affected: 361 | 2026-07-25T02:36:05+00:00 | Vulnerability · Source |
| CVE-2023-38472 | suse_vex | SUSE CVE CVE-2023-38472 | known affected: 623 known not affected: 95 recommended: 964 | 2026-07-25T02:35:59+00:00 | Vulnerability · Source |
| CVE-2023-38473 | suse_vex | SUSE CVE CVE-2023-38473 | known affected: 424 recommended: 1038 | 2026-07-25T02:35:57+00:00 | Vulnerability · Source |
| CVE-2023-38560 | suse_vex | SUSE CVE CVE-2023-38560 | known not affected: 147 | 2026-07-25T02:35:55+00:00 | Vulnerability · Source |
| CVE-2023-38595 | suse_vex | SUSE CVE CVE-2023-38595 | known affected: 119 known not affected: 139 recommended: 773 | 2026-07-25T02:35:50+00:00 | Vulnerability · Source |
| CVE-2023-38599 | suse_vex | SUSE CVE CVE-2023-38599 | known affected: 119 known not affected: 139 recommended: 773 | 2026-07-25T02:35:48+00:00 | Vulnerability · Source |
| CVE-2023-39130 | suse_vex | SUSE CVE CVE-2023-39130 | known not affected: 108 | 2026-07-25T02:35:40+00:00 | Vulnerability · Source |
| CVE-2023-39190 | suse_vex | SUSE CVE CVE-2023-39190 | known not affected: 337 | 2026-07-25T02:35:31+00:00 | Vulnerability · Source |
| CVE-2023-39328 | suse_vex | SUSE CVE CVE-2023-39328 | known affected: 137 known not affected: 134 | 2026-07-25T02:35:29+00:00 | Vulnerability · Source |
| CVE-2023-39434 | suse_vex | SUSE CVE CVE-2023-39434 | known affected: 95 known not affected: 85 recommended: 803 | 2026-07-25T02:35:24+00:00 | Vulnerability · Source |
| CVE-2023-40217 | suse_vex | SUSE CVE CVE-2023-40217 | known affected: 327 recommended: 1823 | 2026-07-25T02:35:20+00:00 | Vulnerability · Source |
| CVE-2023-40360 | suse_vex | SUSE CVE CVE-2023-40360 | known not affected: 1299 | 2026-07-25T02:35:18+00:00 | Vulnerability · Source |
| CVE-2023-40400 | suse_vex | SUSE CVE CVE-2023-40400 | known not affected: 143 | 2026-07-25T02:35:14+00:00 | Vulnerability · Source |
| CVE-2023-40551 | suse_vex | SUSE CVE CVE-2023-40551 | known affected: 433 recommended: 57 | 2026-07-25T02:34:59+00:00 | Vulnerability · Source |
| CVE-2023-41080 | suse_vex | SUSE CVE CVE-2023-41080 | known affected: 521 recommended: 398 | 2026-07-25T02:34:57+00:00 | Vulnerability · Source |
| CVE-2023-41334 | suse_vex | SUSE CVE CVE-2023-41334 | recommended: 6 | 2026-07-25T02:34:55+00:00 | Vulnerability · Source |
| CVE-2023-41913 | suse_vex | SUSE CVE CVE-2023-41913 | known affected: 31 known not affected: 53 recommended: 206 | 2026-07-25T02:34:51+00:00 | Vulnerability · Source |
| CVE-2023-41993 | suse_vex | SUSE CVE CVE-2023-41993 | known affected: 95 known not affected: 115 recommended: 807 | 2026-07-25T02:34:46+00:00 | Vulnerability · Source |
| CVE-2023-42852 | suse_vex | SUSE CVE CVE-2023-42852 | known affected: 109 recommended: 787 | 2026-07-25T02:34:36+00:00 | Vulnerability · Source |
| CVE-2023-42916 | suse_vex | SUSE CVE CVE-2023-42916 | known affected: 110 recommended: 779 | 2026-07-25T02:34:34+00:00 | Vulnerability · Source |
| CVE-2023-43114 | suse_vex | SUSE CVE CVE-2023-43114 | known not affected: 2120 recommended: 528 | 2026-07-25T02:34:28+00:00 | Vulnerability · Source |
| CVE-2023-43789 | suse_vex | SUSE CVE CVE-2023-43789 | known affected: 475 recommended: 124 | 2026-07-25T02:34:21+00:00 | Vulnerability · Source |
| CVE-2023-44487 | suse_vex | SUSE CVE CVE-2023-44487 | first fixed: 26 known affected: 317 known not affected: 296 recommended: 2727 | 2026-07-25T02:34:12+00:00 | Vulnerability · Source |
| CVE-2023-45221 | suse_vex | SUSE CVE CVE-2023-45221 | known not affected: 2 recommended: 173 | 2026-07-25T02:34:09+00:00 | Vulnerability · Source |