VEX records
Browse vendor VEX statements available in this Vulnerability-Lookup instance and pivot to the related vulnerability.
283447 VEX records
API response| Vulnerability | Source | Title | Product status | Imported | Links |
|---|---|---|---|---|---|
| CVE-2023-30456 | suse_vex | SUSE CVE CVE-2023-30456 | known affected: 198 known not affected: 39 recommended: 905 | 2026-07-25T02:38:11+00:00 | Vulnerability · Source |
| CVE-2023-30772 | suse_vex | SUSE CVE CVE-2023-30772 | known affected: 292 known not affected: 6 recommended: 1252 | 2026-07-25T02:38:08+00:00 | Vulnerability · Source |
| CVE-2023-30775 | suse_vex | SUSE CVE CVE-2023-30775 | known affected: 13 known not affected: 164 recommended: 3 | 2026-07-25T02:38:06+00:00 | Vulnerability · Source |
| CVE-2023-31085 | suse_vex | SUSE CVE CVE-2023-31085 | known affected: 229 recommended: 1283 | 2026-07-25T02:38:03+00:00 | Vulnerability · Source |
| CVE-2023-31124 | suse_vex | SUSE CVE CVE-2023-31124 | known affected: 295 recommended: 470 | 2026-07-25T02:38:00+00:00 | Vulnerability · Source |
| 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-32001 | suse_vex | SUSE CVE CVE-2023-32001 | known affected: 180 known not affected: 127 recommended: 364 | 2026-07-25T02:37:54+00:00 | Vulnerability · Source |
| CVE-2023-32067 | suse_vex | SUSE CVE CVE-2023-32067 | known affected: 295 recommended: 476 | 2026-07-25T02:37:52+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-32207 | suse_vex | SUSE CVE CVE-2023-32207 | known affected: 65 recommended: 308 | 2026-07-25T02:37:46+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-32213 | suse_vex | SUSE CVE CVE-2023-32213 | known affected: 65 recommended: 308 | 2026-07-25T02:37:41+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-32249 | suse_vex | SUSE CVE CVE-2023-32249 | known not affected: 416 | 2026-07-25T02:37:32+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-32370 | suse_vex | SUSE CVE CVE-2023-32370 | known affected: 35 known not affected: 96 recommended: 598 | 2026-07-25T02:37:23+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-32435 | suse_vex | SUSE CVE CVE-2023-32435 | known affected: 111 recommended: 773 | 2026-07-25T02:37:17+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-33952 | suse_vex | SUSE CVE CVE-2023-33952 | known not affected: 418 recommended: 490 | 2026-07-25T02:37:06+00:00 | Vulnerability · Source |
| 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 |