VEX records
Browse vendor VEX statements available in this Vulnerability-Lookup instance and pivot to the related vulnerability.
294458 VEX records
API response| Vulnerability | Source | Title | Product status | Imported | Links |
|---|---|---|---|---|---|
| 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-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 |
| CVE-2026-4704 | suse_vex | SUSE CVE CVE-2026-4704 | known affected: 36 recommended: 133 | 2026-07-15T05:40:40+00:00 | Vulnerability · Source |
| CVE-2026-4705 | suse_vex | SUSE CVE CVE-2026-4705 | known affected: 36 recommended: 133 | 2026-07-15T05:40:39+00:00 | Vulnerability · Source |
| CVE-2026-4706 | suse_vex | SUSE CVE CVE-2026-4706 | known affected: 36 recommended: 133 | 2026-07-15T05:40:37+00:00 | Vulnerability · Source |
| CVE-2026-4707 | suse_vex | SUSE CVE CVE-2026-4707 | known affected: 36 recommended: 133 | 2026-07-15T05:40:36+00:00 | Vulnerability · Source |
| CVE-2026-4708 | suse_vex | SUSE CVE CVE-2026-4708 | known affected: 36 recommended: 133 | 2026-07-15T05:40:35+00:00 | Vulnerability · Source |
| CVE-2026-4709 | suse_vex | SUSE CVE CVE-2026-4709 | known affected: 36 recommended: 133 | 2026-07-15T05:40:34+00:00 | Vulnerability · Source |
| CVE-2026-4710 | suse_vex | SUSE CVE CVE-2026-4710 | known affected: 36 recommended: 133 | 2026-07-15T05:40:33+00:00 | Vulnerability · Source |
| CVE-2026-4712 | suse_vex | SUSE CVE CVE-2026-4712 | known affected: 36 recommended: 133 | 2026-07-15T05:40:32+00:00 | Vulnerability · Source |
| CVE-2026-4713 | suse_vex | SUSE CVE CVE-2026-4713 | known affected: 36 recommended: 133 | 2026-07-15T05:40:30+00:00 | Vulnerability · Source |
| CVE-2026-4714 | suse_vex | SUSE CVE CVE-2026-4714 | known affected: 36 recommended: 133 | 2026-07-15T05:40:29+00:00 | Vulnerability · Source |
| CVE-2026-4715 | suse_vex | SUSE CVE CVE-2026-4715 | known affected: 36 recommended: 133 | 2026-07-15T05:40:28+00:00 | Vulnerability · Source |
| CVE-2026-4718 | suse_vex | SUSE CVE CVE-2026-4718 | known affected: 36 recommended: 133 | 2026-07-15T05:40:27+00:00 | Vulnerability · Source |
| CVE-2026-4719 | suse_vex | SUSE CVE CVE-2026-4719 | known affected: 36 recommended: 133 | 2026-07-15T05:40:26+00:00 | Vulnerability · Source |
| CVE-2026-4720 | suse_vex | SUSE CVE CVE-2026-4720 | known affected: 36 recommended: 133 | 2026-07-15T05:40:25+00:00 | Vulnerability · Source |
| CVE-2026-4721 | suse_vex | SUSE CVE CVE-2026-4721 | known affected: 36 recommended: 133 | 2026-07-15T05:40:24+00:00 | Vulnerability · Source |
| CVE-2026-6104 | suse_vex | SUSE CVE CVE-2026-6104 | known affected: 394 known not affected: 1561 recommended: 232 | 2026-07-15T05:39:35+00:00 | Vulnerability · Source |