VEX records
Browse vendor VEX statements available in this Vulnerability-Lookup instance and pivot to the related vulnerability.
283900 VEX records
API response| Vulnerability | Source | Title | Product status | Imported | Links |
|---|---|---|---|---|---|
| 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 |
| CVE-2022-22742 | suse_vex | SUSE CVE CVE-2022-22742 | recommended: 413 | 2026-07-25T17:26:51+00:00 | Vulnerability · Source |
| CVE-2022-22754 | suse_vex | SUSE CVE CVE-2022-22754 | recommended: 408 | 2026-07-25T17:26:50+00:00 | Vulnerability · Source |
| CVE-2022-22756 | suse_vex | SUSE CVE CVE-2022-22756 | recommended: 408 | 2026-07-25T17:26:48+00:00 | Vulnerability · Source |
| CVE-2022-22759 | suse_vex | SUSE CVE CVE-2022-22759 | recommended: 408 | 2026-07-25T17:26:47+00:00 | Vulnerability · Source |
| CVE-2022-22760 | suse_vex | SUSE CVE CVE-2022-22760 | recommended: 408 | 2026-07-25T17:26:45+00:00 | Vulnerability · Source |
| CVE-2022-22761 | suse_vex | SUSE CVE CVE-2022-22761 | recommended: 408 | 2026-07-25T17:26:44+00:00 | Vulnerability · Source |
| CVE-2022-22825 | suse_vex | SUSE CVE CVE-2022-22825 | known affected: 330 known not affected: 32 recommended: 384 | 2026-07-25T17:26:42+00:00 | Vulnerability · Source |
| CVE-2022-23034 | suse_vex | SUSE CVE CVE-2022-23034 | known affected: 340 known not affected: 47 recommended: 470 | 2026-07-25T17:26:41+00:00 | Vulnerability · Source |
| CVE-2022-23040 | suse_vex | SUSE CVE CVE-2022-23040 | known affected: 344 known not affected: 61 recommended: 1327 | 2026-07-25T17:26:39+00:00 | Vulnerability · Source |
| CVE-2022-23042 | suse_vex | SUSE CVE CVE-2022-23042 | known affected: 344 known not affected: 61 recommended: 1327 | 2026-07-25T17:26:37+00:00 | Vulnerability · Source |
| CVE-2022-23132 | suse_vex | SUSE CVE CVE-2022-23132 | known not affected: 37 | 2026-07-25T17:26:36+00:00 | Vulnerability · Source |
| CVE-2022-23222 | suse_vex | SUSE CVE CVE-2022-23222 | known not affected: 368 recommended: 580 | 2026-07-25T17:26:34+00:00 | Vulnerability · Source |
| CVE-2022-23307 | suse_vex | SUSE CVE CVE-2022-23307 | known affected: 395 known not affected: 36 recommended: 352 | 2026-07-25T17:26:33+00:00 | Vulnerability · Source |
| CVE-2022-23308 | suse_vex | SUSE CVE CVE-2022-23308 | known affected: 216 known not affected: 44 recommended: 664 | 2026-07-25T17:26:31+00:00 | Vulnerability · Source |
| CVE-2022-23468 | suse_vex | SUSE CVE CVE-2022-23468 | known affected: 395 known not affected: 1 recommended: 202 | 2026-07-25T17:26:30+00:00 | Vulnerability · Source |
| CVE-2022-23483 | suse_vex | SUSE CVE CVE-2022-23483 | known affected: 395 known not affected: 1 recommended: 202 | 2026-07-25T17:26:28+00:00 | Vulnerability · Source |
| CVE-2022-23521 | suse_vex | SUSE CVE CVE-2022-23521 | known affected: 1 known not affected: 131 recommended: 726 | 2026-07-25T17:26:27+00:00 | Vulnerability · Source |
| CVE-2022-23525 | suse_vex | SUSE CVE CVE-2022-23525 | known affected: 406 recommended: 99 | 2026-07-25T17:26:25+00:00 | Vulnerability · Source |
| CVE-2022-23527 | suse_vex | SUSE CVE CVE-2022-23527 | known affected: 18 recommended: 39 | 2026-07-25T17:26:24+00:00 | Vulnerability · Source |
| CVE-2022-23820 | suse_vex | SUSE CVE CVE-2022-23820 | known affected: 22 recommended: 1381 | 2026-07-25T17:26:22+00:00 | Vulnerability · Source |
| CVE-2022-23824 | suse_vex | SUSE CVE CVE-2022-23824 | known affected: 274 recommended: 381 | 2026-07-25T17:26:21+00:00 | Vulnerability · Source |
| CVE-2022-23901 | suse_vex | SUSE CVE CVE-2022-23901 | known not affected: 66 | 2026-07-25T17:26:19+00:00 | Vulnerability · Source |
| CVE-2022-23943 | suse_vex | SUSE CVE CVE-2022-23943 | known affected: 395 known not affected: 21 recommended: 519 | 2026-07-25T17:26:18+00:00 | Vulnerability · Source |
| CVE-2022-23990 | suse_vex | SUSE CVE CVE-2022-23990 | known affected: 339 known not affected: 32 recommended: 373 | 2026-07-25T17:26:16+00:00 | Vulnerability · Source |
| CVE-2022-24052 | suse_vex | SUSE CVE CVE-2022-24052 | known affected: 1 recommended: 505 | 2026-07-25T17:26:14+00:00 | Vulnerability · Source |
| CVE-2022-24107 | suse_vex | SUSE CVE CVE-2022-24107 | known affected: 1 known not affected: 259 | 2026-07-25T17:26:13+00:00 | Vulnerability · Source |
| CVE-2022-24713 | suse_vex | SUSE CVE CVE-2022-24713 | known affected: 620 known not affected: 882 recommended: 610 | 2026-07-25T17:26:11+00:00 | Vulnerability · Source |
| CVE-2022-24765 | suse_vex | SUSE CVE CVE-2022-24765 | recommended: 1094 | 2026-07-25T17:26:09+00:00 | Vulnerability · Source |
| CVE-2022-24810 | suse_vex | SUSE CVE CVE-2022-24810 | known affected: 394 known not affected: 190 recommended: 254 | 2026-07-25T17:26:08+00:00 | Vulnerability · Source |
| CVE-2022-24903 | suse_vex | SUSE CVE CVE-2022-24903 | known affected: 144 known not affected: 66 recommended: 956 | 2026-07-25T17:26:06+00:00 | Vulnerability · Source |
| CVE-2022-25235 | suse_vex | SUSE CVE CVE-2022-25235 | known affected: 282 recommended: 449 | 2026-07-25T17:26:05+00:00 | Vulnerability · Source |
| CVE-2022-25258 | suse_vex | SUSE CVE CVE-2022-25258 | known affected: 210 known not affected: 252 recommended: 556 | 2026-07-25T17:26:01+00:00 | Vulnerability · Source |
| CVE-2022-25265 | suse_vex | SUSE CVE CVE-2022-25265 | known not affected: 3490 recommended: 20 | 2026-07-25T17:26:00+00:00 | Vulnerability · Source |
| CVE-2022-25309 | suse_vex | SUSE CVE CVE-2022-25309 | known affected: 437 recommended: 205 | 2026-07-25T17:25:58+00:00 | Vulnerability · Source |
| CVE-2022-25310 | suse_vex | SUSE CVE CVE-2022-25310 | known affected: 437 recommended: 205 | 2026-07-25T17:25:57+00:00 | Vulnerability · Source |
| CVE-2022-25315 | suse_vex | SUSE CVE CVE-2022-25315 | known affected: 282 recommended: 444 | 2026-07-25T17:25:55+00:00 | Vulnerability · Source |
| CVE-2022-25368 | suse_vex | SUSE CVE CVE-2022-25368 | known not affected: 401 | 2026-07-25T17:25:54+00:00 | Vulnerability · Source |
| CVE-2022-26356 | suse_vex | SUSE CVE CVE-2022-26356 | known affected: 349 known not affected: 46 recommended: 453 | 2026-07-25T17:25:52+00:00 | Vulnerability · Source |