VEX records
Browse vendor VEX statements available in this Vulnerability-Lookup instance and pivot to the related vulnerability.
306222 VEX records
API response| Vulnerability | Source | Title | Product status | Imported | Links |
|---|---|---|---|---|---|
| CVE-2025-59942 | suse_vex | SUSE CVE CVE-2025-59942 | recommended: 1 | 2026-10-10T01:43:48+00:00 | Vulnerability · Source |
| CVE-2025-60753 | suse_vex | SUSE CVE CVE-2025-60753 | known affected: 506 recommended: 62 | 2026-10-10T01:43:46+00:00 | Vulnerability · Source |
| CVE-2025-60876 | suse_vex | SUSE CVE CVE-2025-60876 | known affected: 35 recommended: 115 | 2026-10-10T01:43:44+00:00 | Vulnerability · Source |
| CVE-2025-61100 | suse_vex | SUSE CVE CVE-2025-61100 | known affected: 267 known not affected: 335 recommended: 111 | 2026-10-10T01:43:42+00:00 | Vulnerability · Source |
| CVE-2025-61143 | suse_vex | SUSE CVE CVE-2025-61143 | known affected: 540 known not affected: 19 recommended: 25 | 2026-10-10T01:43:40+00:00 | Vulnerability · Source |
| CVE-2025-61524 | suse_vex | SUSE CVE CVE-2025-61524 | recommended: 1 | 2026-10-10T01:43:37+00:00 | Vulnerability · Source |
| CVE-2025-61662 | suse_vex | SUSE CVE CVE-2025-61662 | known affected: 734 recommended: 340 | 2026-10-10T01:43:36+00:00 | Vulnerability · Source |
| CVE-2025-61723 | suse_vex | SUSE CVE CVE-2025-61723 | known affected: 30 known not affected: 99 recommended: 293 | 2026-10-10T01:43:33+00:00 | Vulnerability · Source |
| CVE-2025-61724 | suse_vex | SUSE CVE CVE-2025-61724 | known affected: 30 known not affected: 69 recommended: 289 | 2026-10-10T01:43:32+00:00 | Vulnerability · Source |
| CVE-2025-61728 | suse_vex | SUSE CVE CVE-2025-61728 | known affected: 48 known not affected: 61 recommended: 355 | 2026-10-10T01:43:29+00:00 | Vulnerability · Source |
| CVE-2025-61731 | suse_vex | SUSE CVE CVE-2025-61731 | known affected: 48 known not affected: 109 recommended: 293 | 2026-10-10T01:43:27+00:00 | Vulnerability · Source |
| CVE-2025-61732 | suse_vex | SUSE CVE CVE-2025-61732 | known affected: 36 known not affected: 121 recommended: 285 | 2026-10-10T01:43:25+00:00 | Vulnerability · Source |
| CVE-2025-61748 | suse_vex | SUSE CVE CVE-2025-61748 | known affected: 394 known not affected: 567 recommended: 342 | 2026-10-10T01:43:23+00:00 | Vulnerability · Source |
| CVE-2025-61907 | suse_vex | SUSE CVE CVE-2025-61907 | known affected: 104 recommended: 8 | 2026-10-10T01:43:21+00:00 | Vulnerability · Source |
| CVE-2025-61908 | suse_vex | SUSE CVE CVE-2025-61908 | known not affected: 104 recommended: 8 | 2026-10-10T01:43:19+00:00 | Vulnerability · Source |
| CVE-2025-61909 | suse_vex | SUSE CVE CVE-2025-61909 | known not affected: 104 recommended: 8 | 2026-10-10T01:43:17+00:00 | Vulnerability · Source |
| CVE-2025-61984 | suse_vex | SUSE CVE CVE-2025-61984 | known affected: 425 recommended: 337 | 2026-10-10T01:43:15+00:00 | Vulnerability · Source |
| CVE-2025-61985 | suse_vex | SUSE CVE CVE-2025-61985 | known affected: 396 known not affected: 45 recommended: 321 | 2026-10-10T01:43:13+00:00 | Vulnerability · Source |
| CVE-2025-62171 | suse_vex | SUSE CVE CVE-2025-62171 | known affected: 322 known not affected: 24 recommended: 217 | 2026-10-10T01:43:11+00:00 | Vulnerability · Source |
| CVE-2025-62230 | suse_vex | SUSE CVE CVE-2025-62230 | known affected: 447 recommended: 196 | 2026-10-10T01:43:09+00:00 | Vulnerability · Source |
| CVE-2025-62231 | suse_vex | SUSE CVE CVE-2025-62231 | known affected: 447 recommended: 196 | 2026-10-10T01:43:07+00:00 | Vulnerability · Source |
| CVE-2025-62291 | suse_vex | SUSE CVE CVE-2025-62291 | known not affected: 106 recommended: 198 | 2026-10-10T01:43:05+00:00 | Vulnerability · Source |
| CVE-2025-62375 | suse_vex | SUSE CVE CVE-2025-62375 | recommended: 1 | 2026-10-10T01:43:02+00:00 | Vulnerability · Source |
| CVE-2025-62506 | suse_vex | SUSE CVE CVE-2025-62506 | recommended: 1 | 2026-10-10T01:42:59+00:00 | Vulnerability · Source |
| CVE-2025-62507 | suse_vex | SUSE CVE CVE-2025-62507 | known not affected: 60 recommended: 2 | 2026-10-10T01:42:58+00:00 | Vulnerability · Source |
| CVE-2025-62705 | suse_vex | SUSE CVE CVE-2025-62705 | recommended: 9 | 2026-10-10T01:42:56+00:00 | Vulnerability · Source |
| CVE-2025-62714 | suse_vex | SUSE CVE CVE-2025-62714 | recommended: 1 | 2026-10-10T01:42:54+00:00 | Vulnerability · Source |
| CVE-2025-62820 | suse_vex | SUSE CVE CVE-2025-62820 | recommended: 1 | 2026-10-10T01:42:52+00:00 | Vulnerability · Source |
| CVE-2025-64101 | suse_vex | SUSE CVE CVE-2025-64101 | recommended: 1 | 2026-10-10T01:42:48+00:00 | Vulnerability · Source |
| CVE-2025-64181 | suse_vex | SUSE CVE CVE-2025-64181 | known not affected: 186 recommended: 67 | 2026-10-10T01:42:46+00:00 | Vulnerability · Source |
| CVE-2025-64183 | suse_vex | SUSE CVE CVE-2025-64183 | known not affected: 186 recommended: 30 | 2026-10-10T01:42:44+00:00 | Vulnerability · Source |
| CVE-2025-64329 | suse_vex | SUSE CVE CVE-2025-64329 | known affected: 378 recommended: 127 | 2026-10-10T01:42:42+00:00 | Vulnerability · Source |
| CVE-2025-64432 | suse_vex | SUSE CVE CVE-2025-64432 | known affected: 1 known not affected: 76 recommended: 26 | 2026-10-10T01:42:40+00:00 | Vulnerability · Source |
| CVE-2025-64434 | suse_vex | SUSE CVE CVE-2025-64434 | known affected: 1 known not affected: 76 recommended: 26 | 2026-10-10T01:42:38+00:00 | Vulnerability · Source |
| CVE-2025-64436 | suse_vex | SUSE CVE CVE-2025-64436 | known not affected: 90 | 2026-10-10T01:42:36+00:00 | Vulnerability · Source |
| CVE-2025-64702 | suse_vex | SUSE CVE CVE-2025-64702 | recommended: 16 | 2026-10-10T01:42:32+00:00 | Vulnerability · Source |
| CVE-2025-64720 | suse_vex | SUSE CVE CVE-2025-64720 | known affected: 497 known not affected: 180 recommended: 559 | 2026-10-10T01:42:29+00:00 | Vulnerability · Source |
| CVE-2025-64751 | suse_vex | SUSE CVE CVE-2025-64751 | recommended: 21 | 2026-10-10T01:42:28+00:00 | Vulnerability · Source |
| CVE-2025-65018 | suse_vex | SUSE CVE CVE-2025-65018 | known affected: 473 known not affected: 207 recommended: 556 | 2026-10-10T01:42:26+00:00 | Vulnerability · Source |
| CVE-2025-66034 | suse_vex | SUSE CVE CVE-2025-66034 | known affected: 2 recommended: 9 | 2026-10-10T01:42:21+00:00 | Vulnerability · Source |
| CVE-2025-66037 | suse_vex | SUSE CVE CVE-2025-66037 | known affected: 406 known not affected: 14 recommended: 33 | 2026-10-10T01:42:19+00:00 | Vulnerability · Source |
| CVE-2025-66287 | suse_vex | SUSE CVE CVE-2025-66287 | known affected: 237 recommended: 588 | 2026-10-10T01:42:17+00:00 | Vulnerability · Source |
| CVE-2025-66418 | suse_vex | SUSE CVE CVE-2025-66418 | known affected: 458 known not affected: 12 recommended: 279 | 2026-10-10T01:42:14+00:00 | Vulnerability · Source |
| CVE-2025-66453 | suse_vex | SUSE CVE CVE-2025-66453 | known affected: 24 recommended: 39 | 2026-10-10T01:42:12+00:00 | Vulnerability · Source |
| CVE-2025-66471 | suse_vex | SUSE CVE CVE-2025-66471 | known affected: 470 recommended: 291 | 2026-10-10T01:42:11+00:00 | Vulnerability · Source |
| CVE-2025-66564 | suse_vex | SUSE CVE CVE-2025-66564 | recommended: 2 | 2026-10-10T01:42:08+00:00 | Vulnerability · Source |
| CVE-2025-66865 | suse_vex | SUSE CVE CVE-2025-66865 | known affected: 21 known not affected: 252 | 2026-10-10T01:42:05+00:00 | Vulnerability · Source |
| CVE-2025-68131 | suse_vex | SUSE CVE CVE-2025-68131 | known affected: 5 recommended: 8 | 2026-10-10T01:42:00+00:00 | Vulnerability · Source |
| CVE-2025-68146 | suse_vex | SUSE CVE CVE-2025-68146 | known affected: 40 recommended: 21 | 2026-10-10T01:41:58+00:00 | Vulnerability · Source |
| CVE-2025-68156 | suse_vex | SUSE CVE CVE-2025-68156 | known affected: 2 recommended: 113 | 2026-10-10T01:41:56+00:00 | Vulnerability · Source |