VEX records
Browse vendor VEX statements available in this Vulnerability-Lookup instance and pivot to the related vulnerability.
291935 VEX records
API response| Vulnerability | Source | Title | Product status | Imported | Links |
|---|---|---|---|---|---|
| CVE-2022-49161 | suse_vex | SUSE CVE CVE-2022-49161 | known affected: 112 known not affected: 240 | 2026-07-26T00:09:38+00:00 | Vulnerability · Source |
| CVE-2022-49209 | suse_vex | SUSE CVE CVE-2022-49209 | known affected: 499 known not affected: 143 recommended: 126 | 2026-07-26T00:09:35+00:00 | Vulnerability · Source |
| CVE-2022-49324 | suse_vex | SUSE CVE CVE-2022-49324 | known not affected: 348 | 2026-07-26T00:09:29+00:00 | Vulnerability · Source |
| CVE-2022-49331 | suse_vex | SUSE CVE CVE-2022-49331 | known affected: 421 known not affected: 245 recommended: 319 | 2026-07-26T00:09:27+00:00 | Vulnerability · Source |
| CVE-2022-49387 | suse_vex | SUSE CVE CVE-2022-49387 | known not affected: 352 | 2026-07-26T00:09:24+00:00 | Vulnerability · Source |
| CVE-2022-49531 | suse_vex | SUSE CVE CVE-2022-49531 | known affected: 230 known not affected: 88 recommended: 22 | 2026-07-26T00:09:14+00:00 | Vulnerability · Source |
| CVE-2022-49536 | suse_vex | SUSE CVE CVE-2022-49536 | known affected: 385 known not affected: 193 recommended: 361 | 2026-07-26T00:09:12+00:00 | Vulnerability · Source |
| CVE-2022-49661 | suse_vex | SUSE CVE CVE-2022-49661 | known affected: 421 known not affected: 157 recommended: 333 | 2026-07-26T00:09:09+00:00 | Vulnerability · Source |
| CVE-2022-49754 | suse_vex | SUSE CVE CVE-2022-49754 | known not affected: 344 recommended: 29 | 2026-07-26T00:09:01+00:00 | Vulnerability · Source |
| CVE-2022-49760 | suse_vex | SUSE CVE CVE-2022-49760 | known not affected: 344 recommended: 29 | 2026-07-26T00:08:59+00:00 | Vulnerability · Source |
| CVE-2022-49782 | suse_vex | SUSE CVE CVE-2022-49782 | known not affected: 397 | 2026-07-26T00:08:54+00:00 | Vulnerability · Source |
| CVE-2022-49859 | suse_vex | SUSE CVE CVE-2022-49859 | known affected: 55 known not affected: 342 | 2026-07-26T00:08:51+00:00 | Vulnerability · Source |
| CVE-2022-49893 | suse_vex | SUSE CVE CVE-2022-49893 | known not affected: 397 | 2026-07-26T00:08:47+00:00 | Vulnerability · Source |
| CVE-2022-49934 | suse_vex | SUSE CVE CVE-2022-49934 | known affected: 429 known not affected: 196 recommended: 357 | 2026-07-26T00:08:45+00:00 | Vulnerability · Source |
| CVE-2022-49956 | suse_vex | SUSE CVE CVE-2022-49956 | known not affected: 264 recommended: 272 | 2026-07-26T00:08:44+00:00 | Vulnerability · Source |
| CVE-2022-50028 | suse_vex | SUSE CVE CVE-2022-50028 | known affected: 425 known not affected: 228 recommended: 300 | 2026-07-26T00:08:42+00:00 | Vulnerability · Source |
| CVE-2022-50106 | suse_vex | SUSE CVE CVE-2022-50106 | known affected: 61 known not affected: 355 | 2026-07-26T00:08:40+00:00 | Vulnerability · Source |
| CVE-2022-50123 | suse_vex | SUSE CVE CVE-2022-50123 | known affected: 61 known not affected: 353 recommended: 27 | 2026-07-26T00:08:38+00:00 | Vulnerability · Source |
| CVE-2022-50132 | suse_vex | SUSE CVE CVE-2022-50132 | known affected: 344 known not affected: 298 recommended: 233 | 2026-07-26T00:08:36+00:00 | Vulnerability · Source |
| CVE-2022-50173 | suse_vex | SUSE CVE CVE-2022-50173 | known affected: 344 known not affected: 283 recommended: 296 | 2026-07-26T00:08:31+00:00 | Vulnerability · Source |
| CVE-2022-50225 | suse_vex | SUSE CVE CVE-2022-50225 | known affected: 55 known not affected: 346 | 2026-07-26T00:08:26+00:00 | Vulnerability · Source |
| CVE-2022-50278 | suse_vex | SUSE CVE CVE-2022-50278 | known affected: 468 known not affected: 181 recommended: 243 | 2026-07-26T00:08:23+00:00 | Vulnerability · Source |
| CVE-2022-50319 | suse_vex | SUSE CVE CVE-2022-50319 | known affected: 55 known not affected: 361 recommended: 43 | 2026-07-26T00:08:19+00:00 | Vulnerability · Source |
| CVE-2022-50350 | suse_vex | SUSE CVE CVE-2022-50350 | known affected: 630 known not affected: 181 recommended: 84 | 2026-07-26T00:08:16+00:00 | Vulnerability · Source |
| CVE-2022-50449 | suse_vex | SUSE CVE CVE-2022-50449 | known affected: 456 known not affected: 160 recommended: 206 | 2026-07-26T00:08:13+00:00 | Vulnerability · Source |
| CVE-2022-50536 | suse_vex | SUSE CVE CVE-2022-50536 | known affected: 55 known not affected: 331 recommended: 72 | 2026-07-26T00:08:10+00:00 | Vulnerability · Source |
| CVE-2022-50580 | suse_vex | SUSE CVE CVE-2022-50580 | known affected: 472 known not affected: 171 recommended: 260 | 2026-07-26T00:08:07+00:00 | Vulnerability · Source |
| CVE-2022-50667 | suse_vex | SUSE CVE CVE-2022-50667 | known affected: 374 known not affected: 351 recommended: 136 | 2026-07-26T00:08:04+00:00 | Vulnerability · Source |
| CVE-2022-50733 | suse_vex | SUSE CVE CVE-2022-50733 | known affected: 437 known not affected: 223 recommended: 272 | 2026-07-26T00:08:00+00:00 | Vulnerability · Source |
| CVE-2022-50750 | suse_vex | SUSE CVE CVE-2022-50750 | known affected: 354 known not affected: 286 recommended: 245 | 2026-07-26T00:07:55+00:00 | Vulnerability · Source |
| CVE-2022-50764 | suse_vex | SUSE CVE CVE-2022-50764 | known affected: 218 known not affected: 171 | 2026-07-26T00:07:52+00:00 | Vulnerability · Source |
| CVE-2022-50782 | suse_vex | SUSE CVE CVE-2022-50782 | known affected: 470 known not affected: 193 recommended: 262 | 2026-07-26T00:07:50+00:00 | Vulnerability · Source |
| CVE-2022-50853 | suse_vex | SUSE CVE CVE-2022-50853 | known affected: 354 known not affected: 341 recommended: 196 | 2026-07-26T00:07:48+00:00 | Vulnerability · Source |
| CVE-2023-0668 | suse_vex | SUSE CVE CVE-2023-0668 | known affected: 103 known not affected: 137 recommended: 195 | 2026-07-26T00:07:43+00:00 | Vulnerability · Source |
| CVE-2023-0803 | suse_vex | SUSE CVE CVE-2023-0803 | known affected: 494 known not affected: 1 recommended: 161 | 2026-07-26T00:07:41+00:00 | Vulnerability · Source |
| CVE-2023-6247 | suse_vex | SUSE CVE CVE-2023-6247 | known not affected: 102 | 2026-07-26T00:07:28+00:00 | Vulnerability · Source |
| CVE-2023-7207 | suse_vex | SUSE CVE CVE-2023-7207 | known affected: 279 recommended: 284 | 2026-07-26T00:07:25+00:00 | Vulnerability · Source |
| CVE-2023-23601 | suse_vex | SUSE CVE CVE-2023-23601 | known affected: 36 recommended: 320 | 2026-07-26T00:07:21+00:00 | Vulnerability · Source |
| CVE-2023-25750 | suse_vex | SUSE CVE CVE-2023-25750 | known affected: 1 recommended: 214 | 2026-07-26T00:07:18+00:00 | Vulnerability · Source |
| CVE-2023-26606 | suse_vex | SUSE CVE CVE-2023-26606 | known not affected: 284 | 2026-07-26T00:07:17+00:00 | Vulnerability · Source |
| CVE-2023-28162 | suse_vex | SUSE CVE CVE-2023-28162 | known affected: 1 recommended: 304 | 2026-07-26T00:07:15+00:00 | Vulnerability · Source |
| CVE-2023-32636 | suse_vex | SUSE CVE CVE-2023-32636 | known not affected: 598 recommended: 64 | 2026-07-26T00:07:11+00:00 | Vulnerability · Source |
| CVE-2023-32763 | suse_vex | SUSE CVE CVE-2023-32763 | known affected: 530 known not affected: 2 recommended: 2773 | 2026-07-26T00:07:09+00:00 | Vulnerability · Source |
| CVE-2023-33850 | suse_vex | SUSE CVE CVE-2023-33850 | known affected: 394 recommended: 125 | 2026-07-26T00:07:08+00:00 | Vulnerability · Source |
| CVE-2023-34981 | suse_vex | SUSE CVE CVE-2023-34981 | known not affected: 333 | 2026-07-26T00:07:06+00:00 | Vulnerability · Source |
| CVE-2023-40481 | suse_vex | SUSE CVE CVE-2023-40481 | known not affected: 79 | 2026-07-26T00:07:02+00:00 | Vulnerability · Source |
| CVE-2023-45898 | suse_vex | SUSE CVE CVE-2023-45898 | known not affected: 337 | 2026-07-26T00:07:00+00:00 | Vulnerability · Source |
| CVE-2023-46835 | suse_vex | SUSE CVE CVE-2023-46835 | known affected: 283 recommended: 426 | 2026-07-26T00:06:58+00:00 | Vulnerability · Source |
| CVE-2023-52747 | suse_vex | SUSE CVE CVE-2023-52747 | known affected: 397 known not affected: 70 recommended: 522 | 2026-07-26T00:06:45+00:00 | Vulnerability · Source |
| CVE-2023-52779 | suse_vex | SUSE CVE CVE-2023-52779 | known not affected: 330 | 2026-07-26T00:06:44+00:00 | Vulnerability · Source |