VEX records
Browse vendor VEX statements available in this Vulnerability-Lookup instance and pivot to the related vulnerability.
292263 VEX records
API response| Vulnerability | Source | Title | Product status | Imported | Links |
|---|---|---|---|---|---|
| CVE-2025-37979 | suse_vex | SUSE CVE CVE-2025-37979 | known affected: 441 known not affected: 239 recommended: 407 | 2026-07-25T00:53:33+00:00 | Vulnerability · Source |
| CVE-2025-37980 | suse_vex | SUSE CVE CVE-2025-37980 | known affected: 637 known not affected: 52 recommended: 444 | 2026-07-25T00:53:32+00:00 | Vulnerability · Source |
| CVE-2025-37986 | suse_vex | SUSE CVE CVE-2025-37986 | known affected: 441 known not affected: 239 recommended: 407 | 2026-07-25T00:53:25+00:00 | Vulnerability · Source |
| CVE-2025-37987 | suse_vex | SUSE CVE CVE-2025-37987 | known affected: 497 known not affected: 220 recommended: 392 | 2026-07-25T00:53:23+00:00 | Vulnerability · Source |
| CVE-2025-37990 | suse_vex | SUSE CVE CVE-2025-37990 | known affected: 639 known not affected: 82 recommended: 421 | 2026-07-25T00:53:21+00:00 | Vulnerability · Source |
| CVE-2025-37995 | suse_vex | SUSE CVE CVE-2025-37995 | known affected: 683 known not affected: 6 recommended: 444 | 2026-07-25T00:53:15+00:00 | Vulnerability · Source |
| CVE-2025-38006 | suse_vex | SUSE CVE CVE-2025-38006 | first fixed: 2 known affected: 448 known not affected: 283 recommended: 508 | 2026-07-25T00:53:01+00:00 | Vulnerability · Source |
| CVE-2025-38009 | suse_vex | SUSE CVE CVE-2025-38009 | known affected: 557 known not affected: 145 recommended: 407 | 2026-07-25T00:52:58+00:00 | Vulnerability · Source |
| CVE-2025-38019 | suse_vex | SUSE CVE CVE-2025-38019 | first fixed: 2 known affected: 5 known not affected: 448 recommended: 154 | 2026-07-25T00:52:49+00:00 | Vulnerability · Source |
| CVE-2025-38031 | suse_vex | SUSE CVE CVE-2025-38031 | known affected: 557 known not affected: 145 recommended: 407 | 2026-07-25T00:52:37+00:00 | Vulnerability · Source |
| CVE-2025-38034 | suse_vex | SUSE CVE CVE-2025-38034 | first fixed: 2 known affected: 689 known not affected: 6 recommended: 545 | 2026-07-25T00:52:35+00:00 | Vulnerability · Source |
| CVE-2025-38036 | suse_vex | SUSE CVE CVE-2025-38036 | known affected: 93 known not affected: 379 | 2026-07-25T00:52:33+00:00 | Vulnerability · Source |
| CVE-2025-38047 | suse_vex | SUSE CVE CVE-2025-38047 | known affected: 720 known not affected: 95 recommended: 164 | 2026-07-25T00:52:24+00:00 | Vulnerability · Source |
| CVE-2025-38051 | suse_vex | SUSE CVE CVE-2025-38051 | known affected: 689 recommended: 493 | 2026-07-25T00:52:21+00:00 | Vulnerability · Source |
| CVE-2025-38053 | suse_vex | SUSE CVE CVE-2025-38053 | known affected: 567 known not affected: 150 recommended: 456 | 2026-07-25T00:52:18+00:00 | Vulnerability · Source |
| CVE-2025-38058 | suse_vex | SUSE CVE CVE-2025-38058 | first fixed: 2 known affected: 675 known not affected: 20 recommended: 545 | 2026-07-25T00:52:13+00:00 | Vulnerability · Source |
| CVE-2025-38059 | suse_vex | SUSE CVE CVE-2025-38059 | known affected: 394 known not affected: 308 recommended: 407 | 2026-07-25T00:52:11+00:00 | Vulnerability · Source |
| CVE-2025-38067 | suse_vex | SUSE CVE CVE-2025-38067 | known affected: 66 known not affected: 46 recommended: 42 | 2026-07-25T00:52:03+00:00 | Vulnerability · Source |
| CVE-2025-38077 | suse_vex | SUSE CVE CVE-2025-38077 | known affected: 506 known not affected: 196 recommended: 407 | 2026-07-25T00:51:58+00:00 | Vulnerability · Source |
| CVE-2025-38080 | suse_vex | SUSE CVE CVE-2025-38080 | known affected: 394 known not affected: 308 recommended: 407 | 2026-07-25T00:51:54+00:00 | Vulnerability · Source |
| CVE-2025-38084 | suse_vex | SUSE CVE CVE-2025-38084 | first fixed: 2 known affected: 513 known not affected: 46 recommended: 732 | 2026-07-25T00:51:52+00:00 | Vulnerability · Source |
| CVE-2025-38089 | suse_vex | SUSE CVE CVE-2025-38089 | first fixed: 2 known affected: 394 known not affected: 323 recommended: 602 | 2026-07-25T00:51:47+00:00 | Vulnerability · Source |
| CVE-2025-38090 | suse_vex | SUSE CVE CVE-2025-38090 | first fixed: 2 known affected: 394 known not affected: 323 recommended: 508 | 2026-07-25T00:51:46+00:00 | Vulnerability · Source |
| CVE-2025-38092 | suse_vex | SUSE CVE CVE-2025-38092 | known not affected: 416 | 2026-07-25T00:51:43+00:00 | Vulnerability · Source |
| CVE-2025-38095 | suse_vex | SUSE CVE CVE-2025-38095 | first fixed: 2 known affected: 572 known not affected: 145 recommended: 508 | 2026-07-25T00:51:39+00:00 | Vulnerability · Source |
| CVE-2025-38099 | suse_vex | SUSE CVE CVE-2025-38099 | first fixed: 2 known affected: 685 known not affected: 32 recommended: 508 | 2026-07-25T00:51:36+00:00 | Vulnerability · Source |
| CVE-2025-38102 | suse_vex | SUSE CVE CVE-2025-38102 | first fixed: 2 known affected: 643 known not affected: 57 recommended: 545 | 2026-07-25T00:51:32+00:00 | Vulnerability · Source |
| CVE-2025-38103 | suse_vex | SUSE CVE CVE-2025-38103 | first fixed: 2 known affected: 708 recommended: 545 | 2026-07-25T00:51:29+00:00 | Vulnerability · Source |
| CVE-2025-38104 | suse_vex | SUSE CVE CVE-2025-38104 | known affected: 451 known not affected: 227 recommended: 407 | 2026-07-25T00:51:27+00:00 | Vulnerability · Source |
| CVE-2025-38107 | suse_vex | SUSE CVE CVE-2025-38107 | first fixed: 2 known affected: 451 known not affected: 266 recommended: 508 | 2026-07-25T00:51:25+00:00 | Vulnerability · Source |
| CVE-2025-38108 | suse_vex | SUSE CVE CVE-2025-38108 | first fixed: 2 known affected: 593 known not affected: 98 recommended: 531 | 2026-07-25T00:51:23+00:00 | Vulnerability · Source |
| CVE-2025-38110 | suse_vex | SUSE CVE CVE-2025-38110 | first fixed: 2 known affected: 394 known not affected: 323 recommended: 601 | 2026-07-25T00:51:20+00:00 | Vulnerability · Source |
| CVE-2025-38111 | suse_vex | SUSE CVE CVE-2025-38111 | first fixed: 2 known affected: 359 known not affected: 196 recommended: 763 | 2026-07-25T00:51:19+00:00 | Vulnerability · Source |
| CVE-2025-38112 | suse_vex | SUSE CVE CVE-2025-38112 | first fixed: 2 known affected: 593 known not affected: 98 recommended: 531 | 2026-07-25T00:51:17+00:00 | Vulnerability · Source |
| CVE-2025-38115 | suse_vex | SUSE CVE CVE-2025-38115 | known affected: 639 known not affected: 52 recommended: 430 | 2026-07-25T00:51:15+00:00 | Vulnerability · Source |
| CVE-2025-38117 | suse_vex | SUSE CVE CVE-2025-38117 | first fixed: 2 known affected: 689 known not affected: 6 recommended: 545 | 2026-07-25T00:51:13+00:00 | Vulnerability · Source |
| CVE-2025-38122 | suse_vex | SUSE CVE CVE-2025-38122 | first fixed: 2 known affected: 593 known not affected: 101 recommended: 531 | 2026-07-25T00:51:10+00:00 | Vulnerability · Source |
| CVE-2025-38123 | suse_vex | SUSE CVE CVE-2025-38123 | first fixed: 2 known affected: 394 known not affected: 323 recommended: 508 | 2026-07-25T00:51:08+00:00 | Vulnerability · Source |
| CVE-2025-38125 | suse_vex | SUSE CVE CVE-2025-38125 | first fixed: 2 known affected: 575 known not affected: 156 recommended: 508 | 2026-07-25T00:51:06+00:00 | Vulnerability · Source |
| CVE-2025-38127 | suse_vex | SUSE CVE CVE-2025-38127 | first fixed: 2 known affected: 572 known not affected: 145 recommended: 549 | 2026-07-25T00:51:03+00:00 | Vulnerability · Source |
| CVE-2025-38129 | suse_vex | SUSE CVE CVE-2025-38129 | first fixed: 2 known affected: 431 known not affected: 98 recommended: 818 | 2026-07-25T00:51:01+00:00 | Vulnerability · Source |
| CVE-2025-38132 | suse_vex | SUSE CVE CVE-2025-38132 | known affected: 440 known not affected: 277 recommended: 407 | 2026-07-25T00:50:57+00:00 | Vulnerability · Source |
| CVE-2025-38135 | suse_vex | SUSE CVE CVE-2025-38135 | first fixed: 2 known affected: 572 known not affected: 158 recommended: 508 | 2026-07-25T00:50:55+00:00 | Vulnerability · Source |
| CVE-2025-38138 | suse_vex | SUSE CVE CVE-2025-38138 | first fixed: 2 known affected: 521 known not affected: 196 recommended: 508 | 2026-07-25T00:50:53+00:00 | Vulnerability · Source |
| CVE-2025-38143 | suse_vex | SUSE CVE CVE-2025-38143 | first fixed: 2 known affected: 572 known not affected: 145 recommended: 508 | 2026-07-25T00:50:50+00:00 | Vulnerability · Source |
| CVE-2025-38146 | suse_vex | SUSE CVE CVE-2025-38146 | first fixed: 2 known affected: 575 known not affected: 156 recommended: 508 | 2026-07-25T00:50:47+00:00 | Vulnerability · Source |
| CVE-2025-38149 | suse_vex | SUSE CVE CVE-2025-38149 | first fixed: 2 known affected: 394 known not affected: 323 recommended: 508 | 2026-07-25T00:50:43+00:00 | Vulnerability · Source |
| CVE-2025-38150 | suse_vex | SUSE CVE CVE-2025-38150 | known not affected: 416 | 2026-07-25T00:50:41+00:00 | Vulnerability · Source |
| CVE-2025-38151 | suse_vex | SUSE CVE CVE-2025-38151 | first fixed: 2 known affected: 394 known not affected: 323 recommended: 508 | 2026-07-25T00:50:39+00:00 | Vulnerability · Source |
| CVE-2025-38152 | suse_vex | SUSE CVE CVE-2025-38152 | known affected: 552 known not affected: 150 recommended: 411 | 2026-07-25T00:50:36+00:00 | Vulnerability · Source |