VEX records
Browse vendor VEX statements available in this Vulnerability-Lookup instance and pivot to the related vulnerability.
291949 VEX records
API response| Vulnerability | Source | Title | Product status | Imported | Links |
|---|---|---|---|---|---|
| CVE-2022-2380 | suse_vex | SUSE CVE CVE-2022-2380 | known not affected: 327 | 2026-07-25T17:29:43+00:00 | Vulnerability · Source |
| CVE-2022-2581 | suse_vex | SUSE CVE CVE-2022-2581 | known affected: 238 recommended: 505 | 2026-07-25T17:29:40+00:00 | Vulnerability · Source |
| CVE-2022-2946 | suse_vex | SUSE CVE CVE-2022-2946 | known affected: 237 known not affected: 2 recommended: 505 | 2026-07-25T17:29:28+00:00 | Vulnerability · Source |
| CVE-2022-2961 | suse_vex | SUSE CVE CVE-2022-2961 | known not affected: 264 | 2026-07-25T17:29:26+00:00 | Vulnerability · Source |
| CVE-2022-2982 | suse_vex | SUSE CVE CVE-2022-2982 | known affected: 259 known not affected: 2 recommended: 485 | 2026-07-25T17:29:23+00:00 | Vulnerability · Source |
| CVE-2022-3103 | suse_vex | SUSE CVE CVE-2022-3103 | known not affected: 327 | 2026-07-25T17:29:17+00:00 | Vulnerability · Source |
| CVE-2022-3170 | suse_vex | SUSE CVE CVE-2022-3170 | known not affected: 327 | 2026-07-25T17:29:10+00:00 | Vulnerability · Source |
| CVE-2022-3219 | suse_vex | SUSE CVE CVE-2022-3219 | known affected: 1 | 2026-07-25T17:29:08+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-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-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-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-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-3637 | suse_vex | SUSE CVE CVE-2022-3637 | known not affected: 167 | 2026-07-25T17:28:23+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-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-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-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-4543 | suse_vex | SUSE CVE CVE-2022-4543 | known not affected: 30 recommended: 14 | 2026-07-25T17:27:52+00:00 | Vulnerability · Source |
| CVE-2022-4696 | suse_vex | SUSE CVE CVE-2022-4696 | known not affected: 362 | 2026-07-25T17:27:51+00:00 | Vulnerability · Source |
| CVE-2022-4883 | suse_vex | SUSE CVE CVE-2022-4883 | known affected: 395 recommended: 170 | 2026-07-25T17:27:49+00:00 | Vulnerability · Source |
| CVE-2022-20153 | suse_vex | SUSE CVE CVE-2022-20153 | known not affected: 377 | 2026-07-25T17:27:46+00:00 | Vulnerability · Source |
| CVE-2022-20154 | suse_vex | SUSE CVE CVE-2022-20154 | known affected: 130 known not affected: 212 recommended: 1923 | 2026-07-25T17:27:45+00:00 | Vulnerability · Source |
| CVE-2022-20158 | suse_vex | SUSE CVE CVE-2022-20158 | known not affected: 327 | 2026-07-25T17:27:43+00:00 | Vulnerability · Source |
| CVE-2022-20382 | suse_vex | SUSE CVE CVE-2022-20382 | known not affected: 327 | 2026-07-25T17:27:37+00:00 | Vulnerability · Source |
| CVE-2022-21136 | suse_vex | SUSE CVE CVE-2022-21136 | known not affected: 87 recommended: 1 | 2026-07-25T17:27:31+00:00 | Vulnerability · Source |
| CVE-2022-21283 | suse_vex | SUSE CVE CVE-2022-21283 | known affected: 466 known not affected: 32 recommended: 1016 | 2026-07-25T17:27:28+00:00 | Vulnerability · Source |
| 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-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-22742 | suse_vex | SUSE CVE CVE-2022-22742 | recommended: 413 | 2026-07-25T17:26:51+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-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-23132 | suse_vex | SUSE CVE CVE-2022-23132 | known not affected: 37 | 2026-07-25T17:26:36+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-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 |