VEX records
Browse vendor VEX statements available in this Vulnerability-Lookup instance and pivot to the related vulnerability.
283121 VEX records
API response| Vulnerability | Source | Title | Product status | Imported | Links |
|---|---|---|---|---|---|
| CVE-2022-45421 | suse_vex | SUSE CVE CVE-2022-45421 | known affected: 1 recommended: 393 | 2026-07-19T18:09:58+00:00 | Vulnerability · Source |
| CVE-2022-45939 | suse_vex | SUSE CVE CVE-2022-45939 | known affected: 120 recommended: 433 | 2026-07-19T18:09:57+00:00 | Vulnerability · Source |
| CVE-2022-46691 | suse_vex | SUSE CVE CVE-2022-46691 | known affected: 1 recommended: 854 | 2026-07-19T18:09:56+00:00 | Vulnerability · Source |
| CVE-2022-46698 | suse_vex | SUSE CVE CVE-2022-46698 | known affected: 1 recommended: 854 | 2026-07-19T18:09:54+00:00 | Vulnerability · Source |
| CVE-2022-46705 | suse_vex | SUSE CVE CVE-2022-46705 | known affected: 109 recommended: 773 | 2026-07-19T18:09:53+00:00 | Vulnerability · Source |
| CVE-2022-48063 | suse_vex | SUSE CVE CVE-2022-48063 | known affected: 434 recommended: 318 | 2026-07-19T18:09:51+00:00 | Vulnerability · Source |
| CVE-2022-48065 | suse_vex | SUSE CVE CVE-2022-48065 | known affected: 434 recommended: 318 | 2026-07-19T18:09:50+00:00 | Vulnerability · Source |
| CVE-2022-48279 | suse_vex | SUSE CVE CVE-2022-48279 | known affected: 1 recommended: 53 | 2026-07-19T18:09:49+00:00 | Vulnerability · Source |
| CVE-2022-48281 | suse_vex | SUSE CVE CVE-2022-48281 | known affected: 394 known not affected: 1 recommended: 212 | 2026-07-19T18:09:48+00:00 | Vulnerability · Source |
| CVE-2022-48303 | suse_vex | SUSE CVE CVE-2022-48303 | known affected: 343 recommended: 241 | 2026-07-19T18:09:46+00:00 | Vulnerability · Source |
| CVE-2022-48337 | suse_vex | SUSE CVE CVE-2022-48337 | known affected: 26 recommended: 346 | 2026-07-19T18:09:45+00:00 | Vulnerability · Source |
| CVE-2022-48628 | suse_vex | SUSE CVE CVE-2022-48628 | known affected: 305 known not affected: 245 recommended: 532 | 2026-07-19T18:09:44+00:00 | Vulnerability · Source |
| CVE-2022-48686 | suse_vex | SUSE CVE CVE-2022-48686 | known affected: 281 known not affected: 151 recommended: 656 | 2026-07-19T18:09:42+00:00 | Vulnerability · Source |
| CVE-2022-49345 | suse_vex | SUSE CVE CVE-2022-49345 | known affected: 490 known not affected: 249 recommended: 250 | 2026-07-19T18:09:36+00:00 | Vulnerability · Source |
| CVE-2022-49563 | suse_vex | SUSE CVE CVE-2022-49563 | known affected: 424 known not affected: 148 recommended: 363 | 2026-07-19T18:09:33+00:00 | Vulnerability · Source |
| CVE-2022-49789 | suse_vex | SUSE CVE CVE-2022-49789 | known affected: 351 known not affected: 226 recommended: 316 | 2026-07-19T18:09:31+00:00 | Vulnerability · Source |
| CVE-2022-50166 | suse_vex | SUSE CVE CVE-2022-50166 | known affected: 587 known not affected: 198 recommended: 119 | 2026-07-19T18:09:27+00:00 | Vulnerability · Source |
| CVE-2022-50381 | suse_vex | SUSE CVE CVE-2022-50381 | known affected: 344 known not affected: 211 recommended: 377 | 2026-07-19T18:09:23+00:00 | Vulnerability · Source |
| CVE-2022-50751 | suse_vex | SUSE CVE CVE-2022-50751 | known affected: 476 known not affected: 187 recommended: 226 | 2026-07-19T18:09:20+00:00 | Vulnerability · Source |
| CVE-2023-0160 | suse_vex | SUSE CVE CVE-2023-0160 | known affected: 337 known not affected: 91 recommended: 1034 | 2026-07-19T18:09:17+00:00 | Vulnerability · Source |
| CVE-2023-0290 | suse_vex | SUSE CVE CVE-2023-0290 | recommended: 20 | 2026-07-19T18:09:16+00:00 | Vulnerability · Source |
| CVE-2023-0361 | suse_vex | SUSE CVE CVE-2023-0361 | known affected: 388 known not affected: 52 recommended: 403 | 2026-07-19T18:09:15+00:00 | Vulnerability · Source |
| CVE-2023-0413 | suse_vex | SUSE CVE CVE-2023-0413 | known not affected: 57 recommended: 270 | 2026-07-19T18:09:14+00:00 | Vulnerability · Source |
| CVE-2023-0417 | suse_vex | SUSE CVE CVE-2023-0417 | known not affected: 57 recommended: 270 | 2026-07-19T18:09:12+00:00 | Vulnerability · Source |
| CVE-2023-0667 | suse_vex | SUSE CVE CVE-2023-0667 | known not affected: 177 recommended: 192 | 2026-07-19T18:09:11+00:00 | Vulnerability · Source |
| CVE-2023-0767 | suse_vex | SUSE CVE CVE-2023-0767 | known affected: 395 recommended: 1167 | 2026-07-19T18:09:10+00:00 | Vulnerability · Source |
| CVE-2023-0800 | suse_vex | SUSE CVE CVE-2023-0800 | known affected: 488 known not affected: 1 recommended: 155 | 2026-07-19T18:09:08+00:00 | Vulnerability · Source |
| CVE-2023-0803 | suse_vex | SUSE CVE CVE-2023-0803 | known affected: 488 known not affected: 1 recommended: 155 | 2026-07-19T18:09:07+00:00 | Vulnerability · Source |
| CVE-2023-1264 | suse_vex | SUSE CVE CVE-2023-1264 | known affected: 387 known not affected: 27 recommended: 312 | 2026-07-19T18:09:05+00:00 | Vulnerability · Source |
| CVE-2023-1289 | suse_vex | SUSE CVE CVE-2023-1289 | known affected: 175 known not affected: 11 recommended: 427 | 2026-07-19T18:09:04+00:00 | Vulnerability · Source |
| CVE-2023-1732 | suse_vex | SUSE CVE CVE-2023-1732 | recommended: 16 | 2026-07-19T18:09:03+00:00 | Vulnerability · Source |
| CVE-2023-1786 | suse_vex | SUSE CVE CVE-2023-1786 | known affected: 254 recommended: 271 | 2026-07-19T18:09:01+00:00 | Vulnerability · Source |
| CVE-2023-2253 | suse_vex | SUSE CVE CVE-2023-2253 | recommended: 35 | 2026-07-19T18:09:00+00:00 | Vulnerability · Source |
| CVE-2023-2454 | suse_vex | SUSE CVE CVE-2023-2454 | known affected: 495 known not affected: 748 recommended: 1419 | 2026-07-19T18:08:58+00:00 | Vulnerability · Source |
| CVE-2023-2857 | suse_vex | SUSE CVE CVE-2023-2857 | known affected: 103 known not affected: 109 recommended: 192 | 2026-07-19T18:08:57+00:00 | Vulnerability · Source |
| CVE-2023-3247 | suse_vex | SUSE CVE CVE-2023-3247 | known affected: 511 recommended: 2513 | 2026-07-19T18:08:55+00:00 | Vulnerability · Source |
| CVE-2023-3354 | suse_vex | SUSE CVE CVE-2023-3354 | known affected: 429 known not affected: 220 recommended: 1750 | 2026-07-19T18:08:53+00:00 | Vulnerability · Source |
| CVE-2023-3446 | suse_vex | SUSE CVE CVE-2023-3446 | known affected: 174 known not affected: 92 recommended: 952 | 2026-07-19T18:08:51+00:00 | Vulnerability · Source |
| CVE-2023-3600 | suse_vex | SUSE CVE CVE-2023-3600 | known affected: 18 recommended: 279 | 2026-07-19T18:08:50+00:00 | Vulnerability · Source |
| CVE-2023-3611 | suse_vex | SUSE CVE CVE-2023-3611 | known affected: 268 known not affected: 4 recommended: 1234 | 2026-07-19T18:08:49+00:00 | Vulnerability · Source |
| CVE-2023-3648 | suse_vex | SUSE CVE CVE-2023-3648 | known affected: 1 known not affected: 74 recommended: 192 | 2026-07-19T18:08:48+00:00 | Vulnerability · Source |
| CVE-2023-3649 | suse_vex | SUSE CVE CVE-2023-3649 | known not affected: 301 recommended: 84 | 2026-07-19T18:08:47+00:00 | Vulnerability · Source |
| CVE-2023-3773 | suse_vex | SUSE CVE CVE-2023-3773 | known not affected: 341 recommended: 235 | 2026-07-19T18:08:46+00:00 | Vulnerability · Source |
| CVE-2023-3776 | suse_vex | SUSE CVE CVE-2023-3776 | known affected: 254 recommended: 1477 | 2026-07-19T18:08:44+00:00 | Vulnerability · Source |
| CVE-2023-3817 | suse_vex | SUSE CVE CVE-2023-3817 | known affected: 346 known not affected: 134 recommended: 866 | 2026-07-19T18:08:43+00:00 | Vulnerability · Source |
| CVE-2023-3823 | suse_vex | SUSE CVE CVE-2023-3823 | recommended: 2924 | 2026-07-19T18:08:41+00:00 | Vulnerability · Source |
| CVE-2023-3863 | suse_vex | SUSE CVE CVE-2023-3863 | known affected: 184 known not affected: 6 recommended: 1276 | 2026-07-19T18:08:40+00:00 | Vulnerability · Source |
| CVE-2023-4016 | suse_vex | SUSE CVE CVE-2023-4016 | known affected: 190 recommended: 407 | 2026-07-19T18:08:38+00:00 | Vulnerability · Source |
| CVE-2023-4045 | suse_vex | SUSE CVE CVE-2023-4045 | known affected: 41 recommended: 262 | 2026-07-19T18:08:37+00:00 | Vulnerability · Source |
| CVE-2023-4050 | suse_vex | SUSE CVE CVE-2023-4050 | known affected: 40 recommended: 262 | 2026-07-19T18:08:36+00:00 | Vulnerability · Source |