VEX records
Browse vendor VEX statements available in this Vulnerability-Lookup instance and pivot to the related vulnerability.
283841 VEX records
API response| Vulnerability | Source | Title | Product status | Imported | Links |
|---|---|---|---|---|---|
| CVE-2023-34153 | suse_vex | SUSE CVE CVE-2023-34153 | known affected: 9 known not affected: 294 recommended: 331 | 2026-07-25T02:37:04+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-34966 | suse_vex | SUSE CVE CVE-2023-34966 | known affected: 174 known not affected: 1302 recommended: 1277 | 2026-07-25T02:36:56+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-35788 | suse_vex | SUSE CVE CVE-2023-35788 | known affected: 197 known not affected: 158 recommended: 1284 | 2026-07-25T02:36:51+00:00 | Vulnerability · Source |
| CVE-2023-35823 | suse_vex | SUSE CVE CVE-2023-35823 | known affected: 197 known not affected: 160 recommended: 1099 | 2026-07-25T02:36:49+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-36054 | suse_vex | SUSE CVE CVE-2023-36054 | known affected: 277 known not affected: 40 recommended: 648 | 2026-07-25T02:36:44+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-37203 | suse_vex | SUSE CVE CVE-2023-37203 | recommended: 268 | 2026-07-25T02:36:34+00:00 | Vulnerability · Source |
| CVE-2023-37208 | suse_vex | SUSE CVE CVE-2023-37208 | recommended: 281 | 2026-07-25T02:36:32+00:00 | Vulnerability · Source |
| CVE-2023-37327 | suse_vex | SUSE CVE CVE-2023-37327 | known affected: 283 known not affected: 6 recommended: 1630 | 2026-07-25T02:36:30+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-37464 | suse_vex | SUSE CVE CVE-2023-37464 | recommended: 89 | 2026-07-25T02:36:25+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-38133 | suse_vex | SUSE CVE CVE-2023-38133 | known affected: 119 known not affected: 139 recommended: 773 | 2026-07-25T02:36:21+00:00 | Vulnerability · Source |
| CVE-2023-38197 | suse_vex | SUSE CVE CVE-2023-38197 | known affected: 621 recommended: 2758 | 2026-07-25T02:36:18+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-38406 | suse_vex | SUSE CVE CVE-2023-38406 | known not affected: 359 recommended: 312 | 2026-07-25T02:36:14+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-38408 | suse_vex | SUSE CVE CVE-2023-38408 | known affected: 195 known not affected: 14 recommended: 627 | 2026-07-25T02:36:09+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-38470 | suse_vex | SUSE CVE CVE-2023-38470 | known affected: 507 recommended: 1038 | 2026-07-25T02:36:02+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-38575 | suse_vex | SUSE CVE CVE-2023-38575 | known affected: 12 known not affected: 67 recommended: 52 | 2026-07-25T02:35:53+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-38633 | suse_vex | SUSE CVE CVE-2023-38633 | known not affected: 117 recommended: 191 | 2026-07-25T02:35:46+00:00 | Vulnerability · Source |
| CVE-2023-38709 | suse_vex | SUSE CVE CVE-2023-38709 | known affected: 450 recommended: 325 | 2026-07-25T02:35:44+00:00 | Vulnerability · Source |
| CVE-2023-38802 | suse_vex | SUSE CVE CVE-2023-38802 | known affected: 88 recommended: 635 | 2026-07-25T02:35:42+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-39176 | suse_vex | SUSE CVE CVE-2023-39176 | known not affected: 506 | 2026-07-25T02:35:37+00:00 | Vulnerability · Source |
| CVE-2023-39179 | suse_vex | SUSE CVE CVE-2023-39179 | known not affected: 506 | 2026-07-25T02:35:35+00:00 | Vulnerability · Source |
| CVE-2023-39180 | suse_vex | SUSE CVE CVE-2023-39180 | known not affected: 506 | 2026-07-25T02:35:33+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-39368 | suse_vex | SUSE CVE CVE-2023-39368 | known affected: 12 known not affected: 67 recommended: 52 | 2026-07-25T02:35:26+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-39615 | suse_vex | SUSE CVE CVE-2023-39615 | known affected: 284 recommended: 536 | 2026-07-25T02:35:22+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-40397 | suse_vex | SUSE CVE CVE-2023-40397 | known affected: 35 known not affected: 96 recommended: 598 | 2026-07-25T02:35:16+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-40414 | suse_vex | SUSE CVE CVE-2023-40414 | known affected: 69 known not affected: 56 recommended: 649 | 2026-07-25T02:35:12+00:00 | Vulnerability · Source |