VEX records
Browse vendor VEX statements available in this Vulnerability-Lookup instance and pivot to the related vulnerability.
306223 VEX records
API response| Vulnerability | Source | Title | Product status | Imported | Links |
|---|---|---|---|---|---|
| CVE-2025-39721 | suse_vex | SUSE CVE CVE-2025-39721 | known affected: 524 known not affected: 259 recommended: 464 | 2026-10-10T01:59:39+00:00 | Vulnerability · Source |
| CVE-2025-39722 | suse_vex | SUSE CVE CVE-2025-39722 | known affected: 69 known not affected: 450 recommended: 154 | 2026-10-10T01:59:37+00:00 | Vulnerability · Source |
| CVE-2025-39724 | suse_vex | SUSE CVE CVE-2025-39724 | known affected: 720 known not affected: 11 recommended: 501 | 2026-10-10T01:59:35+00:00 | Vulnerability · Source |
| CVE-2025-39726 | suse_vex | SUSE CVE CVE-2025-39726 | known affected: 479 known not affected: 68 recommended: 693 | 2026-10-10T01:59:33+00:00 | Vulnerability · Source |
| CVE-2025-39732 | suse_vex | SUSE CVE CVE-2025-39732 | known affected: 524 known not affected: 259 recommended: 464 | 2026-10-10T01:59:30+00:00 | Vulnerability · Source |
| CVE-2025-39735 | suse_vex | SUSE CVE CVE-2025-39735 | known affected: 376 known not affected: 423 recommended: 29 | 2026-10-10T01:59:27+00:00 | Vulnerability · Source |
| CVE-2025-39736 | suse_vex | SUSE CVE CVE-2025-39736 | known not affected: 560 | 2026-10-10T01:59:25+00:00 | Vulnerability · Source |
| CVE-2025-39738 | suse_vex | SUSE CVE CVE-2025-39738 | known affected: 791 recommended: 464 | 2026-10-10T01:59:23+00:00 | Vulnerability · Source |
| CVE-2025-39739 | suse_vex | SUSE CVE CVE-2025-39739 | known affected: 396 known not affected: 387 recommended: 464 | 2026-10-10T01:59:21+00:00 | Vulnerability · Source |
| CVE-2025-39743 | suse_vex | SUSE CVE CVE-2025-39743 | known affected: 394 known not affected: 441 recommended: 310 | 2026-10-10T01:59:19+00:00 | Vulnerability · Source |
| CVE-2025-39744 | suse_vex | SUSE CVE CVE-2025-39744 | known affected: 604 known not affected: 187 recommended: 464 | 2026-10-10T01:59:17+00:00 | Vulnerability · Source |
| CVE-2025-39747 | suse_vex | SUSE CVE CVE-2025-39747 | known affected: 517 known not affected: 208 recommended: 247 | 2026-10-10T01:59:15+00:00 | Vulnerability · Source |
| CVE-2025-39750 | suse_vex | SUSE CVE CVE-2025-39750 | known affected: 396 known not affected: 391 recommended: 464 | 2026-10-10T01:59:13+00:00 | Vulnerability · Source |
| CVE-2025-39754 | suse_vex | SUSE CVE CVE-2025-39754 | known affected: 725 known not affected: 6 recommended: 501 | 2026-10-10T01:59:10+00:00 | Vulnerability · Source |
| CVE-2025-39757 | suse_vex | SUSE CVE CVE-2025-39757 | known affected: 626 known not affected: 99 recommended: 606 | 2026-10-10T01:59:08+00:00 | Vulnerability · Source |
| CVE-2025-39758 | suse_vex | SUSE CVE CVE-2025-39758 | known affected: 463 known not affected: 320 recommended: 464 | 2026-10-10T01:59:06+00:00 | Vulnerability · Source |
| CVE-2025-39759 | suse_vex | SUSE CVE CVE-2025-39759 | known affected: 731 recommended: 501 | 2026-10-10T01:59:04+00:00 | Vulnerability · Source |
| CVE-2025-39760 | suse_vex | SUSE CVE CVE-2025-39760 | known affected: 726 known not affected: 28 recommended: 646 | 2026-10-10T01:59:02+00:00 | Vulnerability · Source |
| CVE-2025-39763 | suse_vex | SUSE CVE CVE-2025-39763 | known affected: 720 known not affected: 21 recommended: 487 | 2026-10-10T01:59:01+00:00 | Vulnerability · Source |
| CVE-2025-39764 | suse_vex | SUSE CVE CVE-2025-39764 | known affected: 731 recommended: 501 | 2026-10-10T01:58:59+00:00 | Vulnerability · Source |
| CVE-2025-39770 | suse_vex | SUSE CVE CVE-2025-39770 | known affected: 401 known not affected: 390 recommended: 464 | 2026-10-10T01:58:56+00:00 | Vulnerability · Source |
| CVE-2025-39773 | suse_vex | SUSE CVE CVE-2025-39773 | known affected: 731 recommended: 509 | 2026-10-10T01:58:54+00:00 | Vulnerability · Source |
| CVE-2025-39778 | suse_vex | SUSE CVE CVE-2025-39778 | known not affected: 467 recommended: 78 | 2026-10-10T01:58:52+00:00 | Vulnerability · Source |
| CVE-2025-39788 | suse_vex | SUSE CVE CVE-2025-39788 | known affected: 524 known not affected: 267 recommended: 464 | 2026-10-10T01:58:49+00:00 | Vulnerability · Source |
| CVE-2025-39790 | suse_vex | SUSE CVE CVE-2025-39790 | known affected: 346 known not affected: 259 recommended: 670 | 2026-10-10T01:58:45+00:00 | Vulnerability · Source |
| CVE-2025-39792 | suse_vex | SUSE CVE CVE-2025-39792 | known affected: 7 known not affected: 542 recommended: 154 | 2026-10-10T01:58:42+00:00 | Vulnerability · Source |
| CVE-2025-39797 | suse_vex | SUSE CVE CVE-2025-39797 | known affected: 354 known not affected: 256 recommended: 708 | 2026-10-10T01:58:39+00:00 | Vulnerability · Source |
| CVE-2025-39798 | suse_vex | SUSE CVE CVE-2025-39798 | known affected: 778 known not affected: 3 recommended: 464 | 2026-10-10T01:58:36+00:00 | Vulnerability · Source |
| CVE-2025-39800 | suse_vex | SUSE CVE CVE-2025-39800 | known affected: 665 known not affected: 66 recommended: 501 | 2026-10-10T01:58:33+00:00 | Vulnerability · Source |
| CVE-2025-39801 | suse_vex | SUSE CVE CVE-2025-39801 | known affected: 718 known not affected: 65 recommended: 464 | 2026-10-10T01:58:29+00:00 | Vulnerability · Source |
| CVE-2025-39805 | suse_vex | SUSE CVE CVE-2025-39805 | known affected: 468 known not affected: 323 recommended: 464 | 2026-10-10T01:58:27+00:00 | Vulnerability · Source |
| CVE-2025-39806 | suse_vex | SUSE CVE CVE-2025-39806 | known affected: 468 known not affected: 323 recommended: 547 | 2026-10-10T01:58:24+00:00 | Vulnerability · Source |
| CVE-2025-39807 | suse_vex | SUSE CVE CVE-2025-39807 | known affected: 401 known not affected: 490 recommended: 247 | 2026-10-10T01:58:22+00:00 | Vulnerability · Source |
| CVE-2025-39808 | suse_vex | SUSE CVE CVE-2025-39808 | known affected: 726 known not affected: 32 recommended: 501 | 2026-10-10T01:58:19+00:00 | Vulnerability · Source |
| CVE-2025-39811 | suse_vex | SUSE CVE CVE-2025-39811 | known affected: 396 known not affected: 467 recommended: 247 | 2026-10-10T01:58:17+00:00 | Vulnerability · Source |
| CVE-2025-39812 | suse_vex | SUSE CVE CVE-2025-39812 | known affected: 726 known not affected: 5 recommended: 501 | 2026-10-10T01:58:15+00:00 | Vulnerability · Source |
| CVE-2025-39814 | suse_vex | SUSE CVE CVE-2025-39814 | known affected: 2 known not affected: 517 recommended: 172 | 2026-10-10T01:58:13+00:00 | Vulnerability · Source |
| CVE-2025-39817 | suse_vex | SUSE CVE CVE-2025-39817 | known affected: 781 recommended: 531 | 2026-10-10T01:58:11+00:00 | Vulnerability · Source |
| CVE-2025-39824 | suse_vex | SUSE CVE CVE-2025-39824 | known affected: 519 known not affected: 36 recommended: 693 | 2026-10-10T01:58:08+00:00 | Vulnerability · Source |
| CVE-2025-39827 | suse_vex | SUSE CVE CVE-2025-39827 | known affected: 396 known not affected: 387 recommended: 464 | 2026-10-10T01:58:05+00:00 | Vulnerability · Source |
| CVE-2025-39828 | suse_vex | SUSE CVE CVE-2025-39828 | known affected: 731 recommended: 464 | 2026-10-10T01:58:03+00:00 | Vulnerability · Source |
| CVE-2025-39833 | suse_vex | SUSE CVE CVE-2025-39833 | known affected: 731 recommended: 501 | 2026-10-10T01:58:01+00:00 | Vulnerability · Source |
| CVE-2025-39838 | suse_vex | SUSE CVE CVE-2025-39838 | known affected: 527 known not affected: 202 recommended: 501 | 2026-10-10T01:57:59+00:00 | Vulnerability · Source |
| CVE-2025-39839 | suse_vex | SUSE CVE CVE-2025-39839 | known affected: 608 known not affected: 181 recommended: 464 | 2026-10-10T01:57:57+00:00 | Vulnerability · Source |
| CVE-2025-39840 | suse_vex | SUSE CVE CVE-2025-39840 | known not affected: 523 recommended: 83 | 2026-10-10T01:57:56+00:00 | Vulnerability · Source |
| CVE-2025-39843 | suse_vex | SUSE CVE CVE-2025-39843 | known affected: 65 known not affected: 317 recommended: 83 | 2026-10-10T01:57:54+00:00 | Vulnerability · Source |
| CVE-2025-39844 | suse_vex | SUSE CVE CVE-2025-39844 | known affected: 527 known not affected: 262 recommended: 464 | 2026-10-10T01:57:52+00:00 | Vulnerability · Source |
| CVE-2025-39845 | suse_vex | SUSE CVE CVE-2025-39845 | known affected: 396 known not affected: 387 recommended: 464 | 2026-10-10T01:57:50+00:00 | Vulnerability · Source |
| CVE-2025-39846 | suse_vex | SUSE CVE CVE-2025-39846 | known affected: 394 known not affected: 393 recommended: 310 | 2026-10-10T01:57:48+00:00 | Vulnerability · Source |
| CVE-2025-39849 | suse_vex | SUSE CVE CVE-2025-39849 | known affected: 466 known not affected: 323 recommended: 613 | 2026-10-10T01:57:46+00:00 | Vulnerability · Source |