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-3255 | suse_vex | SUSE CVE CVE-2023-3255 | known affected: 394 known not affected: 935 recommended: 1272 | 2026-10-16T13:59:08+00:00 | Vulnerability · Source |
| CVE-2023-3268 | suse_vex | SUSE CVE CVE-2023-3268 | known affected: 207 recommended: 1349 | 2026-10-16T13:59:06+00:00 | Vulnerability · Source |
| CVE-2023-3269 | suse_vex | SUSE CVE CVE-2023-3269 | known affected: 0 known not affected: 402 recommended: 239 | 2026-10-16T13:59:05+00:00 | Vulnerability · Source |
| CVE-2023-3301 | suse_vex | SUSE CVE CVE-2023-3301 | known affected: 394 known not affected: 546 recommended: 1518 | 2026-10-16T13:59:03+00:00 | Vulnerability · Source |
| CVE-2023-3312 | suse_vex | SUSE CVE CVE-2023-3312 | known affected: 0 known not affected: 402 | 2026-10-16T13:59:01+00:00 | Vulnerability · Source |
| CVE-2023-3316 | suse_vex | SUSE CVE CVE-2023-3316 | known affected: 537 recommended: 101 | 2026-10-16T13:58:59+00:00 | Vulnerability · Source |
| CVE-2023-3341 | suse_vex | SUSE CVE CVE-2023-3341 | known affected: 278 known not affected: 9 recommended: 754 | 2026-10-16T13:58:57+00:00 | Vulnerability · Source |
| CVE-2023-3347 | suse_vex | SUSE CVE CVE-2023-3347 | known affected: 260 known not affected: 2141 recommended: 653 | 2026-10-16T13:58:55+00:00 | Vulnerability · Source |
| CVE-2023-3355 | suse_vex | SUSE CVE CVE-2023-3355 | known affected: 0 known not affected: 402 | 2026-10-16T13:58:53+00:00 | Vulnerability · Source |
| CVE-2023-3358 | suse_vex | SUSE CVE CVE-2023-3358 | known affected: 199 known not affected: 78 recommended: 1255 | 2026-10-16T13:58:51+00:00 | Vulnerability · Source |
| CVE-2023-3359 | suse_vex | SUSE CVE CVE-2023-3359 | known affected: 0 known not affected: 402 | 2026-10-16T13:58:49+00:00 | Vulnerability · Source |
| CVE-2023-3389 | suse_vex | SUSE CVE CVE-2023-3389 | known affected: 203 known not affected: 310 recommended: 822 | 2026-10-16T13:58:46+00:00 | Vulnerability · Source |
| CVE-2023-3446 | suse_vex | SUSE CVE CVE-2023-3446 | known affected: 174 known not affected: 105 recommended: 974 | 2026-10-16T13:58:44+00:00 | Vulnerability · Source |
| CVE-2023-3482 | suse_vex | SUSE CVE CVE-2023-3482 | recommended: 268 | 2026-10-16T13:58:42+00:00 | Vulnerability · Source |
| CVE-2023-3600 | suse_vex | SUSE CVE CVE-2023-3600 | known affected: 29 recommended: 296 | 2026-10-16T13:58:40+00:00 | Vulnerability · Source |
| CVE-2023-3603 | suse_vex | SUSE CVE CVE-2023-3603 | known affected: 0 known not affected: 235 | 2026-10-16T13:58:38+00:00 | Vulnerability · Source |
| CVE-2023-3609 | suse_vex | SUSE CVE CVE-2023-3609 | known affected: 254 known not affected: 126 recommended: 1390 | 2026-10-16T13:58:36+00:00 | Vulnerability · Source |
| CVE-2023-3610 | suse_vex | SUSE CVE CVE-2023-3610 | known affected: 200 known not affected: 310 recommended: 956 | 2026-10-16T13:58:33+00:00 | Vulnerability · Source |
| CVE-2023-3611 | suse_vex | SUSE CVE CVE-2023-3611 | known affected: 282 known not affected: 4 recommended: 1296 | 2026-10-16T13:58:31+00:00 | Vulnerability · Source |
| CVE-2023-3640 | suse_vex | SUSE CVE CVE-2023-3640 | known affected: 0 known not affected: 103 recommended: 58 | 2026-10-16T13:58:29+00:00 | Vulnerability · Source |
| CVE-2023-3648 | suse_vex | SUSE CVE CVE-2023-3648 | known affected: 1 known not affected: 93 recommended: 192 | 2026-10-16T13:58:27+00:00 | Vulnerability · Source |
| CVE-2023-3649 | suse_vex | SUSE CVE CVE-2023-3649 | known affected: 0 known not affected: 350 recommended: 84 | 2026-10-16T13:58:24+00:00 | Vulnerability · Source |
| CVE-2023-3676 | suse_vex | SUSE CVE CVE-2023-3676 | recommended: 4 | 2026-10-16T13:58:22+00:00 | Vulnerability · Source |
| CVE-2023-3772 | suse_vex | SUSE CVE CVE-2023-3772 | known affected: 206 recommended: 1735 | 2026-10-16T13:58:20+00:00 | Vulnerability · Source |
| CVE-2023-3773 | suse_vex | SUSE CVE CVE-2023-3773 | known not affected: 404 recommended: 231 | 2026-10-16T13:58:17+00:00 | Vulnerability · Source |
| CVE-2023-3776 | suse_vex | SUSE CVE CVE-2023-3776 | known affected: 254 recommended: 1566 | 2026-10-16T13:58:14+00:00 | Vulnerability · Source |
| CVE-2023-3777 | suse_vex | SUSE CVE CVE-2023-3777 | known affected: 209 known not affected: 234 recommended: 1051 | 2026-10-16T13:58:11+00:00 | Vulnerability · Source |
| CVE-2023-3817 | suse_vex | SUSE CVE CVE-2023-3817 | known affected: 393 known not affected: 149 recommended: 881 | 2026-10-16T13:58:09+00:00 | Vulnerability · Source |
| CVE-2023-3823 | suse_vex | SUSE CVE CVE-2023-3823 | recommended: 3106 | 2026-10-16T13:58:06+00:00 | Vulnerability · Source |
| CVE-2023-3824 | suse_vex | SUSE CVE CVE-2023-3824 | recommended: 3154 | 2026-10-16T13:58:04+00:00 | Vulnerability · Source |
| CVE-2023-3865 | suse_vex | SUSE CVE CVE-2023-3865 | known affected: 0 known not affected: 400 | 2026-10-16T13:58:02+00:00 | Vulnerability · Source |
| CVE-2023-3955 | suse_vex | SUSE CVE CVE-2023-3955 | recommended: 4 | 2026-10-16T13:57:58+00:00 | Vulnerability · Source |
| CVE-2023-3961 | suse_vex | SUSE CVE CVE-2023-3961 | known affected: 270 known not affected: 2026 recommended: 644 | 2026-10-16T13:57:56+00:00 | Vulnerability · Source |
| CVE-2023-3966 | suse_vex | SUSE CVE CVE-2023-3966 | known affected: 195 known not affected: 62 recommended: 665 | 2026-10-16T13:57:54+00:00 | Vulnerability · Source |
| CVE-2023-4001 | suse_vex | SUSE CVE CVE-2023-4001 | known affected: 296 known not affected: 104 recommended: 10 | 2026-10-16T13:57:52+00:00 | Vulnerability · Source |
| CVE-2023-4004 | suse_vex | SUSE CVE CVE-2023-4004 | known affected: 179 known not affected: 249 recommended: 1293 | 2026-10-16T13:57:49+00:00 | Vulnerability · Source |
| CVE-2023-4010 | suse_vex | SUSE CVE CVE-2023-4010 | known affected: 0 known not affected: 6 | 2026-10-16T13:57:47+00:00 | Vulnerability · Source |
| CVE-2023-4015 | suse_vex | SUSE CVE CVE-2023-4015 | known affected: 0 known not affected: 316 recommended: 58 | 2026-10-16T13:57:45+00:00 | Vulnerability · Source |
| CVE-2023-4016 | suse_vex | SUSE CVE CVE-2023-4016 | known affected: 190 recommended: 416 | 2026-10-16T13:57:42+00:00 | Vulnerability · Source |
| CVE-2023-4039 | suse_vex | SUSE CVE CVE-2023-4039 | known affected: 469 known not affected: 264 recommended: 4900 | 2026-10-16T13:57:40+00:00 | Vulnerability · Source |
| CVE-2023-4045 | suse_vex | SUSE CVE CVE-2023-4045 | known affected: 55 recommended: 276 | 2026-10-16T13:57:37+00:00 | Vulnerability · Source |
| CVE-2023-4046 | suse_vex | SUSE CVE CVE-2023-4046 | known affected: 54 recommended: 276 | 2026-10-16T13:57:35+00:00 | Vulnerability · Source |
| CVE-2023-4047 | suse_vex | SUSE CVE CVE-2023-4047 | known affected: 54 recommended: 276 | 2026-10-16T13:57:33+00:00 | Vulnerability · Source |
| CVE-2023-4049 | suse_vex | SUSE CVE CVE-2023-4049 | known affected: 54 recommended: 276 | 2026-10-16T13:57:31+00:00 | Vulnerability · Source |
| CVE-2023-4050 | suse_vex | SUSE CVE CVE-2023-4050 | known affected: 54 recommended: 276 | 2026-10-16T13:57:28+00:00 | Vulnerability · Source |
| CVE-2023-4051 | suse_vex | SUSE CVE CVE-2023-4051 | known affected: 54 recommended: 290 | 2026-10-16T13:57:26+00:00 | Vulnerability · Source |
| CVE-2023-4053 | suse_vex | SUSE CVE CVE-2023-4053 | known affected: 54 recommended: 290 | 2026-10-16T13:57:23+00:00 | Vulnerability · Source |
| CVE-2023-4134 | suse_vex | SUSE CVE CVE-2023-4134 | known affected: 246 known not affected: 6 recommended: 1321 | 2026-10-16T13:57:19+00:00 | Vulnerability · Source |
| CVE-2023-4154 | suse_vex | SUSE CVE CVE-2023-4154 | known affected: 199 known not affected: 763 recommended: 1073 | 2026-10-16T13:57:17+00:00 | Vulnerability · Source |
| CVE-2023-4206 | suse_vex | SUSE CVE CVE-2023-4206 | recommended: 91 | 2026-10-16T13:57:15+00:00 | Vulnerability · Source |