VEX records
Browse vendor VEX statements available in this Vulnerability-Lookup instance and pivot to the related vulnerability.
286510 VEX records
API response| Vulnerability | Source | Title | Product status | Imported | Links |
|---|---|---|---|---|---|
| CVE-2023-23603 | suse_vex | SUSE CVE CVE-2023-23603 | known affected: 36 recommended: 308 | 2026-07-27T23:48:31+00:00 | Vulnerability · Source |
| CVE-2023-24021 | suse_vex | SUSE CVE CVE-2023-24021 | known affected: 1 known not affected: 13 recommended: 40 | 2026-07-27T23:48:29+00:00 | Vulnerability · Source |
| CVE-2023-24329 | suse_vex | SUSE CVE CVE-2023-24329 | known affected: 286 recommended: 1845 | 2026-07-27T23:48:27+00:00 | Vulnerability · Source |
| CVE-2023-25012 | suse_vex | SUSE CVE CVE-2023-25012 | known affected: 288 known not affected: 89 recommended: 1008 | 2026-07-27T23:48:25+00:00 | Vulnerability · Source |
| CVE-2023-25738 | suse_vex | SUSE CVE CVE-2023-25738 | known affected: 1 recommended: 294 | 2026-07-27T23:48:23+00:00 | Vulnerability · Source |
| CVE-2023-28327 | suse_vex | SUSE CVE CVE-2023-28327 | known affected: 250 known not affected: 93 recommended: 1128 | 2026-07-27T23:48:21+00:00 | Vulnerability · Source |
| CVE-2023-28328 | suse_vex | SUSE CVE CVE-2023-28328 | known affected: 266 known not affected: 8 recommended: 1318 | 2026-07-27T23:48:19+00:00 | Vulnerability · Source |
| CVE-2023-28410 | suse_vex | SUSE CVE CVE-2023-28410 | known affected: 192 known not affected: 247 recommended: 1001 | 2026-07-27T23:48:17+00:00 | Vulnerability · Source |
| CVE-2023-28708 | suse_vex | SUSE CVE CVE-2023-28708 | known affected: 423 known not affected: 12 recommended: 424 | 2026-07-27T23:48:15+00:00 | Vulnerability · Source |
| CVE-2023-29499 | suse_vex | SUSE CVE CVE-2023-29499 | known not affected: 511 recommended: 69 | 2026-07-27T23:48:14+00:00 | Vulnerability · Source |
| CVE-2023-29532 | suse_vex | SUSE CVE CVE-2023-29532 | known affected: 15 recommended: 286 | 2026-07-27T23:48:12+00:00 | Vulnerability · Source |
| CVE-2023-32209 | suse_vex | SUSE CVE CVE-2023-32209 | known affected: 63 recommended: 9 | 2026-07-27T23:48:10+00:00 | Vulnerability · Source |
| CVE-2023-32725 | suse_vex | SUSE CVE CVE-2023-32725 | known not affected: 14 | 2026-07-27T23:48:08+00:00 | Vulnerability · Source |
| CVE-2023-34323 | suse_vex | SUSE CVE CVE-2023-34323 | known affected: 250 recommended: 447 | 2026-07-27T23:48:06+00:00 | Vulnerability · Source |
| CVE-2023-34967 | suse_vex | SUSE CVE CVE-2023-34967 | known affected: 304 known not affected: 1083 recommended: 1232 | 2026-07-27T23:48:04+00:00 | Vulnerability · Source |
| CVE-2023-35829 | suse_vex | SUSE CVE CVE-2023-35829 | known affected: 203 known not affected: 253 recommended: 813 | 2026-07-27T23:48:03+00:00 | Vulnerability · Source |
| CVE-2023-37201 | suse_vex | SUSE CVE CVE-2023-37201 | recommended: 265 | 2026-07-27T23:48:01+00:00 | Vulnerability · Source |
| CVE-2023-38431 | suse_vex | SUSE CVE CVE-2023-38431 | known not affected: 301 | 2026-07-27T23:47:59+00:00 | Vulnerability · Source |
| CVE-2023-38597 | suse_vex | SUSE CVE CVE-2023-38597 | known affected: 111 known not affected: 123 recommended: 751 | 2026-07-27T23:47:58+00:00 | Vulnerability · Source |
| CVE-2023-40791 | suse_vex | SUSE CVE CVE-2023-40791 | known not affected: 289 | 2026-07-27T23:47:55+00:00 | Vulnerability · Source |
| CVE-2023-41360 | suse_vex | SUSE CVE CVE-2023-41360 | known not affected: 481 recommended: 177 | 2026-07-27T23:47:54+00:00 | Vulnerability · Source |
| CVE-2023-45229 | suse_vex | SUSE CVE CVE-2023-45229 | known affected: 147 known not affected: 21 recommended: 147 | 2026-07-27T23:47:51+00:00 | Vulnerability · Source |
| CVE-2023-45237 | suse_vex | SUSE CVE CVE-2023-45237 | known affected: 193 recommended: 111 | 2026-07-27T23:47:49+00:00 | Vulnerability · Source |
| CVE-2023-45871 | suse_vex | SUSE CVE CVE-2023-45871 | known affected: 272 known not affected: 6 recommended: 1220 | 2026-07-27T23:47:47+00:00 | Vulnerability · Source |
| CVE-2023-46047 | suse_vex | SUSE CVE CVE-2023-46047 | known affected: 125 | 2026-07-27T23:47:46+00:00 | Vulnerability · Source |
| CVE-2023-52460 | suse_vex | SUSE CVE CVE-2023-52460 | known not affected: 306 recommended: 206 | 2026-07-27T23:47:42+00:00 | Vulnerability · Source |
| CVE-2023-52495 | suse_vex | SUSE CVE CVE-2023-52495 | known not affected: 286 recommended: 206 | 2026-07-27T23:47:40+00:00 | Vulnerability · Source |
| CVE-2023-52525 | suse_vex | SUSE CVE CVE-2023-52525 | known affected: 260 known not affected: 194 recommended: 707 | 2026-07-27T23:47:38+00:00 | Vulnerability · Source |
| CVE-2023-52562 | suse_vex | SUSE CVE CVE-2023-52562 | known not affected: 286 recommended: 199 | 2026-07-27T23:47:36+00:00 | Vulnerability · Source |
| CVE-2023-52598 | suse_vex | SUSE CVE CVE-2023-52598 | known affected: 498 known not affected: 66 recommended: 615 | 2026-07-27T23:47:34+00:00 | Vulnerability · Source |
| CVE-2023-52671 | suse_vex | SUSE CVE CVE-2023-52671 | known affected: 315 known not affected: 202 recommended: 648 | 2026-07-27T23:47:32+00:00 | Vulnerability · Source |
| CVE-2023-52750 | suse_vex | SUSE CVE CVE-2023-52750 | known affected: 532 known not affected: 214 recommended: 331 | 2026-07-27T23:47:30+00:00 | Vulnerability · Source |
| CVE-2023-52760 | suse_vex | SUSE CVE CVE-2023-52760 | known not affected: 283 | 2026-07-27T23:47:28+00:00 | Vulnerability · Source |
| CVE-2023-52780 | suse_vex | SUSE CVE CVE-2023-52780 | known affected: 394 known not affected: 291 recommended: 358 | 2026-07-27T23:47:26+00:00 | Vulnerability · Source |
| CVE-2023-52809 | suse_vex | SUSE CVE CVE-2023-52809 | known affected: 417 known not affected: 38 recommended: 783 | 2026-07-27T23:47:24+00:00 | Vulnerability · Source |
| CVE-2023-52826 | suse_vex | SUSE CVE CVE-2023-52826 | known affected: 330 known not affected: 119 recommended: 810 | 2026-07-27T23:47:23+00:00 | Vulnerability · Source |
| CVE-2023-52867 | suse_vex | SUSE CVE CVE-2023-52867 | known affected: 310 known not affected: 69 recommended: 866 | 2026-07-27T23:47:21+00:00 | Vulnerability · Source |
| CVE-2023-52873 | suse_vex | SUSE CVE CVE-2023-52873 | known affected: 275 known not affected: 178 recommended: 810 | 2026-07-27T23:47:19+00:00 | Vulnerability · Source |
| CVE-2023-52991 | suse_vex | SUSE CVE CVE-2023-52991 | known affected: 80 known not affected: 193 recommended: 49 | 2026-07-27T23:47:17+00:00 | Vulnerability · Source |
| CVE-2023-53074 | suse_vex | SUSE CVE CVE-2023-53074 | known affected: 362 known not affected: 282 recommended: 87 | 2026-07-27T23:47:15+00:00 | Vulnerability · Source |
| CVE-2023-53092 | suse_vex | SUSE CVE CVE-2023-53092 | known affected: 339 known not affected: 239 recommended: 202 | 2026-07-27T23:47:13+00:00 | Vulnerability · Source |
| CVE-2023-53193 | suse_vex | SUSE CVE CVE-2023-53193 | known affected: 359 known not affected: 298 recommended: 111 | 2026-07-27T23:47:11+00:00 | Vulnerability · Source |
| CVE-2023-53253 | suse_vex | SUSE CVE CVE-2023-53253 | known not affected: 345 | 2026-07-27T23:47:09+00:00 | Vulnerability · Source |
| CVE-2023-53301 | suse_vex | SUSE CVE CVE-2023-53301 | known affected: 47 known not affected: 298 | 2026-07-27T23:47:07+00:00 | Vulnerability · Source |
| CVE-2023-53382 | suse_vex | SUSE CVE CVE-2023-53382 | known affected: 49 known not affected: 296 | 2026-07-27T23:47:04+00:00 | Vulnerability · Source |
| CVE-2023-53434 | suse_vex | SUSE CVE CVE-2023-53434 | known not affected: 345 | 2026-07-27T23:47:02+00:00 | Vulnerability · Source |
| CVE-2023-53468 | suse_vex | SUSE CVE CVE-2023-53468 | known affected: 348 known not affected: 245 recommended: 194 | 2026-07-27T23:47:00+00:00 | Vulnerability · Source |
| CVE-2023-53471 | suse_vex | SUSE CVE CVE-2023-53471 | known affected: 383 known not affected: 210 recommended: 215 | 2026-07-27T23:46:59+00:00 | Vulnerability · Source |
| CVE-2023-53482 | suse_vex | SUSE CVE CVE-2023-53482 | known affected: 474 known not affected: 167 recommended: 87 | 2026-07-27T23:46:57+00:00 | Vulnerability · Source |
| CVE-2023-53542 | suse_vex | SUSE CVE CVE-2023-53542 | known affected: 424 known not affected: 160 recommended: 214 | 2026-07-27T23:46:55+00:00 | Vulnerability · Source |