VEX records
Browse vendor VEX statements available in this Vulnerability-Lookup instance and pivot to the related vulnerability.
287177 VEX records
API response| Vulnerability | Source | Title | Product status | Imported | Links |
|---|---|---|---|---|---|
| CVE-2021-47121 | suse_vex | SUSE CVE CVE-2021-47121 | known affected: 60 known not affected: 309 | 2026-07-31T01:34:41+00:00 | Vulnerability · Source |
| CVE-2021-47147 | suse_vex | SUSE CVE CVE-2021-47147 | known not affected: 292 | 2026-07-31T01:34:40+00:00 | Vulnerability · Source |
| CVE-2021-47180 | suse_vex | SUSE CVE CVE-2021-47180 | known affected: 477 known not affected: 207 recommended: 221 | 2026-07-31T01:34:36+00:00 | Vulnerability · Source |
| CVE-2021-47244 | suse_vex | SUSE CVE CVE-2021-47244 | known not affected: 330 | 2026-07-31T01:34:34+00:00 | Vulnerability · Source |
| CVE-2021-47318 | suse_vex | SUSE CVE CVE-2021-47318 | known not affected: 325 | 2026-07-31T01:34:28+00:00 | Vulnerability · Source |
| CVE-2021-47361 | suse_vex | SUSE CVE CVE-2021-47361 | known affected: 397 known not affected: 70 recommended: 522 | 2026-07-31T01:34:26+00:00 | Vulnerability · Source |
| CVE-2021-47407 | suse_vex | SUSE CVE CVE-2021-47407 | known affected: 395 known not affected: 70 recommended: 522 | 2026-07-31T01:34:22+00:00 | Vulnerability · Source |
| CVE-2021-47408 | suse_vex | SUSE CVE CVE-2021-47408 | known affected: 415 known not affected: 80 recommended: 484 | 2026-07-31T01:34:20+00:00 | Vulnerability · Source |
| CVE-2021-47414 | suse_vex | SUSE CVE CVE-2021-47414 | known affected: 275 known not affected: 158 recommended: 452 | 2026-07-31T01:34:19+00:00 | Vulnerability · Source |
| CVE-2021-47422 | suse_vex | SUSE CVE CVE-2021-47422 | known affected: 269 known not affected: 181 recommended: 543 | 2026-07-31T01:34:18+00:00 | Vulnerability · Source |
| CVE-2021-47440 | suse_vex | SUSE CVE CVE-2021-47440 | known affected: 291 known not affected: 285 recommended: 452 | 2026-07-31T01:34:16+00:00 | Vulnerability · Source |
| CVE-2021-47441 | suse_vex | SUSE CVE CVE-2021-47441 | known affected: 336 known not affected: 70 recommended: 704 | 2026-07-31T01:34:15+00:00 | Vulnerability · Source |
| CVE-2021-47498 | suse_vex | SUSE CVE CVE-2021-47498 | known affected: 377 known not affected: 67 recommended: 647 | 2026-07-31T01:34:10+00:00 | Vulnerability · Source |
| CVE-2021-47531 | suse_vex | SUSE CVE CVE-2021-47531 | known affected: 315 known not affected: 268 recommended: 313 | 2026-07-31T01:34:08+00:00 | Vulnerability · Source |
| CVE-2021-47540 | suse_vex | SUSE CVE CVE-2021-47540 | known affected: 269 known not affected: 181 recommended: 543 | 2026-07-31T01:34:06+00:00 | Vulnerability · Source |
| CVE-2021-47546 | suse_vex | SUSE CVE CVE-2021-47546 | known affected: 357 known not affected: 181 recommended: 302 | 2026-07-31T01:34:04+00:00 | Vulnerability · Source |
| CVE-2021-47581 | suse_vex | SUSE CVE CVE-2021-47581 | known not affected: 318 | 2026-07-31T01:34:02+00:00 | Vulnerability · Source |
| CVE-2021-47609 | suse_vex | SUSE CVE CVE-2021-47609 | known affected: 416 known not affected: 70 recommended: 572 | 2026-07-31T01:34:00+00:00 | Vulnerability · Source |
| CVE-2021-47659 | suse_vex | SUSE CVE CVE-2021-47659 | known affected: 407 known not affected: 270 recommended: 319 | 2026-07-31T01:33:58+00:00 | Vulnerability · Source |
| CVE-2022-0286 | suse_vex | SUSE CVE CVE-2022-0286 | known affected: 344 known not affected: 580 recommended: 433 | 2026-07-31T01:33:56+00:00 | Vulnerability · Source |
| CVE-2022-0742 | suse_vex | SUSE CVE CVE-2022-0742 | known not affected: 401 recommended: 364 | 2026-07-31T01:33:53+00:00 | Vulnerability · Source |
| CVE-2022-0886 | suse_vex | SUSE CVE CVE-2022-0886 | known affected: 347 known not affected: 208 recommended: 471 | 2026-07-31T01:33:51+00:00 | Vulnerability · Source |
| CVE-2022-1196 | suse_vex | SUSE CVE CVE-2022-1196 | known affected: 3 known not affected: 128 recommended: 396 | 2026-07-31T01:33:49+00:00 | Vulnerability · Source |
| CVE-2022-1292 | suse_vex | SUSE CVE CVE-2022-1292 | known affected: 213 known not affected: 98 recommended: 1123 | 2026-07-31T01:33:47+00:00 | Vulnerability · Source |
| CVE-2022-1552 | suse_vex | SUSE CVE CVE-2022-1552 | known affected: 394 known not affected: 93 recommended: 2080 | 2026-07-31T01:33:44+00:00 | Vulnerability · Source |
| CVE-2022-1678 | suse_vex | SUSE CVE CVE-2022-1678 | known not affected: 390 | 2026-07-31T01:33:42+00:00 | Vulnerability · Source |
| CVE-2022-1802 | suse_vex | SUSE CVE CVE-2022-1802 | known affected: 1 recommended: 405 | 2026-07-31T01:33:40+00:00 | Vulnerability · Source |
| CVE-2022-2125 | suse_vex | SUSE CVE CVE-2022-2125 | known affected: 247 recommended: 505 | 2026-07-31T01:33:38+00:00 | Vulnerability · Source |
| CVE-2022-2264 | suse_vex | SUSE CVE CVE-2022-2264 | known affected: 237 known not affected: 26 recommended: 505 | 2026-07-31T01:33:34+00:00 | Vulnerability · Source |
| CVE-2022-2308 | suse_vex | SUSE CVE CVE-2022-2308 | known not affected: 564 recommended: 6 | 2026-07-31T01:33:32+00:00 | Vulnerability · Source |
| CVE-2022-2889 | suse_vex | SUSE CVE CVE-2022-2889 | known affected: 237 known not affected: 2 recommended: 505 | 2026-07-31T01:33:28+00:00 | Vulnerability · Source |
| CVE-2022-3115 | suse_vex | SUSE CVE CVE-2022-3115 | known affected: 272 known not affected: 255 recommended: 880 | 2026-07-31T01:33:26+00:00 | Vulnerability · Source |
| CVE-2022-3534 | suse_vex | SUSE CVE CVE-2022-3534 | known not affected: 95 recommended: 60 | 2026-07-31T01:33:23+00:00 | Vulnerability · Source |
| CVE-2022-3566 | suse_vex | SUSE CVE CVE-2022-3566 | known affected: 275 known not affected: 276 recommended: 1157 | 2026-07-31T01:33:21+00:00 | Vulnerability · Source |
| CVE-2022-3567 | suse_vex | SUSE CVE CVE-2022-3567 | known affected: 269 known not affected: 257 recommended: 1589 | 2026-07-31T01:33:19+00:00 | Vulnerability · Source |
| CVE-2022-3624 | suse_vex | SUSE CVE CVE-2022-3624 | known not affected: 564 | 2026-07-31T01:33:17+00:00 | Vulnerability · Source |
| CVE-2022-3629 | suse_vex | SUSE CVE CVE-2022-3629 | known affected: 261 known not affected: 325 recommended: 1465 | 2026-07-31T01:33:15+00:00 | Vulnerability · Source |
| CVE-2022-3630 | suse_vex | SUSE CVE CVE-2022-3630 | known not affected: 564 | 2026-07-31T01:33:13+00:00 | Vulnerability · Source |
| CVE-2022-3633 | suse_vex | SUSE CVE CVE-2022-3633 | known affected: 271 known not affected: 568 recommended: 635 | 2026-07-31T01:33:11+00:00 | Vulnerability · Source |
| CVE-2022-3636 | suse_vex | SUSE CVE CVE-2022-3636 | known not affected: 720 | 2026-07-31T01:33:09+00:00 | Vulnerability · Source |
| CVE-2022-4603 | suse_vex | SUSE CVE CVE-2022-4603 | known affected: 95 recommended: 61 | 2026-07-31T01:33:05+00:00 | Vulnerability · Source |
| CVE-2022-21216 | suse_vex | SUSE CVE CVE-2022-21216 | recommended: 71 | 2026-07-31T01:33:00+00:00 | Vulnerability · Source |
| CVE-2022-21538 | suse_vex | SUSE CVE CVE-2022-21538 | recommended: 17 | 2026-07-31T01:32:58+00:00 | Vulnerability · Source |
| CVE-2022-21539 | suse_vex | SUSE CVE CVE-2022-21539 | recommended: 17 | 2026-07-31T01:32:56+00:00 | Vulnerability · Source |
| CVE-2022-22753 | suse_vex | SUSE CVE CVE-2022-22753 | recommended: 404 | 2026-07-31T01:32:53+00:00 | Vulnerability · Source |
| CVE-2022-23041 | suse_vex | SUSE CVE CVE-2022-23041 | known affected: 344 known not affected: 61 recommended: 1327 | 2026-07-31T01:32:50+00:00 | Vulnerability · Source |
| CVE-2022-23478 | suse_vex | SUSE CVE CVE-2022-23478 | known affected: 394 known not affected: 3 recommended: 171 | 2026-07-31T01:32:48+00:00 | Vulnerability · Source |
| CVE-2022-26490 | suse_vex | SUSE CVE CVE-2022-26490 | known affected: 209 known not affected: 21 recommended: 1749 | 2026-07-31T01:32:43+00:00 | Vulnerability · Source |
| CVE-2022-26520 | suse_vex | SUSE CVE CVE-2022-26520 | known affected: 395 known not affected: 28 recommended: 137 | 2026-07-31T01:32:41+00:00 | Vulnerability · Source |
| CVE-2022-28349 | suse_vex | SUSE CVE CVE-2022-28349 | known not affected: 390 | 2026-07-31T01:32:39+00:00 | Vulnerability · Source |