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-39713 | suse_vex | SUSE CVE CVE-2025-39713 | first fixed: 2 known affected: 604 known not affected: 25 recommended: 500 | 2026-07-25T00:41:25+00:00 | Vulnerability · Source |
| CVE-2025-39719 | suse_vex | SUSE CVE CVE-2025-39719 | first fixed: 2 known affected: 451 known not affected: 208 recommended: 500 | 2026-07-25T00:41:23+00:00 | Vulnerability · Source |
| CVE-2025-39722 | suse_vex | SUSE CVE CVE-2025-39722 | first fixed: 2 known affected: 57 known not affected: 353 recommended: 154 | 2026-07-25T00:41:21+00:00 | Vulnerability · Source |
| CVE-2025-39724 | suse_vex | SUSE CVE CVE-2025-39724 | first fixed: 2 known affected: 624 known not affected: 11 recommended: 537 | 2026-07-25T00:41:20+00:00 | Vulnerability · Source |
| CVE-2025-39726 | suse_vex | SUSE CVE CVE-2025-39726 | first fixed: 2 known affected: 429 known not affected: 38 recommended: 729 | 2026-07-25T00:41:18+00:00 | Vulnerability · Source |
| CVE-2025-39739 | suse_vex | SUSE CVE CVE-2025-39739 | first fixed: 2 known affected: 394 known not affected: 265 recommended: 500 | 2026-07-25T00:41:11+00:00 | Vulnerability · Source |
| CVE-2025-39742 | suse_vex | SUSE CVE CVE-2025-39742 | first fixed: 2 known affected: 394 known not affected: 99 recommended: 725 | 2026-07-25T00:41:09+00:00 | Vulnerability · Source |
| CVE-2025-39746 | suse_vex | SUSE CVE CVE-2025-39746 | first fixed: 2 known affected: 344 known not affected: 172 recommended: 714 | 2026-07-25T00:41:03+00:00 | Vulnerability · Source |
| CVE-2025-39748 | suse_vex | SUSE CVE CVE-2025-39748 | first fixed: 2 known affected: 474 known not affected: 235 recommended: 300 | 2026-07-25T00:41:01+00:00 | Vulnerability · Source |
| CVE-2025-39749 | suse_vex | SUSE CVE CVE-2025-39749 | first fixed: 2 known affected: 560 known not affected: 99 recommended: 500 | 2026-07-25T00:40:58+00:00 | Vulnerability · Source |
| CVE-2025-39750 | suse_vex | SUSE CVE CVE-2025-39750 | first fixed: 2 known affected: 394 known not affected: 269 recommended: 500 | 2026-07-25T00:40:55+00:00 | Vulnerability · Source |
| CVE-2025-39758 | suse_vex | SUSE CVE CVE-2025-39758 | first fixed: 2 known affected: 451 known not affected: 208 recommended: 500 | 2026-07-25T00:40:48+00:00 | Vulnerability · Source |
| CVE-2025-39761 | suse_vex | SUSE CVE CVE-2025-39761 | first fixed: 2 known affected: 394 known not affected: 265 recommended: 543 | 2026-07-25T00:40:43+00:00 | Vulnerability · Source |
| CVE-2025-39763 | suse_vex | SUSE CVE CVE-2025-39763 | first fixed: 2 known affected: 624 known not affected: 21 recommended: 523 | 2026-07-25T00:40:40+00:00 | Vulnerability · Source |
| CVE-2025-39764 | suse_vex | SUSE CVE CVE-2025-39764 | first fixed: 2 known affected: 635 recommended: 537 | 2026-07-25T00:40:38+00:00 | Vulnerability · Source |
| CVE-2025-39765 | suse_vex | SUSE CVE CVE-2025-39765 | first fixed: 2 known affected: 62 known not affected: 376 recommended: 154 | 2026-07-25T00:40:35+00:00 | Vulnerability · Source |
| CVE-2025-39768 | suse_vex | SUSE CVE CVE-2025-39768 | known not affected: 416 | 2026-07-25T00:40:31+00:00 | Vulnerability · Source |
| CVE-2025-39770 | suse_vex | SUSE CVE CVE-2025-39770 | first fixed: 2 known affected: 399 known not affected: 268 recommended: 500 | 2026-07-25T00:40:28+00:00 | Vulnerability · Source |
| CVE-2025-39775 | suse_vex | SUSE CVE CVE-2025-39775 | first fixed: 2 known affected: 229 known not affected: 211 recommended: 154 | 2026-07-25T00:40:25+00:00 | Vulnerability · Source |
| CVE-2025-39776 | suse_vex | SUSE CVE CVE-2025-39776 | known affected: 246 known not affected: 211 | 2026-07-25T00:40:23+00:00 | Vulnerability · Source |
| CVE-2025-39783 | suse_vex | SUSE CVE CVE-2025-39783 | first fixed: 2 known affected: 557 known not affected: 102 recommended: 500 | 2026-07-25T00:40:20+00:00 | Vulnerability · Source |
| CVE-2025-39789 | suse_vex | SUSE CVE CVE-2025-39789 | known affected: 358 known not affected: 99 | 2026-07-25T00:40:17+00:00 | Vulnerability · Source |
| CVE-2025-39790 | suse_vex | SUSE CVE CVE-2025-39790 | first fixed: 2 known affected: 344 known not affected: 153 recommended: 706 | 2026-07-25T00:40:15+00:00 | Vulnerability · Source |
| CVE-2025-39793 | suse_vex | SUSE CVE CVE-2025-39793 | known not affected: 416 | 2026-07-25T00:40:13+00:00 | Vulnerability · Source |
| CVE-2025-39798 | suse_vex | SUSE CVE CVE-2025-39798 | first fixed: 2 known affected: 654 known not affected: 3 recommended: 500 | 2026-07-25T00:40:07+00:00 | Vulnerability · Source |
| CVE-2025-39801 | suse_vex | SUSE CVE CVE-2025-39801 | first fixed: 2 known affected: 620 known not affected: 39 recommended: 500 | 2026-07-25T00:40:04+00:00 | Vulnerability · Source |
| CVE-2025-39810 | suse_vex | SUSE CVE CVE-2025-39810 | first fixed: 2 known affected: 568 known not affected: 99 recommended: 500 | 2026-07-25T00:40:00+00:00 | Vulnerability · Source |
| CVE-2025-39821 | suse_vex | SUSE CVE CVE-2025-39821 | known not affected: 416 recommended: 27 | 2026-07-25T00:39:56+00:00 | Vulnerability · Source |
| CVE-2025-39831 | suse_vex | SUSE CVE CVE-2025-39831 | first fixed: 2 known affected: 62 known not affected: 376 recommended: 154 | 2026-07-25T00:39:51+00:00 | Vulnerability · Source |
| CVE-2025-39832 | suse_vex | SUSE CVE CVE-2025-39832 | first fixed: 2 known affected: 394 known not affected: 265 recommended: 500 | 2026-07-25T00:39:49+00:00 | Vulnerability · Source |
| CVE-2025-39838 | suse_vex | SUSE CVE CVE-2025-39838 | first fixed: 2 known affected: 509 known not affected: 124 recommended: 537 | 2026-07-25T00:39:46+00:00 | Vulnerability · Source |
| CVE-2025-39839 | suse_vex | SUSE CVE CVE-2025-39839 | first fixed: 2 known affected: 568 known not affected: 97 recommended: 500 | 2026-07-25T00:39:45+00:00 | Vulnerability · Source |
| CVE-2025-39841 | suse_vex | SUSE CVE CVE-2025-39841 | first fixed: 2 known affected: 583 known not affected: 52 recommended: 586 | 2026-07-25T00:39:40+00:00 | Vulnerability · Source |
| CVE-2025-39846 | suse_vex | SUSE CVE CVE-2025-39846 | known affected: 394 known not affected: 271 recommended: 346 | 2026-07-25T00:39:37+00:00 | Vulnerability · Source |
| CVE-2025-39847 | suse_vex | SUSE CVE CVE-2025-39847 | first fixed: 2 known affected: 633 recommended: 537 | 2026-07-25T00:39:34+00:00 | Vulnerability · Source |
| CVE-2025-39850 | suse_vex | SUSE CVE CVE-2025-39850 | first fixed: 2 known affected: 552 known not affected: 113 recommended: 500 | 2026-07-25T00:39:29+00:00 | Vulnerability · Source |
| CVE-2025-39852 | suse_vex | SUSE CVE CVE-2025-39852 | first fixed: 2 known affected: 62 known not affected: 376 recommended: 154 | 2026-07-25T00:39:27+00:00 | Vulnerability · Source |
| CVE-2025-39854 | suse_vex | SUSE CVE CVE-2025-39854 | first fixed: 2 known affected: 394 known not affected: 271 recommended: 500 | 2026-07-25T00:39:24+00:00 | Vulnerability · Source |
| CVE-2025-39857 | suse_vex | SUSE CVE CVE-2025-39857 | first fixed: 2 known affected: 456 known not affected: 213 recommended: 500 | 2026-07-25T00:39:21+00:00 | Vulnerability · Source |
| CVE-2025-39861 | suse_vex | SUSE CVE CVE-2025-39861 | first fixed: 2 known affected: 394 known not affected: 265 recommended: 500 | 2026-07-25T00:39:17+00:00 | Vulnerability · Source |
| CVE-2025-39864 | suse_vex | SUSE CVE CVE-2025-39864 | first fixed: 2 known affected: 552 known not affected: 113 recommended: 561 | 2026-07-25T00:39:14+00:00 | Vulnerability · Source |
| CVE-2025-39865 | suse_vex | SUSE CVE CVE-2025-39865 | first fixed: 2 known affected: 613 known not affected: 22 recommended: 523 | 2026-07-25T00:39:11+00:00 | Vulnerability · Source |
| CVE-2025-39870 | suse_vex | SUSE CVE CVE-2025-39870 | first fixed: 2 known affected: 397 known not affected: 262 recommended: 500 | 2026-07-25T00:39:07+00:00 | Vulnerability · Source |
| CVE-2025-39874 | suse_vex | SUSE CVE CVE-2025-39874 | known not affected: 416 | 2026-07-25T00:39:04+00:00 | Vulnerability · Source |
| CVE-2025-39875 | suse_vex | SUSE CVE CVE-2025-39875 | first fixed: 2 known affected: 5 known not affected: 435 recommended: 154 | 2026-07-25T00:39:01+00:00 | Vulnerability · Source |
| CVE-2025-39878 | suse_vex | SUSE CVE CVE-2025-39878 | known not affected: 416 | 2026-07-25T00:38:58+00:00 | Vulnerability · Source |
| CVE-2025-39879 | suse_vex | SUSE CVE CVE-2025-39879 | known not affected: 416 | 2026-07-25T00:38:55+00:00 | Vulnerability · Source |
| CVE-2025-39880 | suse_vex | SUSE CVE CVE-2025-39880 | first fixed: 2 known affected: 607 known not affected: 156 recommended: 307 | 2026-07-25T00:38:53+00:00 | Vulnerability · Source |
| CVE-2025-39885 | suse_vex | SUSE CVE CVE-2025-39885 | first fixed: 2 known affected: 635 recommended: 537 | 2026-07-25T00:38:49+00:00 | Vulnerability · Source |
| CVE-2025-39890 | suse_vex | SUSE CVE CVE-2025-39890 | first fixed: 2 known affected: 449 known not affected: 288 recommended: 384 | 2026-07-25T00:38:46+00:00 | Vulnerability · Source |