VEX records
Browse vendor VEX statements available in this Vulnerability-Lookup instance and pivot to the related vulnerability.
307361 VEX records
API response| Vulnerability | Source | Title | Product status | Imported | Links |
|---|---|---|---|---|---|
| CVE-2022-2849 | suse_vex | SUSE CVE CVE-2022-2849 | known affected: 238 recommended: 501 | 2026-10-11T01:55:35+00:00 | Vulnerability · Source |
| CVE-2022-2873 | suse_vex | SUSE CVE CVE-2022-2873 | known affected: 263 known not affected: 306 recommended: 676 | 2026-10-11T01:55:32+00:00 | Vulnerability · Source |
| CVE-2022-2946 | suse_vex | SUSE CVE CVE-2022-2946 | known affected: 237 known not affected: 2 recommended: 501 | 2026-10-11T01:55:29+00:00 | Vulnerability · Source |
| CVE-2022-2953 | suse_vex | SUSE CVE CVE-2022-2953 | known not affected: 198 recommended: 9 | 2026-10-11T01:55:27+00:00 | Vulnerability · Source |
| CVE-2022-2959 | suse_vex | SUSE CVE CVE-2022-2959 | known affected: 265 known not affected: 306 recommended: 660 | 2026-10-11T01:55:25+00:00 | Vulnerability · Source |
| CVE-2022-3033 | suse_vex | SUSE CVE CVE-2022-3033 | recommended: 94 | 2026-10-11T01:55:23+00:00 | Vulnerability · Source |
| CVE-2022-3077 | suse_vex | SUSE CVE CVE-2022-3077 | known not affected: 357 recommended: 44 | 2026-10-11T01:55:21+00:00 | Vulnerability · Source |
| CVE-2022-3094 | suse_vex | SUSE CVE CVE-2022-3094 | known affected: 272 recommended: 599 | 2026-10-11T01:55:19+00:00 | Vulnerability · Source |
| CVE-2022-3162 | suse_vex | SUSE CVE CVE-2022-3162 | known not affected: 24 recommended: 64 | 2026-10-11T01:55:17+00:00 | Vulnerability · Source |
| CVE-2022-3190 | suse_vex | SUSE CVE CVE-2022-3190 | known affected: 68 known not affected: 84 recommended: 228 | 2026-10-11T01:55:15+00:00 | Vulnerability · Source |
| CVE-2022-3424 | suse_vex | SUSE CVE CVE-2022-3424 | known affected: 253 recommended: 1772 | 2026-10-11T01:55:13+00:00 | Vulnerability · Source |
| CVE-2022-3435 | suse_vex | SUSE CVE CVE-2022-3435 | known affected: 219 known not affected: 386 recommended: 1246 | 2026-10-11T01:55:11+00:00 | Vulnerability · Source |
| CVE-2022-3500 | suse_vex | SUSE CVE CVE-2022-3500 | recommended: 197 | 2026-10-11T01:55:09+00:00 | Vulnerability · Source |
| CVE-2022-3515 | suse_vex | SUSE CVE CVE-2022-3515 | known affected: 253 known not affected: 1 recommended: 290 | 2026-10-11T01:55:07+00:00 | Vulnerability · Source |
| CVE-2022-3522 | suse_vex | SUSE CVE CVE-2022-3522 | recommended: 74 | 2026-10-11T01:55:05+00:00 | Vulnerability · Source |
| CVE-2022-3560 | suse_vex | SUSE CVE CVE-2022-3560 | known not affected: 17 recommended: 57 | 2026-10-11T01:55:03+00:00 | Vulnerability · Source |
| CVE-2022-3566 | suse_vex | SUSE CVE CVE-2022-3566 | known affected: 275 known not affected: 308 recommended: 1155 | 2026-10-11T01:55:00+00:00 | Vulnerability · Source |
| CVE-2022-3567 | suse_vex | SUSE CVE CVE-2022-3567 | known affected: 269 known not affected: 307 recommended: 1587 | 2026-10-11T01:54:58+00:00 | Vulnerability · Source |
| CVE-2022-3570 | suse_vex | SUSE CVE CVE-2022-3570 | known affected: 426 known not affected: 1 recommended: 233 | 2026-10-11T01:54:56+00:00 | Vulnerability · Source |
| CVE-2022-3597 | suse_vex | SUSE CVE CVE-2022-3597 | known affected: 395 known not affected: 1 recommended: 263 | 2026-10-11T01:54:53+00:00 | Vulnerability · Source |
| CVE-2022-3599 | suse_vex | SUSE CVE CVE-2022-3599 | known affected: 395 known not affected: 1 recommended: 263 | 2026-10-11T01:54:50+00:00 | Vulnerability · Source |
| CVE-2022-3602 | suse_vex | SUSE CVE CVE-2022-3602 | known not affected: 663 recommended: 175 | 2026-10-11T01:54:48+00:00 | Vulnerability · Source |
| CVE-2022-3623 | suse_vex | SUSE CVE CVE-2022-3623 | known not affected: 277 recommended: 128 | 2026-10-11T01:54:46+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-11T01:54:44+00:00 | Vulnerability · Source |
| CVE-2022-3649 | suse_vex | SUSE CVE CVE-2022-3649 | known affected: 255 known not affected: 8 recommended: 1464 | 2026-10-11T01:54:39+00:00 | Vulnerability · Source |
| CVE-2022-3707 | suse_vex | SUSE CVE CVE-2022-3707 | known affected: 267 known not affected: 199 recommended: 1231 | 2026-10-11T01:54:36+00:00 | Vulnerability · Source |
| CVE-2022-3736 | suse_vex | SUSE CVE CVE-2022-3736 | known affected: 284 known not affected: 424 recommended: 242 | 2026-10-11T01:54:33+00:00 | Vulnerability · Source |
| CVE-2022-3775 | suse_vex | SUSE CVE CVE-2022-3775 | known affected: 260 recommended: 816 | 2026-10-11T01:54:31+00:00 | Vulnerability · Source |
| CVE-2022-4055 | suse_vex | SUSE CVE CVE-2022-4055 | recommended: 2 | 2026-10-11T01:54:28+00:00 | Vulnerability · Source |
| CVE-2022-4122 | suse_vex | SUSE CVE CVE-2022-4122 | known not affected: 52 recommended: 10 | 2026-10-11T01:54:25+00:00 | Vulnerability · Source |
| CVE-2022-4129 | suse_vex | SUSE CVE CVE-2022-4129 | known affected: 273 known not affected: 115 recommended: 1472 | 2026-10-11T01:54:22+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-11T01:54:19+00:00 | Vulnerability · Source |
| CVE-2022-4172 | suse_vex | SUSE CVE CVE-2022-4172 | known not affected: 1198 recommended: 449 | 2026-10-11T01:54:16+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-11T01:54:13+00:00 | Vulnerability · Source |
| CVE-2022-4283 | suse_vex | SUSE CVE CVE-2022-4283 | known affected: 406 known not affected: 25 recommended: 319 | 2026-10-11T01:54:12+00:00 | Vulnerability · Source |
| CVE-2022-4292 | suse_vex | SUSE CVE CVE-2022-4292 | known affected: 267 known not affected: 26 recommended: 407 | 2026-10-11T01:54:09+00:00 | Vulnerability · Source |
| CVE-2022-4293 | suse_vex | SUSE CVE CVE-2022-4293 | known affected: 267 known not affected: 26 recommended: 407 | 2026-10-11T01:54:07+00:00 | Vulnerability · Source |
| CVE-2022-4645 | suse_vex | SUSE CVE CVE-2022-4645 | known not affected: 168 recommended: 9 | 2026-10-11T01:54:04+00:00 | Vulnerability · Source |
| CVE-2022-4883 | suse_vex | SUSE CVE CVE-2022-4883 | known affected: 395 recommended: 171 | 2026-10-11T01:54:01+00:00 | Vulnerability · Source |
| CVE-2022-4899 | suse_vex | SUSE CVE CVE-2022-4899 | known affected: 383 known not affected: 27 recommended: 244 | 2026-10-11T01:53:59+00:00 | Vulnerability · Source |
| CVE-2022-4904 | suse_vex | SUSE CVE CVE-2022-4904 | known affected: 277 recommended: 271 | 2026-10-11T01:53:56+00:00 | Vulnerability · Source |
| CVE-2022-21123 | suse_vex | SUSE CVE CVE-2022-21123 | known affected: 225 recommended: 1976 | 2026-10-11T01:53:51+00:00 | Vulnerability · Source |
| CVE-2022-21423 | suse_vex | SUSE CVE CVE-2022-21423 | recommended: 24 | 2026-10-11T01:53:48+00:00 | Vulnerability · Source |
| CVE-2022-21425 | suse_vex | SUSE CVE CVE-2022-21425 | recommended: 24 | 2026-10-11T01:53:46+00:00 | Vulnerability · Source |
| CVE-2022-21434 | suse_vex | SUSE CVE CVE-2022-21434 | known affected: 406 known not affected: 75 recommended: 1229 | 2026-10-11T01:53:44+00:00 | Vulnerability · Source |
| CVE-2022-21435 | suse_vex | SUSE CVE CVE-2022-21435 | recommended: 24 | 2026-10-11T01:53:42+00:00 | Vulnerability · Source |
| CVE-2022-21440 | suse_vex | SUSE CVE CVE-2022-21440 | recommended: 24 | 2026-10-11T01:53:40+00:00 | Vulnerability · Source |
| CVE-2022-21444 | suse_vex | SUSE CVE CVE-2022-21444 | recommended: 24 | 2026-10-11T01:53:38+00:00 | Vulnerability · Source |
| CVE-2022-21451 | suse_vex | SUSE CVE CVE-2022-21451 | recommended: 40 | 2026-10-11T01:53:37+00:00 | Vulnerability · Source |
| CVE-2022-21454 | suse_vex | SUSE CVE CVE-2022-21454 | recommended: 24 | 2026-10-11T01:53:35+00:00 | Vulnerability · Source |