VEX records
Browse vendor VEX statements available in this Vulnerability-Lookup instance and pivot to the related vulnerability.
291935 VEX records
API response| Vulnerability | Source | Title | Product status | Imported | Links |
|---|---|---|---|---|---|
| CVE-2021-31535 | suse_vex | SUSE CVE CVE-2021-31535 | known affected: 403 recommended: 504 | 2026-07-31T17:05:33+00:00 | Vulnerability · Source |
| CVE-2021-34798 | suse_vex | SUSE CVE CVE-2021-34798 | known affected: 419 known not affected: 5 recommended: 396 | 2026-07-31T17:05:29+00:00 | Vulnerability · Source |
| CVE-2021-45469 | suse_vex | SUSE CVE CVE-2021-45469 | known not affected: 416 | 2026-07-31T17:05:17+00:00 | Vulnerability · Source |
| CVE-2021-46904 | suse_vex | SUSE CVE CVE-2021-46904 | known affected: 480 known not affected: 180 recommended: 264 | 2026-07-31T17:05:15+00:00 | Vulnerability · Source |
| CVE-2021-47279 | suse_vex | SUSE CVE CVE-2021-47279 | known not affected: 330 | 2026-07-31T17:05:10+00:00 | Vulnerability · Source |
| CVE-2022-1015 | suse_vex | SUSE CVE CVE-2022-1015 | known affected: 32 known not affected: 18 recommended: 364 | 2026-07-31T17:04:55+00:00 | Vulnerability · Source |
| CVE-2022-1651 | suse_vex | SUSE CVE CVE-2022-1651 | known affected: 257 known not affected: 339 recommended: 615 | 2026-07-31T17:04:51+00:00 | Vulnerability · Source |
| CVE-2022-3531 | suse_vex | SUSE CVE CVE-2022-3531 | known not affected: 327 | 2026-07-31T17:04:43+00:00 | Vulnerability · Source |
| CVE-2022-22737 | suse_vex | SUSE CVE CVE-2022-22737 | recommended: 413 | 2026-07-31T17:04:31+00:00 | Vulnerability · Source |
| CVE-2022-27666 | suse_vex | SUSE CVE CVE-2022-27666 | known not affected: 208 recommended: 1026 | 2026-07-31T17:04:26+00:00 | Vulnerability · Source |
| CVE-2022-34468 | suse_vex | SUSE CVE CVE-2022-34468 | known affected: 1 recommended: 482 | 2026-07-31T17:04:20+00:00 | Vulnerability · Source |
| CVE-2022-35948 | suse_vex | SUSE CVE CVE-2022-35948 | known not affected: 194 recommended: 128 | 2026-07-31T17:04:19+00:00 | Vulnerability · Source |
| CVE-2022-38238 | suse_vex | SUSE CVE CVE-2022-38238 | known not affected: 330 | 2026-07-31T17:04:16+00:00 | Vulnerability · Source |
| CVE-2022-42890 | suse_vex | SUSE CVE CVE-2022-42890 | recommended: 71 | 2026-07-31T17:04:05+00:00 | Vulnerability · Source |
| CVE-2022-46344 | suse_vex | SUSE CVE CVE-2022-46344 | known affected: 395 recommended: 309 | 2026-07-31T17:03:59+00:00 | Vulnerability · Source |
| CVE-2022-48770 | suse_vex | SUSE CVE CVE-2022-48770 | known affected: 434 known not affected: 202 recommended: 298 | 2026-07-31T17:03:55+00:00 | Vulnerability · Source |
| CVE-2022-48966 | suse_vex | SUSE CVE CVE-2022-48966 | known affected: 390 known not affected: 260 recommended: 311 | 2026-07-31T17:03:45+00:00 | Vulnerability · Source |
| CVE-2022-49048 | suse_vex | SUSE CVE CVE-2022-49048 | known affected: 112 known not affected: 240 | 2026-07-31T17:03:39+00:00 | Vulnerability · Source |
| CVE-2022-49192 | suse_vex | SUSE CVE CVE-2022-49192 | known not affected: 302 recommended: 70 | 2026-07-31T17:03:36+00:00 | Vulnerability · Source |
| CVE-2022-49245 | suse_vex | SUSE CVE CVE-2022-49245 | known not affected: 352 | 2026-07-31T17:03:33+00:00 | Vulnerability · Source |
| CVE-2022-49510 | suse_vex | SUSE CVE CVE-2022-49510 | known affected: 364 known not affected: 302 recommended: 100 | 2026-07-31T17:03:28+00:00 | Vulnerability · Source |
| CVE-2022-49563 | suse_vex | SUSE CVE CVE-2022-49563 | known affected: 424 known not affected: 148 recommended: 370 | 2026-07-31T17:03:25+00:00 | Vulnerability · Source |
| CVE-2022-49883 | suse_vex | SUSE CVE CVE-2022-49883 | known not affected: 397 | 2026-07-31T17:03:19+00:00 | Vulnerability · Source |
| CVE-2022-49911 | suse_vex | SUSE CVE CVE-2022-49911 | known affected: 55 known not affected: 342 recommended: 27 | 2026-07-31T17:03:17+00:00 | Vulnerability · Source |
| CVE-2022-49926 | suse_vex | SUSE CVE CVE-2022-49926 | known affected: 154 known not affected: 258 | 2026-07-31T17:03:16+00:00 | Vulnerability · Source |
| CVE-2022-50113 | suse_vex | SUSE CVE CVE-2022-50113 | known not affected: 401 recommended: 47 | 2026-07-31T17:03:12+00:00 | Vulnerability · Source |
| CVE-2022-50639 | suse_vex | SUSE CVE CVE-2022-50639 | known not affected: 408 recommended: 29 | 2026-07-31T17:03:03+00:00 | Vulnerability · Source |
| CVE-2022-50645 | suse_vex | SUSE CVE CVE-2022-50645 | known affected: 191 known not affected: 217 recommended: 29 | 2026-07-31T17:03:01+00:00 | Vulnerability · Source |
| CVE-2022-50758 | suse_vex | SUSE CVE CVE-2022-50758 | known affected: 354 known not affected: 329 recommended: 200 | 2026-07-31T17:02:59+00:00 | Vulnerability · Source |
| CVE-2022-50763 | suse_vex | SUSE CVE CVE-2022-50763 | known affected: 354 known not affected: 309 recommended: 196 | 2026-07-31T17:02:57+00:00 | Vulnerability · Source |
| CVE-2022-50779 | suse_vex | SUSE CVE CVE-2022-50779 | known affected: 354 known not affected: 204 recommended: 219 | 2026-07-31T17:02:55+00:00 | Vulnerability · Source |
| CVE-2023-1601 | suse_vex | SUSE CVE CVE-2023-1601 | known not affected: 340 | 2026-07-31T17:02:51+00:00 | Vulnerability · Source |
| CVE-2023-36661 | suse_vex | SUSE CVE CVE-2023-36661 | known affected: 84 known not affected: 178 recommended: 108 | 2026-07-31T17:02:31+00:00 | Vulnerability · Source |
| CVE-2024-26886 | suse_vex | SUSE CVE CVE-2024-26886 | known affected: 620 known not affected: 114 recommended: 385 | 2026-07-31T17:01:46+00:00 | Vulnerability · Source |
| CVE-2024-41053 | suse_vex | SUSE CVE CVE-2024-41053 | known not affected: 324 | 2026-07-31T17:01:23+00:00 | Vulnerability · Source |
| CVE-2024-49940 | suse_vex | SUSE CVE CVE-2024-49940 | known affected: 759 known not affected: 38 recommended: 355 | 2026-07-31T17:01:08+00:00 | Vulnerability · Source |
| CVE-2024-50191 | suse_vex | SUSE CVE CVE-2024-50191 | known affected: 129 recommended: 49 | 2026-07-31T17:01:04+00:00 | Vulnerability · Source |
| CVE-2024-50251 | suse_vex | SUSE CVE CVE-2024-50251 | known affected: 702 known not affected: 60 recommended: 372 | 2026-07-31T17:01:02+00:00 | Vulnerability · Source |
| CVE-2024-50304 | suse_vex | SUSE CVE CVE-2024-50304 | known affected: 705 known not affected: 42 recommended: 393 | 2026-07-31T17:01:00+00:00 | Vulnerability · Source |
| CVE-2024-53051 | suse_vex | SUSE CVE CVE-2024-53051 | known affected: 624 known not affected: 36 recommended: 463 | 2026-07-31T17:00:58+00:00 | Vulnerability · Source |
| CVE-2024-56378 | suse_vex | SUSE CVE CVE-2024-56378 | known affected: 284 recommended: 186 | 2026-07-31T17:00:45+00:00 | Vulnerability · Source |
| CVE-2025-2830 | suse_vex | SUSE CVE CVE-2025-2830 | known affected: 16 known not affected: 134 recommended: 24 | 2026-07-31T17:00:17+00:00 | Vulnerability · Source |
| CVE-2025-21860 | suse_vex | SUSE CVE CVE-2025-21860 | known affected: 57 known not affected: 291 | 2026-07-31T16:59:50+00:00 | Vulnerability · Source |
| CVE-2025-23153 | suse_vex | SUSE CVE CVE-2025-23153 | known not affected: 397 | 2026-07-31T16:59:40+00:00 | Vulnerability · Source |
| CVE-2025-31133 | suse_vex | SUSE CVE CVE-2025-31133 | known affected: 388 known not affected: 1148 recommended: 237 | 2026-07-31T16:59:33+00:00 | Vulnerability · Source |
| CVE-2025-52565 | suse_vex | SUSE CVE CVE-2025-52565 | known affected: 388 known not affected: 1148 recommended: 236 | 2026-07-31T16:57:50+00:00 | Vulnerability · Source |
| CVE-2025-52881 | suse_vex | SUSE CVE CVE-2025-52881 | known affected: 388 known not affected: 1148 recommended: 288 | 2026-07-31T16:57:48+00:00 | Vulnerability · Source |
| CVE-2025-64181 | suse_vex | SUSE CVE CVE-2025-64181 | known not affected: 143 recommended: 67 | 2026-07-31T16:57:18+00:00 | Vulnerability · Source |
| CVE-2025-64344 | suse_vex | SUSE CVE CVE-2025-64344 | recommended: 3 | 2026-07-31T16:57:15+00:00 | Vulnerability · Source |
| CVE-2025-64432 | suse_vex | SUSE CVE CVE-2025-64432 | first fixed: 1 known not affected: 70 recommended: 28 | 2026-07-31T16:57:14+00:00 | Vulnerability · Source |