VEX records
Browse vendor VEX statements available in this Vulnerability-Lookup instance and pivot to the related vulnerability.
292076 VEX records
API response| Vulnerability | Source | Title | Product status | Imported | Links |
|---|---|---|---|---|---|
| CVE-2021-3947 | suse_vex | SUSE CVE CVE-2021-3947 | known not affected: 1077 | 2026-07-26T00:12:47+00:00 | Vulnerability · Source |
| CVE-2021-20311 | suse_vex | SUSE CVE CVE-2021-20311 | known not affected: 87 recommended: 568 | 2026-07-26T00:12:38+00:00 | Vulnerability · Source |
| CVE-2021-23983 | suse_vex | SUSE CVE CVE-2021-23983 | recommended: 9 | 2026-07-26T00:12:33+00:00 | Vulnerability · Source |
| CVE-2021-28714 | suse_vex | SUSE CVE CVE-2021-28714 | known affected: 332 known not affected: 70 recommended: 1227 | 2026-07-26T00:12:28+00:00 | Vulnerability · Source |
| CVE-2021-33430 | suse_vex | SUSE CVE CVE-2021-33430 | known affected: 409 known not affected: 11 recommended: 420 | 2026-07-26T00:12:20+00:00 | Vulnerability · Source |
| CVE-2021-41079 | suse_vex | SUSE CVE CVE-2021-41079 | known affected: 394 known not affected: 129 recommended: 536 | 2026-07-26T00:12:12+00:00 | Vulnerability · Source |
| CVE-2021-41617 | suse_vex | SUSE CVE CVE-2021-41617 | known affected: 331 recommended: 549 | 2026-07-26T00:12:09+00:00 | Vulnerability · Source |
| CVE-2021-47010 | suse_vex | SUSE CVE CVE-2021-47010 | known not affected: 292 | 2026-07-26T00:12:05+00:00 | Vulnerability · Source |
| CVE-2021-47158 | suse_vex | SUSE CVE CVE-2021-47158 | known affected: 55 known not affected: 298 | 2026-07-26T00:12:01+00:00 | Vulnerability · Source |
| CVE-2021-47241 | suse_vex | SUSE CVE CVE-2021-47241 | known affected: 388 known not affected: 294 recommended: 91 | 2026-07-26T00:11:54+00:00 | Vulnerability · Source |
| CVE-2022-1508 | suse_vex | SUSE CVE CVE-2022-1508 | known affected: 257 known not affected: 343 recommended: 615 | 2026-07-26T00:11:30+00:00 | Vulnerability · Source |
| CVE-2022-4129 | suse_vex | SUSE CVE CVE-2022-4129 | known affected: 273 known not affected: 122 recommended: 1474 | 2026-07-26T00:11:14+00:00 | Vulnerability · Source |
| CVE-2022-23131 | suse_vex | SUSE CVE CVE-2022-23131 | known not affected: 37 | 2026-07-26T00:10:58+00:00 | Vulnerability · Source |
| CVE-2022-28391 | suse_vex | SUSE CVE CVE-2022-28391 | known affected: 5 known not affected: 63 | 2026-07-26T00:10:47+00:00 | Vulnerability · Source |
| CVE-2022-34473 | suse_vex | SUSE CVE CVE-2022-34473 | known affected: 1 recommended: 365 | 2026-07-26T00:10:38+00:00 | Vulnerability · Source |
| CVE-2022-38177 | suse_vex | SUSE CVE CVE-2022-38177 | known affected: 254 known not affected: 1 recommended: 1064 | 2026-07-26T00:10:35+00:00 | Vulnerability · Source |
| CVE-2022-38235 | suse_vex | SUSE CVE CVE-2022-38235 | known not affected: 330 | 2026-07-26T00:10:32+00:00 | Vulnerability · Source |
| CVE-2022-38349 | suse_vex | SUSE CVE CVE-2022-38349 | known affected: 80 known not affected: 5 recommended: 273 | 2026-07-26T00:10:31+00:00 | Vulnerability · Source |
| CVE-2022-42310 | suse_vex | SUSE CVE CVE-2022-42310 | known affected: 253 recommended: 518 | 2026-07-26T00:10:25+00:00 | Vulnerability · Source |
| CVE-2022-42824 | suse_vex | SUSE CVE CVE-2022-42824 | known affected: 1 known not affected: 164 recommended: 976 | 2026-07-26T00:10:23+00:00 | Vulnerability · Source |
| CVE-2022-47521 | suse_vex | SUSE CVE CVE-2022-47521 | known not affected: 362 | 2026-07-26T00:10:17+00:00 | Vulnerability · Source |
| CVE-2022-48655 | suse_vex | SUSE CVE CVE-2022-48655 | known affected: 265 known not affected: 225 recommended: 462 | 2026-07-26T00:10:15+00:00 | Vulnerability · Source |
| CVE-2022-48750 | suse_vex | SUSE CVE CVE-2022-48750 | known not affected: 318 | 2026-07-26T00:10:11+00:00 | Vulnerability · Source |
| CVE-2022-48857 | suse_vex | SUSE CVE CVE-2022-48857 | known affected: 377 known not affected: 98 recommended: 595 | 2026-07-26T00:10:03+00:00 | Vulnerability · Source |
| CVE-2022-48874 | suse_vex | SUSE CVE CVE-2022-48874 | known not affected: 310 | 2026-07-26T00:10:01+00:00 | Vulnerability · Source |
| CVE-2022-48894 | suse_vex | SUSE CVE CVE-2022-48894 | known not affected: 310 | 2026-07-26T00:09:56+00:00 | Vulnerability · Source |
| 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 |