VEX records
Browse vendor VEX statements available in this Vulnerability-Lookup instance and pivot to the related vulnerability.
292126 VEX records
API response| Vulnerability | Source | Title | Product status | Imported | Links |
|---|---|---|---|---|---|
| CVE-2025-39738 | suse_vex | SUSE CVE CVE-2025-39738 | first fixed: 2 known affected: 665 recommended: 500 | 2026-07-22T16:42:23+00:00 | Vulnerability · Source |
| CVE-2025-39744 | suse_vex | SUSE CVE CVE-2025-39744 | first fixed: 2 known affected: 568 known not affected: 97 recommended: 500 | 2026-07-22T16:42:22+00:00 | Vulnerability · Source |
| CVE-2025-39754 | suse_vex | SUSE CVE CVE-2025-39754 | first fixed: 2 known affected: 629 known not affected: 6 recommended: 530 | 2026-07-22T16:42:20+00:00 | Vulnerability · Source |
| CVE-2025-39759 | suse_vex | SUSE CVE CVE-2025-39759 | first fixed: 2 known affected: 635 recommended: 530 | 2026-07-22T16:42:19+00:00 | Vulnerability · Source |
| CVE-2025-39773 | suse_vex | SUSE CVE CVE-2025-39773 | first fixed: 2 known affected: 635 recommended: 538 | 2026-07-22T16:42:17+00:00 | Vulnerability · Source |
| CVE-2025-39782 | suse_vex | SUSE CVE CVE-2025-39782 | first fixed: 2 known affected: 629 known not affected: 6 recommended: 538 | 2026-07-22T16:42:15+00:00 | Vulnerability · Source |
| CVE-2025-39800 | suse_vex | SUSE CVE CVE-2025-39800 | first fixed: 2 known affected: 599 known not affected: 36 recommended: 530 | 2026-07-22T16:42:14+00:00 | Vulnerability · Source |
| CVE-2025-39805 | suse_vex | SUSE CVE CVE-2025-39805 | first fixed: 2 known affected: 456 known not affected: 209 recommended: 500 | 2026-07-22T16:42:12+00:00 | Vulnerability · Source |
| CVE-2025-39813 | suse_vex | SUSE CVE CVE-2025-39813 | first fixed: 2 known affected: 635 recommended: 580 | 2026-07-22T16:42:11+00:00 | Vulnerability · Source |
| CVE-2025-39817 | suse_vex | SUSE CVE CVE-2025-39817 | first fixed: 2 known affected: 694 recommended: 496 | 2026-07-22T16:42:09+00:00 | Vulnerability · Source |
| CVE-2025-39825 | suse_vex | SUSE CVE CVE-2025-39825 | first fixed: 2 known affected: 511 known not affected: 154 recommended: 563 | 2026-07-22T16:42:07+00:00 | Vulnerability · Source |
| CVE-2025-39828 | suse_vex | SUSE CVE CVE-2025-39828 | first fixed: 2 known affected: 635 recommended: 500 | 2026-07-22T16:42:06+00:00 | Vulnerability · Source |
| CVE-2025-39829 | suse_vex | SUSE CVE CVE-2025-39829 | first fixed: 2 known affected: 296 recommended: 432 | 2026-07-22T16:42:05+00:00 | Vulnerability · Source |
| CVE-2025-39833 | suse_vex | SUSE CVE CVE-2025-39833 | first fixed: 2 known affected: 635 recommended: 530 | 2026-07-22T16:42:03+00:00 | Vulnerability · Source |
| CVE-2025-39835 | suse_vex | SUSE CVE CVE-2025-39835 | first fixed: 2 known affected: 511 known not affected: 154 recommended: 500 | 2026-07-22T16:42:02+00:00 | Vulnerability · Source |
| CVE-2025-39842 | suse_vex | SUSE CVE CVE-2025-39842 | first fixed: 2 known affected: 456 known not affected: 209 recommended: 500 | 2026-07-22T16:42:00+00:00 | Vulnerability · Source |
| CVE-2025-39853 | suse_vex | SUSE CVE CVE-2025-39853 | first fixed: 2 known affected: 629 known not affected: 6 recommended: 530 | 2026-07-22T16:41:59+00:00 | Vulnerability · Source |
| CVE-2025-39860 | suse_vex | SUSE CVE CVE-2025-39860 | first fixed: 2 known affected: 349 known not affected: 124 recommended: 736 | 2026-07-22T16:41:57+00:00 | Vulnerability · Source |
| CVE-2025-39866 | suse_vex | SUSE CVE CVE-2025-39866 | first fixed: 2 known affected: 635 recommended: 530 | 2026-07-22T16:41:56+00:00 | Vulnerability · Source |
| CVE-2025-39869 | suse_vex | SUSE CVE CVE-2025-39869 | first fixed: 2 known affected: 467 known not affected: 6 recommended: 736 | 2026-07-22T16:41:55+00:00 | Vulnerability · Source |
| CVE-2025-39871 | suse_vex | SUSE CVE CVE-2025-39871 | first fixed: 2 known affected: 399 known not affected: 266 recommended: 500 | 2026-07-22T16:41:53+00:00 | Vulnerability · Source |
| CVE-2025-39873 | suse_vex | SUSE CVE CVE-2025-39873 | first fixed: 2 known affected: 568 known not affected: 97 recommended: 500 | 2026-07-22T16:41:52+00:00 | Vulnerability · Source |
| CVE-2025-39881 | suse_vex | SUSE CVE CVE-2025-39881 | first fixed: 2 known affected: 456 known not affected: 209 recommended: 541 | 2026-07-22T16:41:50+00:00 | Vulnerability · Source |
| CVE-2025-39889 | suse_vex | SUSE CVE CVE-2025-39889 | first fixed: 2 known affected: 654 known not affected: 40 recommended: 500 | 2026-07-22T16:41:48+00:00 | Vulnerability · Source |
| CVE-2025-39931 | suse_vex | SUSE CVE CVE-2025-39931 | first fixed: 2 known affected: 635 recommended: 530 | 2026-07-22T16:41:45+00:00 | Vulnerability · Source |
| CVE-2025-39937 | suse_vex | SUSE CVE CVE-2025-39937 | first fixed: 2 known affected: 643 known not affected: 22 recommended: 500 | 2026-07-22T16:41:44+00:00 | Vulnerability · Source |
| CVE-2025-39944 | suse_vex | SUSE CVE CVE-2025-39944 | first fixed: 2 known affected: 511 known not affected: 154 recommended: 500 | 2026-07-22T16:41:43+00:00 | Vulnerability · Source |
| CVE-2025-39946 | suse_vex | SUSE CVE CVE-2025-39946 | first fixed: 2 known affected: 456 known not affected: 209 recommended: 500 | 2026-07-22T16:41:41+00:00 | Vulnerability · Source |
| CVE-2025-39998 | suse_vex | SUSE CVE CVE-2025-39998 | first fixed: 2 known affected: 711 recommended: 362 | 2026-07-22T16:41:38+00:00 | Vulnerability · Source |
| CVE-2025-40000 | suse_vex | SUSE CVE CVE-2025-40000 | first fixed: 2 known affected: 456 known not affected: 209 recommended: 506 | 2026-07-22T16:41:37+00:00 | Vulnerability · Source |
| CVE-2025-40001 | suse_vex | SUSE CVE CVE-2025-40001 | first fixed: 2 known affected: 635 recommended: 536 | 2026-07-22T16:41:36+00:00 | Vulnerability · Source |
| CVE-2025-40024 | suse_vex | SUSE CVE CVE-2025-40024 | first fixed: 2 known affected: 449 known not affected: 266 recommended: 384 | 2026-07-22T16:41:33+00:00 | Vulnerability · Source |
| CVE-2025-40027 | suse_vex | SUSE CVE CVE-2025-40027 | first fixed: 2 known affected: 624 known not affected: 6 recommended: 536 | 2026-07-22T16:41:31+00:00 | Vulnerability · Source |
| CVE-2025-40030 | suse_vex | SUSE CVE CVE-2025-40030 | first fixed: 2 known affected: 624 known not affected: 6 recommended: 554 | 2026-07-22T16:41:30+00:00 | Vulnerability · Source |
| CVE-2025-40033 | suse_vex | SUSE CVE CVE-2025-40033 | first fixed: 2 known affected: 449 known not affected: 266 recommended: 390 | 2026-07-22T16:41:28+00:00 | Vulnerability · Source |
| CVE-2025-40035 | suse_vex | SUSE CVE CVE-2025-40035 | first fixed: 2 known affected: 630 recommended: 536 | 2026-07-22T16:41:27+00:00 | Vulnerability · Source |
| CVE-2025-40040 | suse_vex | SUSE CVE CVE-2025-40040 | first fixed: 2 known affected: 436 recommended: 807 | 2026-07-22T16:41:26+00:00 | Vulnerability · Source |
| CVE-2025-40052 | suse_vex | SUSE CVE CVE-2025-40052 | first fixed: 2 known affected: 451 known not affected: 209 recommended: 506 | 2026-07-22T16:41:24+00:00 | Vulnerability · Source |
| CVE-2025-40053 | suse_vex | SUSE CVE CVE-2025-40053 | first fixed: 2 known affected: 685 recommended: 420 | 2026-07-22T16:41:22+00:00 | Vulnerability · Source |
| CVE-2025-40055 | suse_vex | SUSE CVE CVE-2025-40055 | first fixed: 2 known affected: 624 known not affected: 6 recommended: 536 | 2026-07-22T16:41:21+00:00 | Vulnerability · Source |
| CVE-2025-40060 | suse_vex | SUSE CVE CVE-2025-40060 | first fixed: 2 known affected: 506 known not affected: 154 recommended: 506 | 2026-07-22T16:41:18+00:00 | Vulnerability · Source |
| CVE-2025-40061 | suse_vex | SUSE CVE CVE-2025-40061 | first fixed: 2 known affected: 451 known not affected: 209 recommended: 506 | 2026-07-22T16:41:17+00:00 | Vulnerability · Source |
| CVE-2025-40071 | suse_vex | SUSE CVE CVE-2025-40071 | first fixed: 2 known affected: 506 known not affected: 154 recommended: 506 | 2026-07-22T16:41:15+00:00 | Vulnerability · Source |
| CVE-2025-40074 | suse_vex | SUSE CVE CVE-2025-40074 | first fixed: 2 known affected: 638 known not affected: 22 recommended: 506 | 2026-07-22T16:41:14+00:00 | Vulnerability · Source |
| CVE-2025-40080 | suse_vex | SUSE CVE CVE-2025-40080 | first fixed: 2 known affected: 591 known not affected: 69 recommended: 506 | 2026-07-22T16:41:12+00:00 | Vulnerability · Source |
| CVE-2025-40083 | suse_vex | SUSE CVE CVE-2025-40083 | first fixed: 2 known affected: 624 known not affected: 6 recommended: 530 | 2026-07-22T16:41:10+00:00 | Vulnerability · Source |
| CVE-2025-40098 | suse_vex | SUSE CVE CVE-2025-40098 | first fixed: 2 known affected: 394 known not affected: 266 recommended: 506 | 2026-07-22T16:41:09+00:00 | Vulnerability · Source |
| CVE-2025-40100 | suse_vex | SUSE CVE CVE-2025-40100 | first fixed: 2 known affected: 638 known not affected: 22 recommended: 506 | 2026-07-22T16:41:07+00:00 | Vulnerability · Source |
| CVE-2025-40103 | suse_vex | SUSE CVE CVE-2025-40103 | first fixed: 2 known affected: 683 known not affected: 6 recommended: 426 | 2026-07-22T16:41:06+00:00 | Vulnerability · Source |
| CVE-2025-40105 | suse_vex | SUSE CVE CVE-2025-40105 | first fixed: 2 known affected: 563 known not affected: 97 recommended: 506 | 2026-07-22T16:41:04+00:00 | Vulnerability · Source |