VEX records
Browse vendor VEX statements available in this Vulnerability-Lookup instance and pivot to the related vulnerability.
283120 VEX records
API response| Vulnerability | Source | Title | Product status | Imported | Links |
|---|---|---|---|---|---|
| CVE-2026-55831 | suse_vex | SUSE CVE CVE-2026-55831 | known affected: 3 known not affected: 42 | 2026-07-21T13:06:16+00:00 | Vulnerability · Source |
| CVE-2026-55833 | suse_vex | SUSE CVE CVE-2026-55833 | known affected: 3 known not affected: 42 | 2026-07-21T13:06:15+00:00 | Vulnerability · Source |
| CVE-2026-56109 | suse_vex | SUSE CVE CVE-2026-56109 | first fixed: 26 known affected: 539 recommended: 26 | 2026-07-21T13:06:13+00:00 | Vulnerability · Source |
| CVE-2026-56375 | suse_vex | SUSE CVE CVE-2026-56375 | No product status | 2026-07-21T13:06:12+00:00 | Vulnerability · Source |
| CVE-2026-56741 | suse_vex | SUSE CVE CVE-2026-56741 | known not affected: 35 | 2026-07-21T13:06:09+00:00 | Vulnerability · Source |
| CVE-2026-58469 | suse_vex | SUSE CVE CVE-2026-58469 | known affected: 32 known not affected: 4 recommended: 2 | 2026-07-21T13:06:02+00:00 | Vulnerability · Source |
| CVE-2026-58470 | suse_vex | SUSE CVE CVE-2026-58470 | known affected: 36 recommended: 2 | 2026-07-21T13:06:01+00:00 | Vulnerability · Source |
| CVE-2026-58471 | suse_vex | SUSE CVE CVE-2026-58471 | known affected: 32 known not affected: 4 recommended: 2 | 2026-07-21T13:06:00+00:00 | Vulnerability · Source |
| CVE-2026-58472 | suse_vex | SUSE CVE CVE-2026-58472 | known affected: 36 recommended: 2 | 2026-07-21T13:05:58+00:00 | Vulnerability · Source |
| CVE-2026-59884 | suse_vex | SUSE CVE CVE-2026-59884 | known affected: 99 | 2026-07-21T13:05:51+00:00 | Vulnerability · Source |
| CVE-2026-59885 | suse_vex | SUSE CVE CVE-2026-59885 | known affected: 99 | 2026-07-21T13:05:50+00:00 | Vulnerability · Source |
| CVE-2026-59886 | suse_vex | SUSE CVE CVE-2026-59886 | first fixed: 22 known affected: 100 | 2026-07-21T13:05:48+00:00 | Vulnerability · Source |
| CVE-2026-59888 | suse_vex | SUSE CVE CVE-2026-59888 | known affected: 27 | 2026-07-21T13:05:47+00:00 | Vulnerability · Source |
| CVE-2026-59889 | suse_vex | SUSE CVE CVE-2026-59889 | first fixed: 24 known affected: 27 recommended: 2 | 2026-07-21T13:05:46+00:00 | Vulnerability · Source |
| CVE-2026-60081 | suse_vex | SUSE CVE CVE-2026-60081 | first fixed: 7 known affected: 31 | 2026-07-21T13:05:44+00:00 | Vulnerability · Source |
| CVE-2026-60082 | suse_vex | SUSE CVE CVE-2026-60082 | first fixed: 22 known affected: 31 | 2026-07-21T13:05:43+00:00 | Vulnerability · Source |
| CVE-2026-61464 | suse_vex | SUSE CVE CVE-2026-61464 | No product status | 2026-07-21T13:05:41+00:00 | Vulnerability · Source |
| CVE-2026-61859 | suse_vex | SUSE CVE CVE-2026-61859 | No product status | 2026-07-21T13:05:40+00:00 | Vulnerability · Source |
| CVE-2026-61860 | suse_vex | SUSE CVE CVE-2026-61860 | No product status | 2026-07-21T13:05:39+00:00 | Vulnerability · Source |
| CVE-2026-61862 | suse_vex | SUSE CVE CVE-2026-61862 | No product status | 2026-07-21T13:05:37+00:00 | Vulnerability · Source |
| CVE-2026-61863 | suse_vex | SUSE CVE CVE-2026-61863 | No product status | 2026-07-21T13:05:36+00:00 | Vulnerability · Source |
| CVE-2026-61864 | suse_vex | SUSE CVE CVE-2026-61864 | No product status | 2026-07-21T13:05:35+00:00 | Vulnerability · Source |
| CVE-2026-61865 | suse_vex | SUSE CVE CVE-2026-61865 | No product status | 2026-07-21T13:05:34+00:00 | Vulnerability · Source |
| CVE-2026-61866 | suse_vex | SUSE CVE CVE-2026-61866 | known affected: 240 known not affected: 36 | 2026-07-21T13:05:32+00:00 | Vulnerability · Source |
| CVE-2026-61868 | suse_vex | SUSE CVE CVE-2026-61868 | known affected: 8 known not affected: 268 | 2026-07-21T13:05:31+00:00 | Vulnerability · Source |
| CVE-2026-62643 | suse_vex | SUSE CVE CVE-2026-62643 | No product status | 2026-07-21T13:05:29+00:00 | Vulnerability · Source |
| CVE-2026-62644 | suse_vex | SUSE CVE CVE-2026-62644 | No product status | 2026-07-21T13:05:28+00:00 | Vulnerability · Source |
| CVE-2026-63090 | suse_vex | SUSE CVE CVE-2026-63090 | known affected: 63 | 2026-07-21T13:05:24+00:00 | Vulnerability · Source |
| CVE-2026-63091 | suse_vex | SUSE CVE CVE-2026-63091 | known affected: 63 | 2026-07-21T13:05:22+00:00 | Vulnerability · Source |
| CVE-2026-63793 | suse_vex | SUSE CVE CVE-2026-63793 | No product status | 2026-07-21T13:05:21+00:00 | Vulnerability · Source |
| CVE-2026-63794 | suse_vex | SUSE CVE CVE-2026-63794 | No product status | 2026-07-21T13:05:20+00:00 | Vulnerability · Source |
| CVE-2026-63795 | suse_vex | SUSE CVE CVE-2026-63795 | No product status | 2026-07-21T13:05:19+00:00 | Vulnerability · Source |
| CVE-2026-63796 | suse_vex | SUSE CVE CVE-2026-63796 | No product status | 2026-07-21T13:05:18+00:00 | Vulnerability · Source |
| CVE-2026-63800 | suse_vex | SUSE CVE CVE-2026-63800 | No product status | 2026-07-21T13:05:12+00:00 | Vulnerability · Source |
| CVE-2026-63801 | suse_vex | SUSE CVE CVE-2026-63801 | No product status | 2026-07-21T13:05:11+00:00 | Vulnerability · Source |
| CVE-2026-63802 | suse_vex | SUSE CVE CVE-2026-63802 | No product status | 2026-07-21T13:05:09+00:00 | Vulnerability · Source |
| CVE-2026-63803 | suse_vex | SUSE CVE CVE-2026-63803 | No product status | 2026-07-21T13:05:08+00:00 | Vulnerability · Source |
| CVE-2026-63804 | suse_vex | SUSE CVE CVE-2026-63804 | No product status | 2026-07-21T13:05:07+00:00 | Vulnerability · Source |
| CVE-2026-63805 | suse_vex | SUSE CVE CVE-2026-63805 | No product status | 2026-07-21T13:05:05+00:00 | Vulnerability · Source |
| CVE-2026-63806 | suse_vex | SUSE CVE CVE-2026-63806 | No product status | 2026-07-21T13:05:04+00:00 | Vulnerability · Source |
| CVE-2026-63807 | suse_vex | SUSE CVE CVE-2026-63807 | No product status | 2026-07-21T13:05:03+00:00 | Vulnerability · Source |
| CVE-2026-63808 | suse_vex | SUSE CVE CVE-2026-63808 | No product status | 2026-07-21T13:05:02+00:00 | Vulnerability · Source |
| CVE-2026-63809 | suse_vex | SUSE CVE CVE-2026-63809 | No product status | 2026-07-21T13:05:00+00:00 | Vulnerability · Source |
| CVE-2026-63810 | suse_vex | SUSE CVE CVE-2026-63810 | No product status | 2026-07-21T13:04:59+00:00 | Vulnerability · Source |
| CVE-2026-63812 | suse_vex | SUSE CVE CVE-2026-63812 | No product status | 2026-07-21T13:04:58+00:00 | Vulnerability · Source |
| CVE-2026-63813 | suse_vex | SUSE CVE CVE-2026-63813 | No product status | 2026-07-21T13:04:56+00:00 | Vulnerability · Source |
| CVE-2026-63815 | suse_vex | SUSE CVE CVE-2026-63815 | No product status | 2026-07-21T13:04:54+00:00 | Vulnerability · Source |
| CVE-2026-63816 | suse_vex | SUSE CVE CVE-2026-63816 | No product status | 2026-07-21T13:04:52+00:00 | Vulnerability · Source |
| CVE-2026-63817 | suse_vex | SUSE CVE CVE-2026-63817 | No product status | 2026-07-21T13:04:51+00:00 | Vulnerability · Source |
| CVE-2026-63818 | suse_vex | SUSE CVE CVE-2026-63818 | No product status | 2026-07-21T13:04:50+00:00 | Vulnerability · Source |