VEX records
Browse vendor VEX statements available in this Vulnerability-Lookup instance and pivot to the related vulnerability.
292257 VEX records
API response| Vulnerability | Source | Title | Product status | Imported | Links |
|---|---|---|---|---|---|
| CVE-2026-2763 | suse_vex | SUSE CVE CVE-2026-2763 | known affected: 36 recommended: 133 | 2026-07-15T05:42:18+00:00 | Vulnerability · Source |
| CVE-2026-2764 | suse_vex | SUSE CVE CVE-2026-2764 | known affected: 36 recommended: 133 | 2026-07-15T05:42:17+00:00 | Vulnerability · Source |
| CVE-2026-2765 | suse_vex | SUSE CVE CVE-2026-2765 | known affected: 36 recommended: 133 | 2026-07-15T05:42:16+00:00 | Vulnerability · Source |
| CVE-2026-2767 | suse_vex | SUSE CVE CVE-2026-2767 | known affected: 36 recommended: 133 | 2026-07-15T05:42:15+00:00 | Vulnerability · Source |
| CVE-2026-2768 | suse_vex | SUSE CVE CVE-2026-2768 | known affected: 36 recommended: 133 | 2026-07-15T05:42:14+00:00 | Vulnerability · Source |
| CVE-2026-2769 | suse_vex | SUSE CVE CVE-2026-2769 | known affected: 36 recommended: 133 | 2026-07-15T05:42:13+00:00 | Vulnerability · Source |
| CVE-2026-2773 | suse_vex | SUSE CVE CVE-2026-2773 | known affected: 36 recommended: 133 | 2026-07-15T05:42:12+00:00 | Vulnerability · Source |
| CVE-2026-2774 | suse_vex | SUSE CVE CVE-2026-2774 | known affected: 36 recommended: 133 | 2026-07-15T05:42:10+00:00 | Vulnerability · Source |
| CVE-2026-2776 | suse_vex | SUSE CVE CVE-2026-2776 | known affected: 36 recommended: 133 | 2026-07-15T05:42:09+00:00 | Vulnerability · Source |
| CVE-2026-2777 | suse_vex | SUSE CVE CVE-2026-2777 | known affected: 36 recommended: 133 | 2026-07-15T05:42:08+00:00 | Vulnerability · Source |
| CVE-2026-2779 | suse_vex | SUSE CVE CVE-2026-2779 | known affected: 36 recommended: 133 | 2026-07-15T05:42:07+00:00 | Vulnerability · Source |
| CVE-2026-2780 | suse_vex | SUSE CVE CVE-2026-2780 | known affected: 36 recommended: 133 | 2026-07-15T05:42:06+00:00 | Vulnerability · Source |
| CVE-2026-2782 | suse_vex | SUSE CVE CVE-2026-2782 | known affected: 36 recommended: 133 | 2026-07-15T05:42:03+00:00 | Vulnerability · Source |
| CVE-2026-2783 | suse_vex | SUSE CVE CVE-2026-2783 | known affected: 36 recommended: 133 | 2026-07-15T05:42:02+00:00 | Vulnerability · Source |
| CVE-2026-2785 | suse_vex | SUSE CVE CVE-2026-2785 | known affected: 36 recommended: 133 | 2026-07-15T05:42:01+00:00 | Vulnerability · Source |
| CVE-2026-2786 | suse_vex | SUSE CVE CVE-2026-2786 | known affected: 36 recommended: 133 | 2026-07-15T05:42:00+00:00 | Vulnerability · Source |
| CVE-2026-2787 | suse_vex | SUSE CVE CVE-2026-2787 | known affected: 36 recommended: 133 | 2026-07-15T05:41:59+00:00 | Vulnerability · Source |
| CVE-2026-2788 | suse_vex | SUSE CVE CVE-2026-2788 | known affected: 36 recommended: 133 | 2026-07-15T05:41:58+00:00 | Vulnerability · Source |
| CVE-2026-2789 | suse_vex | SUSE CVE CVE-2026-2789 | known affected: 36 recommended: 133 | 2026-07-15T05:41:57+00:00 | Vulnerability · Source |
| CVE-2026-2790 | suse_vex | SUSE CVE CVE-2026-2790 | known affected: 36 recommended: 133 | 2026-07-15T05:41:56+00:00 | Vulnerability · Source |
| CVE-2026-2791 | suse_vex | SUSE CVE CVE-2026-2791 | known affected: 36 recommended: 133 | 2026-07-15T05:41:55+00:00 | Vulnerability · Source |
| CVE-2026-2792 | suse_vex | SUSE CVE CVE-2026-2792 | known affected: 36 recommended: 133 | 2026-07-15T05:41:54+00:00 | Vulnerability · Source |
| CVE-2026-2793 | suse_vex | SUSE CVE CVE-2026-2793 | known affected: 36 recommended: 133 | 2026-07-15T05:41:53+00:00 | Vulnerability · Source |
| CVE-2026-3119 | suse_vex | SUSE CVE CVE-2026-3119 | known affected: 394 known not affected: 232 recommended: 47 | 2026-07-15T05:41:45+00:00 | Vulnerability · Source |
| CVE-2026-3172 | suse_vex | SUSE CVE CVE-2026-3172 | known affected: 5 recommended: 53 | 2026-07-15T05:41:44+00:00 | Vulnerability · Source |
| CVE-2026-3196 | suse_vex | SUSE CVE CVE-2026-3196 | known affected: 394 known not affected: 654 recommended: 566 | 2026-07-15T05:41:41+00:00 | Vulnerability · Source |
| CVE-2026-3201 | suse_vex | SUSE CVE CVE-2026-3201 | known affected: 118 known not affected: 40 recommended: 210 | 2026-07-15T05:41:40+00:00 | Vulnerability · Source |
| CVE-2026-3202 | suse_vex | SUSE CVE CVE-2026-3202 | known not affected: 178 recommended: 177 | 2026-07-15T05:41:39+00:00 | Vulnerability · Source |
| CVE-2026-3203 | suse_vex | SUSE CVE CVE-2026-3203 | known not affected: 165 recommended: 198 | 2026-07-15T05:41:38+00:00 | Vulnerability · Source |
| CVE-2026-3591 | suse_vex | SUSE CVE CVE-2026-3591 | known affected: 394 known not affected: 232 recommended: 47 | 2026-07-15T05:41:28+00:00 | Vulnerability · Source |
| CVE-2026-3608 | suse_vex | SUSE CVE CVE-2026-3608 | recommended: 294 | 2026-07-15T05:41:25+00:00 | Vulnerability · Source |
| CVE-2026-3949 | suse_vex | SUSE CVE CVE-2026-3949 | known affected: 21 known not affected: 28 recommended: 69 | 2026-07-15T05:41:13+00:00 | Vulnerability · Source |
| CVE-2026-3950 | suse_vex | SUSE CVE CVE-2026-3950 | known not affected: 49 recommended: 69 | 2026-07-15T05:41:12+00:00 | Vulnerability · Source |
| CVE-2026-4271 | suse_vex | SUSE CVE CVE-2026-4271 | known not affected: 205 recommended: 52 | 2026-07-15T05:41:07+00:00 | Vulnerability · Source |
| CVE-2026-4427 | suse_vex | SUSE CVE CVE-2026-4427 | recommended: 25 | 2026-07-15T05:41:04+00:00 | Vulnerability · Source |
| CVE-2026-4684 | suse_vex | SUSE CVE CVE-2026-4684 | known affected: 36 recommended: 133 | 2026-07-15T05:40:57+00:00 | Vulnerability · Source |
| CVE-2026-4686 | suse_vex | SUSE CVE CVE-2026-4686 | known affected: 36 recommended: 133 | 2026-07-15T05:40:56+00:00 | Vulnerability · Source |
| CVE-2026-4687 | suse_vex | SUSE CVE CVE-2026-4687 | known affected: 36 recommended: 133 | 2026-07-15T05:40:54+00:00 | Vulnerability · Source |
| CVE-2026-4688 | suse_vex | SUSE CVE CVE-2026-4688 | known affected: 36 recommended: 133 | 2026-07-15T05:40:53+00:00 | Vulnerability · Source |
| CVE-2026-4689 | suse_vex | SUSE CVE CVE-2026-4689 | known affected: 36 recommended: 133 | 2026-07-15T05:40:52+00:00 | Vulnerability · Source |
| CVE-2026-4690 | suse_vex | SUSE CVE CVE-2026-4690 | known affected: 36 recommended: 133 | 2026-07-15T05:40:51+00:00 | Vulnerability · Source |
| CVE-2026-4691 | suse_vex | SUSE CVE CVE-2026-4691 | known affected: 36 recommended: 133 | 2026-07-15T05:40:50+00:00 | Vulnerability · Source |
| CVE-2026-4692 | suse_vex | SUSE CVE CVE-2026-4692 | known affected: 36 recommended: 133 | 2026-07-15T05:40:49+00:00 | Vulnerability · Source |
| CVE-2026-4693 | suse_vex | SUSE CVE CVE-2026-4693 | known affected: 36 recommended: 133 | 2026-07-15T05:40:48+00:00 | Vulnerability · Source |
| CVE-2026-4694 | suse_vex | SUSE CVE CVE-2026-4694 | known affected: 36 recommended: 133 | 2026-07-15T05:40:47+00:00 | Vulnerability · Source |
| CVE-2026-4695 | suse_vex | SUSE CVE CVE-2026-4695 | known affected: 36 recommended: 133 | 2026-07-15T05:40:45+00:00 | Vulnerability · Source |
| CVE-2026-4696 | suse_vex | SUSE CVE CVE-2026-4696 | known affected: 36 recommended: 133 | 2026-07-15T05:40:44+00:00 | Vulnerability · Source |
| CVE-2026-4699 | suse_vex | SUSE CVE CVE-2026-4699 | known affected: 36 recommended: 133 | 2026-07-15T05:40:43+00:00 | Vulnerability · Source |
| CVE-2026-4700 | suse_vex | SUSE CVE CVE-2026-4700 | known affected: 36 recommended: 133 | 2026-07-15T05:40:42+00:00 | Vulnerability · Source |
| CVE-2026-4701 | suse_vex | SUSE CVE CVE-2026-4701 | known affected: 36 recommended: 133 | 2026-07-15T05:40:41+00:00 | Vulnerability · Source |