VEX records
Browse vendor VEX statements available in this Vulnerability-Lookup instance and pivot to the related vulnerability.
292108 VEX records
API response| Vulnerability | Source | Title | Product status | Imported | Links |
|---|---|---|---|---|---|
| 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 |
| CVE-2025-38155 | suse_vex | SUSE CVE CVE-2025-38155 | first fixed: 2 known affected: 394 known not affected: 323 recommended: 508 | 2026-07-25T00:50:33+00:00 | Vulnerability · Source |
| CVE-2025-38157 | suse_vex | SUSE CVE CVE-2025-38157 | first fixed: 2 known affected: 643 known not affected: 46 recommended: 545 | 2026-07-25T00:50:30+00:00 | Vulnerability · Source |
| CVE-2025-38160 | suse_vex | SUSE CVE CVE-2025-38160 | first fixed: 2 known affected: 633 known not affected: 117 recommended: 508 | 2026-07-25T00:50:25+00:00 | Vulnerability · Source |
| CVE-2025-38161 | suse_vex | SUSE CVE CVE-2025-38161 | first fixed: 2 known affected: 637 known not affected: 52 recommended: 545 | 2026-07-25T00:50:23+00:00 | Vulnerability · Source |
| CVE-2025-38174 | suse_vex | SUSE CVE CVE-2025-38174 | first fixed: 2 known affected: 398 known not affected: 296 recommended: 531 | 2026-07-25T00:50:16+00:00 | Vulnerability · Source |
| CVE-2025-38183 | suse_vex | SUSE CVE CVE-2025-38183 | known affected: 440 known not affected: 277 recommended: 407 | 2026-07-25T00:50:12+00:00 | Vulnerability · Source |
| CVE-2025-38185 | suse_vex | SUSE CVE CVE-2025-38185 | first fixed: 2 known affected: 527 known not affected: 5 recommended: 545 | 2026-07-25T00:50:10+00:00 | Vulnerability · Source |
| CVE-2025-38187 | suse_vex | SUSE CVE CVE-2025-38187 | known affected: 440 known not affected: 277 recommended: 407 | 2026-07-25T00:50:08+00:00 | Vulnerability · Source |
| CVE-2025-38188 | suse_vex | SUSE CVE CVE-2025-38188 | first fixed: 2 known affected: 410 known not affected: 307 recommended: 508 | 2026-07-25T00:50:06+00:00 | Vulnerability · Source |
| CVE-2025-38190 | suse_vex | SUSE CVE CVE-2025-38190 | first fixed: 2 known affected: 683 known not affected: 27 recommended: 531 | 2026-07-25T00:50:04+00:00 | Vulnerability · Source |
| CVE-2025-38191 | suse_vex | SUSE CVE CVE-2025-38191 | known not affected: 472 | 2026-07-25T00:50:02+00:00 | Vulnerability · Source |
| CVE-2025-38193 | suse_vex | SUSE CVE CVE-2025-38193 | first fixed: 2 known affected: 643 known not affected: 46 recommended: 545 | 2026-07-25T00:49:59+00:00 | Vulnerability · Source |
| CVE-2025-38197 | suse_vex | SUSE CVE CVE-2025-38197 | first fixed: 2 known affected: 521 known not affected: 196 recommended: 508 | 2026-07-25T00:49:56+00:00 | Vulnerability · Source |
| CVE-2025-38198 | suse_vex | SUSE CVE CVE-2025-38198 | first fixed: 2 known affected: 627 known not affected: 62 recommended: 545 | 2026-07-25T00:49:55+00:00 | Vulnerability · Source |
| CVE-2025-38201 | suse_vex | SUSE CVE CVE-2025-38201 | first fixed: 2 known affected: 618 known not affected: 118 recommended: 508 | 2026-07-25T00:49:51+00:00 | Vulnerability · Source |
| CVE-2025-38202 | suse_vex | SUSE CVE CVE-2025-38202 | known affected: 497 known not affected: 220 recommended: 407 | 2026-07-25T00:49:49+00:00 | Vulnerability · Source |
| CVE-2025-38208 | suse_vex | SUSE CVE CVE-2025-38208 | first fixed: 2 known affected: 618 known not affected: 113 recommended: 508 | 2026-07-25T00:49:39+00:00 | Vulnerability · Source |
| CVE-2025-38209 | suse_vex | SUSE CVE CVE-2025-38209 | first fixed: 2 known affected: 394 known not affected: 359 recommended: 265 | 2026-07-25T00:49:36+00:00 | Vulnerability · Source |
| CVE-2025-38211 | suse_vex | SUSE CVE CVE-2025-38211 | first fixed: 2 known affected: 623 known not affected: 66 recommended: 608 | 2026-07-25T00:49:31+00:00 | Vulnerability · Source |
| CVE-2025-38214 | suse_vex | SUSE CVE CVE-2025-38214 | first fixed: 2 known affected: 649 known not affected: 51 recommended: 545 | 2026-07-25T00:49:24+00:00 | Vulnerability · Source |
| CVE-2025-38226 | suse_vex | SUSE CVE CVE-2025-38226 | first fixed: 2 known affected: 394 known not affected: 323 recommended: 508 | 2026-07-25T00:49:18+00:00 | Vulnerability · Source |