VEX records
Browse vendor VEX statements available in this Vulnerability-Lookup instance and pivot to the related vulnerability.
283120 VEX records
API response| Vulnerability | Source | Title | Product status | Imported | Links |
|---|---|---|---|---|---|
| CVE-2022-3953 | suse_vex | SUSE CVE CVE-2022-3953 | known not affected: 135 recommended: 10 | 2026-07-19T18:13:15+00:00 | Vulnerability · Source |
| CVE-2022-3970 | suse_vex | SUSE CVE CVE-2022-3970 | known affected: 394 known not affected: 29 recommended: 261 | 2026-07-19T18:13:13+00:00 | Vulnerability · Source |
| CVE-2022-3996 | suse_vex | SUSE CVE CVE-2022-3996 | known not affected: 632 recommended: 136 | 2026-07-19T18:13:12+00:00 | Vulnerability · Source |
| CVE-2022-4203 | suse_vex | SUSE CVE CVE-2022-4203 | known not affected: 480 recommended: 142 | 2026-07-19T18:13:11+00:00 | Vulnerability · Source |
| CVE-2022-4515 | suse_vex | SUSE CVE CVE-2022-4515 | known affected: 1 recommended: 56 | 2026-07-19T18:13:09+00:00 | Vulnerability · Source |
| CVE-2022-4806 | suse_vex | SUSE CVE CVE-2022-4806 | recommended: 26 | 2026-07-19T18:13:08+00:00 | Vulnerability · Source |
| CVE-2022-4883 | suse_vex | SUSE CVE CVE-2022-4883 | known affected: 395 recommended: 162 | 2026-07-19T18:13:07+00:00 | Vulnerability · Source |
| CVE-2022-20698 | suse_vex | SUSE CVE CVE-2022-20698 | known affected: 1 recommended: 273 | 2026-07-19T18:13:05+00:00 | Vulnerability · Source |
| CVE-2022-20771 | suse_vex | SUSE CVE CVE-2022-20771 | known affected: 49 recommended: 179 | 2026-07-19T18:13:04+00:00 | Vulnerability · Source |
| CVE-2022-20792 | suse_vex | SUSE CVE CVE-2022-20792 | known affected: 49 recommended: 179 | 2026-07-19T18:13:03+00:00 | Vulnerability · Source |
| CVE-2022-21283 | suse_vex | SUSE CVE CVE-2022-21283 | known affected: 466 known not affected: 32 recommended: 960 | 2026-07-19T18:13:01+00:00 | Vulnerability · Source |
| CVE-2022-21296 | suse_vex | SUSE CVE CVE-2022-21296 | known affected: 406 known not affected: 32 recommended: 1020 | 2026-07-19T18:13:00+00:00 | Vulnerability · Source |
| CVE-2022-21443 | suse_vex | SUSE CVE CVE-2022-21443 | known affected: 406 known not affected: 67 recommended: 1146 | 2026-07-19T18:12:59+00:00 | Vulnerability · Source |
| CVE-2022-21540 | suse_vex | SUSE CVE CVE-2022-21540 | known affected: 397 known not affected: 22 recommended: 1174 | 2026-07-19T18:12:57+00:00 | Vulnerability · Source |
| CVE-2022-21619 | suse_vex | SUSE CVE CVE-2022-21619 | known affected: 396 recommended: 1112 | 2026-07-19T18:12:55+00:00 | Vulnerability · Source |
| CVE-2022-21698 | suse_vex | SUSE CVE CVE-2022-21698 | known affected: 32 known not affected: 98 recommended: 624 | 2026-07-19T18:12:54+00:00 | Vulnerability · Source |
| CVE-2022-22594 | suse_vex | SUSE CVE CVE-2022-22594 | known not affected: 9 recommended: 913 | 2026-07-19T18:12:53+00:00 | Vulnerability · Source |
| CVE-2022-22624 | suse_vex | SUSE CVE CVE-2022-22624 | known affected: 24 known not affected: 344 recommended: 923 | 2026-07-19T18:12:51+00:00 | Vulnerability · Source |
| CVE-2022-22637 | suse_vex | SUSE CVE CVE-2022-22637 | known affected: 24 known not affected: 344 recommended: 913 | 2026-07-19T18:12:50+00:00 | Vulnerability · Source |
| CVE-2022-22677 | suse_vex | SUSE CVE CVE-2022-22677 | known affected: 25 recommended: 938 | 2026-07-19T18:12:48+00:00 | Vulnerability · Source |
| CVE-2022-22738 | suse_vex | SUSE CVE CVE-2022-22738 | recommended: 401 | 2026-07-19T18:12:47+00:00 | Vulnerability · Source |
| CVE-2022-22745 | suse_vex | SUSE CVE CVE-2022-22745 | recommended: 401 | 2026-07-19T18:12:46+00:00 | Vulnerability · Source |
| CVE-2022-22747 | suse_vex | SUSE CVE CVE-2022-22747 | recommended: 401 | 2026-07-19T18:12:45+00:00 | Vulnerability · Source |
| CVE-2022-22748 | suse_vex | SUSE CVE CVE-2022-22748 | recommended: 401 | 2026-07-19T18:12:44+00:00 | Vulnerability · Source |
| CVE-2022-22763 | suse_vex | SUSE CVE CVE-2022-22763 | recommended: 387 | 2026-07-19T18:12:42+00:00 | Vulnerability · Source |
| CVE-2022-22764 | suse_vex | SUSE CVE CVE-2022-22764 | recommended: 396 | 2026-07-19T18:12:41+00:00 | Vulnerability · Source |
| CVE-2022-22817 | suse_vex | SUSE CVE CVE-2022-22817 | recommended: 138 | 2026-07-19T18:12:40+00:00 | Vulnerability · Source |
| CVE-2022-22822 | suse_vex | SUSE CVE CVE-2022-22822 | known affected: 330 known not affected: 32 recommended: 374 | 2026-07-19T18:12:38+00:00 | Vulnerability · Source |
| CVE-2022-23308 | suse_vex | SUSE CVE CVE-2022-23308 | known affected: 216 known not affected: 44 recommended: 644 | 2026-07-19T18:12:37+00:00 | Vulnerability · Source |
| CVE-2022-23491 | suse_vex | SUSE CVE CVE-2022-23491 | known affected: 321 known not affected: 68 recommended: 1019 | 2026-07-19T18:12:35+00:00 | Vulnerability · Source |
| CVE-2022-23648 | suse_vex | SUSE CVE CVE-2022-23648 | known affected: 341 recommended: 348 | 2026-07-19T18:12:34+00:00 | Vulnerability · Source |
| CVE-2022-23649 | suse_vex | SUSE CVE CVE-2022-23649 | known not affected: 8 recommended: 39 | 2026-07-19T18:12:33+00:00 | Vulnerability · Source |
| CVE-2022-23806 | suse_vex | SUSE CVE CVE-2022-23806 | known not affected: 8 recommended: 294 | 2026-07-19T18:12:31+00:00 | Vulnerability · Source |
| CVE-2022-23852 | suse_vex | SUSE CVE CVE-2022-23852 | known affected: 339 known not affected: 32 recommended: 373 | 2026-07-19T18:12:30+00:00 | Vulnerability · Source |
| CVE-2022-23949 | suse_vex | SUSE CVE CVE-2022-23949 | known not affected: 72 recommended: 201 | 2026-07-19T18:12:29+00:00 | Vulnerability · Source |
| CVE-2022-23960 | suse_vex | SUSE CVE CVE-2022-23960 | known affected: 394 known not affected: 376 recommended: 804 | 2026-07-19T18:12:28+00:00 | Vulnerability · Source |
| CVE-2022-24050 | suse_vex | SUSE CVE CVE-2022-24050 | known affected: 1 recommended: 484 | 2026-07-19T18:12:26+00:00 | Vulnerability · Source |
| CVE-2022-24052 | suse_vex | SUSE CVE CVE-2022-24052 | known affected: 1 recommended: 484 | 2026-07-19T18:12:25+00:00 | Vulnerability · Source |
| CVE-2022-24439 | suse_vex | SUSE CVE CVE-2022-24439 | known not affected: 3 recommended: 14 | 2026-07-19T18:12:24+00:00 | Vulnerability · Source |
| CVE-2022-24791 | suse_vex | SUSE CVE CVE-2022-24791 | recommended: 3 | 2026-07-19T18:12:23+00:00 | Vulnerability · Source |
| CVE-2022-24795 | suse_vex | SUSE CVE CVE-2022-24795 | known affected: 267 recommended: 289 | 2026-07-19T18:12:22+00:00 | Vulnerability · Source |
| CVE-2022-24809 | suse_vex | SUSE CVE CVE-2022-24809 | known affected: 394 known not affected: 169 recommended: 249 | 2026-07-19T18:12:20+00:00 | Vulnerability · Source |
| CVE-2022-24903 | suse_vex | SUSE CVE CVE-2022-24903 | known affected: 144 known not affected: 66 recommended: 914 | 2026-07-19T18:12:19+00:00 | Vulnerability · Source |
| CVE-2022-25236 | suse_vex | SUSE CVE CVE-2022-25236 | known affected: 172 known not affected: 26 recommended: 1123 | 2026-07-19T18:12:17+00:00 | Vulnerability · Source |
| CVE-2022-25315 | suse_vex | SUSE CVE CVE-2022-25315 | known affected: 282 recommended: 432 | 2026-07-19T18:12:16+00:00 | Vulnerability · Source |
| CVE-2022-26354 | suse_vex | SUSE CVE CVE-2022-26354 | known affected: 530 known not affected: 291 recommended: 1424 | 2026-07-19T18:12:14+00:00 | Vulnerability · Source |
| CVE-2022-26381 | suse_vex | SUSE CVE CVE-2022-26381 | known affected: 1 recommended: 399 | 2026-07-19T18:12:13+00:00 | Vulnerability · Source |
| CVE-2022-26387 | suse_vex | SUSE CVE CVE-2022-26387 | known affected: 1 recommended: 399 | 2026-07-19T18:12:12+00:00 | Vulnerability · Source |
| CVE-2022-26486 | suse_vex | SUSE CVE CVE-2022-26486 | known affected: 13 recommended: 390 | 2026-07-19T18:12:10+00:00 | Vulnerability · Source |
| CVE-2022-26700 | suse_vex | SUSE CVE CVE-2022-26700 | known affected: 1 recommended: 987 | 2026-07-19T18:12:09+00:00 | Vulnerability · Source |