VEX records
Browse vendor VEX statements available in this Vulnerability-Lookup instance and pivot to the related vulnerability.
283484 VEX records
API response| Vulnerability | Source | Title | Product status | Imported | Links |
|---|---|---|---|---|---|
| CVE-2022-3219 | suse_vex | SUSE CVE CVE-2022-3219 | known affected: 1 | 2026-07-25T17:29:08+00:00 | Vulnerability · Source |
| CVE-2022-3235 | suse_vex | SUSE CVE CVE-2022-3235 | known affected: 259 known not affected: 2 recommended: 485 | 2026-07-25T17:29:07+00:00 | Vulnerability · Source |
| CVE-2022-3239 | suse_vex | SUSE CVE CVE-2022-3239 | known affected: 253 known not affected: 2 recommended: 1509 | 2026-07-25T17:29:05+00:00 | Vulnerability · Source |
| CVE-2022-3324 | suse_vex | SUSE CVE CVE-2022-3324 | known affected: 260 recommended: 464 | 2026-07-25T17:29:03+00:00 | Vulnerability · Source |
| CVE-2022-3352 | suse_vex | SUSE CVE CVE-2022-3352 | known affected: 259 known not affected: 2 recommended: 485 | 2026-07-25T17:29:02+00:00 | Vulnerability · Source |
| CVE-2022-3424 | suse_vex | SUSE CVE CVE-2022-3424 | known affected: 253 recommended: 1758 | 2026-07-25T17:29:00+00:00 | Vulnerability · Source |
| CVE-2022-3435 | suse_vex | SUSE CVE CVE-2022-3435 | known affected: 219 known not affected: 339 recommended: 1248 | 2026-07-25T17:28:58+00:00 | Vulnerability · Source |
| CVE-2022-3491 | suse_vex | SUSE CVE CVE-2022-3491 | known affected: 267 known not affected: 10 recommended: 417 | 2026-07-25T17:28:57+00:00 | Vulnerability · Source |
| CVE-2022-3521 | suse_vex | SUSE CVE CVE-2022-3521 | known affected: 255 known not affected: 153 recommended: 1416 | 2026-07-25T17:28:55+00:00 | Vulnerability · Source |
| CVE-2022-3523 | suse_vex | SUSE CVE CVE-2022-3523 | known affected: 310 known not affected: 311 recommended: 698 | 2026-07-25T17:28:54+00:00 | Vulnerability · Source |
| CVE-2022-3529 | suse_vex | SUSE CVE CVE-2022-3529 | known not affected: 117 | 2026-07-25T17:28:52+00:00 | Vulnerability · Source |
| CVE-2022-3530 | suse_vex | SUSE CVE CVE-2022-3530 | known not affected: 54 | 2026-07-25T17:28:51+00:00 | Vulnerability · Source |
| CVE-2022-3532 | suse_vex | SUSE CVE CVE-2022-3532 | known not affected: 327 | 2026-07-25T17:28:50+00:00 | Vulnerability · Source |
| CVE-2022-3535 | suse_vex | SUSE CVE CVE-2022-3535 | known affected: 279 known not affected: 297 recommended: 1137 | 2026-07-25T17:28:48+00:00 | Vulnerability · Source |
| CVE-2022-3541 | suse_vex | SUSE CVE CVE-2022-3541 | known not affected: 327 | 2026-07-25T17:28:47+00:00 | Vulnerability · Source |
| CVE-2022-3544 | suse_vex | SUSE CVE CVE-2022-3544 | known not affected: 327 | 2026-07-25T17:28:46+00:00 | Vulnerability · Source |
| CVE-2022-3553 | suse_vex | SUSE CVE CVE-2022-3553 | known not affected: 150 | 2026-07-25T17:28:44+00:00 | Vulnerability · Source |
| CVE-2022-3555 | suse_vex | SUSE CVE CVE-2022-3555 | known affected: 516 recommended: 293 | 2026-07-25T17:28:43+00:00 | Vulnerability · Source |
| CVE-2022-3563 | suse_vex | SUSE CVE CVE-2022-3563 | known not affected: 142 recommended: 50 | 2026-07-25T17:28:41+00:00 | Vulnerability · Source |
| CVE-2022-3564 | suse_vex | SUSE CVE CVE-2022-3564 | known affected: 247 known not affected: 55 recommended: 1573 | 2026-07-25T17:28:40+00:00 | Vulnerability · Source |
| CVE-2022-3570 | suse_vex | SUSE CVE CVE-2022-3570 | known affected: 424 known not affected: 1 recommended: 237 | 2026-07-25T17:28:38+00:00 | Vulnerability · Source |
| CVE-2022-3577 | suse_vex | SUSE CVE CVE-2022-3577 | known affected: 253 known not affected: 298 recommended: 1274 | 2026-07-25T17:28:37+00:00 | Vulnerability · Source |
| CVE-2022-3592 | suse_vex | SUSE CVE CVE-2022-3592 | known not affected: 2051 recommended: 377 | 2026-07-25T17:28:35+00:00 | Vulnerability · Source |
| CVE-2022-3594 | suse_vex | SUSE CVE CVE-2022-3594 | known affected: 255 known not affected: 103 recommended: 1514 | 2026-07-25T17:28:34+00:00 | Vulnerability · Source |
| CVE-2022-3606 | suse_vex | SUSE CVE CVE-2022-3606 | known affected: 382 known not affected: 462 recommended: 254 | 2026-07-25T17:28:32+00:00 | Vulnerability · Source |
| CVE-2022-3619 | suse_vex | SUSE CVE CVE-2022-3619 | known affected: 246 known not affected: 448 recommended: 844 | 2026-07-25T17:28:31+00:00 | Vulnerability · Source |
| CVE-2022-3621 | suse_vex | SUSE CVE CVE-2022-3621 | known affected: 255 known not affected: 346 recommended: 1493 | 2026-07-25T17:28:29+00:00 | Vulnerability · Source |
| CVE-2022-3626 | suse_vex | SUSE CVE CVE-2022-3626 | known affected: 395 known not affected: 1 recommended: 267 | 2026-07-25T17:28:28+00:00 | Vulnerability · Source |
| CVE-2022-3628 | suse_vex | SUSE CVE CVE-2022-3628 | known affected: 261 known not affected: 2 recommended: 1587 | 2026-07-25T17:28:26+00:00 | Vulnerability · Source |
| CVE-2022-3633 | suse_vex | SUSE CVE CVE-2022-3633 | known affected: 271 known not affected: 321 recommended: 635 | 2026-07-25T17:28:24+00:00 | Vulnerability · Source |
| CVE-2022-3637 | suse_vex | SUSE CVE CVE-2022-3637 | known not affected: 167 | 2026-07-25T17:28:23+00:00 | Vulnerability · Source |
| CVE-2022-3640 | suse_vex | SUSE CVE CVE-2022-3640 | known affected: 228 known not affected: 213 recommended: 1264 | 2026-07-25T17:28:21+00:00 | Vulnerability · Source |
| CVE-2022-3646 | suse_vex | SUSE CVE CVE-2022-3646 | known affected: 261 known not affected: 321 recommended: 1493 | 2026-07-25T17:28:20+00:00 | Vulnerability · Source |
| CVE-2022-3676 | suse_vex | SUSE CVE CVE-2022-3676 | known affected: 394 recommended: 376 | 2026-07-25T17:28:18+00:00 | Vulnerability · Source |
| CVE-2022-3705 | suse_vex | SUSE CVE CVE-2022-3705 | known affected: 259 known not affected: 2 recommended: 510 | 2026-07-25T17:28:17+00:00 | Vulnerability · Source |
| CVE-2022-3718 | suse_vex | SUSE CVE CVE-2022-3718 | known not affected: 142 | 2026-07-25T17:28:15+00:00 | Vulnerability · Source |
| CVE-2022-3724 | suse_vex | SUSE CVE CVE-2022-3724 | known not affected: 319 | 2026-07-25T17:28:14+00:00 | Vulnerability · Source |
| 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 |