VEX records
Browse vendor VEX statements available in this Vulnerability-Lookup instance and pivot to the related vulnerability.
100548 VEX records
API response| Vulnerability | Source | Title | Product status | Imported | Links |
|---|---|---|---|---|---|
| CVE-2022-23852 | suse_vex | SUSE CVE CVE-2022-23852 | known affected: 339 known not affected: 32 recommended: 385 | 2026-10-16T14:52:23+00:00 | Vulnerability · Source |
| CVE-2022-23943 | suse_vex | SUSE CVE CVE-2022-23943 | known affected: 395 known not affected: 33 recommended: 536 | 2026-10-16T14:52:20+00:00 | Vulnerability · Source |
| CVE-2022-23949 | suse_vex | SUSE CVE CVE-2022-23949 | known affected: 0 known not affected: 72 recommended: 201 | 2026-10-16T14:52:18+00:00 | Vulnerability · Source |
| CVE-2022-23951 | suse_vex | SUSE CVE CVE-2022-23951 | known affected: 0 known not affected: 72 recommended: 201 | 2026-10-16T14:52:15+00:00 | Vulnerability · Source |
| CVE-2022-23960 | suse_vex | SUSE CVE CVE-2022-23960 | known affected: 394 known not affected: 439 recommended: 758 | 2026-10-16T14:52:12+00:00 | Vulnerability · Source |
| CVE-2022-23990 | suse_vex | SUSE CVE CVE-2022-23990 | known affected: 339 known not affected: 32 recommended: 373 | 2026-10-16T14:52:09+00:00 | Vulnerability · Source |
| CVE-2022-24050 | suse_vex | SUSE CVE CVE-2022-24050 | known affected: 1 recommended: 529 | 2026-10-16T14:52:07+00:00 | Vulnerability · Source |
| CVE-2022-24130 | suse_vex | SUSE CVE CVE-2022-24130 | known affected: 422 known not affected: 4 recommended: 84 | 2026-10-16T14:52:04+00:00 | Vulnerability · Source |
| CVE-2022-24302 | suse_vex | SUSE CVE CVE-2022-24302 | known affected: 394 known not affected: 22 recommended: 106 | 2026-10-16T14:52:02+00:00 | Vulnerability · Source |
| CVE-2022-24407 | suse_vex | SUSE CVE CVE-2022-24407 | known affected: 454 known not affected: 17 recommended: 1716 | 2026-10-16T14:51:59+00:00 | Vulnerability · Source |
| CVE-2022-24695 | suse_vex | SUSE CVE CVE-2022-24695 | No product status | 2026-10-16T14:51:56+00:00 | Vulnerability · Source |
| CVE-2022-24761 | suse_vex | SUSE CVE CVE-2022-24761 | recommended: 89 | 2026-10-16T14:51:54+00:00 | Vulnerability · Source |
| CVE-2022-24769 | suse_vex | SUSE CVE CVE-2022-24769 | known affected: 350 recommended: 444 | 2026-10-16T14:51:51+00:00 | Vulnerability · Source |
| CVE-2022-24806 | suse_vex | SUSE CVE CVE-2022-24806 | known affected: 394 known not affected: 205 recommended: 263 | 2026-10-16T14:51:49+00:00 | Vulnerability · Source |
| CVE-2022-24808 | suse_vex | SUSE CVE CVE-2022-24808 | known affected: 394 known not affected: 205 recommended: 263 | 2026-10-16T14:51:47+00:00 | Vulnerability · Source |
| CVE-2022-24828 | suse_vex | SUSE CVE CVE-2022-24828 | recommended: 30 | 2026-10-16T14:51:45+00:00 | Vulnerability · Source |
| CVE-2022-24882 | suse_vex | SUSE CVE CVE-2022-24882 | recommended: 209 | 2026-10-16T14:51:42+00:00 | Vulnerability · Source |
| CVE-2022-24903 | suse_vex | SUSE CVE CVE-2022-24903 | known affected: 144 known not affected: 66 recommended: 983 | 2026-10-16T14:51:39+00:00 | Vulnerability · Source |
| CVE-2022-24958 | suse_vex | SUSE CVE CVE-2022-24958 | known affected: 347 known not affected: 315 recommended: 905 | 2026-10-16T14:51:37+00:00 | Vulnerability · Source |
| CVE-2022-24963 | suse_vex | SUSE CVE CVE-2022-24963 | known affected: 0 known not affected: 103 recommended: 14 | 2026-10-16T14:51:35+00:00 | Vulnerability · Source |
| CVE-2022-25147 | suse_vex | SUSE CVE CVE-2022-25147 | known affected: 409 recommended: 346 | 2026-10-16T14:51:33+00:00 | Vulnerability · Source |
| CVE-2022-25235 | suse_vex | SUSE CVE CVE-2022-25235 | known affected: 282 recommended: 449 | 2026-10-16T14:51:30+00:00 | Vulnerability · Source |
| CVE-2022-25236 | suse_vex | SUSE CVE CVE-2022-25236 | known affected: 172 known not affected: 21 recommended: 1147 | 2026-10-16T14:51:28+00:00 | Vulnerability · Source |
| CVE-2022-25265 | suse_vex | SUSE CVE CVE-2022-25265 | known affected: 0 known not affected: 3812 recommended: 20 | 2026-10-16T14:51:25+00:00 | Vulnerability · Source |
| CVE-2022-25308 | suse_vex | SUSE CVE CVE-2022-25308 | known affected: 441 recommended: 199 | 2026-10-16T14:51:22+00:00 | Vulnerability · Source |
| CVE-2022-25313 | suse_vex | SUSE CVE CVE-2022-25313 | known affected: 282 recommended: 439 | 2026-10-16T14:51:19+00:00 | Vulnerability · Source |
| CVE-2022-25314 | suse_vex | SUSE CVE CVE-2022-25314 | known affected: 282 recommended: 439 | 2026-10-16T14:51:16+00:00 | Vulnerability · Source |
| CVE-2022-25315 | suse_vex | SUSE CVE CVE-2022-25315 | known affected: 282 recommended: 444 | 2026-10-16T14:51:13+00:00 | Vulnerability · Source |
| CVE-2022-25375 | suse_vex | SUSE CVE CVE-2022-25375 | known affected: 207 known not affected: 284 recommended: 898 | 2026-10-16T14:51:11+00:00 | Vulnerability · Source |
| CVE-2022-25647 | suse_vex | SUSE CVE CVE-2022-25647 | known affected: 394 recommended: 60 | 2026-10-16T14:51:08+00:00 | Vulnerability · Source |
| CVE-2022-25883 | suse_vex | SUSE CVE CVE-2022-25883 | known affected: 0 known not affected: 310 recommended: 47 | 2026-10-16T14:51:03+00:00 | Vulnerability · Source |
| CVE-2022-26127 | suse_vex | SUSE CVE CVE-2022-26127 | recommended: 264 | 2026-10-16T14:51:01+00:00 | Vulnerability · Source |
| CVE-2022-26128 | suse_vex | SUSE CVE CVE-2022-26128 | recommended: 264 | 2026-10-16T14:50:58+00:00 | Vulnerability · Source |
| CVE-2022-26129 | suse_vex | SUSE CVE CVE-2022-26129 | recommended: 254 | 2026-10-16T14:50:55+00:00 | Vulnerability · Source |
| CVE-2022-26280 | suse_vex | SUSE CVE CVE-2022-26280 | known affected: 394 known not affected: 93 recommended: 128 | 2026-10-16T14:50:52+00:00 | Vulnerability · Source |
| CVE-2022-26354 | suse_vex | SUSE CVE CVE-2022-26354 | known affected: 549 known not affected: 306 recommended: 1514 | 2026-10-16T14:50:49+00:00 | Vulnerability · Source |
| CVE-2022-26373 | suse_vex | SUSE CVE CVE-2022-26373 | known affected: 236 recommended: 1558 | 2026-10-16T14:50:46+00:00 | Vulnerability · Source |
| CVE-2022-26377 | suse_vex | SUSE CVE CVE-2022-26377 | known affected: 395 recommended: 560 | 2026-10-16T14:50:44+00:00 | Vulnerability · Source |
| CVE-2022-26386 | suse_vex | SUSE CVE CVE-2022-26386 | known affected: 1 recommended: 402 | 2026-10-16T14:50:41+00:00 | Vulnerability · Source |
| CVE-2022-26387 | suse_vex | SUSE CVE CVE-2022-26387 | known affected: 1 recommended: 411 | 2026-10-16T14:50:39+00:00 | Vulnerability · Source |
| CVE-2022-26485 | suse_vex | SUSE CVE CVE-2022-26485 | known affected: 13 recommended: 402 | 2026-10-16T14:50:36+00:00 | Vulnerability · Source |
| CVE-2022-26488 | suse_vex | SUSE CVE CVE-2022-26488 | known affected: 0 known not affected: 543 | 2026-10-16T14:50:34+00:00 | Vulnerability · Source |
| CVE-2022-26520 | suse_vex | SUSE CVE CVE-2022-26520 | known affected: 395 known not affected: 30 recommended: 139 | 2026-10-16T14:50:31+00:00 | Vulnerability · Source |
| CVE-2022-26700 | suse_vex | SUSE CVE CVE-2022-26700 | known affected: 1 recommended: 1008 | 2026-10-16T14:50:28+00:00 | Vulnerability · Source |
| CVE-2022-26709 | suse_vex | SUSE CVE CVE-2022-26709 | known affected: 1 recommended: 1008 | 2026-10-16T14:50:25+00:00 | Vulnerability · Source |
| CVE-2022-26719 | suse_vex | SUSE CVE CVE-2022-26719 | known affected: 1 recommended: 1008 | 2026-10-16T14:50:22+00:00 | Vulnerability · Source |
| CVE-2022-26966 | suse_vex | SUSE CVE CVE-2022-26966 | known affected: 344 known not affected: 31 recommended: 1244 | 2026-10-16T14:50:19+00:00 | Vulnerability · Source |
| CVE-2022-27223 | suse_vex | SUSE CVE CVE-2022-27223 | known affected: 217 known not affected: 337 recommended: 450 | 2026-10-16T14:50:17+00:00 | Vulnerability · Source |
| CVE-2022-27239 | suse_vex | SUSE CVE CVE-2022-27239 | known affected: 209 known not affected: 5 recommended: 354 | 2026-10-16T14:50:15+00:00 | Vulnerability · Source |
| CVE-2022-27376 | suse_vex | SUSE CVE CVE-2022-27376 | known affected: 0 known not affected: 93 recommended: 402 | 2026-10-16T14:50:12+00:00 | Vulnerability · Source |