VEX records
Browse vendor VEX statements available in this Vulnerability-Lookup instance and pivot to the related vulnerability.
292225 VEX records
API response| Vulnerability | Source | Title | Product status | Imported | Links |
|---|---|---|---|---|---|
| CVE-2026-2766 | suse_vex | SUSE CVE CVE-2026-2766 | known affected: 36 recommended: 133 | 2026-07-15T19:00:18+00:00 | Vulnerability · Source |
| CVE-2026-2770 | suse_vex | SUSE CVE CVE-2026-2770 | known affected: 36 recommended: 133 | 2026-07-15T19:00:16+00:00 | Vulnerability · Source |
| CVE-2026-2771 | suse_vex | SUSE CVE CVE-2026-2771 | known affected: 36 recommended: 133 | 2026-07-15T19:00:15+00:00 | Vulnerability · Source |
| CVE-2026-2772 | suse_vex | SUSE CVE CVE-2026-2772 | known affected: 36 recommended: 133 | 2026-07-15T19:00:13+00:00 | Vulnerability · Source |
| CVE-2026-2775 | suse_vex | SUSE CVE CVE-2026-2775 | known affected: 36 recommended: 133 | 2026-07-15T19:00:07+00:00 | Vulnerability · Source |
| CVE-2026-2778 | suse_vex | SUSE CVE CVE-2026-2778 | known affected: 36 recommended: 133 | 2026-07-15T19:00:05+00:00 | Vulnerability · Source |
| CVE-2026-2784 | suse_vex | SUSE CVE CVE-2026-2784 | known affected: 36 recommended: 133 | 2026-07-15T19:00:04+00:00 | Vulnerability · Source |
| CVE-2026-2920 | suse_vex | SUSE CVE CVE-2026-2920 | recommended: 41 | 2026-07-15T19:00:01+00:00 | Vulnerability · Source |
| CVE-2026-2922 | suse_vex | SUSE CVE CVE-2026-2922 | recommended: 35 | 2026-07-15T19:00:00+00:00 | Vulnerability · Source |
| CVE-2026-4685 | suse_vex | SUSE CVE CVE-2026-4685 | known affected: 36 recommended: 133 | 2026-07-15T18:59:43+00:00 | Vulnerability · Source |
| CVE-2026-4697 | suse_vex | SUSE CVE CVE-2026-4697 | known affected: 36 recommended: 133 | 2026-07-15T18:59:39+00:00 | Vulnerability · Source |
| CVE-2026-4698 | suse_vex | SUSE CVE CVE-2026-4698 | known affected: 36 recommended: 133 | 2026-07-15T18:59:38+00:00 | Vulnerability · Source |
| CVE-2026-4702 | suse_vex | SUSE CVE CVE-2026-4702 | known affected: 36 recommended: 133 | 2026-07-15T18:59:37+00:00 | Vulnerability · Source |
| CVE-2026-4711 | suse_vex | SUSE CVE CVE-2026-4711 | known affected: 36 recommended: 133 | 2026-07-15T18:59:36+00:00 | Vulnerability · Source |
| CVE-2026-4716 | suse_vex | SUSE CVE CVE-2026-4716 | known affected: 36 recommended: 133 | 2026-07-15T18:59:35+00:00 | Vulnerability · Source |
| CVE-2026-4717 | suse_vex | SUSE CVE CVE-2026-4717 | known affected: 36 recommended: 133 | 2026-07-15T18:59:34+00:00 | Vulnerability · Source |
| CVE-2026-5731 | suse_vex | SUSE CVE CVE-2026-5731 | known affected: 39 recommended: 125 | 2026-07-15T18:59:20+00:00 | Vulnerability · Source |
| CVE-2026-5732 | suse_vex | SUSE CVE CVE-2026-5732 | known affected: 39 recommended: 125 | 2026-07-15T18:59:19+00:00 | Vulnerability · Source |
| CVE-2026-5734 | suse_vex | SUSE CVE CVE-2026-5734 | known affected: 39 recommended: 125 | 2026-07-15T18:59:18+00:00 | Vulnerability · Source |
| CVE-2026-6321 | suse_vex | SUSE CVE CVE-2026-6321 | known not affected: 117 recommended: 70 | 2026-07-15T18:59:12+00:00 | Vulnerability · Source |
| CVE-2026-6732 | suse_vex | SUSE CVE CVE-2026-6732 | first fixed: 10 known affected: 14 known not affected: 208 recommended: 8 | 2026-07-15T18:59:07+00:00 | Vulnerability · Source |
| CVE-2026-6746 | suse_vex | SUSE CVE CVE-2026-6746 | known affected: 48 recommended: 121 | 2026-07-15T18:59:06+00:00 | Vulnerability · Source |
| CVE-2026-6747 | suse_vex | SUSE CVE CVE-2026-6747 | known affected: 48 recommended: 121 | 2026-07-15T18:59:05+00:00 | Vulnerability · Source |
| CVE-2026-6748 | suse_vex | SUSE CVE CVE-2026-6748 | known affected: 48 recommended: 121 | 2026-07-15T18:59:04+00:00 | Vulnerability · Source |
| CVE-2026-6749 | suse_vex | SUSE CVE CVE-2026-6749 | known affected: 48 recommended: 121 | 2026-07-15T18:59:03+00:00 | Vulnerability · Source |
| CVE-2026-6750 | suse_vex | SUSE CVE CVE-2026-6750 | known affected: 48 recommended: 121 | 2026-07-15T18:59:02+00:00 | Vulnerability · Source |
| CVE-2026-6751 | suse_vex | SUSE CVE CVE-2026-6751 | known affected: 48 recommended: 121 | 2026-07-15T18:59:00+00:00 | Vulnerability · Source |
| CVE-2026-6752 | suse_vex | SUSE CVE CVE-2026-6752 | known affected: 48 recommended: 121 | 2026-07-15T18:58:59+00:00 | Vulnerability · Source |
| CVE-2026-6753 | suse_vex | SUSE CVE CVE-2026-6753 | known affected: 48 recommended: 121 | 2026-07-15T18:58:58+00:00 | Vulnerability · Source |
| CVE-2026-6754 | suse_vex | SUSE CVE CVE-2026-6754 | known affected: 48 recommended: 121 | 2026-07-15T18:58:57+00:00 | Vulnerability · Source |
| CVE-2026-6757 | suse_vex | SUSE CVE CVE-2026-6757 | known affected: 48 recommended: 121 | 2026-07-15T18:58:56+00:00 | Vulnerability · Source |
| CVE-2026-6759 | suse_vex | SUSE CVE CVE-2026-6759 | known affected: 48 recommended: 121 | 2026-07-15T18:58:55+00:00 | Vulnerability · Source |
| CVE-2026-6761 | suse_vex | SUSE CVE CVE-2026-6761 | known affected: 48 recommended: 121 | 2026-07-15T18:58:54+00:00 | Vulnerability · Source |
| CVE-2026-6762 | suse_vex | SUSE CVE CVE-2026-6762 | known affected: 48 recommended: 121 | 2026-07-15T18:58:53+00:00 | Vulnerability · Source |
| CVE-2026-6763 | suse_vex | SUSE CVE CVE-2026-6763 | known affected: 48 recommended: 121 | 2026-07-15T18:58:52+00:00 | Vulnerability · Source |
| CVE-2026-6764 | suse_vex | SUSE CVE CVE-2026-6764 | known affected: 48 recommended: 121 | 2026-07-15T18:58:51+00:00 | Vulnerability · Source |
| CVE-2026-6765 | suse_vex | SUSE CVE CVE-2026-6765 | known affected: 48 recommended: 121 | 2026-07-15T18:58:50+00:00 | Vulnerability · Source |
| CVE-2026-6766 | suse_vex | SUSE CVE CVE-2026-6766 | known affected: 48 recommended: 121 | 2026-07-15T18:58:49+00:00 | Vulnerability · Source |
| CVE-2026-6767 | suse_vex | SUSE CVE CVE-2026-6767 | known affected: 48 recommended: 121 | 2026-07-15T18:58:48+00:00 | Vulnerability · Source |
| CVE-2026-6769 | suse_vex | SUSE CVE CVE-2026-6769 | known affected: 48 recommended: 121 | 2026-07-15T18:58:47+00:00 | Vulnerability · Source |
| CVE-2026-6770 | suse_vex | SUSE CVE CVE-2026-6770 | known affected: 48 recommended: 121 | 2026-07-15T18:58:46+00:00 | Vulnerability · Source |
| CVE-2026-6771 | suse_vex | SUSE CVE CVE-2026-6771 | known affected: 48 recommended: 121 | 2026-07-15T18:58:45+00:00 | Vulnerability · Source |
| CVE-2026-6772 | suse_vex | SUSE CVE CVE-2026-6772 | known affected: 48 recommended: 121 | 2026-07-15T18:58:44+00:00 | Vulnerability · Source |
| CVE-2026-6776 | suse_vex | SUSE CVE CVE-2026-6776 | known affected: 48 recommended: 121 | 2026-07-15T18:58:43+00:00 | Vulnerability · Source |
| CVE-2026-6785 | suse_vex | SUSE CVE CVE-2026-6785 | known affected: 48 recommended: 121 | 2026-07-15T18:58:41+00:00 | Vulnerability · Source |
| CVE-2026-6786 | suse_vex | SUSE CVE CVE-2026-6786 | known affected: 48 recommended: 121 | 2026-07-15T18:58:40+00:00 | Vulnerability · Source |
| CVE-2026-8177 | suse_vex | SUSE CVE CVE-2026-8177 | known affected: 405 known not affected: 32 recommended: 28 | 2026-07-15T18:58:34+00:00 | Vulnerability · Source |
| CVE-2026-8695 | suse_vex | SUSE CVE CVE-2026-8695 | recommended: 8 | 2026-07-15T18:58:26+00:00 | Vulnerability · Source |
| CVE-2026-8949 | suse_vex | SUSE CVE CVE-2026-8949 | known affected: 30 recommended: 118 | 2026-07-15T18:58:21+00:00 | Vulnerability · Source |
| CVE-2026-8954 | suse_vex | SUSE CVE CVE-2026-8954 | known affected: 30 recommended: 125 | 2026-07-15T18:58:20+00:00 | Vulnerability · Source |