VEX records
Browse vendor VEX statements available in this Vulnerability-Lookup instance and pivot to the related vulnerability.
283445 VEX records
API response| Vulnerability | Source | Title | Product status | Imported | Links |
|---|---|---|---|---|---|
| CVE-2022-3775 | suse_vex | SUSE CVE CVE-2022-3775 | known affected: 260 recommended: 816 | 2026-07-25T17:28:13+00:00 | Vulnerability · Source |
| CVE-2022-3786 | suse_vex | SUSE CVE CVE-2022-3786 | known not affected: 621 recommended: 171 | 2026-07-25T17:28:11+00:00 | Vulnerability · Source |
| CVE-2022-3821 | suse_vex | SUSE CVE CVE-2022-3821 | known affected: 254 known not affected: 121 recommended: 967 | 2026-07-25T17:28:10+00:00 | Vulnerability · Source |
| CVE-2022-3970 | suse_vex | SUSE CVE CVE-2022-3970 | known affected: 394 known not affected: 29 recommended: 273 | 2026-07-25T17:28:08+00:00 | Vulnerability · Source |
| CVE-2022-3996 | suse_vex | SUSE CVE CVE-2022-3996 | known not affected: 671 recommended: 136 | 2026-07-25T17:28:07+00:00 | Vulnerability · Source |
| CVE-2022-4128 | suse_vex | SUSE CVE CVE-2022-4128 | known not affected: 333 recommended: 27 | 2026-07-25T17:28:05+00:00 | Vulnerability · Source |
| CVE-2022-4269 | suse_vex | SUSE CVE CVE-2022-4269 | known affected: 194 known not affected: 143 recommended: 1126 | 2026-07-25T17:28:04+00:00 | Vulnerability · Source |
| CVE-2022-4303 | suse_vex | SUSE CVE CVE-2022-4303 | recommended: 150 | 2026-07-25T17:28:02+00:00 | Vulnerability · Source |
| CVE-2022-4304 | suse_vex | SUSE CVE CVE-2022-4304 | known affected: 132 known not affected: 103 recommended: 1117 | 2026-07-25T17:28:01+00:00 | Vulnerability · Source |
| CVE-2022-4337 | suse_vex | SUSE CVE CVE-2022-4337 | known affected: 21 known not affected: 60 recommended: 569 | 2026-07-25T17:27:59+00:00 | Vulnerability · Source |
| CVE-2022-4378 | suse_vex | SUSE CVE CVE-2022-4378 | known affected: 267 known not affected: 34 recommended: 1813 | 2026-07-25T17:27:57+00:00 | Vulnerability · Source |
| CVE-2022-4382 | suse_vex | SUSE CVE CVE-2022-4382 | known affected: 235 known not affected: 524 recommended: 827 | 2026-07-25T17:27:56+00:00 | Vulnerability · Source |
| CVE-2022-4415 | suse_vex | SUSE CVE CVE-2022-4415 | known affected: 268 recommended: 1048 | 2026-07-25T17:27:54+00:00 | Vulnerability · Source |
| CVE-2022-4450 | suse_vex | SUSE CVE CVE-2022-4450 | known affected: 273 known not affected: 382 recommended: 590 | 2026-07-25T17:27:53+00:00 | Vulnerability · Source |
| CVE-2022-4543 | suse_vex | SUSE CVE CVE-2022-4543 | known not affected: 30 recommended: 14 | 2026-07-25T17:27:52+00:00 | Vulnerability · Source |
| CVE-2022-4696 | suse_vex | SUSE CVE CVE-2022-4696 | known not affected: 362 | 2026-07-25T17:27:51+00:00 | Vulnerability · Source |
| CVE-2022-4883 | suse_vex | SUSE CVE CVE-2022-4883 | known affected: 395 recommended: 170 | 2026-07-25T17:27:49+00:00 | Vulnerability · Source |
| CVE-2022-4904 | suse_vex | SUSE CVE CVE-2022-4904 | known affected: 277 recommended: 261 | 2026-07-25T17:27:48+00:00 | Vulnerability · Source |
| CVE-2022-20153 | suse_vex | SUSE CVE CVE-2022-20153 | known not affected: 377 | 2026-07-25T17:27:46+00:00 | Vulnerability · Source |
| CVE-2022-20154 | suse_vex | SUSE CVE CVE-2022-20154 | known affected: 130 known not affected: 212 recommended: 1923 | 2026-07-25T17:27:45+00:00 | Vulnerability · Source |
| CVE-2022-20158 | suse_vex | SUSE CVE CVE-2022-20158 | known not affected: 327 | 2026-07-25T17:27:43+00:00 | Vulnerability · Source |
| CVE-2022-20166 | suse_vex | SUSE CVE CVE-2022-20166 | known affected: 394 known not affected: 63 recommended: 862 | 2026-07-25T17:27:42+00:00 | Vulnerability · Source |
| CVE-2022-20368 | suse_vex | SUSE CVE CVE-2022-20368 | known affected: 173 recommended: 1756 | 2026-07-25T17:27:40+00:00 | Vulnerability · Source |
| CVE-2022-20369 | suse_vex | SUSE CVE CVE-2022-20369 | known affected: 237 recommended: 1509 | 2026-07-25T17:27:39+00:00 | Vulnerability · Source |
| CVE-2022-20382 | suse_vex | SUSE CVE CVE-2022-20382 | known not affected: 327 | 2026-07-25T17:27:37+00:00 | Vulnerability · Source |
| CVE-2022-20567 | suse_vex | SUSE CVE CVE-2022-20567 | known affected: 394 known not affected: 186 recommended: 204 | 2026-07-25T17:27:36+00:00 | Vulnerability · Source |
| CVE-2022-20698 | suse_vex | SUSE CVE CVE-2022-20698 | known affected: 1 recommended: 277 | 2026-07-25T17:27:34+00:00 | Vulnerability · Source |
| CVE-2022-21125 | suse_vex | SUSE CVE CVE-2022-21125 | known affected: 254 recommended: 1953 | 2026-07-25T17:27:33+00:00 | Vulnerability · Source |
| CVE-2022-21136 | suse_vex | SUSE CVE CVE-2022-21136 | known not affected: 87 recommended: 1 | 2026-07-25T17:27:31+00:00 | Vulnerability · Source |
| CVE-2022-21166 | suse_vex | SUSE CVE CVE-2022-21166 | known affected: 216 recommended: 1992 | 2026-07-25T17:27:29+00:00 | Vulnerability · Source |
| CVE-2022-21283 | suse_vex | SUSE CVE CVE-2022-21283 | known affected: 466 known not affected: 32 recommended: 1016 | 2026-07-25T17:27:28+00:00 | Vulnerability · Source |
| CVE-2022-21291 | suse_vex | SUSE CVE CVE-2022-21291 | known affected: 406 known not affected: 240 recommended: 775 | 2026-07-25T17:27:26+00:00 | Vulnerability · Source |
| CVE-2022-21340 | suse_vex | SUSE CVE CVE-2022-21340 | known affected: 406 known not affected: 32 recommended: 1069 | 2026-07-25T17:27:25+00:00 | Vulnerability · Source |
| CVE-2022-21360 | suse_vex | SUSE CVE CVE-2022-21360 | known affected: 406 known not affected: 32 recommended: 1069 | 2026-07-25T17:27:23+00:00 | Vulnerability · Source |
| CVE-2022-21426 | suse_vex | SUSE CVE CVE-2022-21426 | known affected: 406 known not affected: 67 recommended: 1226 | 2026-07-25T17:27:20+00:00 | Vulnerability · Source |
| CVE-2022-21427 | suse_vex | SUSE CVE CVE-2022-21427 | recommended: 403 | 2026-07-25T17:27:18+00:00 | Vulnerability · Source |
| CVE-2022-21476 | suse_vex | SUSE CVE CVE-2022-21476 | known affected: 406 known not affected: 92 recommended: 1179 | 2026-07-25T17:27:14+00:00 | Vulnerability · Source |
| CVE-2022-21505 | suse_vex | SUSE CVE CVE-2022-21505 | known affected: 234 known not affected: 175 recommended: 1137 | 2026-07-25T17:27:11+00:00 | Vulnerability · Source |
| CVE-2022-21541 | suse_vex | SUSE CVE CVE-2022-21541 | known affected: 397 known not affected: 25 recommended: 1207 | 2026-07-25T17:27:09+00:00 | Vulnerability · Source |
| CVE-2022-21556 | suse_vex | SUSE CVE CVE-2022-21556 | recommended: 17 | 2026-07-25T17:27:08+00:00 | Vulnerability · Source |
| CVE-2022-21618 | suse_vex | SUSE CVE CVE-2022-21618 | known affected: 395 recommended: 805 | 2026-07-25T17:27:06+00:00 | Vulnerability · Source |
| CVE-2022-21624 | suse_vex | SUSE CVE CVE-2022-21624 | known affected: 396 recommended: 1148 | 2026-07-25T17:27:05+00:00 | Vulnerability · Source |
| CVE-2022-21673 | suse_vex | SUSE CVE CVE-2022-21673 | known affected: 5 recommended: 163 | 2026-07-25T17:27:03+00:00 | Vulnerability · Source |
| CVE-2022-21682 | suse_vex | SUSE CVE CVE-2022-21682 | known not affected: 56 recommended: 323 | 2026-07-25T17:27:02+00:00 | Vulnerability · Source |
| CVE-2022-22058 | suse_vex | SUSE CVE CVE-2022-22058 | known not affected: 327 | 2026-07-25T17:27:00+00:00 | Vulnerability · Source |
| CVE-2022-22594 | suse_vex | SUSE CVE CVE-2022-22594 | known not affected: 9 recommended: 942 | 2026-07-25T17:26:59+00:00 | Vulnerability · Source |
| CVE-2022-22662 | suse_vex | SUSE CVE CVE-2022-22662 | known affected: 25 recommended: 981 | 2026-07-25T17:26:58+00:00 | Vulnerability · Source |
| CVE-2022-22677 | suse_vex | SUSE CVE CVE-2022-22677 | known affected: 25 recommended: 967 | 2026-07-25T17:26:56+00:00 | Vulnerability · Source |
| CVE-2022-22719 | suse_vex | SUSE CVE CVE-2022-22719 | known affected: 395 known not affected: 67 recommended: 519 | 2026-07-25T17:26:55+00:00 | Vulnerability · Source |
| CVE-2022-22721 | suse_vex | SUSE CVE CVE-2022-22721 | known affected: 395 recommended: 544 | 2026-07-25T17:26:53+00:00 | Vulnerability · Source |