VEX records
Browse vendor VEX statements available in this Vulnerability-Lookup instance and pivot to the related vulnerability.
99436 VEX records
API response| Vulnerability | Source | Title | Product status | Imported | Links |
|---|---|---|---|---|---|
| CVE-2022-20001 | suse_vex | SUSE CVE CVE-2022-20001 | known affected: 0 known not affected: 16 recommended: 14 | 2026-10-16T14:55:27+00:00 | Vulnerability · Source |
| CVE-2022-20118 | suse_vex | SUSE CVE CVE-2022-20118 | known affected: 0 known not affected: 418 | 2026-10-16T14:55:24+00:00 | Vulnerability · Source |
| CVE-2022-20119 | suse_vex | SUSE CVE CVE-2022-20119 | known affected: 0 known not affected: 418 | 2026-10-16T14:55:23+00:00 | Vulnerability · Source |
| CVE-2022-20132 | suse_vex | SUSE CVE CVE-2022-20132 | known affected: 219 recommended: 1529 | 2026-10-16T14:55:21+00:00 | Vulnerability · Source |
| CVE-2022-20148 | suse_vex | SUSE CVE CVE-2022-20148 | known affected: 0 known not affected: 405 | 2026-10-16T14:55:19+00:00 | Vulnerability · Source |
| CVE-2022-20154 | suse_vex | SUSE CVE CVE-2022-20154 | known affected: 130 known not affected: 204 recommended: 1894 | 2026-10-16T14:55:17+00:00 | Vulnerability · Source |
| CVE-2022-20368 | suse_vex | SUSE CVE CVE-2022-20368 | known affected: 173 recommended: 1749 | 2026-10-16T14:55:15+00:00 | Vulnerability · Source |
| CVE-2022-20421 | suse_vex | SUSE CVE CVE-2022-20421 | known affected: 0 known not affected: 216 | 2026-10-16T14:55:13+00:00 | Vulnerability · Source |
| CVE-2022-20567 | suse_vex | SUSE CVE CVE-2022-20567 | known affected: 394 known not affected: 202 recommended: 204 | 2026-10-16T14:55:11+00:00 | Vulnerability · Source |
| CVE-2022-20572 | suse_vex | SUSE CVE CVE-2022-20572 | known affected: 0 known not affected: 350 recommended: 42 | 2026-10-16T14:55:09+00:00 | Vulnerability · Source |
| CVE-2022-20698 | suse_vex | SUSE CVE CVE-2022-20698 | known affected: 1 recommended: 282 | 2026-10-16T14:55:08+00:00 | Vulnerability · Source |
| CVE-2022-20785 | suse_vex | SUSE CVE CVE-2022-20785 | known affected: 59 recommended: 186 | 2026-10-16T14:55:05+00:00 | Vulnerability · Source |
| CVE-2022-21123 | suse_vex | SUSE CVE CVE-2022-21123 | known affected: 225 recommended: 1976 | 2026-10-16T14:55:02+00:00 | Vulnerability · Source |
| CVE-2022-21125 | suse_vex | SUSE CVE CVE-2022-21125 | known affected: 254 recommended: 1938 | 2026-10-16T14:54:59+00:00 | Vulnerability · Source |
| CVE-2022-21127 | suse_vex | SUSE CVE CVE-2022-21127 | recommended: 1352 | 2026-10-16T14:54:57+00:00 | Vulnerability · Source |
| CVE-2022-21131 | suse_vex | SUSE CVE CVE-2022-21131 | known affected: 0 known not affected: 91 | 2026-10-16T14:54:54+00:00 | Vulnerability · Source |
| CVE-2022-21151 | suse_vex | SUSE CVE CVE-2022-21151 | recommended: 87 | 2026-10-16T14:54:52+00:00 | Vulnerability · Source |
| CVE-2022-21166 | suse_vex | SUSE CVE CVE-2022-21166 | known affected: 216 recommended: 1977 | 2026-10-16T14:54:49+00:00 | Vulnerability · Source |
| CVE-2022-21216 | suse_vex | SUSE CVE CVE-2022-21216 | recommended: 71 | 2026-10-16T14:54:47+00:00 | Vulnerability · Source |
| CVE-2022-21233 | suse_vex | SUSE CVE CVE-2022-21233 | recommended: 81 | 2026-10-16T14:54:45+00:00 | Vulnerability · Source |
| CVE-2022-21277 | suse_vex | SUSE CVE CVE-2022-21277 | known affected: 475 known not affected: 32 recommended: 769 | 2026-10-16T14:54:43+00:00 | Vulnerability · Source |
| CVE-2022-21283 | suse_vex | SUSE CVE CVE-2022-21283 | known affected: 474 known not affected: 32 recommended: 1002 | 2026-10-16T14:54:40+00:00 | Vulnerability · Source |
| CVE-2022-21293 | suse_vex | SUSE CVE CVE-2022-21293 | known affected: 406 known not affected: 32 recommended: 1062 | 2026-10-16T14:54:37+00:00 | Vulnerability · Source |
| CVE-2022-21299 | suse_vex | SUSE CVE CVE-2022-21299 | known affected: 406 known not affected: 32 recommended: 1085 | 2026-10-16T14:54:34+00:00 | Vulnerability · Source |
| CVE-2022-21340 | suse_vex | SUSE CVE CVE-2022-21340 | known affected: 406 known not affected: 32 recommended: 1055 | 2026-10-16T14:54:32+00:00 | Vulnerability · Source |
| CVE-2022-21360 | suse_vex | SUSE CVE CVE-2022-21360 | known affected: 406 known not affected: 32 recommended: 1055 | 2026-10-16T14:54:30+00:00 | Vulnerability · Source |
| CVE-2022-21366 | suse_vex | SUSE CVE CVE-2022-21366 | known affected: 394 known not affected: 302 recommended: 769 | 2026-10-16T14:54:27+00:00 | Vulnerability · Source |
| CVE-2022-21412 | suse_vex | SUSE CVE CVE-2022-21412 | recommended: 24 | 2026-10-16T14:54:25+00:00 | Vulnerability · Source |
| CVE-2022-21414 | suse_vex | SUSE CVE CVE-2022-21414 | recommended: 24 | 2026-10-16T14:54:22+00:00 | Vulnerability · Source |
| CVE-2022-21417 | suse_vex | SUSE CVE CVE-2022-21417 | recommended: 24 | 2026-10-16T14:54:19+00:00 | Vulnerability · Source |
| CVE-2022-21425 | suse_vex | SUSE CVE CVE-2022-21425 | recommended: 24 | 2026-10-16T14:54:17+00:00 | Vulnerability · Source |
| CVE-2022-21434 | suse_vex | SUSE CVE CVE-2022-21434 | known affected: 406 known not affected: 75 recommended: 1236 | 2026-10-16T14:54:15+00:00 | Vulnerability · Source |
| CVE-2022-21436 | suse_vex | SUSE CVE CVE-2022-21436 | recommended: 24 | 2026-10-16T14:54:13+00:00 | Vulnerability · Source |
| CVE-2022-21437 | suse_vex | SUSE CVE CVE-2022-21437 | recommended: 24 | 2026-10-16T14:54:12+00:00 | Vulnerability · Source |
| CVE-2022-21444 | suse_vex | SUSE CVE CVE-2022-21444 | recommended: 24 | 2026-10-16T14:54:10+00:00 | Vulnerability · Source |
| CVE-2022-21449 | suse_vex | SUSE CVE CVE-2022-21449 | known affected: 1 known not affected: 490 recommended: 521 | 2026-10-16T14:54:08+00:00 | Vulnerability · Source |
| CVE-2022-21462 | suse_vex | SUSE CVE CVE-2022-21462 | recommended: 24 | 2026-10-16T14:54:06+00:00 | Vulnerability · Source |
| CVE-2022-21478 | suse_vex | SUSE CVE CVE-2022-21478 | recommended: 24 | 2026-10-16T14:54:04+00:00 | Vulnerability · Source |
| CVE-2022-21482 | suse_vex | SUSE CVE CVE-2022-21482 | No product status | 2026-10-16T14:54:02+00:00 | Vulnerability · Source |
| CVE-2022-21485 | suse_vex | SUSE CVE CVE-2022-21485 | No product status | 2026-10-16T14:54:00+00:00 | Vulnerability · Source |
| CVE-2022-21486 | suse_vex | SUSE CVE CVE-2022-21486 | No product status | 2026-10-16T14:53:59+00:00 | Vulnerability · Source |
| CVE-2022-21505 | suse_vex | SUSE CVE CVE-2022-21505 | known affected: 234 known not affected: 199 recommended: 1135 | 2026-10-16T14:53:57+00:00 | Vulnerability · Source |
| CVE-2022-21530 | suse_vex | SUSE CVE CVE-2022-21530 | recommended: 24 | 2026-10-16T14:53:55+00:00 | Vulnerability · Source |
| CVE-2022-21541 | suse_vex | SUSE CVE CVE-2022-21541 | known affected: 397 known not affected: 27 recommended: 1256 | 2026-10-16T14:53:53+00:00 | Vulnerability · Source |
| CVE-2022-21549 | suse_vex | SUSE CVE CVE-2022-21549 | known affected: 395 known not affected: 431 recommended: 537 | 2026-10-16T14:53:51+00:00 | Vulnerability · Source |
| CVE-2022-21599 | suse_vex | SUSE CVE CVE-2022-21599 | recommended: 25 | 2026-10-16T14:53:49+00:00 | Vulnerability · Source |
| CVE-2022-21619 | suse_vex | SUSE CVE CVE-2022-21619 | known affected: 396 recommended: 1197 | 2026-10-16T14:53:46+00:00 | Vulnerability · Source |
| CVE-2022-21624 | suse_vex | SUSE CVE CVE-2022-21624 | known affected: 396 recommended: 1197 | 2026-10-16T14:53:44+00:00 | Vulnerability · Source |
| CVE-2022-21682 | suse_vex | SUSE CVE CVE-2022-21682 | known affected: 0 known not affected: 56 recommended: 323 | 2026-10-16T14:53:42+00:00 | Vulnerability · Source |
| CVE-2022-21698 | suse_vex | SUSE CVE CVE-2022-21698 | known affected: 30 known not affected: 99 recommended: 641 | 2026-10-16T14:53:40+00:00 | Vulnerability · Source |