VEX records
Browse vendor VEX statements available in this Vulnerability-Lookup instance and pivot to the related vulnerability.
292268 VEX records
API response| Vulnerability | Source | Title | Product status | Imported | Links |
|---|---|---|---|---|---|
| CVE-2025-39969 | suse_vex | SUSE CVE CVE-2025-39969 | first fixed: 2 known affected: 394 known not affected: 265 recommended: 500 | 2026-07-25T00:37:37+00:00 | Vulnerability · Source |
| CVE-2025-39972 | suse_vex | SUSE CVE CVE-2025-39972 | first fixed: 2 known affected: 394 known not affected: 235 recommended: 523 | 2026-07-25T00:37:33+00:00 | Vulnerability · Source |
| CVE-2025-39975 | suse_vex | SUSE CVE CVE-2025-39975 | known not affected: 416 | 2026-07-25T00:37:28+00:00 | Vulnerability · Source |
| CVE-2025-39977 | suse_vex | SUSE CVE CVE-2025-39977 | first fixed: 2 known affected: 407 known not affected: 156 recommended: 695 | 2026-07-25T00:37:25+00:00 | Vulnerability · Source |
| CVE-2025-39980 | suse_vex | SUSE CVE CVE-2025-39980 | first fixed: 2 known affected: 549 known not affected: 113 recommended: 500 | 2026-07-25T00:37:22+00:00 | Vulnerability · Source |
| CVE-2025-39985 | suse_vex | SUSE CVE CVE-2025-39985 | first fixed: 2 known affected: 394 known not affected: 265 recommended: 500 | 2026-07-25T00:37:12+00:00 | Vulnerability · Source |
| CVE-2025-39987 | suse_vex | SUSE CVE CVE-2025-39987 | first fixed: 2 known affected: 394 known not affected: 265 recommended: 500 | 2026-07-25T00:37:09+00:00 | Vulnerability · Source |
| CVE-2025-39988 | suse_vex | SUSE CVE CVE-2025-39988 | first fixed: 2 known affected: 394 known not affected: 265 recommended: 500 | 2026-07-25T00:37:06+00:00 | Vulnerability · Source |
| CVE-2025-39991 | suse_vex | SUSE CVE CVE-2025-39991 | first fixed: 2 known affected: 394 known not affected: 265 recommended: 506 | 2026-07-25T00:37:03+00:00 | Vulnerability · Source |
| CVE-2025-39993 | suse_vex | SUSE CVE CVE-2025-39993 | first fixed: 2 known affected: 394 known not affected: 265 recommended: 539 | 2026-07-25T00:37:00+00:00 | Vulnerability · Source |
| CVE-2025-39996 | suse_vex | SUSE CVE CVE-2025-39996 | first fixed: 2 known affected: 394 known not affected: 265 recommended: 506 | 2026-07-25T00:36:56+00:00 | Vulnerability · Source |
| CVE-2025-40010 | suse_vex | SUSE CVE CVE-2025-40010 | known affected: 506 known not affected: 159 recommended: 346 | 2026-07-25T00:36:49+00:00 | Vulnerability · Source |
| CVE-2025-40013 | suse_vex | SUSE CVE CVE-2025-40013 | first fixed: 2 known affected: 399 known not affected: 268 recommended: 506 | 2026-07-25T00:36:46+00:00 | Vulnerability · Source |
| CVE-2025-40016 | suse_vex | SUSE CVE CVE-2025-40016 | first fixed: 2 known affected: 400 known not affected: 277 recommended: 506 | 2026-07-25T00:36:43+00:00 | Vulnerability · Source |
| CVE-2025-40018 | suse_vex | SUSE CVE CVE-2025-40018 | first fixed: 2 known affected: 410 known not affected: 19 recommended: 916 | 2026-07-25T00:36:40+00:00 | Vulnerability · Source |
| CVE-2025-40019 | suse_vex | SUSE CVE CVE-2025-40019 | first fixed: 2 known affected: 391 known not affected: 125 recommended: 706 | 2026-07-25T00:36:37+00:00 | Vulnerability · Source |
| CVE-2025-40020 | suse_vex | SUSE CVE CVE-2025-40020 | first fixed: 2 known affected: 394 known not affected: 274 recommended: 500 | 2026-07-25T00:36:34+00:00 | Vulnerability · Source |
| CVE-2025-40029 | suse_vex | SUSE CVE CVE-2025-40029 | first fixed: 2 known affected: 533 known not affected: 135 recommended: 506 | 2026-07-25T00:36:27+00:00 | Vulnerability · Source |
| CVE-2025-40032 | suse_vex | SUSE CVE CVE-2025-40032 | first fixed: 2 known affected: 506 known not affected: 150 recommended: 506 | 2026-07-25T00:36:24+00:00 | Vulnerability · Source |
| CVE-2025-40036 | suse_vex | SUSE CVE CVE-2025-40036 | first fixed: 2 known affected: 394 known not affected: 273 recommended: 506 | 2026-07-25T00:36:20+00:00 | Vulnerability · Source |
| CVE-2025-40043 | suse_vex | SUSE CVE CVE-2025-40043 | first fixed: 2 known affected: 618 known not affected: 38 recommended: 506 | 2026-07-25T00:36:16+00:00 | Vulnerability · Source |
| CVE-2025-40044 | suse_vex | SUSE CVE CVE-2025-40044 | first fixed: 2 known affected: 478 recommended: 739 | 2026-07-25T00:36:14+00:00 | Vulnerability · Source |
| CVE-2025-40045 | suse_vex | SUSE CVE CVE-2025-40045 | first fixed: 2 known not affected: 407 recommended: 178 | 2026-07-25T00:36:11+00:00 | Vulnerability · Source |
| CVE-2025-40051 | suse_vex | SUSE CVE CVE-2025-40051 | first fixed: 2 known affected: 451 known not affected: 211 recommended: 506 | 2026-07-25T00:36:08+00:00 | Vulnerability · Source |
| CVE-2025-40056 | suse_vex | SUSE CVE CVE-2025-40056 | first fixed: 2 known affected: 394 known not affected: 268 recommended: 506 | 2026-07-25T00:36:04+00:00 | Vulnerability · Source |
| CVE-2025-40062 | suse_vex | SUSE CVE CVE-2025-40062 | first fixed: 2 known affected: 451 known not affected: 211 recommended: 506 | 2026-07-25T00:36:00+00:00 | Vulnerability · Source |
| CVE-2025-40063 | suse_vex | SUSE CVE CVE-2025-40063 | known not affected: 407 recommended: 6 | 2026-07-25T00:35:58+00:00 | Vulnerability · Source |
| CVE-2025-40065 | suse_vex | SUSE CVE CVE-2025-40065 | known not affected: 410 recommended: 6 | 2026-07-25T00:35:53+00:00 | Vulnerability · Source |
| CVE-2025-40070 | suse_vex | SUSE CVE CVE-2025-40070 | first fixed: 2 known affected: 451 known not affected: 181 recommended: 529 | 2026-07-25T00:35:51+00:00 | Vulnerability · Source |
| CVE-2025-40073 | suse_vex | SUSE CVE CVE-2025-40073 | known not affected: 407 recommended: 6 | 2026-07-25T00:35:49+00:00 | Vulnerability · Source |
| CVE-2025-40075 | suse_vex | SUSE CVE CVE-2025-40075 | first fixed: 2 known affected: 610 known not affected: 22 recommended: 529 | 2026-07-25T00:35:46+00:00 | Vulnerability · Source |
| CVE-2025-40085 | suse_vex | SUSE CVE CVE-2025-40085 | first fixed: 2 known affected: 506 known not affected: 150 recommended: 506 | 2026-07-25T00:35:39+00:00 | Vulnerability · Source |
| CVE-2025-40088 | suse_vex | SUSE CVE CVE-2025-40088 | known affected: 549 known not affected: 6 recommended: 498 | 2026-07-25T00:35:37+00:00 | Vulnerability · Source |
| CVE-2025-40089 | suse_vex | SUSE CVE CVE-2025-40089 | known not affected: 407 recommended: 6 | 2026-07-25T00:35:35+00:00 | Vulnerability · Source |
| CVE-2025-40099 | suse_vex | SUSE CVE CVE-2025-40099 | first fixed: 2 known affected: 689 recommended: 433 | 2026-07-25T00:35:29+00:00 | Vulnerability · Source |
| CVE-2025-40102 | suse_vex | SUSE CVE CVE-2025-40102 | first fixed: 2 known affected: 543 known not affected: 103 recommended: 499 | 2026-07-25T00:35:26+00:00 | Vulnerability · Source |
| CVE-2025-40107 | suse_vex | SUSE CVE CVE-2025-40107 | first fixed: 2 known affected: 394 known not affected: 260 recommended: 500 | 2026-07-25T00:35:22+00:00 | Vulnerability · Source |
| CVE-2025-40108 | suse_vex | SUSE CVE CVE-2025-40108 | known not affected: 408 | 2026-07-25T00:35:20+00:00 | Vulnerability · Source |
| CVE-2025-40110 | suse_vex | SUSE CVE CVE-2025-40110 | first fixed: 2 known affected: 622 known not affected: 6 recommended: 537 | 2026-07-25T00:35:17+00:00 | Vulnerability · Source |
| CVE-2025-40114 | suse_vex | SUSE CVE CVE-2025-40114 | known not affected: 348 recommended: 53 | 2026-07-25T00:35:14+00:00 | Vulnerability · Source |
| CVE-2025-40117 | suse_vex | SUSE CVE CVE-2025-40117 | known not affected: 408 | 2026-07-25T00:35:11+00:00 | Vulnerability · Source |
| CVE-2025-40120 | suse_vex | SUSE CVE CVE-2025-40120 | first fixed: 2 known affected: 506 known not affected: 154 recommended: 500 | 2026-07-25T00:35:09+00:00 | Vulnerability · Source |
| CVE-2025-40121 | suse_vex | SUSE CVE CVE-2025-40121 | first fixed: 2 known affected: 366 known not affected: 99 recommended: 771 | 2026-07-25T00:35:06+00:00 | Vulnerability · Source |
| CVE-2025-40123 | suse_vex | SUSE CVE CVE-2025-40123 | first fixed: 2 known affected: 674 known not affected: 52 recommended: 330 | 2026-07-25T00:35:04+00:00 | Vulnerability · Source |
| CVE-2025-40124 | suse_vex | SUSE CVE CVE-2025-40124 | known not affected: 437 | 2026-07-25T00:35:02+00:00 | Vulnerability · Source |
| CVE-2025-40127 | suse_vex | SUSE CVE CVE-2025-40127 | first fixed: 2 known affected: 449 known not affected: 211 recommended: 500 | 2026-07-25T00:35:00+00:00 | Vulnerability · Source |
| CVE-2025-40129 | suse_vex | SUSE CVE CVE-2025-40129 | first fixed: 2 known affected: 394 known not affected: 260 recommended: 562 | 2026-07-25T00:34:58+00:00 | Vulnerability · Source |
| CVE-2025-40140 | suse_vex | SUSE CVE CVE-2025-40140 | first fixed: 2 known affected: 622 recommended: 500 | 2026-07-25T00:34:54+00:00 | Vulnerability · Source |
| CVE-2025-40145 | suse_vex | SUSE CVE CVE-2025-40145 | known not affected: 408 | 2026-07-25T00:34:52+00:00 | Vulnerability · Source |
| CVE-2025-40149 | suse_vex | SUSE CVE CVE-2025-40149 | first fixed: 2 known affected: 578 known not affected: 52 recommended: 523 | 2026-07-25T00:34:49+00:00 | Vulnerability · Source |