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-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 |
| CVE-2025-38525 | suse_vex | SUSE CVE CVE-2025-38525 | known not affected: 416 | 2026-07-25T00:45:08+00:00 | Vulnerability · Source |
| CVE-2025-38526 | suse_vex | SUSE CVE CVE-2025-38526 | first fixed: 2 known affected: 399 known not affected: 283 recommended: 508 | 2026-07-25T00:45:07+00:00 | Vulnerability · Source |
| CVE-2025-38527 | suse_vex | SUSE CVE CVE-2025-38527 | first fixed: 2 known affected: 639 known not affected: 6 recommended: 608 | 2026-07-25T00:45:05+00:00 | Vulnerability · Source |
| CVE-2025-38528 | suse_vex | SUSE CVE CVE-2025-38528 | first fixed: 2 known affected: 585 known not affected: 165 recommended: 508 | 2026-07-25T00:45:03+00:00 | Vulnerability · Source |
| CVE-2025-38529 | suse_vex | SUSE CVE CVE-2025-38529 | first fixed: 2 known affected: 633 known not affected: 98 recommended: 526 | 2026-07-25T00:45:01+00:00 | Vulnerability · Source |
| CVE-2025-38530 | suse_vex | SUSE CVE CVE-2025-38530 | first fixed: 2 known affected: 639 known not affected: 92 recommended: 526 | 2026-07-25T00:44:59+00:00 | Vulnerability · Source |
| CVE-2025-38533 | suse_vex | SUSE CVE CVE-2025-38533 | first fixed: 2 known affected: 394 known not affected: 280 recommended: 508 | 2026-07-25T00:44:56+00:00 | Vulnerability · Source |
| CVE-2025-38534 | suse_vex | SUSE CVE CVE-2025-38534 | known not affected: 416 | 2026-07-25T00:44:54+00:00 | Vulnerability · Source |
| CVE-2025-38535 | suse_vex | SUSE CVE CVE-2025-38535 | first fixed: 2 known affected: 558 known not affected: 173 recommended: 526 | 2026-07-25T00:44:52+00:00 | Vulnerability · Source |
| CVE-2025-38537 | suse_vex | SUSE CVE CVE-2025-38537 | first fixed: 2 known affected: 394 known not affected: 337 recommended: 526 | 2026-07-25T00:44:50+00:00 | Vulnerability · Source |
| CVE-2025-38538 | suse_vex | SUSE CVE CVE-2025-38538 | first fixed: 2 known affected: 633 known not affected: 109 recommended: 526 | 2026-07-25T00:44:48+00:00 | Vulnerability · Source |
| CVE-2025-38539 | suse_vex | SUSE CVE CVE-2025-38539 | first fixed: 2 known affected: 650 recommended: 587 | 2026-07-25T00:44:47+00:00 | Vulnerability · Source |
| CVE-2025-38540 | suse_vex | SUSE CVE CVE-2025-38540 | first fixed: 2 known affected: 639 known not affected: 60 recommended: 526 | 2026-07-25T00:44:45+00:00 | Vulnerability · Source |
| CVE-2025-38541 | suse_vex | SUSE CVE CVE-2025-38541 | first fixed: 2 known affected: 394 known not affected: 337 recommended: 526 | 2026-07-25T00:44:43+00:00 | Vulnerability · Source |
| CVE-2025-38543 | suse_vex | SUSE CVE CVE-2025-38543 | first fixed: 2 known affected: 451 known not affected: 280 recommended: 526 | 2026-07-25T00:44:40+00:00 | Vulnerability · Source |
| CVE-2025-38548 | suse_vex | SUSE CVE CVE-2025-38548 | first fixed: 2 known affected: 521 known not affected: 210 recommended: 526 | 2026-07-25T00:44:38+00:00 | Vulnerability · Source |
| CVE-2025-38549 | suse_vex | SUSE CVE CVE-2025-38549 | first fixed: 2 known affected: 494 known not affected: 283 recommended: 276 | 2026-07-25T00:44:36+00:00 | Vulnerability · Source |
| CVE-2025-38556 | suse_vex | SUSE CVE CVE-2025-38556 | first fixed: 2 known affected: 654 recommended: 621 | 2026-07-25T00:44:29+00:00 | Vulnerability · Source |
| CVE-2025-38560 | suse_vex | SUSE CVE CVE-2025-38560 | first fixed: 2 known affected: 426 known not affected: 156 recommended: 714 | 2026-07-25T00:44:27+00:00 | Vulnerability · Source |
| CVE-2025-38565 | suse_vex | SUSE CVE CVE-2025-38565 | first fixed: 2 known affected: 185 known not affected: 6 recommended: 705 | 2026-07-25T00:44:23+00:00 | Vulnerability · Source |
| CVE-2025-38566 | suse_vex | SUSE CVE CVE-2025-38566 | first fixed: 2 known affected: 394 known not affected: 337 recommended: 617 | 2026-07-25T00:44:21+00:00 | Vulnerability · Source |
| CVE-2025-38571 | suse_vex | SUSE CVE CVE-2025-38571 | first fixed: 2 known affected: 394 known not affected: 337 recommended: 551 | 2026-07-25T00:44:18+00:00 | Vulnerability · Source |
| CVE-2025-38572 | suse_vex | SUSE CVE CVE-2025-38572 | first fixed: 2 known affected: 344 known not affected: 154 recommended: 905 | 2026-07-25T00:44:17+00:00 | Vulnerability · Source |