VEX records
Browse vendor VEX statements available in this Vulnerability-Lookup instance and pivot to the related vulnerability.
293999 VEX records
API response| Vulnerability | Source | Title | Product status | Imported | Links |
|---|---|---|---|---|---|
| CVE-2024-57843 | suse_vex | SUSE CVE CVE-2024-57843 | known not affected: 453 recommended: 43 | 2026-07-31T01:23:39+00:00 | Vulnerability · Source |
| CVE-2024-58010 | suse_vex | SUSE CVE CVE-2024-58010 | known not affected: 461 | 2026-07-31T01:23:14+00:00 | Vulnerability · Source |
| CVE-2025-2786 | suse_vex | SUSE CVE CVE-2025-2786 | No product status | 2026-07-31T01:22:50+00:00 | Vulnerability · Source |
| CVE-2025-2842 | suse_vex | SUSE CVE CVE-2025-2842 | No product status | 2026-07-31T01:22:47+00:00 | Vulnerability · Source |
| CVE-2025-2843 | suse_vex | SUSE CVE CVE-2025-2843 | No product status | 2026-07-31T01:22:45+00:00 | Vulnerability · Source |
| CVE-2025-6203 | suse_vex | SUSE CVE CVE-2025-6203 | recommended: 9 | 2026-07-31T01:22:23+00:00 | Vulnerability · Source |
| CVE-2025-7453 | suse_vex | SUSE CVE CVE-2025-7453 | No product status | 2026-07-31T01:22:20+00:00 | Vulnerability · Source |
| CVE-2025-11776 | suse_vex | SUSE CVE CVE-2025-11776 | No product status | 2026-07-31T01:21:51+00:00 | Vulnerability · Source |
| CVE-2025-11794 | suse_vex | SUSE CVE CVE-2025-11794 | No product status | 2026-07-31T01:21:49+00:00 | Vulnerability · Source |
| CVE-2025-13353 | suse_vex | SUSE CVE CVE-2025-13353 | No product status | 2026-07-31T01:21:46+00:00 | Vulnerability · Source |
| CVE-2025-14576 | suse_vex | SUSE CVE CVE-2025-14576 | known affected: 169 known not affected: 402 recommended: 4 | 2026-07-31T01:21:38+00:00 | Vulnerability · Source |
| CVE-2025-21672 | suse_vex | SUSE CVE CVE-2025-21672 | known not affected: 459 recommended: 41 | 2026-07-31T01:20:58+00:00 | Vulnerability · Source |
| CVE-2025-37802 | suse_vex | SUSE CVE CVE-2025-37802 | known not affected: 456 | 2026-07-31T01:15:57+00:00 | Vulnerability · Source |
| CVE-2025-37883 | suse_vex | SUSE CVE CVE-2025-37883 | known affected: 180 known not affected: 120 | 2026-07-31T01:15:09+00:00 | Vulnerability · Source |
| CVE-2025-37906 | suse_vex | SUSE CVE CVE-2025-37906 | known not affected: 455 | 2026-07-31T01:14:56+00:00 | Vulnerability · Source |
| CVE-2025-37956 | suse_vex | SUSE CVE CVE-2025-37956 | known not affected: 449 | 2026-07-31T01:14:28+00:00 | Vulnerability · Source |
| CVE-2025-38037 | suse_vex | SUSE CVE CVE-2025-38037 | known affected: 269 known not affected: 70 | 2026-07-31T01:13:49+00:00 | Vulnerability · Source |
| CVE-2025-38194 | suse_vex | SUSE CVE CVE-2025-38194 | known affected: 394 known not affected: 378 recommended: 354 | 2026-07-31T01:12:22+00:00 | Vulnerability · Source |
| CVE-2025-38366 | suse_vex | SUSE CVE CVE-2025-38366 | known not affected: 416 | 2026-07-31T01:10:24+00:00 | Vulnerability · Source |
| CVE-2025-38657 | suse_vex | SUSE CVE CVE-2025-38657 | known not affected: 416 | 2026-07-31T01:07:41+00:00 | Vulnerability · Source |
| CVE-2025-39697 | suse_vex | SUSE CVE CVE-2025-39697 | first fixed: 2 known affected: 557 known not affected: 102 recommended: 604 | 2026-07-31T01:06:47+00:00 | Vulnerability · Source |
| CVE-2025-39791 | suse_vex | SUSE CVE CVE-2025-39791 | first fixed: 2 known affected: 5 known not affected: 435 recommended: 154 | 2026-07-31T01:06:17+00:00 | Vulnerability · Source |
| CVE-2025-39908 | suse_vex | SUSE CVE CVE-2025-39908 | known not affected: 416 | 2026-07-31T01:05:23+00:00 | Vulnerability · Source |
| CVE-2025-39966 | suse_vex | SUSE CVE CVE-2025-39966 | known not affected: 416 recommended: 83 | 2026-07-31T01:04:51+00:00 | Vulnerability · Source |
| CVE-2025-39990 | suse_vex | SUSE CVE CVE-2025-39990 | first fixed: 2 known affected: 247 known not affected: 6 recommended: 154 | 2026-07-31T01:04:30+00:00 | Vulnerability · Source |
| CVE-2025-40079 | suse_vex | SUSE CVE CVE-2025-40079 | known not affected: 410 recommended: 6 | 2026-07-31T01:03:52+00:00 | Vulnerability · Source |
| CVE-2025-40151 | suse_vex | SUSE CVE CVE-2025-40151 | known not affected: 408 | 2026-07-31T01:03:16+00:00 | Vulnerability · Source |
| CVE-2025-40356 | suse_vex | SUSE CVE CVE-2025-40356 | known not affected: 418 | 2026-07-31T01:01:30+00:00 | Vulnerability · Source |
| CVE-2025-41436 | suse_vex | SUSE CVE CVE-2025-41436 | No product status | 2026-07-31T01:01:24+00:00 | Vulnerability · Source |
| CVE-2025-46809 | suse_vex | SUSE CVE CVE-2025-46809 | known affected: 394 known not affected: 3 recommended: 68 | 2026-07-31T01:01:15+00:00 | Vulnerability · Source |
| CVE-2025-50327 | suse_vex | SUSE CVE CVE-2025-50327 | No product status | 2026-07-31T01:01:03+00:00 | Vulnerability · Source |
| CVE-2025-52490 | suse_vex | SUSE CVE CVE-2025-52490 | No product status | 2026-07-31T01:00:57+00:00 | Vulnerability · Source |
| CVE-2025-55070 | suse_vex | SUSE CVE CVE-2025-55070 | No product status | 2026-07-31T01:00:47+00:00 | Vulnerability · Source |
| CVE-2025-55073 | suse_vex | SUSE CVE CVE-2025-55073 | No product status | 2026-07-31T01:00:45+00:00 | Vulnerability · Source |
| CVE-2025-63811 | suse_vex | SUSE CVE CVE-2025-63811 | No product status | 2026-07-31T01:00:13+00:00 | Vulnerability · Source |
| CVE-2025-63913 | suse_vex | SUSE CVE CVE-2025-63913 | No product status | 2026-07-31T01:00:10+00:00 | Vulnerability · Source |
| CVE-2025-64171 | suse_vex | SUSE CVE CVE-2025-64171 | No product status | 2026-07-31T01:00:07+00:00 | Vulnerability · Source |
| CVE-2025-64178 | suse_vex | SUSE CVE CVE-2025-64178 | No product status | 2026-07-31T01:00:05+00:00 | Vulnerability · Source |
| CVE-2025-64179 | suse_vex | SUSE CVE CVE-2025-64179 | No product status | 2026-07-31T01:00:02+00:00 | Vulnerability · Source |
| CVE-2025-64186 | suse_vex | SUSE CVE CVE-2025-64186 | No product status | 2026-07-31T00:59:57+00:00 | Vulnerability · Source |
| CVE-2025-64323 | suse_vex | SUSE CVE CVE-2025-64323 | No product status | 2026-07-31T00:59:54+00:00 | Vulnerability · Source |
| CVE-2025-64431 | suse_vex | SUSE CVE CVE-2025-64431 | No product status | 2026-07-31T00:59:51+00:00 | Vulnerability · Source |
| CVE-2025-64484 | suse_vex | SUSE CVE CVE-2025-64484 | No product status | 2026-07-31T00:59:48+00:00 | Vulnerability · Source |
| CVE-2025-64494 | suse_vex | SUSE CVE CVE-2025-64494 | No product status | 2026-07-31T00:59:46+00:00 | Vulnerability · Source |
| CVE-2025-64513 | suse_vex | SUSE CVE CVE-2025-64513 | No product status | 2026-07-31T00:59:43+00:00 | Vulnerability · Source |
| CVE-2025-64522 | suse_vex | SUSE CVE CVE-2025-64522 | No product status | 2026-07-31T00:59:41+00:00 | Vulnerability · Source |
| CVE-2025-64523 | suse_vex | SUSE CVE CVE-2025-64523 | No product status | 2026-07-31T00:59:40+00:00 | Vulnerability · Source |
| CVE-2025-64529 | suse_vex | SUSE CVE CVE-2025-64529 | No product status | 2026-07-31T00:59:38+00:00 | Vulnerability · Source |
| CVE-2025-64717 | suse_vex | SUSE CVE CVE-2025-64717 | No product status | 2026-07-31T00:59:36+00:00 | Vulnerability · Source |
| CVE-2025-64719 | suse_vex | SUSE CVE CVE-2025-64719 | No product status | 2026-07-31T00:59:34+00:00 | Vulnerability · Source |