VEX records
Browse vendor VEX statements available in this Vulnerability-Lookup instance and pivot to the related vulnerability.
104719 VEX records
API response| Vulnerability | Source | Title | Product status | Imported | Links |
|---|---|---|---|---|---|
| CVE-2025-38119 | suse_vex | SUSE CVE CVE-2025-38119 | known affected: 735 known not affected: 6 recommended: 495 | 2026-10-15T16:45:36+00:00 | Vulnerability · Source |
| CVE-2025-38120 | suse_vex | SUSE CVE CVE-2025-38120 | known affected: 2 known not affected: 294 recommended: 726 | 2026-10-15T16:45:35+00:00 | Vulnerability · Source |
| CVE-2025-38121 | suse_vex | SUSE CVE CVE-2025-38121 | known affected: 0 known not affected: 521 recommended: 58 | 2026-10-15T16:45:33+00:00 | Vulnerability · Source |
| CVE-2025-38124 | suse_vex | SUSE CVE CVE-2025-38124 | known affected: 396 known not affected: 442 recommended: 589 | 2026-10-15T16:45:31+00:00 | Vulnerability · Source |
| CVE-2025-38125 | suse_vex | SUSE CVE CVE-2025-38125 | known affected: 587 known not affected: 262 recommended: 503 | 2026-10-15T16:45:30+00:00 | Vulnerability · Source |
| CVE-2025-38126 | suse_vex | SUSE CVE CVE-2025-38126 | known affected: 746 known not affected: 36 recommended: 450 | 2026-10-15T16:45:28+00:00 | Vulnerability · Source |
| CVE-2025-38128 | suse_vex | SUSE CVE CVE-2025-38128 | known affected: 2 known not affected: 521 recommended: 185 | 2026-10-15T16:45:26+00:00 | Vulnerability · Source |
| CVE-2025-38129 | suse_vex | SUSE CVE CVE-2025-38129 | known affected: 467 known not affected: 139 recommended: 854 | 2026-10-15T16:45:24+00:00 | Vulnerability · Source |
| CVE-2025-38130 | suse_vex | SUSE CVE CVE-2025-38130 | known not affected: 524 | 2026-10-15T16:45:23+00:00 | Vulnerability · Source |
| CVE-2025-38131 | suse_vex | SUSE CVE CVE-2025-38131 | known affected: 437 known not affected: 399 recommended: 427 | 2026-10-15T16:45:21+00:00 | Vulnerability · Source |
| CVE-2025-38132 | suse_vex | SUSE CVE CVE-2025-38132 | known affected: 437 known not affected: 399 recommended: 427 | 2026-10-15T16:45:19+00:00 | Vulnerability · Source |
| CVE-2025-38133 | suse_vex | SUSE CVE CVE-2025-38133 | known affected: 0 known not affected: 521 | 2026-10-15T16:45:17+00:00 | Vulnerability · Source |
| CVE-2025-38134 | suse_vex | SUSE CVE CVE-2025-38134 | known affected: 2 known not affected: 521 recommended: 185 | 2026-10-15T16:45:15+00:00 | Vulnerability · Source |
| CVE-2025-38136 | suse_vex | SUSE CVE CVE-2025-38136 | known affected: 396 known not affected: 442 recommended: 503 | 2026-10-15T16:45:14+00:00 | Vulnerability · Source |
| CVE-2025-38138 | suse_vex | SUSE CVE CVE-2025-38138 | known affected: 539 known not affected: 299 recommended: 503 | 2026-10-15T16:45:12+00:00 | Vulnerability · Source |
| CVE-2025-38140 | suse_vex | SUSE CVE CVE-2025-38140 | known affected: 2 known not affected: 521 recommended: 197 | 2026-10-15T16:45:10+00:00 | Vulnerability · Source |
| CVE-2025-38142 | suse_vex | SUSE CVE CVE-2025-38142 | known affected: 396 known not affected: 442 recommended: 503 | 2026-10-15T16:45:09+00:00 | Vulnerability · Source |
| CVE-2025-38143 | suse_vex | SUSE CVE CVE-2025-38143 | known affected: 608 known not affected: 230 recommended: 503 | 2026-10-15T16:45:07+00:00 | Vulnerability · Source |
| CVE-2025-38145 | suse_vex | SUSE CVE CVE-2025-38145 | known affected: 539 known not affected: 299 recommended: 503 | 2026-10-15T16:45:05+00:00 | Vulnerability · Source |
| CVE-2025-38146 | suse_vex | SUSE CVE CVE-2025-38146 | known affected: 587 known not affected: 262 recommended: 503 | 2026-10-15T16:45:04+00:00 | Vulnerability · Source |
| CVE-2025-38152 | suse_vex | SUSE CVE CVE-2025-38152 | known affected: 565 known not affected: 256 recommended: 431 | 2026-10-15T16:45:02+00:00 | Vulnerability · Source |
| CVE-2025-38153 | suse_vex | SUSE CVE CVE-2025-38153 | known affected: 400 known not affected: 387 recommended: 526 | 2026-10-15T16:45:00+00:00 | Vulnerability · Source |
| CVE-2025-38156 | suse_vex | SUSE CVE CVE-2025-38156 | known affected: 2 known not affected: 521 recommended: 185 | 2026-10-15T16:44:59+00:00 | Vulnerability · Source |
| CVE-2025-38157 | suse_vex | SUSE CVE CVE-2025-38157 | known affected: 739 known not affected: 43 recommended: 540 | 2026-10-15T16:44:57+00:00 | Vulnerability · Source |
| CVE-2025-38158 | suse_vex | SUSE CVE CVE-2025-38158 | known affected: 504 known not affected: 332 recommended: 427 | 2026-10-15T16:44:55+00:00 | Vulnerability · Source |
| CVE-2025-38159 | suse_vex | SUSE CVE CVE-2025-38159 | known affected: 407 known not affected: 256 recommended: 855 | 2026-10-15T16:44:53+00:00 | Vulnerability · Source |
| CVE-2025-38162 | suse_vex | SUSE CVE CVE-2025-38162 | known affected: 623 known not affected: 213 recommended: 427 | 2026-10-15T16:44:51+00:00 | Vulnerability · Source |
| CVE-2025-38163 | suse_vex | SUSE CVE CVE-2025-38163 | known affected: 0 known not affected: 575 | 2026-10-15T16:44:49+00:00 | Vulnerability · Source |
| CVE-2025-38167 | suse_vex | SUSE CVE CVE-2025-38167 | known affected: 0 known not affected: 575 | 2026-10-15T16:44:47+00:00 | Vulnerability · Source |
| CVE-2025-38168 | suse_vex | SUSE CVE CVE-2025-38168 | known affected: 7 known not affected: 552 recommended: 185 | 2026-10-15T16:44:46+00:00 | Vulnerability · Source |
| CVE-2025-38169 | suse_vex | SUSE CVE CVE-2025-38169 | known affected: 2 known not affected: 521 recommended: 185 | 2026-10-15T16:44:44+00:00 | Vulnerability · Source |
| CVE-2025-38176 | suse_vex | SUSE CVE CVE-2025-38176 | known affected: 0 known not affected: 521 | 2026-10-15T16:44:43+00:00 | Vulnerability · Source |
| CVE-2025-38178 | suse_vex | SUSE CVE CVE-2025-38178 | known affected: 0 known not affected: 521 | 2026-10-15T16:44:41+00:00 | Vulnerability · Source |
| CVE-2025-38184 | suse_vex | SUSE CVE CVE-2025-38184 | known affected: 550 known not affected: 36 recommended: 811 | 2026-10-15T16:44:39+00:00 | Vulnerability · Source |
| CVE-2025-38185 | suse_vex | SUSE CVE CVE-2025-38185 | known affected: 595 known not affected: 5 recommended: 540 | 2026-10-15T16:44:37+00:00 | Vulnerability · Source |
| CVE-2025-38187 | suse_vex | SUSE CVE CVE-2025-38187 | known affected: 437 known not affected: 399 recommended: 427 | 2026-10-15T16:44:35+00:00 | Vulnerability · Source |
| CVE-2025-38188 | suse_vex | SUSE CVE CVE-2025-38188 | known affected: 412 known not affected: 426 recommended: 503 | 2026-10-15T16:44:33+00:00 | Vulnerability · Source |
| CVE-2025-38192 | suse_vex | SUSE CVE CVE-2025-38192 | known affected: 746 known not affected: 36 recommended: 450 | 2026-10-15T16:44:31+00:00 | Vulnerability · Source |
| CVE-2025-38193 | suse_vex | SUSE CVE CVE-2025-38193 | known affected: 739 known not affected: 43 recommended: 540 | 2026-10-15T16:44:29+00:00 | Vulnerability · Source |
| CVE-2025-38195 | suse_vex | SUSE CVE CVE-2025-38195 | known affected: 0 known not affected: 521 | 2026-10-15T16:44:27+00:00 | Vulnerability · Source |
| CVE-2025-38197 | suse_vex | SUSE CVE CVE-2025-38197 | known affected: 539 known not affected: 299 recommended: 503 | 2026-10-15T16:44:25+00:00 | Vulnerability · Source |
| CVE-2025-38198 | suse_vex | SUSE CVE CVE-2025-38198 | known affected: 707 known not affected: 75 recommended: 540 | 2026-10-15T16:44:23+00:00 | Vulnerability · Source |
| CVE-2025-38199 | suse_vex | SUSE CVE CVE-2025-38199 | known affected: 0 known not affected: 451 recommended: 58 | 2026-10-15T16:44:21+00:00 | Vulnerability · Source |
| CVE-2025-38201 | suse_vex | SUSE CVE CVE-2025-38201 | known affected: 636 known not affected: 217 recommended: 503 | 2026-10-15T16:44:19+00:00 | Vulnerability · Source |
| CVE-2025-38202 | suse_vex | SUSE CVE CVE-2025-38202 | known affected: 504 known not affected: 332 recommended: 427 | 2026-10-15T16:44:17+00:00 | Vulnerability · Source |
| CVE-2025-38204 | suse_vex | SUSE CVE CVE-2025-38204 | known affected: 394 known not affected: 497 recommended: 318 | 2026-10-15T16:44:15+00:00 | Vulnerability · Source |
| CVE-2025-38206 | suse_vex | SUSE CVE CVE-2025-38206 | known affected: 447 known not affected: 187 recommended: 875 | 2026-10-15T16:44:14+00:00 | Vulnerability · Source |
| CVE-2025-38207 | suse_vex | SUSE CVE CVE-2025-38207 | known affected: 0 known not affected: 521 recommended: 109 | 2026-10-15T16:44:12+00:00 | Vulnerability · Source |
| CVE-2025-38209 | suse_vex | SUSE CVE CVE-2025-38209 | known affected: 396 known not affected: 471 recommended: 278 | 2026-10-15T16:44:10+00:00 | Vulnerability · Source |
| CVE-2025-38210 | suse_vex | SUSE CVE CVE-2025-38210 | known affected: 504 known not affected: 332 recommended: 427 | 2026-10-15T16:44:08+00:00 | Vulnerability · Source |