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-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 |
| CVE-2025-38228 | suse_vex | SUSE CVE CVE-2025-38228 | first fixed: 2 known not affected: 416 recommended: 154 | 2026-07-25T00:49:16+00:00 | Vulnerability · Source |
| CVE-2025-38235 | suse_vex | SUSE CVE CVE-2025-38235 | known not affected: 416 | 2026-07-25T00:49:10+00:00 | Vulnerability · Source |
| CVE-2025-38236 | suse_vex | SUSE CVE CVE-2025-38236 | known affected: 440 known not affected: 277 recommended: 407 | 2026-07-25T00:49:08+00:00 | Vulnerability · Source |
| CVE-2025-38243 | suse_vex | SUSE CVE CVE-2025-38243 | first fixed: 2 known affected: 394 known not affected: 326 recommended: 402 | 2026-07-25T00:49:06+00:00 | Vulnerability · Source |
| CVE-2025-38248 | suse_vex | SUSE CVE CVE-2025-38248 | known affected: 440 known not affected: 277 recommended: 427 | 2026-07-25T00:49:03+00:00 | Vulnerability · Source |
| CVE-2025-38249 | suse_vex | SUSE CVE CVE-2025-38249 | first fixed: 2 known affected: 593 known not affected: 98 recommended: 531 | 2026-07-25T00:49:02+00:00 | Vulnerability · Source |
| CVE-2025-38257 | suse_vex | SUSE CVE CVE-2025-38257 | first fixed: 2 known affected: 393 known not affected: 145 recommended: 801 | 2026-07-25T00:48:58+00:00 | Vulnerability · Source |
| CVE-2025-38258 | suse_vex | SUSE CVE CVE-2025-38258 | first fixed: 2 known not affected: 453 recommended: 154 | 2026-07-25T00:48:56+00:00 | Vulnerability · Source |
| CVE-2025-38259 | suse_vex | SUSE CVE CVE-2025-38259 | first fixed: 2 known affected: 572 known not affected: 145 recommended: 508 | 2026-07-25T00:48:55+00:00 | Vulnerability · Source |
| CVE-2025-38267 | suse_vex | SUSE CVE CVE-2025-38267 | first fixed: 2 known affected: 5 known not affected: 450 recommended: 154 | 2026-07-25T00:48:53+00:00 | Vulnerability · Source |
| CVE-2025-38271 | suse_vex | SUSE CVE CVE-2025-38271 | known not affected: 416 | 2026-07-25T00:48:51+00:00 | Vulnerability · Source |
| CVE-2025-38272 | suse_vex | SUSE CVE CVE-2025-38272 | first fixed: 2 known affected: 629 known not affected: 99 recommended: 508 | 2026-07-25T00:48:50+00:00 | Vulnerability · Source |
| CVE-2025-38277 | suse_vex | SUSE CVE CVE-2025-38277 | first fixed: 2 known affected: 394 known not affected: 323 recommended: 508 | 2026-07-25T00:48:47+00:00 | Vulnerability · Source |
| CVE-2025-38286 | suse_vex | SUSE CVE CVE-2025-38286 | first fixed: 2 known affected: 394 known not affected: 323 recommended: 508 | 2026-07-25T00:48:42+00:00 | Vulnerability · Source |
| CVE-2025-38289 | suse_vex | SUSE CVE CVE-2025-38289 | first fixed: 2 known affected: 372 known not affected: 266 recommended: 600 | 2026-07-25T00:48:39+00:00 | Vulnerability · Source |
| CVE-2025-38290 | suse_vex | SUSE CVE CVE-2025-38290 | first fixed: 2 known affected: 394 known not affected: 323 recommended: 508 | 2026-07-25T00:48:37+00:00 | Vulnerability · Source |
| CVE-2025-38292 | suse_vex | SUSE CVE CVE-2025-38292 | first fixed: 2 known affected: 394 known not affected: 323 recommended: 551 | 2026-07-25T00:48:35+00:00 | Vulnerability · Source |
| CVE-2025-38293 | suse_vex | SUSE CVE CVE-2025-38293 | first fixed: 2 known affected: 521 known not affected: 196 recommended: 508 | 2026-07-25T00:48:33+00:00 | Vulnerability · Source |
| CVE-2025-38297 | suse_vex | SUSE CVE CVE-2025-38297 | first fixed: 2 recommended: 172 | 2026-07-25T00:48:32+00:00 | Vulnerability · Source |
| CVE-2025-38301 | suse_vex | SUSE CVE CVE-2025-38301 | first fixed: 2 known affected: 3 known not affected: 422 recommended: 154 | 2026-07-25T00:48:30+00:00 | Vulnerability · Source |
| CVE-2025-38304 | suse_vex | SUSE CVE CVE-2025-38304 | first fixed: 2 known affected: 451 known not affected: 266 recommended: 508 | 2026-07-25T00:48:27+00:00 | Vulnerability · Source |
| CVE-2025-38307 | suse_vex | SUSE CVE CVE-2025-38307 | first fixed: 2 known affected: 394 known not affected: 323 recommended: 508 | 2026-07-25T00:48:24+00:00 | Vulnerability · Source |
| CVE-2025-38313 | suse_vex | SUSE CVE CVE-2025-38313 | first fixed: 2 known affected: 593 known not affected: 101 recommended: 531 | 2026-07-25T00:48:20+00:00 | Vulnerability · Source |