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-38676 | suse_vex | SUSE CVE CVE-2025-38676 | known affected: 463 known not affected: 338 recommended: 503 | 2026-10-15T16:36:13+00:00 | Vulnerability · Source |
| CVE-2025-38677 | suse_vex | SUSE CVE CVE-2025-38677 | known affected: 0 known not affected: 530 | 2026-10-15T16:36:12+00:00 | Vulnerability · Source |
| CVE-2025-38680 | suse_vex | SUSE CVE CVE-2025-38680 | known affected: 726 known not affected: 32 recommended: 532 | 2026-10-15T16:36:10+00:00 | Vulnerability · Source |
| CVE-2025-38681 | suse_vex | SUSE CVE CVE-2025-38681 | known affected: 524 known not affected: 277 recommended: 495 | 2026-10-15T16:36:08+00:00 | Vulnerability · Source |
| CVE-2025-38685 | suse_vex | SUSE CVE CVE-2025-38685 | known affected: 370 known not affected: 126 recommended: 832 | 2026-10-15T16:36:07+00:00 | Vulnerability · Source |
| CVE-2025-38687 | suse_vex | SUSE CVE CVE-2025-38687 | known affected: 774 known not affected: 6 recommended: 495 | 2026-10-15T16:36:04+00:00 | Vulnerability · Source |
| CVE-2025-38690 | suse_vex | SUSE CVE CVE-2025-38690 | known affected: 0 known not affected: 506 recommended: 58 | 2026-10-15T16:36:03+00:00 | Vulnerability · Source |
| CVE-2025-38691 | suse_vex | SUSE CVE CVE-2025-38691 | known affected: 726 known not affected: 32 recommended: 532 | 2026-10-15T16:36:01+00:00 | Vulnerability · Source |
| CVE-2025-38692 | suse_vex | SUSE CVE CVE-2025-38692 | known affected: 593 known not affected: 208 recommended: 495 | 2026-10-15T16:35:59+00:00 | Vulnerability · Source |
| CVE-2025-38693 | suse_vex | SUSE CVE CVE-2025-38693 | known affected: 658 known not affected: 9 recommended: 495 | 2026-10-15T16:35:58+00:00 | Vulnerability · Source |
| CVE-2025-38695 | suse_vex | SUSE CVE CVE-2025-38695 | known affected: 720 known not affected: 21 recommended: 518 | 2026-10-15T16:35:56+00:00 | Vulnerability · Source |
| CVE-2025-38698 | suse_vex | SUSE CVE CVE-2025-38698 | known affected: 394 known not affected: 393 recommended: 310 | 2026-10-15T16:35:54+00:00 | Vulnerability · Source |
| CVE-2025-38700 | suse_vex | SUSE CVE CVE-2025-38700 | known affected: 731 recommended: 532 | 2026-10-15T16:35:52+00:00 | Vulnerability · Source |
| CVE-2025-38701 | suse_vex | SUSE CVE CVE-2025-38701 | known affected: 725 known not affected: 6 recommended: 540 | 2026-10-15T16:35:50+00:00 | Vulnerability · Source |
| CVE-2025-38702 | suse_vex | SUSE CVE CVE-2025-38702 | known affected: 694 known not affected: 37 recommended: 532 | 2026-10-15T16:35:49+00:00 | Vulnerability · Source |
| CVE-2025-38703 | suse_vex | SUSE CVE CVE-2025-38703 | known affected: 401 known not affected: 487 recommended: 404 | 2026-10-15T16:35:47+00:00 | Vulnerability · Source |
| CVE-2025-38707 | suse_vex | SUSE CVE CVE-2025-38707 | known affected: 0 known not affected: 520 | 2026-10-15T16:35:43+00:00 | Vulnerability · Source |
| CVE-2025-38708 | suse_vex | SUSE CVE CVE-2025-38708 | known affected: 0 known not affected: 520 | 2026-10-15T16:35:41+00:00 | Vulnerability · Source |
| CVE-2025-38713 | suse_vex | SUSE CVE CVE-2025-38713 | known affected: 513 known not affected: 1 recommended: 647 | 2026-10-15T16:35:39+00:00 | Vulnerability · Source |
| CVE-2025-38715 | suse_vex | SUSE CVE CVE-2025-38715 | known affected: 394 known not affected: 393 recommended: 310 | 2026-10-15T16:35:37+00:00 | Vulnerability · Source |
| CVE-2025-38717 | suse_vex | SUSE CVE CVE-2025-38717 | known affected: 472 known not affected: 36 recommended: 185 | 2026-10-15T16:35:36+00:00 | Vulnerability · Source |
| CVE-2025-38718 | suse_vex | SUSE CVE CVE-2025-38718 | known affected: 686 known not affected: 36 recommended: 637 | 2026-10-15T16:35:34+00:00 | Vulnerability · Source |
| CVE-2025-38721 | suse_vex | SUSE CVE CVE-2025-38721 | known affected: 786 recommended: 503 | 2026-10-15T16:35:32+00:00 | Vulnerability · Source |
| CVE-2025-38724 | suse_vex | SUSE CVE CVE-2025-38724 | known affected: 720 known not affected: 11 recommended: 635 | 2026-10-15T16:35:30+00:00 | Vulnerability · Source |
| CVE-2025-38725 | suse_vex | SUSE CVE CVE-2025-38725 | known affected: 524 known not affected: 256 recommended: 495 | 2026-10-15T16:35:28+00:00 | Vulnerability · Source |
| CVE-2025-38727 | suse_vex | SUSE CVE CVE-2025-38727 | known affected: 2 known not affected: 327 recommended: 532 | 2026-10-15T16:35:25+00:00 | Vulnerability · Source |
| CVE-2025-38728 | suse_vex | SUSE CVE CVE-2025-38728 | known affected: 725 known not affected: 41 recommended: 420 | 2026-10-15T16:35:23+00:00 | Vulnerability · Source |
| CVE-2025-38729 | suse_vex | SUSE CVE CVE-2025-38729 | known affected: 626 known not affected: 96 recommended: 531 | 2026-10-15T16:35:20+00:00 | Vulnerability · Source |
| CVE-2025-38730 | suse_vex | SUSE CVE CVE-2025-38730 | known affected: 463 known not affected: 317 recommended: 615 | 2026-10-15T16:35:18+00:00 | Vulnerability · Source |
| CVE-2025-38732 | suse_vex | SUSE CVE CVE-2025-38732 | known affected: 576 known not affected: 213 recommended: 503 | 2026-10-15T16:35:17+00:00 | Vulnerability · Source |
| CVE-2025-38734 | suse_vex | SUSE CVE CVE-2025-38734 | known affected: 349 known not affected: 262 recommended: 701 | 2026-10-15T16:35:15+00:00 | Vulnerability · Source |
| CVE-2025-38735 | suse_vex | SUSE CVE CVE-2025-38735 | known affected: 637 known not affected: 96 recommended: 518 | 2026-10-15T16:35:13+00:00 | Vulnerability · Source |
| CVE-2025-38736 | suse_vex | SUSE CVE CVE-2025-38736 | known affected: 396 known not affected: 387 recommended: 495 | 2026-10-15T16:35:11+00:00 | Vulnerability · Source |
| CVE-2025-39675 | suse_vex | SUSE CVE CVE-2025-39675 | known affected: 567 known not affected: 216 recommended: 495 | 2026-10-15T16:35:09+00:00 | Vulnerability · Source |
| CVE-2025-39676 | suse_vex | SUSE CVE CVE-2025-39676 | known affected: 720 known not affected: 6 recommended: 532 | 2026-10-15T16:35:08+00:00 | Vulnerability · Source |
| CVE-2025-39681 | suse_vex | SUSE CVE CVE-2025-39681 | known affected: 573 known not affected: 213 recommended: 495 | 2026-10-15T16:35:05+00:00 | Vulnerability · Source |
| CVE-2025-39683 | suse_vex | SUSE CVE CVE-2025-39683 | known affected: 662 known not affected: 129 recommended: 495 | 2026-10-15T16:35:01+00:00 | Vulnerability · Source |
| CVE-2025-39685 | suse_vex | SUSE CVE CVE-2025-39685 | known affected: 517 known not affected: 206 recommended: 495 | 2026-10-15T16:34:59+00:00 | Vulnerability · Source |
| CVE-2025-39686 | suse_vex | SUSE CVE CVE-2025-39686 | known affected: 791 recommended: 495 | 2026-10-15T16:34:57+00:00 | Vulnerability · Source |
| CVE-2025-39687 | suse_vex | SUSE CVE CVE-2025-39687 | known affected: 284 known not affected: 262 recommended: 185 | 2026-10-15T16:34:55+00:00 | Vulnerability · Source |
| CVE-2025-39688 | suse_vex | SUSE CVE CVE-2025-39688 | known affected: 0 known not affected: 460 recommended: 109 | 2026-10-15T16:34:53+00:00 | Vulnerability · Source |
| CVE-2025-39689 | suse_vex | SUSE CVE CVE-2025-39689 | known affected: 347 known not affected: 36 recommended: 438 | 2026-10-15T16:34:51+00:00 | Vulnerability · Source |
| CVE-2025-39691 | suse_vex | SUSE CVE CVE-2025-39691 | known affected: 548 known not affected: 5 recommended: 746 | 2026-10-15T16:34:48+00:00 | Vulnerability · Source |
| CVE-2025-39693 | suse_vex | SUSE CVE CVE-2025-39693 | known affected: 524 known not affected: 259 recommended: 495 | 2026-10-15T16:34:46+00:00 | Vulnerability · Source |
| CVE-2025-39694 | suse_vex | SUSE CVE CVE-2025-39694 | known affected: 468 known not affected: 323 recommended: 581 | 2026-10-15T16:34:44+00:00 | Vulnerability · Source |
| CVE-2025-39697 | suse_vex | SUSE CVE CVE-2025-39697 | known affected: 593 known not affected: 190 recommended: 599 | 2026-10-15T16:34:42+00:00 | Vulnerability · Source |
| CVE-2025-39698 | suse_vex | SUSE CVE CVE-2025-39698 | known affected: 7 known not affected: 539 recommended: 275 | 2026-10-15T16:34:40+00:00 | Vulnerability · Source |
| CVE-2025-39700 | suse_vex | SUSE CVE CVE-2025-39700 | known affected: 2 known not affected: 514 recommended: 185 | 2026-10-15T16:34:39+00:00 | Vulnerability · Source |
| CVE-2025-39702 | suse_vex | SUSE CVE CVE-2025-39702 | known affected: 697 known not affected: 36 recommended: 604 | 2026-10-15T16:34:37+00:00 | Vulnerability · Source |
| CVE-2025-39703 | suse_vex | SUSE CVE CVE-2025-39703 | known affected: 351 known not affected: 262 recommended: 678 | 2026-10-15T16:34:35+00:00 | Vulnerability · Source |