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-38391 | suse_vex | SUSE CVE CVE-2025-38391 | first fixed: 2 known affected: 593 known not affected: 98 recommended: 531 | 2026-07-25T00:46:59+00:00 | Vulnerability · Source |
| CVE-2025-38392 | suse_vex | SUSE CVE CVE-2025-38392 | first fixed: 2 known affected: 567 known not affected: 156 recommended: 571 | 2026-07-25T00:46:57+00:00 | Vulnerability · Source |
| CVE-2025-38393 | suse_vex | SUSE CVE CVE-2025-38393 | first fixed: 2 known affected: 521 known not affected: 196 recommended: 555 | 2026-07-25T00:46:55+00:00 | Vulnerability · Source |
| CVE-2025-38395 | suse_vex | SUSE CVE CVE-2025-38395 | first fixed: 2 known affected: 572 known not affected: 145 recommended: 508 | 2026-07-25T00:46:54+00:00 | Vulnerability · Source |
| CVE-2025-38396 | suse_vex | SUSE CVE CVE-2025-38396 | first fixed: 2 known affected: 440 known not affected: 283 recommended: 607 | 2026-07-25T00:46:52+00:00 | Vulnerability · Source |
| CVE-2025-38400 | suse_vex | SUSE CVE CVE-2025-38400 | first fixed: 2 known affected: 451 known not affected: 266 recommended: 550 | 2026-07-25T00:46:50+00:00 | Vulnerability · Source |
| CVE-2025-38401 | suse_vex | SUSE CVE CVE-2025-38401 | first fixed: 2 known affected: 404 known not affected: 325 recommended: 508 | 2026-07-25T00:46:49+00:00 | Vulnerability · Source |
| CVE-2025-38404 | suse_vex | SUSE CVE CVE-2025-38404 | first fixed: 2 known affected: 394 known not affected: 323 recommended: 508 | 2026-07-25T00:46:44+00:00 | Vulnerability · Source |
| CVE-2025-38406 | suse_vex | SUSE CVE CVE-2025-38406 | first fixed: 2 known affected: 639 known not affected: 57 recommended: 508 | 2026-07-25T00:46:42+00:00 | Vulnerability · Source |
| CVE-2025-38408 | suse_vex | SUSE CVE CVE-2025-38408 | first fixed: 2 known affected: 521 known not affected: 156 recommended: 508 | 2026-07-25T00:46:41+00:00 | Vulnerability · Source |
| CVE-2025-38409 | suse_vex | SUSE CVE CVE-2025-38409 | first fixed: 2 known affected: 582 known not affected: 105 recommended: 508 | 2026-07-25T00:46:39+00:00 | Vulnerability · Source |
| CVE-2025-38410 | suse_vex | SUSE CVE CVE-2025-38410 | first fixed: 2 known affected: 633 known not affected: 84 recommended: 508 | 2026-07-25T00:46:37+00:00 | Vulnerability · Source |
| CVE-2025-38416 | suse_vex | SUSE CVE CVE-2025-38416 | first fixed: 2 known affected: 633 known not affected: 52 recommended: 508 | 2026-07-25T00:46:33+00:00 | Vulnerability · Source |
| CVE-2025-38420 | suse_vex | SUSE CVE CVE-2025-38420 | first fixed: 2 known affected: 643 known not affected: 46 recommended: 531 | 2026-07-25T00:46:29+00:00 | Vulnerability · Source |
| CVE-2025-38423 | suse_vex | SUSE CVE CVE-2025-38423 | first fixed: 2 known not affected: 416 recommended: 172 | 2026-07-25T00:46:27+00:00 | Vulnerability · Source |
| CVE-2025-38424 | suse_vex | SUSE CVE CVE-2025-38424 | first fixed: 2 known affected: 643 known not affected: 57 recommended: 545 | 2026-07-25T00:46:25+00:00 | Vulnerability · Source |
| CVE-2025-38425 | suse_vex | SUSE CVE CVE-2025-38425 | first fixed: 2 known affected: 521 known not affected: 196 recommended: 508 | 2026-07-25T00:46:24+00:00 | Vulnerability · Source |
| CVE-2025-38429 | suse_vex | SUSE CVE CVE-2025-38429 | first fixed: 2 known affected: 440 known not affected: 277 recommended: 508 | 2026-07-25T00:46:21+00:00 | Vulnerability · Source |
| CVE-2025-38430 | suse_vex | SUSE CVE CVE-2025-38430 | first fixed: 2 known affected: 623 known not affected: 71 recommended: 531 | 2026-07-25T00:46:20+00:00 | Vulnerability · Source |
| CVE-2025-38436 | suse_vex | SUSE CVE CVE-2025-38436 | first fixed: 2 known affected: 641 known not affected: 57 recommended: 531 | 2026-07-25T00:46:18+00:00 | Vulnerability · Source |
| CVE-2025-38442 | suse_vex | SUSE CVE CVE-2025-38442 | known not affected: 416 | 2026-07-25T00:46:16+00:00 | Vulnerability · Source |
| CVE-2025-38443 | suse_vex | SUSE CVE CVE-2025-38443 | first fixed: 2 known affected: 521 known not affected: 196 recommended: 508 | 2026-07-25T00:46:15+00:00 | Vulnerability · Source |
| CVE-2025-38447 | suse_vex | SUSE CVE CVE-2025-38447 | known not affected: 416 | 2026-07-25T00:46:12+00:00 | Vulnerability · Source |
| CVE-2025-38448 | suse_vex | SUSE CVE CVE-2025-38448 | first fixed: 2 known affected: 558 known not affected: 159 recommended: 508 | 2026-07-25T00:46:10+00:00 | Vulnerability · Source |
| CVE-2025-38449 | suse_vex | SUSE CVE CVE-2025-38449 | first fixed: 2 known affected: 623 known not affected: 89 recommended: 594 | 2026-07-25T00:46:08+00:00 | Vulnerability · Source |
| CVE-2025-38455 | suse_vex | SUSE CVE CVE-2025-38455 | first fixed: 2 known affected: 567 known not affected: 150 recommended: 508 | 2026-07-25T00:46:05+00:00 | Vulnerability · Source |
| CVE-2025-38462 | suse_vex | SUSE CVE CVE-2025-38462 | first fixed: 2 known affected: 567 known not affected: 150 recommended: 508 | 2026-07-25T00:46:02+00:00 | Vulnerability · Source |
| CVE-2025-38465 | suse_vex | SUSE CVE CVE-2025-38465 | first fixed: 2 known affected: 650 recommended: 547 | 2026-07-25T00:45:59+00:00 | Vulnerability · Source |
| CVE-2025-38466 | suse_vex | SUSE CVE CVE-2025-38466 | first fixed: 2 known affected: 521 known not affected: 159 recommended: 508 | 2026-07-25T00:45:58+00:00 | Vulnerability · Source |
| CVE-2025-38470 | suse_vex | SUSE CVE CVE-2025-38470 | first fixed: 2 known affected: 615 recommended: 659 | 2026-07-25T00:45:55+00:00 | Vulnerability · Source |
| CVE-2025-38472 | suse_vex | SUSE CVE CVE-2025-38472 | first fixed: 2 known affected: 448 known not affected: 283 recommended: 551 | 2026-07-25T00:45:53+00:00 | Vulnerability · Source |
| CVE-2025-38473 | suse_vex | SUSE CVE CVE-2025-38473 | first fixed: 2 known affected: 643 known not affected: 57 recommended: 545 | 2026-07-25T00:45:51+00:00 | Vulnerability · Source |
| CVE-2025-38474 | suse_vex | SUSE CVE CVE-2025-38474 | first fixed: 2 known affected: 649 known not affected: 51 recommended: 545 | 2026-07-25T00:45:50+00:00 | Vulnerability · Source |
| CVE-2025-38476 | suse_vex | SUSE CVE CVE-2025-38476 | first fixed: 2 known affected: 367 known not affected: 159 recommended: 834 | 2026-07-25T00:45:48+00:00 | Vulnerability · Source |
| CVE-2025-38478 | suse_vex | SUSE CVE CVE-2025-38478 | first fixed: 2 known affected: 639 known not affected: 46 recommended: 508 | 2026-07-25T00:45:46+00:00 | Vulnerability · Source |
| CVE-2025-38480 | suse_vex | SUSE CVE CVE-2025-38480 | first fixed: 2 known affected: 639 known not affected: 46 recommended: 508 | 2026-07-25T00:45:44+00:00 | Vulnerability · Source |
| CVE-2025-38483 | suse_vex | SUSE CVE CVE-2025-38483 | first fixed: 2 known affected: 633 known not affected: 52 recommended: 508 | 2026-07-25T00:45:41+00:00 | Vulnerability · Source |
| CVE-2025-38485 | suse_vex | SUSE CVE CVE-2025-38485 | first fixed: 2 known affected: 394 known not affected: 323 recommended: 508 | 2026-07-25T00:45:40+00:00 | Vulnerability · Source |
| CVE-2025-38487 | suse_vex | SUSE CVE CVE-2025-38487 | first fixed: 2 known affected: 572 known not affected: 145 recommended: 508 | 2026-07-25T00:45:38+00:00 | Vulnerability · Source |
| CVE-2025-38489 | suse_vex | SUSE CVE CVE-2025-38489 | first fixed: 2 known affected: 394 known not affected: 323 recommended: 508 | 2026-07-25T00:45:36+00:00 | Vulnerability · Source |
| CVE-2025-38493 | suse_vex | SUSE CVE CVE-2025-38493 | first fixed: 2 known affected: 5 known not affected: 450 recommended: 154 | 2026-07-25T00:45:34+00:00 | Vulnerability · Source |
| CVE-2025-38496 | suse_vex | SUSE CVE CVE-2025-38496 | first fixed: 2 known affected: 394 known not affected: 331 recommended: 508 | 2026-07-25T00:45:30+00:00 | Vulnerability · Source |
| CVE-2025-38503 | suse_vex | SUSE CVE CVE-2025-38503 | first fixed: 2 known affected: 619 known not affected: 111 recommended: 508 | 2026-07-25T00:45:23+00:00 | Vulnerability · Source |
| CVE-2025-38504 | suse_vex | SUSE CVE CVE-2025-38504 | known not affected: 416 | 2026-07-25T00:45:21+00:00 | Vulnerability · Source |
| CVE-2025-38506 | suse_vex | SUSE CVE CVE-2025-38506 | first fixed: 2 known affected: 458 known not affected: 292 recommended: 508 | 2026-07-25T00:45:20+00:00 | Vulnerability · Source |
| CVE-2025-38509 | suse_vex | SUSE CVE CVE-2025-38509 | known affected: 472 | 2026-07-25T00:45:18+00:00 | Vulnerability · Source |
| CVE-2025-38515 | suse_vex | SUSE CVE CVE-2025-38515 | first fixed: 2 known affected: 593 known not affected: 123 recommended: 549 | 2026-07-25T00:45:15+00:00 | Vulnerability · Source |
| CVE-2025-38516 | suse_vex | SUSE CVE CVE-2025-38516 | first fixed: 2 known affected: 633 known not affected: 77 recommended: 526 | 2026-07-25T00:45:13+00:00 | Vulnerability · Source |
| CVE-2025-38520 | suse_vex | SUSE CVE CVE-2025-38520 | first fixed: 2 known affected: 555 known not affected: 195 recommended: 526 | 2026-07-25T00:45:12+00:00 | Vulnerability · Source |
| CVE-2025-38523 | suse_vex | SUSE CVE CVE-2025-38523 | known not affected: 416 | 2026-07-25T00:45:10+00:00 | Vulnerability · Source |