VEX records
Browse vendor VEX statements available in this Vulnerability-Lookup instance and pivot to the related vulnerability.
104719 VEX records
API response| Vulnerability | Source | Title | Product status | Imported | Links |
|---|---|---|---|---|---|
| CVE-2023-32570 | suse_vex | SUSE CVE CVE-2023-32570 | known affected: 0 known not affected: 47 recommended: 51 | 2026-10-16T13:36:29+00:00 | Vulnerability · Source |
| CVE-2023-32611 | suse_vex | SUSE CVE CVE-2023-32611 | known affected: 0 known not affected: 777 recommended: 78 | 2026-10-16T13:36:28+00:00 | Vulnerability · Source |
| CVE-2023-32636 | suse_vex | SUSE CVE CVE-2023-32636 | known affected: 0 known not affected: 626 recommended: 68 | 2026-10-16T13:36:26+00:00 | Vulnerability · Source |
| CVE-2023-32643 | suse_vex | SUSE CVE CVE-2023-32643 | known affected: 0 known not affected: 693 recommended: 60 | 2026-10-16T13:36:25+00:00 | Vulnerability · Source |
| CVE-2023-32665 | suse_vex | SUSE CVE CVE-2023-32665 | known affected: 0 known not affected: 641 recommended: 78 | 2026-10-16T13:36:23+00:00 | Vulnerability · Source |
| CVE-2023-32731 | suse_vex | SUSE CVE CVE-2023-32731 | known affected: 82 known not affected: 202 recommended: 265 | 2026-10-16T13:36:22+00:00 | Vulnerability · Source |
| CVE-2023-32762 | suse_vex | SUSE CVE CVE-2023-32762 | known affected: 394 known not affected: 780 recommended: 2341 | 2026-10-16T13:36:20+00:00 | Vulnerability · Source |
| CVE-2023-33201 | suse_vex | SUSE CVE CVE-2023-33201 | recommended: 191 | 2026-10-16T13:36:18+00:00 | Vulnerability · Source |
| CVE-2023-33285 | suse_vex | SUSE CVE CVE-2023-33285 | known affected: 466 known not affected: 210 recommended: 2745 | 2026-10-16T13:36:16+00:00 | Vulnerability · Source |
| CVE-2023-33288 | suse_vex | SUSE CVE CVE-2023-33288 | known affected: 192 known not affected: 267 recommended: 1055 | 2026-10-16T13:36:14+00:00 | Vulnerability · Source |
| CVE-2023-33460 | suse_vex | SUSE CVE CVE-2023-33460 | known affected: 184 known not affected: 54 recommended: 318 | 2026-10-16T13:36:13+00:00 | Vulnerability · Source |
| CVE-2023-34059 | suse_vex | SUSE CVE CVE-2023-34059 | recommended: 339 | 2026-10-16T13:36:11+00:00 | Vulnerability · Source |
| CVE-2023-34151 | suse_vex | SUSE CVE CVE-2023-34151 | known affected: 0 known not affected: 221 recommended: 434 | 2026-10-16T13:36:10+00:00 | Vulnerability · Source |
| CVE-2023-34153 | suse_vex | SUSE CVE CVE-2023-34153 | known affected: 9 known not affected: 343 recommended: 329 | 2026-10-16T13:36:08+00:00 | Vulnerability · Source |
| CVE-2023-34241 | suse_vex | SUSE CVE CVE-2023-34241 | known affected: 347 known not affected: 18 recommended: 698 | 2026-10-16T13:36:07+00:00 | Vulnerability · Source |
| CVE-2023-34319 | suse_vex | SUSE CVE CVE-2023-34319 | known affected: 254 known not affected: 328 recommended: 1315 | 2026-10-16T13:36:05+00:00 | Vulnerability · Source |
| CVE-2023-34324 | suse_vex | SUSE CVE CVE-2023-34324 | known affected: 80 known not affected: 232 recommended: 927 | 2026-10-16T13:36:04+00:00 | Vulnerability · Source |
| CVE-2023-34474 | suse_vex | SUSE CVE CVE-2023-34474 | known affected: 0 known not affected: 316 recommended: 326 | 2026-10-16T13:36:02+00:00 | Vulnerability · Source |
| CVE-2023-34475 | suse_vex | SUSE CVE CVE-2023-34475 | known affected: 0 known not affected: 436 recommended: 160 | 2026-10-16T13:36:01+00:00 | Vulnerability · Source |
| CVE-2023-34623 | suse_vex | SUSE CVE CVE-2023-34623 | known affected: 1 recommended: 55 | 2026-10-16T13:36:00+00:00 | Vulnerability · Source |
| CVE-2023-34968 | suse_vex | SUSE CVE CVE-2023-34968 | known affected: 174 known not affected: 1574 recommended: 1321 | 2026-10-16T13:35:58+00:00 | Vulnerability · Source |
| CVE-2023-34969 | suse_vex | SUSE CVE CVE-2023-34969 | known affected: 298 known not affected: 1 recommended: 452 | 2026-10-16T13:35:57+00:00 | Vulnerability · Source |
| CVE-2023-35001 | suse_vex | SUSE CVE CVE-2023-35001 | known affected: 174 known not affected: 6 recommended: 1638 | 2026-10-16T13:35:55+00:00 | Vulnerability · Source |
| CVE-2023-35823 | suse_vex | SUSE CVE CVE-2023-35823 | known affected: 197 known not affected: 193 recommended: 1070 | 2026-10-16T13:35:53+00:00 | Vulnerability · Source |
| CVE-2023-35827 | suse_vex | SUSE CVE CVE-2023-35827 | known affected: 254 known not affected: 317 recommended: 963 | 2026-10-16T13:35:51+00:00 | Vulnerability · Source |
| CVE-2023-35945 | suse_vex | SUSE CVE CVE-2023-35945 | known affected: 256 recommended: 436 | 2026-10-16T13:35:49+00:00 | Vulnerability · Source |
| CVE-2023-36054 | suse_vex | SUSE CVE CVE-2023-36054 | known affected: 301 known not affected: 34 recommended: 657 | 2026-10-16T13:35:47+00:00 | Vulnerability · Source |
| CVE-2023-36191 | suse_vex | SUSE CVE CVE-2023-36191 | known affected: 0 known not affected: 12 | 2026-10-16T13:35:46+00:00 | Vulnerability · Source |
| CVE-2023-36660 | suse_vex | SUSE CVE CVE-2023-36660 | known affected: 0 known not affected: 348 recommended: 77 | 2026-10-16T13:35:44+00:00 | Vulnerability · Source |
| CVE-2023-36664 | suse_vex | SUSE CVE CVE-2023-36664 | known affected: 21 recommended: 199 | 2026-10-16T13:35:43+00:00 | Vulnerability · Source |
| CVE-2023-36824 | suse_vex | SUSE CVE CVE-2023-36824 | known affected: 0 known not affected: 28 recommended: 6 | 2026-10-16T13:35:42+00:00 | Vulnerability · Source |
| CVE-2023-37203 | suse_vex | SUSE CVE CVE-2023-37203 | recommended: 268 | 2026-10-16T13:35:40+00:00 | Vulnerability · Source |
| CVE-2023-37205 | suse_vex | SUSE CVE CVE-2023-37205 | recommended: 268 | 2026-10-16T13:35:39+00:00 | Vulnerability · Source |
| CVE-2023-37206 | suse_vex | SUSE CVE CVE-2023-37206 | recommended: 268 | 2026-10-16T13:35:38+00:00 | Vulnerability · Source |
| CVE-2023-37207 | suse_vex | SUSE CVE CVE-2023-37207 | recommended: 284 | 2026-10-16T13:35:36+00:00 | Vulnerability · Source |
| CVE-2023-37211 | suse_vex | SUSE CVE CVE-2023-37211 | recommended: 284 | 2026-10-16T13:35:35+00:00 | Vulnerability · Source |
| CVE-2023-37327 | suse_vex | SUSE CVE CVE-2023-37327 | known affected: 355 known not affected: 6 recommended: 1637 | 2026-10-16T13:35:33+00:00 | Vulnerability · Source |
| CVE-2023-37369 | suse_vex | SUSE CVE CVE-2023-37369 | known affected: 1235 known not affected: 550 recommended: 2276 | 2026-10-16T13:35:29+00:00 | Vulnerability · Source |
| CVE-2023-37453 | suse_vex | SUSE CVE CVE-2023-37453 | known affected: 200 known not affected: 310 recommended: 1105 | 2026-10-16T13:35:28+00:00 | Vulnerability · Source |
| CVE-2023-37454 | suse_vex | SUSE CVE CVE-2023-37454 | No product status | 2026-10-16T13:35:26+00:00 | Vulnerability · Source |
| CVE-2023-37460 | suse_vex | SUSE CVE CVE-2023-37460 | known affected: 10 recommended: 299 | 2026-10-16T13:35:25+00:00 | Vulnerability · Source |
| CVE-2023-37463 | suse_vex | SUSE CVE CVE-2023-37463 | known affected: 0 known not affected: 29 recommended: 13 | 2026-10-16T13:35:23+00:00 | Vulnerability · Source |
| CVE-2023-37464 | suse_vex | SUSE CVE CVE-2023-37464 | recommended: 92 | 2026-10-16T13:35:22+00:00 | Vulnerability · Source |
| CVE-2023-38039 | suse_vex | SUSE CVE CVE-2023-38039 | known affected: 243 known not affected: 143 recommended: 347 | 2026-10-16T13:35:20+00:00 | Vulnerability · Source |
| CVE-2023-38103 | suse_vex | SUSE CVE CVE-2023-38103 | recommended: 33 | 2026-10-16T13:35:18+00:00 | Vulnerability · Source |
| CVE-2023-38197 | suse_vex | SUSE CVE CVE-2023-38197 | known affected: 621 recommended: 2874 | 2026-10-16T13:35:16+00:00 | Vulnerability · Source |
| CVE-2023-38403 | suse_vex | SUSE CVE CVE-2023-38403 | recommended: 50 | 2026-10-16T13:35:15+00:00 | Vulnerability · Source |
| CVE-2023-38406 | suse_vex | SUSE CVE CVE-2023-38406 | known affected: 0 known not affected: 419 recommended: 314 | 2026-10-16T13:35:13+00:00 | Vulnerability · Source |
| CVE-2023-38407 | suse_vex | SUSE CVE CVE-2023-38407 | known affected: 0 known not affected: 419 recommended: 314 | 2026-10-16T13:35:12+00:00 | Vulnerability · Source |
| CVE-2023-38408 | suse_vex | SUSE CVE CVE-2023-38408 | known affected: 201 known not affected: 30 recommended: 631 | 2026-10-16T13:35:10+00:00 | Vulnerability · Source |