VEX records
Browse vendor VEX statements available in this Vulnerability-Lookup instance and pivot to the related vulnerability.
288107 VEX records
API response| Vulnerability | Source | Title | Product status | Imported | Links |
|---|---|---|---|---|---|
| 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-39698 | suse_vex | SUSE CVE CVE-2025-39698 | first fixed: 2 known affected: 5 known not affected: 435 recommended: 201 | 2026-07-31T01:06:45+00:00 | Vulnerability · Source |
| CVE-2025-39718 | suse_vex | SUSE CVE CVE-2025-39718 | first fixed: 2 known affected: 451 known not affected: 205 recommended: 614 | 2026-07-31T01:06:38+00:00 | Vulnerability · Source |
| CVE-2025-39779 | suse_vex | SUSE CVE CVE-2025-39779 | first fixed: 2 known affected: 506 known not affected: 156 recommended: 154 | 2026-07-31T01:06:23+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-39802 | suse_vex | SUSE CVE CVE-2025-39802 | known not affected: 416 | 2026-07-31T01:06:12+00:00 | Vulnerability · Source |
| CVE-2025-39804 | suse_vex | SUSE CVE CVE-2025-39804 | known not affected: 416 | 2026-07-31T01:06:10+00:00 | Vulnerability · Source |
| CVE-2025-39806 | suse_vex | SUSE CVE CVE-2025-39806 | first fixed: 2 known affected: 456 known not affected: 211 recommended: 583 | 2026-07-31T01:06:07+00:00 | Vulnerability · Source |
| CVE-2025-39815 | suse_vex | SUSE CVE CVE-2025-39815 | known affected: 2 known not affected: 414 | 2026-07-31T01:06:02+00:00 | Vulnerability · Source |
| CVE-2025-39818 | suse_vex | SUSE CVE CVE-2025-39818 | known not affected: 416 recommended: 110 | 2026-07-31T01:05:59+00:00 | Vulnerability · Source |
| CVE-2025-39837 | suse_vex | SUSE CVE CVE-2025-39837 | known not affected: 416 | 2026-07-31T01:05:51+00:00 | Vulnerability · Source |
| CVE-2025-39840 | suse_vex | SUSE CVE CVE-2025-39840 | known not affected: 416 recommended: 83 | 2026-07-31T01:05:48+00:00 | Vulnerability · Source |
| CVE-2025-39849 | suse_vex | SUSE CVE CVE-2025-39849 | first fixed: 2 known affected: 454 known not affected: 211 recommended: 606 | 2026-07-31T01:05:45+00:00 | Vulnerability · Source |
| CVE-2025-39862 | suse_vex | SUSE CVE CVE-2025-39862 | known not affected: 205 | 2026-07-31T01:05:41+00:00 | Vulnerability · Source |
| CVE-2025-39868 | suse_vex | SUSE CVE CVE-2025-39868 | known not affected: 416 | 2026-07-31T01:05:37+00:00 | Vulnerability · Source |
| CVE-2025-39872 | suse_vex | SUSE CVE CVE-2025-39872 | known not affected: 416 | 2026-07-31T01:05:34+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-39918 | suse_vex | SUSE CVE CVE-2025-39918 | first fixed: 2 known not affected: 410 recommended: 237 | 2026-07-31T01:05:21+00:00 | Vulnerability · Source |
| CVE-2025-39928 | suse_vex | SUSE CVE CVE-2025-39928 | known not affected: 416 | 2026-07-31T01:05:17+00:00 | Vulnerability · Source |
| CVE-2025-39933 | suse_vex | SUSE CVE CVE-2025-39933 | known not affected: 416 recommended: 103 | 2026-07-31T01:05:12+00:00 | Vulnerability · Source |
| CVE-2025-39942 | suse_vex | SUSE CVE CVE-2025-39942 | known not affected: 416 | 2026-07-31T01:05:07+00:00 | Vulnerability · Source |
| CVE-2025-39943 | suse_vex | SUSE CVE CVE-2025-39943 | known not affected: 416 | 2026-07-31T01:05:05+00:00 | Vulnerability · Source |
| CVE-2025-39961 | suse_vex | SUSE CVE CVE-2025-39961 | first fixed: 2 known affected: 233 known not affected: 22 recommended: 154 | 2026-07-31T01:04:57+00:00 | Vulnerability · Source |
| CVE-2025-39963 | suse_vex | SUSE CVE CVE-2025-39963 | first fixed: 2 known affected: 399 known not affected: 433 recommended: 162 | 2026-07-31T01:04:54+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-39979 | suse_vex | SUSE CVE CVE-2025-39979 | first fixed: 2 known affected: 394 known not affected: 435 recommended: 237 | 2026-07-31T01:04:40+00:00 | Vulnerability · Source |
| CVE-2025-39981 | suse_vex | SUSE CVE CVE-2025-39981 | first fixed: 2 known affected: 374 known not affected: 211 recommended: 690 | 2026-07-31T01:04:38+00:00 | Vulnerability · Source |
| CVE-2025-39982 | suse_vex | SUSE CVE CVE-2025-39982 | first fixed: 2 known affected: 394 known not affected: 265 recommended: 583 | 2026-07-31T01:04:36+00:00 | Vulnerability · Source |
| CVE-2025-39983 | suse_vex | SUSE CVE CVE-2025-39983 | known not affected: 416 recommended: 83 | 2026-07-31T01:04:34+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-40028 | suse_vex | SUSE CVE CVE-2025-40028 | known not affected: 407 recommended: 6 | 2026-07-31T01:04:19+00:00 | Vulnerability · Source |
| CVE-2025-40039 | suse_vex | SUSE CVE CVE-2025-40039 | known not affected: 459 recommended: 6 | 2026-07-31T01:04:15+00:00 | Vulnerability · Source |
| CVE-2025-40046 | suse_vex | SUSE CVE CVE-2025-40046 | known not affected: 407 recommended: 6 | 2026-07-31T01:04:10+00:00 | Vulnerability · Source |
| CVE-2025-40047 | suse_vex | SUSE CVE CVE-2025-40047 | first fixed: 2 known affected: 394 known not affected: 376 recommended: 354 | 2026-07-31T01:04:07+00:00 | Vulnerability · Source |
| CVE-2025-40064 | suse_vex | SUSE CVE CVE-2025-40064 | first fixed: 2 known affected: 594 known not affected: 38 recommended: 632 | 2026-07-31T01:03:59+00:00 | Vulnerability · Source |
| CVE-2025-40069 | suse_vex | SUSE CVE CVE-2025-40069 | known not affected: 407 recommended: 6 | 2026-07-31T01:03:56+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-40090 | suse_vex | SUSE CVE CVE-2025-40090 | known not affected: 407 recommended: 6 | 2026-07-31T01:03:45+00:00 | Vulnerability · Source |
| CVE-2025-40092 | suse_vex | SUSE CVE CVE-2025-40092 | known affected: 336 recommended: 6 | 2026-07-31T01:03:43+00:00 | Vulnerability · Source |
| CVE-2025-40094 | suse_vex | SUSE CVE CVE-2025-40094 | known not affected: 407 recommended: 6 | 2026-07-31T01:03:41+00:00 | Vulnerability · Source |
| CVE-2025-40096 | suse_vex | SUSE CVE CVE-2025-40096 | first fixed: 2 known affected: 451 known not affected: 205 recommended: 609 | 2026-07-31T01:03:38+00:00 | Vulnerability · Source |
| CVE-2025-40104 | suse_vex | SUSE CVE CVE-2025-40104 | first fixed: 2 known affected: 718 known not affected: 52 recommended: 271 | 2026-07-31T01:03:33+00:00 | Vulnerability · Source |
| CVE-2025-40133 | suse_vex | SUSE CVE CVE-2025-40133 | first fixed: 2 known not affected: 433 recommended: 196 | 2026-07-31T01:03:25+00:00 | Vulnerability · Source |
| CVE-2025-40135 | suse_vex | SUSE CVE CVE-2025-40135 | first fixed: 2 known affected: 663 known not affected: 22 recommended: 510 | 2026-07-31T01:03:22+00:00 | Vulnerability · Source |
| CVE-2025-40141 | suse_vex | SUSE CVE CVE-2025-40141 | first fixed: 2 known affected: 451 known not affected: 203 recommended: 583 | 2026-07-31T01:03:19+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-40166 | suse_vex | SUSE CVE CVE-2025-40166 | first fixed: 2 known affected: 394 known not affected: 374 recommended: 265 | 2026-07-31T01:03:11+00:00 | Vulnerability · Source |
| CVE-2025-40168 | suse_vex | SUSE CVE CVE-2025-40168 | first fixed: 2 known affected: 627 known not affected: 8 recommended: 626 | 2026-07-31T01:03:08+00:00 | Vulnerability · Source |
| CVE-2025-40174 | suse_vex | SUSE CVE CVE-2025-40174 | known not affected: 408 | 2026-07-31T01:03:04+00:00 | Vulnerability · Source |
| CVE-2025-40176 | suse_vex | SUSE CVE CVE-2025-40176 | first fixed: 2 known affected: 394 known not affected: 266 recommended: 583 | 2026-07-31T01:03:02+00:00 | Vulnerability · Source |