VEX records
Browse vendor VEX statements available in this Vulnerability-Lookup instance and pivot to the related vulnerability.
294017 VEX records
API response| Vulnerability | Source | Title | Product status | Imported | Links |
|---|---|---|---|---|---|
| CVE-2021-46999 | suse_vex | SUSE CVE CVE-2021-46999 | known not affected: 292 | 2026-07-25T17:36:43+00:00 | Vulnerability · Source |
| CVE-2021-47002 | suse_vex | SUSE CVE CVE-2021-47002 | known not affected: 292 | 2026-07-25T17:36:41+00:00 | Vulnerability · Source |
| CVE-2021-47004 | suse_vex | SUSE CVE CVE-2021-47004 | known not affected: 292 | 2026-07-25T17:36:40+00:00 | Vulnerability · Source |
| CVE-2021-47023 | suse_vex | SUSE CVE CVE-2021-47023 | known not affected: 292 | 2026-07-25T17:36:28+00:00 | Vulnerability · Source |
| CVE-2021-47027 | suse_vex | SUSE CVE CVE-2021-47027 | known not affected: 292 | 2026-07-25T17:36:26+00:00 | Vulnerability · Source |
| CVE-2021-47028 | suse_vex | SUSE CVE CVE-2021-47028 | known not affected: 292 | 2026-07-25T17:36:24+00:00 | Vulnerability · Source |
| CVE-2021-47037 | suse_vex | SUSE CVE CVE-2021-47037 | known not affected: 292 | 2026-07-25T17:36:20+00:00 | Vulnerability · Source |
| CVE-2021-47048 | suse_vex | SUSE CVE CVE-2021-47048 | known not affected: 275 | 2026-07-25T17:36:15+00:00 | Vulnerability · Source |
| CVE-2021-47050 | suse_vex | SUSE CVE CVE-2021-47050 | known not affected: 292 | 2026-07-25T17:36:12+00:00 | Vulnerability · Source |
| CVE-2021-47057 | suse_vex | SUSE CVE CVE-2021-47057 | known not affected: 292 | 2026-07-25T17:36:08+00:00 | Vulnerability · Source |
| CVE-2021-47058 | suse_vex | SUSE CVE CVE-2021-47058 | known affected: 388 known not affected: 233 recommended: 137 | 2026-07-25T17:36:07+00:00 | Vulnerability · Source |
| CVE-2021-47065 | suse_vex | SUSE CVE CVE-2021-47065 | known affected: 388 known not affected: 233 recommended: 137 | 2026-07-25T17:36:03+00:00 | Vulnerability · Source |
| CVE-2021-47079 | suse_vex | SUSE CVE CVE-2021-47079 | known not affected: 292 | 2026-07-25T17:35:56+00:00 | Vulnerability · Source |
| CVE-2021-47122 | suse_vex | SUSE CVE CVE-2021-47122 | known affected: 44 known not affected: 329 | 2026-07-25T17:35:37+00:00 | Vulnerability · Source |
| CVE-2021-47152 | suse_vex | SUSE CVE CVE-2021-47152 | known not affected: 292 | 2026-07-25T17:35:28+00:00 | Vulnerability · Source |
| CVE-2021-47262 | suse_vex | SUSE CVE CVE-2021-47262 | known not affected: 330 | 2026-07-25T17:34:40+00:00 | Vulnerability · Source |
| CVE-2021-47271 | suse_vex | SUSE CVE CVE-2021-47271 | known not affected: 330 | 2026-07-25T17:34:39+00:00 | Vulnerability · Source |
| CVE-2021-47290 | suse_vex | SUSE CVE CVE-2021-47290 | known not affected: 330 | 2026-07-25T17:34:29+00:00 | Vulnerability · Source |
| CVE-2021-47326 | suse_vex | SUSE CVE CVE-2021-47326 | known not affected: 247 | 2026-07-25T17:34:11+00:00 | Vulnerability · Source |
| CVE-2021-47329 | suse_vex | SUSE CVE CVE-2021-47329 | known affected: 486 known not affected: 173 recommended: 91 | 2026-07-25T17:34:09+00:00 | Vulnerability · Source |
| CVE-2021-47339 | suse_vex | SUSE CVE CVE-2021-47339 | known not affected: 330 | 2026-07-25T17:34:03+00:00 | Vulnerability · Source |
| CVE-2021-47365 | suse_vex | SUSE CVE CVE-2021-47365 | known affected: 275 known not affected: 217 recommended: 452 | 2026-07-25T17:33:49+00:00 | Vulnerability · Source |
| CVE-2021-47619 | suse_vex | SUSE CVE CVE-2021-47619 | known affected: 412 known not affected: 60 recommended: 566 | 2026-07-25T17:31:57+00:00 | Vulnerability · Source |
| CVE-2021-47645 | suse_vex | SUSE CVE CVE-2021-47645 | known affected: 334 known not affected: 270 recommended: 263 | 2026-07-25T17:31:49+00:00 | Vulnerability · Source |
| CVE-2021-47655 | suse_vex | SUSE CVE CVE-2021-47655 | known not affected: 352 | 2026-07-25T17:31:43+00:00 | Vulnerability · Source |
| CVE-2022-1270 | suse_vex | SUSE CVE CVE-2022-1270 | known affected: 3 known not affected: 335 recommended: 142 | 2026-07-25T17:30:40+00:00 | Vulnerability · Source |
| CVE-2022-1304 | suse_vex | SUSE CVE CVE-2022-1304 | known affected: 351 known not affected: 3 recommended: 679 | 2026-07-25T17:30:37+00:00 | Vulnerability · Source |
| CVE-2022-1725 | suse_vex | SUSE CVE CVE-2022-1725 | known not affected: 240 | 2026-07-25T17:30:21+00:00 | Vulnerability · Source |
| CVE-2022-2209 | suse_vex | SUSE CVE CVE-2022-2209 | known not affected: 327 | 2026-07-25T17:29:58+00:00 | Vulnerability · Source |
| CVE-2022-2287 | suse_vex | SUSE CVE CVE-2022-2287 | known affected: 237 known not affected: 26 recommended: 505 | 2026-07-25T17:29:50+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-3529 | suse_vex | SUSE CVE CVE-2022-3529 | known not affected: 117 | 2026-07-25T17:28:52+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-3544 | suse_vex | SUSE CVE CVE-2022-3544 | known not affected: 327 | 2026-07-25T17:28:46+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-20158 | suse_vex | SUSE CVE CVE-2022-20158 | known not affected: 327 | 2026-07-25T17:27:43+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-22058 | suse_vex | SUSE CVE CVE-2022-22058 | known not affected: 327 | 2026-07-25T17:27:00+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-23901 | suse_vex | SUSE CVE CVE-2022-23901 | known not affected: 66 | 2026-07-25T17:26:19+00:00 | Vulnerability · Source |
| CVE-2022-24107 | suse_vex | SUSE CVE CVE-2022-24107 | known affected: 1 known not affected: 259 | 2026-07-25T17:26:13+00:00 | Vulnerability · Source |
| CVE-2022-25368 | suse_vex | SUSE CVE CVE-2022-25368 | known not affected: 401 | 2026-07-25T17:25:54+00:00 | Vulnerability · Source |
| CVE-2022-26357 | suse_vex | SUSE CVE CVE-2022-26357 | known affected: 349 known not affected: 74 recommended: 446 | 2026-07-25T17:25:51+00:00 | Vulnerability · Source |
| CVE-2022-27385 | suse_vex | SUSE CVE CVE-2022-27385 | known not affected: 347 recommended: 16 | 2026-07-25T17:25:37+00:00 | Vulnerability · Source |
| CVE-2022-33748 | suse_vex | SUSE CVE CVE-2022-33748 | known affected: 252 recommended: 517 | 2026-07-25T17:24:16+00:00 | Vulnerability · Source |
| CVE-2022-34485 | suse_vex | SUSE CVE CVE-2022-34485 | known affected: 1 recommended: 365 | 2026-07-25T17:24:06+00:00 | Vulnerability · Source |