VEX records
Browse vendor VEX statements available in this Vulnerability-Lookup instance and pivot to the related vulnerability.
283449 VEX records
API response| Vulnerability | Source | Title | Product status | Imported | Links |
|---|---|---|---|---|---|
| CVE-2023-3220 | suse_vex | SUSE CVE CVE-2023-3220 | known affected: 283 known not affected: 322 recommended: 481 | 2026-07-25T02:45:36+00:00 | Vulnerability · Source |
| CVE-2023-3268 | suse_vex | SUSE CVE CVE-2023-3268 | known affected: 193 recommended: 1349 | 2026-07-25T02:45:34+00:00 | Vulnerability · Source |
| CVE-2023-3354 | suse_vex | SUSE CVE CVE-2023-3354 | known affected: 429 known not affected: 220 recommended: 1788 | 2026-07-25T02:45:31+00:00 | Vulnerability · Source |
| CVE-2023-3357 | suse_vex | SUSE CVE CVE-2023-3357 | known affected: 203 known not affected: 265 recommended: 851 | 2026-07-25T02:45:29+00:00 | Vulnerability · Source |
| CVE-2023-3358 | suse_vex | SUSE CVE CVE-2023-3358 | known affected: 199 known not affected: 56 recommended: 1255 | 2026-07-25T02:45:26+00:00 | Vulnerability · Source |
| CVE-2023-3439 | suse_vex | SUSE CVE CVE-2023-3439 | known not affected: 361 | 2026-07-25T02:45:23+00:00 | Vulnerability · Source |
| CVE-2023-3446 | suse_vex | SUSE CVE CVE-2023-3446 | known affected: 174 known not affected: 95 recommended: 978 | 2026-07-25T02:45:21+00:00 | Vulnerability · Source |
| CVE-2023-3600 | suse_vex | SUSE CVE CVE-2023-3600 | known affected: 18 recommended: 291 | 2026-07-25T02:45:19+00:00 | Vulnerability · Source |
| CVE-2023-3603 | suse_vex | SUSE CVE CVE-2023-3603 | known not affected: 213 | 2026-07-25T02:45:16+00:00 | Vulnerability · Source |
| CVE-2023-3610 | suse_vex | SUSE CVE CVE-2023-3610 | known affected: 200 known not affected: 265 recommended: 958 | 2026-07-25T02:45:14+00:00 | Vulnerability · Source |
| CVE-2023-3649 | suse_vex | SUSE CVE CVE-2023-3649 | known not affected: 318 recommended: 84 | 2026-07-25T02:45:11+00:00 | Vulnerability · Source |
| CVE-2023-3750 | suse_vex | SUSE CVE CVE-2023-3750 | known affected: 394 known not affected: 1355 recommended: 508 | 2026-07-25T02:45:09+00:00 | Vulnerability · Source |
| CVE-2023-3777 | suse_vex | SUSE CVE CVE-2023-3777 | known affected: 209 known not affected: 195 recommended: 1022 | 2026-07-25T02:45:06+00:00 | Vulnerability · Source |
| CVE-2023-3812 | suse_vex | SUSE CVE CVE-2023-3812 | known affected: 190 known not affected: 92 recommended: 1441 | 2026-07-25T02:45:04+00:00 | Vulnerability · Source |
| CVE-2023-3817 | suse_vex | SUSE CVE CVE-2023-3817 | known affected: 358 known not affected: 137 recommended: 892 | 2026-07-25T02:45:01+00:00 | Vulnerability · Source |
| CVE-2023-4010 | suse_vex | SUSE CVE CVE-2023-4010 | known not affected: 6 | 2026-07-25T02:44:58+00:00 | Vulnerability · Source |
| CVE-2023-4042 | suse_vex | SUSE CVE CVE-2023-4042 | known not affected: 149 recommended: 8 | 2026-07-25T02:44:55+00:00 | Vulnerability · Source |
| CVE-2023-4047 | suse_vex | SUSE CVE CVE-2023-4047 | known affected: 43 recommended: 271 | 2026-07-25T02:44:53+00:00 | Vulnerability · Source |
| CVE-2023-4049 | suse_vex | SUSE CVE CVE-2023-4049 | known affected: 43 recommended: 271 | 2026-07-25T02:44:51+00:00 | Vulnerability · Source |
| CVE-2023-4050 | suse_vex | SUSE CVE CVE-2023-4050 | known affected: 43 recommended: 271 | 2026-07-25T02:44:49+00:00 | Vulnerability · Source |
| CVE-2023-4051 | suse_vex | SUSE CVE CVE-2023-4051 | known affected: 43 recommended: 289 | 2026-07-25T02:44:46+00:00 | Vulnerability · Source |
| CVE-2023-4052 | suse_vex | SUSE CVE CVE-2023-4052 | known affected: 43 recommended: 253 | 2026-07-25T02:44:44+00:00 | Vulnerability · Source |
| CVE-2023-4054 | suse_vex | SUSE CVE CVE-2023-4054 | known affected: 43 recommended: 264 | 2026-07-25T02:44:42+00:00 | Vulnerability · Source |
| CVE-2023-4056 | suse_vex | SUSE CVE CVE-2023-4056 | known affected: 43 recommended: 271 | 2026-07-25T02:44:40+00:00 | Vulnerability · Source |
| CVE-2023-4058 | suse_vex | SUSE CVE CVE-2023-4058 | known affected: 43 recommended: 9 | 2026-07-25T02:44:38+00:00 | Vulnerability · Source |
| CVE-2023-4091 | suse_vex | SUSE CVE CVE-2023-4091 | known affected: 552 recommended: 1360 | 2026-07-25T02:44:35+00:00 | Vulnerability · Source |
| CVE-2023-4130 | suse_vex | SUSE CVE CVE-2023-4130 | known affected: 394 known not affected: 349 recommended: 354 | 2026-07-25T02:44:32+00:00 | Vulnerability · Source |
| CVE-2023-4133 | suse_vex | SUSE CVE CVE-2023-4133 | known affected: 228 known not affected: 42 recommended: 1241 | 2026-07-25T02:44:30+00:00 | Vulnerability · Source |
| CVE-2023-4194 | suse_vex | SUSE CVE CVE-2023-4194 | known affected: 390 known not affected: 42 recommended: 1101 | 2026-07-25T02:44:27+00:00 | Vulnerability · Source |
| CVE-2023-4385 | suse_vex | SUSE CVE CVE-2023-4385 | known affected: 420 known not affected: 96 recommended: 374 | 2026-07-25T02:44:24+00:00 | Vulnerability · Source |
| CVE-2023-4387 | suse_vex | SUSE CVE CVE-2023-4387 | known affected: 210 known not affected: 8 recommended: 1124 | 2026-07-25T02:44:21+00:00 | Vulnerability · Source |
| CVE-2023-4408 | suse_vex | SUSE CVE CVE-2023-4408 | known affected: 442 known not affected: 141 recommended: 565 | 2026-07-25T02:44:20+00:00 | Vulnerability · Source |
| CVE-2023-4513 | suse_vex | SUSE CVE CVE-2023-4513 | known affected: 109 recommended: 186 | 2026-07-25T02:44:17+00:00 | Vulnerability · Source |
| CVE-2023-4515 | suse_vex | SUSE CVE CVE-2023-4515 | known affected: 394 known not affected: 337 recommended: 354 | 2026-07-25T02:44:15+00:00 | Vulnerability · Source |
| CVE-2023-4527 | suse_vex | SUSE CVE CVE-2023-4527 | known not affected: 612 recommended: 645 | 2026-07-25T02:44:12+00:00 | Vulnerability · Source |
| CVE-2023-4563 | suse_vex | SUSE CVE CVE-2023-4563 | known affected: 247 known not affected: 169 recommended: 922 | 2026-07-25T02:44:09+00:00 | Vulnerability · Source |
| CVE-2023-4578 | suse_vex | SUSE CVE CVE-2023-4578 | known affected: 49 recommended: 289 | 2026-07-25T02:44:06+00:00 | Vulnerability · Source |
| CVE-2023-4579 | suse_vex | SUSE CVE CVE-2023-4579 | known affected: 49 recommended: 9 | 2026-07-25T02:44:04+00:00 | Vulnerability · Source |
| CVE-2023-4581 | suse_vex | SUSE CVE CVE-2023-4581 | known affected: 49 recommended: 292 | 2026-07-25T02:44:02+00:00 | Vulnerability · Source |
| CVE-2023-4583 | suse_vex | SUSE CVE CVE-2023-4583 | known affected: 49 recommended: 289 | 2026-07-25T02:44:00+00:00 | Vulnerability · Source |
| CVE-2023-4584 | suse_vex | SUSE CVE CVE-2023-4584 | known affected: 49 recommended: 292 | 2026-07-25T02:43:57+00:00 | Vulnerability · Source |
| CVE-2023-4622 | suse_vex | SUSE CVE CVE-2023-4622 | known affected: 215 known not affected: 6 recommended: 1570 | 2026-07-25T02:43:55+00:00 | Vulnerability · Source |
| CVE-2023-4641 | suse_vex | SUSE CVE CVE-2023-4641 | known affected: 214 recommended: 323 | 2026-07-25T02:43:53+00:00 | Vulnerability · Source |
| CVE-2023-4733 | suse_vex | SUSE CVE CVE-2023-4733 | known affected: 270 recommended: 436 | 2026-07-25T02:43:50+00:00 | Vulnerability · Source |
| CVE-2023-4734 | suse_vex | SUSE CVE CVE-2023-4734 | known affected: 269 known not affected: 1 recommended: 442 | 2026-07-25T02:43:48+00:00 | Vulnerability · Source |
| CVE-2023-4735 | suse_vex | SUSE CVE CVE-2023-4735 | known affected: 269 known not affected: 1 recommended: 442 | 2026-07-25T02:43:46+00:00 | Vulnerability · Source |
| CVE-2023-4736 | suse_vex | SUSE CVE CVE-2023-4736 | known not affected: 259 | 2026-07-25T02:43:45+00:00 | Vulnerability · Source |
| CVE-2023-4738 | suse_vex | SUSE CVE CVE-2023-4738 | known affected: 270 recommended: 442 | 2026-07-25T02:43:42+00:00 | Vulnerability · Source |
| CVE-2023-4750 | suse_vex | SUSE CVE CVE-2023-4750 | known affected: 411 recommended: 345 | 2026-07-25T02:43:40+00:00 | Vulnerability · Source |
| CVE-2023-4751 | suse_vex | SUSE CVE CVE-2023-4751 | known affected: 1 known not affected: 316 recommended: 22 | 2026-07-25T02:43:38+00:00 | Vulnerability · Source |