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-3541 | suse_vex | SUSE CVE CVE-2022-3541 | known affected: 0 known not affected: 357 | 2026-10-16T14:57:26+00:00 | Vulnerability · Source |
| CVE-2022-3544 | suse_vex | SUSE CVE CVE-2022-3544 | known affected: 0 known not affected: 357 | 2026-10-16T14:57:23+00:00 | Vulnerability · Source |
| CVE-2022-3545 | suse_vex | SUSE CVE CVE-2022-3545 | known affected: 253 known not affected: 34 recommended: 1746 | 2026-10-16T14:57:21+00:00 | Vulnerability · Source |
| CVE-2022-3550 | suse_vex | SUSE CVE CVE-2022-3550 | known affected: 394 recommended: 293 | 2026-10-16T14:57:18+00:00 | Vulnerability · Source |
| CVE-2022-3564 | suse_vex | SUSE CVE CVE-2022-3564 | known affected: 247 known not affected: 55 recommended: 1566 | 2026-10-16T14:57:15+00:00 | Vulnerability · Source |
| CVE-2022-3565 | suse_vex | SUSE CVE CVE-2022-3565 | known affected: 253 recommended: 1559 | 2026-10-16T14:57:12+00:00 | Vulnerability · Source |
| CVE-2022-3566 | suse_vex | SUSE CVE CVE-2022-3566 | known affected: 275 known not affected: 304 recommended: 1155 | 2026-10-16T14:57:10+00:00 | Vulnerability · Source |
| CVE-2022-3586 | suse_vex | SUSE CVE CVE-2022-3586 | known affected: 253 recommended: 1745 | 2026-10-16T14:57:08+00:00 | Vulnerability · Source |
| CVE-2022-3594 | suse_vex | SUSE CVE CVE-2022-3594 | known affected: 255 known not affected: 2 recommended: 1514 | 2026-10-16T14:57:05+00:00 | Vulnerability · Source |
| CVE-2022-3598 | suse_vex | SUSE CVE CVE-2022-3598 | known affected: 426 known not affected: 1 recommended: 238 | 2026-10-16T14:57:04+00:00 | Vulnerability · Source |
| CVE-2022-3606 | suse_vex | SUSE CVE CVE-2022-3606 | known affected: 382 known not affected: 700 recommended: 256 | 2026-10-16T14:57:02+00:00 | Vulnerability · Source |
| CVE-2022-3619 | suse_vex | SUSE CVE CVE-2022-3619 | known affected: 246 known not affected: 494 recommended: 842 | 2026-10-16T14:57:00+00:00 | Vulnerability · Source |
| CVE-2022-3621 | suse_vex | SUSE CVE CVE-2022-3621 | known affected: 255 known not affected: 305 recommended: 1464 | 2026-10-16T14:56:58+00:00 | Vulnerability · Source |
| CVE-2022-3623 | suse_vex | SUSE CVE CVE-2022-3623 | known affected: 0 known not affected: 277 recommended: 128 | 2026-10-16T14:56:56+00:00 | Vulnerability · Source |
| CVE-2022-3624 | suse_vex | SUSE CVE CVE-2022-3624 | known affected: 0 known not affected: 622 | 2026-10-16T14:56:54+00:00 | Vulnerability · Source |
| CVE-2022-3625 | suse_vex | SUSE CVE CVE-2022-3625 | known affected: 253 known not affected: 201 recommended: 1182 | 2026-10-16T14:56:52+00:00 | Vulnerability · Source |
| CVE-2022-3628 | suse_vex | SUSE CVE CVE-2022-3628 | known affected: 261 known not affected: 2 recommended: 1585 | 2026-10-16T14:56:51+00:00 | Vulnerability · Source |
| CVE-2022-3629 | suse_vex | SUSE CVE CVE-2022-3629 | known affected: 261 known not affected: 350 recommended: 1436 | 2026-10-16T14:56:48+00:00 | Vulnerability · Source |
| CVE-2022-3630 | suse_vex | SUSE CVE CVE-2022-3630 | known affected: 0 known not affected: 622 | 2026-10-16T14:56:46+00:00 | Vulnerability · Source |
| CVE-2022-3635 | suse_vex | SUSE CVE CVE-2022-3635 | known affected: 269 recommended: 1513 | 2026-10-16T14:56:41+00:00 | Vulnerability · Source |
| CVE-2022-3646 | suse_vex | SUSE CVE CVE-2022-3646 | known affected: 261 known not affected: 346 recommended: 1464 | 2026-10-16T14:56:36+00:00 | Vulnerability · Source |
| CVE-2022-3715 | suse_vex | SUSE CVE CVE-2022-3715 | known affected: 0 known not affected: 376 recommended: 4 | 2026-10-16T14:56:31+00:00 | Vulnerability · Source |
| CVE-2022-3775 | suse_vex | SUSE CVE CVE-2022-3775 | known affected: 260 recommended: 824 | 2026-10-16T14:56:29+00:00 | Vulnerability · Source |
| CVE-2022-3786 | suse_vex | SUSE CVE CVE-2022-3786 | known affected: 0 known not affected: 663 recommended: 181 | 2026-10-16T14:56:28+00:00 | Vulnerability · Source |
| CVE-2022-3821 | suse_vex | SUSE CVE CVE-2022-3821 | known affected: 254 known not affected: 121 recommended: 976 | 2026-10-16T14:56:26+00:00 | Vulnerability · Source |
| CVE-2022-3872 | suse_vex | SUSE CVE CVE-2022-3872 | known affected: 2198 | 2026-10-16T14:56:24+00:00 | Vulnerability · Source |
| CVE-2022-3924 | suse_vex | SUSE CVE CVE-2022-3924 | known affected: 284 known not affected: 424 recommended: 250 | 2026-10-16T14:56:22+00:00 | Vulnerability · Source |
| CVE-2022-3977 | suse_vex | SUSE CVE CVE-2022-3977 | known affected: 0 known not affected: 384 | 2026-10-16T14:56:20+00:00 | Vulnerability · Source |
| CVE-2022-3996 | suse_vex | SUSE CVE CVE-2022-3996 | known affected: 0 known not affected: 713 recommended: 138 | 2026-10-16T14:56:18+00:00 | Vulnerability · Source |
| CVE-2022-4055 | suse_vex | SUSE CVE CVE-2022-4055 | recommended: 2 | 2026-10-16T14:56:16+00:00 | Vulnerability · Source |
| CVE-2022-4095 | suse_vex | SUSE CVE CVE-2022-4095 | known affected: 242 known not affected: 2 recommended: 1749 | 2026-10-16T14:56:14+00:00 | Vulnerability · Source |
| CVE-2022-4129 | suse_vex | SUSE CVE CVE-2022-4129 | known affected: 273 known not affected: 108 recommended: 1472 | 2026-10-16T14:56:11+00:00 | Vulnerability · Source |
| CVE-2022-4132 | suse_vex | SUSE CVE CVE-2022-4132 | known affected: 0 known not affected: 469 | 2026-10-16T14:56:09+00:00 | Vulnerability · Source |
| CVE-2022-4139 | suse_vex | SUSE CVE CVE-2022-4139 | known affected: 267 known not affected: 199 recommended: 1420 | 2026-10-16T14:56:07+00:00 | Vulnerability · Source |
| CVE-2022-4141 | suse_vex | SUSE CVE CVE-2022-4141 | known affected: 267 recommended: 407 | 2026-10-16T14:56:04+00:00 | Vulnerability · Source |
| CVE-2022-4269 | suse_vex | SUSE CVE CVE-2022-4269 | known affected: 194 known not affected: 174 recommended: 1119 | 2026-10-16T14:56:01+00:00 | Vulnerability · Source |
| CVE-2022-4285 | suse_vex | SUSE CVE CVE-2022-4285 | known affected: 480 known not affected: 1 recommended: 338 | 2026-10-16T14:56:00+00:00 | Vulnerability · Source |
| CVE-2022-4303 | suse_vex | SUSE CVE CVE-2022-4303 | recommended: 164 | 2026-10-16T14:55:58+00:00 | Vulnerability · Source |
| CVE-2022-4304 | suse_vex | SUSE CVE CVE-2022-4304 | known affected: 132 known not affected: 107 recommended: 1112 | 2026-10-16T14:55:56+00:00 | Vulnerability · Source |
| CVE-2022-4382 | suse_vex | SUSE CVE CVE-2022-4382 | known affected: 235 known not affected: 578 recommended: 798 | 2026-10-16T14:55:54+00:00 | Vulnerability · Source |
| CVE-2022-4415 | suse_vex | SUSE CVE CVE-2022-4415 | known affected: 268 recommended: 1057 | 2026-10-16T14:55:52+00:00 | Vulnerability · Source |
| CVE-2022-4450 | suse_vex | SUSE CVE CVE-2022-4450 | known affected: 273 known not affected: 407 recommended: 591 | 2026-10-16T14:55:49+00:00 | Vulnerability · Source |
| CVE-2022-4515 | suse_vex | SUSE CVE CVE-2022-4515 | known affected: 1 recommended: 60 | 2026-10-16T14:55:47+00:00 | Vulnerability · Source |
| CVE-2022-4603 | suse_vex | SUSE CVE CVE-2022-4603 | known affected: 103 recommended: 63 | 2026-10-16T14:55:44+00:00 | Vulnerability · Source |
| CVE-2022-4662 | suse_vex | SUSE CVE CVE-2022-4662 | known affected: 255 known not affected: 98 recommended: 1367 | 2026-10-16T14:55:41+00:00 | Vulnerability · Source |
| CVE-2022-4696 | suse_vex | SUSE CVE CVE-2022-4696 | known affected: 0 known not affected: 392 | 2026-10-16T14:55:39+00:00 | Vulnerability · Source |
| CVE-2022-4744 | suse_vex | SUSE CVE CVE-2022-4744 | known affected: 201 known not affected: 141 recommended: 1289 | 2026-10-16T14:55:37+00:00 | Vulnerability · Source |
| CVE-2022-4806 | suse_vex | SUSE CVE CVE-2022-4806 | recommended: 26 | 2026-10-16T14:55:35+00:00 | Vulnerability · Source |
| CVE-2022-4842 | suse_vex | SUSE CVE CVE-2022-4842 | known affected: 0 known not affected: 392 | 2026-10-16T14:55:33+00:00 | Vulnerability · Source |
| CVE-2022-4994 | suse_vex | SUSE CVE CVE-2022-4994 | known affected: 394 known not affected: 278 recommended: 161 | 2026-10-16T14:55:31+00:00 | Vulnerability · Source |