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-39814 | suse_vex | SUSE CVE CVE-2025-39814 | known affected: 2 known not affected: 514 recommended: 203 | 2026-10-15T16:32:53+00:00 | Vulnerability · Source |
| CVE-2025-39816 | suse_vex | SUSE CVE CVE-2025-39816 | known affected: 468 known not affected: 420 recommended: 278 | 2026-10-15T16:32:51+00:00 | Vulnerability · Source |
| CVE-2025-39817 | suse_vex | SUSE CVE CVE-2025-39817 | known affected: 778 recommended: 562 | 2026-10-15T16:32:49+00:00 | Vulnerability · Source |
| CVE-2025-39819 | suse_vex | SUSE CVE CVE-2025-39819 | known affected: 529 known not affected: 204 recommended: 604 | 2026-10-15T16:32:48+00:00 | Vulnerability · Source |
| CVE-2025-39821 | suse_vex | SUSE CVE CVE-2025-39821 | known affected: 0 known not affected: 520 recommended: 58 | 2026-10-15T16:32:46+00:00 | Vulnerability · Source |
| CVE-2025-39822 | suse_vex | SUSE CVE CVE-2025-39822 | known affected: 468 known not affected: 420 recommended: 278 | 2026-10-15T16:32:44+00:00 | Vulnerability · Source |
| CVE-2025-39823 | suse_vex | SUSE CVE CVE-2025-39823 | known affected: 375 known not affected: 187 recommended: 780 | 2026-10-15T16:32:42+00:00 | Vulnerability · Source |
| CVE-2025-39826 | suse_vex | SUSE CVE CVE-2025-39826 | known affected: 396 known not affected: 387 recommended: 495 | 2026-10-15T16:32:41+00:00 | Vulnerability · Source |
| CVE-2025-39827 | suse_vex | SUSE CVE CVE-2025-39827 | known affected: 396 known not affected: 387 recommended: 495 | 2026-10-15T16:32:39+00:00 | Vulnerability · Source |
| CVE-2025-39829 | suse_vex | SUSE CVE CVE-2025-39829 | known affected: 381 recommended: 452 | 2026-10-15T16:32:38+00:00 | Vulnerability · Source |
| CVE-2025-39830 | suse_vex | SUSE CVE CVE-2025-39830 | known affected: 468 known not affected: 420 recommended: 278 | 2026-10-15T16:32:36+00:00 | Vulnerability · Source |
| CVE-2025-39831 | suse_vex | SUSE CVE CVE-2025-39831 | known affected: 74 known not affected: 470 recommended: 185 | 2026-10-15T16:32:34+00:00 | Vulnerability · Source |
| CVE-2025-39832 | suse_vex | SUSE CVE CVE-2025-39832 | known affected: 396 known not affected: 387 recommended: 495 | 2026-10-15T16:32:33+00:00 | Vulnerability · Source |
| CVE-2025-39834 | suse_vex | SUSE CVE CVE-2025-39834 | known affected: 468 known not affected: 420 recommended: 278 | 2026-10-15T16:32:31+00:00 | Vulnerability · Source |
| CVE-2025-39836 | suse_vex | SUSE CVE CVE-2025-39836 | known affected: 396 known not affected: 464 recommended: 278 | 2026-10-15T16:32:29+00:00 | Vulnerability · Source |
| CVE-2025-39837 | suse_vex | SUSE CVE CVE-2025-39837 | known affected: 0 known not affected: 520 | 2026-10-15T16:32:27+00:00 | Vulnerability · Source |
| CVE-2025-39842 | suse_vex | SUSE CVE CVE-2025-39842 | known affected: 468 known not affected: 323 recommended: 495 | 2026-10-15T16:32:25+00:00 | Vulnerability · Source |
| CVE-2025-39844 | suse_vex | SUSE CVE CVE-2025-39844 | known affected: 527 known not affected: 262 recommended: 495 | 2026-10-15T16:32:24+00:00 | Vulnerability · Source |
| CVE-2025-39845 | suse_vex | SUSE CVE CVE-2025-39845 | known affected: 396 known not affected: 387 recommended: 495 | 2026-10-15T16:32:22+00:00 | Vulnerability · Source |
| CVE-2025-39848 | suse_vex | SUSE CVE CVE-2025-39848 | known affected: 396 known not affected: 387 recommended: 495 | 2026-10-15T16:32:20+00:00 | Vulnerability · Source |
| CVE-2025-39849 | suse_vex | SUSE CVE CVE-2025-39849 | known affected: 466 known not affected: 323 recommended: 644 | 2026-10-15T16:32:18+00:00 | Vulnerability · Source |
| CVE-2025-39851 | suse_vex | SUSE CVE CVE-2025-39851 | known affected: 576 known not affected: 213 recommended: 495 | 2026-10-15T16:32:16+00:00 | Vulnerability · Source |
| CVE-2025-39852 | suse_vex | SUSE CVE CVE-2025-39852 | known affected: 74 known not affected: 470 recommended: 185 | 2026-10-15T16:32:13+00:00 | Vulnerability · Source |
| CVE-2025-39853 | suse_vex | SUSE CVE CVE-2025-39853 | known affected: 725 known not affected: 6 recommended: 532 | 2026-10-15T16:32:11+00:00 | Vulnerability · Source |
| CVE-2025-39854 | suse_vex | SUSE CVE CVE-2025-39854 | known affected: 396 known not affected: 393 recommended: 495 | 2026-10-15T16:32:09+00:00 | Vulnerability · Source |
| CVE-2025-39855 | suse_vex | SUSE CVE CVE-2025-39855 | known affected: 0 known not affected: 520 recommended: 58 | 2026-10-15T16:32:07+00:00 | Vulnerability · Source |
| CVE-2025-39860 | suse_vex | SUSE CVE CVE-2025-39860 | known affected: 351 known not affected: 202 recommended: 738 | 2026-10-15T16:32:05+00:00 | Vulnerability · Source |
| CVE-2025-39861 | suse_vex | SUSE CVE CVE-2025-39861 | known affected: 396 known not affected: 387 recommended: 495 | 2026-10-15T16:32:02+00:00 | Vulnerability · Source |
| CVE-2025-39862 | suse_vex | SUSE CVE CVE-2025-39862 | known affected: 0 known not affected: 317 recommended: 58 | 2026-10-15T16:32:00+00:00 | Vulnerability · Source |
| CVE-2025-39863 | suse_vex | SUSE CVE CVE-2025-39863 | known affected: 725 known not affected: 6 recommended: 532 | 2026-10-15T16:31:58+00:00 | Vulnerability · Source |
| CVE-2025-39864 | suse_vex | SUSE CVE CVE-2025-39864 | known affected: 576 known not affected: 213 recommended: 556 | 2026-10-15T16:31:56+00:00 | Vulnerability · Source |
| CVE-2025-39865 | suse_vex | SUSE CVE CVE-2025-39865 | known affected: 695 known not affected: 36 recommended: 518 | 2026-10-15T16:31:54+00:00 | Vulnerability · Source |
| CVE-2025-39866 | suse_vex | SUSE CVE CVE-2025-39866 | known affected: 731 recommended: 532 | 2026-10-15T16:31:52+00:00 | Vulnerability · Source |
| CVE-2025-39870 | suse_vex | SUSE CVE CVE-2025-39870 | known affected: 399 known not affected: 384 recommended: 495 | 2026-10-15T16:31:50+00:00 | Vulnerability · Source |
| CVE-2025-39871 | suse_vex | SUSE CVE CVE-2025-39871 | known affected: 401 known not affected: 390 recommended: 495 | 2026-10-15T16:31:48+00:00 | Vulnerability · Source |
| CVE-2025-39873 | suse_vex | SUSE CVE CVE-2025-39873 | known affected: 604 known not affected: 187 recommended: 495 | 2026-10-15T16:31:46+00:00 | Vulnerability · Source |
| CVE-2025-39875 | suse_vex | SUSE CVE CVE-2025-39875 | known affected: 7 known not affected: 539 recommended: 185 | 2026-10-15T16:31:44+00:00 | Vulnerability · Source |
| CVE-2025-39876 | suse_vex | SUSE CVE CVE-2025-39876 | known affected: 637 known not affected: 96 recommended: 518 | 2026-10-15T16:31:42+00:00 | Vulnerability · Source |
| CVE-2025-39881 | suse_vex | SUSE CVE CVE-2025-39881 | known affected: 468 known not affected: 323 recommended: 536 | 2026-10-15T16:31:40+00:00 | Vulnerability · Source |
| CVE-2025-39882 | suse_vex | SUSE CVE CVE-2025-39882 | known affected: 396 known not affected: 387 recommended: 495 | 2026-10-15T16:31:38+00:00 | Vulnerability · Source |
| CVE-2025-39884 | suse_vex | SUSE CVE CVE-2025-39884 | known affected: 69 known not affected: 447 recommended: 185 | 2026-10-15T16:31:36+00:00 | Vulnerability · Source |
| CVE-2025-39885 | suse_vex | SUSE CVE CVE-2025-39885 | known affected: 731 recommended: 532 | 2026-10-15T16:31:35+00:00 | Vulnerability · Source |
| CVE-2025-39894 | suse_vex | SUSE CVE CVE-2025-39894 | known affected: 2 known not affected: 384 recommended: 203 | 2026-10-15T16:31:33+00:00 | Vulnerability · Source |
| CVE-2025-39903 | suse_vex | SUSE CVE CVE-2025-39903 | known affected: 396 known not affected: 539 recommended: 185 | 2026-10-15T16:31:31+00:00 | Vulnerability · Source |
| CVE-2025-39905 | suse_vex | SUSE CVE CVE-2025-39905 | known affected: 0 known not affected: 520 recommended: 42 | 2026-10-15T16:31:30+00:00 | Vulnerability · Source |
| CVE-2025-39906 | suse_vex | SUSE CVE CVE-2025-39906 | known affected: 0 known not affected: 520 recommended: 58 | 2026-10-15T16:31:28+00:00 | Vulnerability · Source |
| CVE-2025-39907 | suse_vex | SUSE CVE CVE-2025-39907 | known affected: 396 known not affected: 387 recommended: 495 | 2026-10-15T16:31:26+00:00 | Vulnerability · Source |
| CVE-2025-39913 | suse_vex | SUSE CVE CVE-2025-39913 | known affected: 664 known not affected: 64 recommended: 438 | 2026-10-15T16:31:24+00:00 | Vulnerability · Source |
| CVE-2025-39919 | suse_vex | SUSE CVE CVE-2025-39919 | known affected: 0 known not affected: 520 recommended: 58 | 2026-10-15T16:31:23+00:00 | Vulnerability · Source |
| CVE-2025-39921 | suse_vex | SUSE CVE CVE-2025-39921 | known affected: 0 known not affected: 520 | 2026-10-15T16:31:21+00:00 | Vulnerability · Source |