VEX records
Browse vendor VEX statements available in this Vulnerability-Lookup instance and pivot to the related vulnerability.
288707 VEX records
API response| Vulnerability | Source | Title | Product status | Imported | Links |
|---|---|---|---|---|---|
| CVE-2026-13698 | suse_vex | SUSE CVE CVE-2026-13698 | first fixed: 8 known affected: 34 known not affected: 25 recommended: 39 | 2026-07-31T16:53:34+00:00 | Vulnerability · Source |
| CVE-2026-13835 | suse_vex | SUSE CVE CVE-2026-13835 | recommended: 6 | 2026-07-31T16:53:25+00:00 | Vulnerability · Source |
| CVE-2026-13845 | suse_vex | SUSE CVE CVE-2026-13845 | recommended: 6 | 2026-07-31T16:53:22+00:00 | Vulnerability · Source |
| CVE-2026-13846 | suse_vex | SUSE CVE CVE-2026-13846 | recommended: 6 | 2026-07-31T16:53:21+00:00 | Vulnerability · Source |
| CVE-2026-13873 | suse_vex | SUSE CVE CVE-2026-13873 | recommended: 6 | 2026-07-31T16:53:15+00:00 | Vulnerability · Source |
| CVE-2026-13877 | suse_vex | SUSE CVE CVE-2026-13877 | recommended: 6 | 2026-07-31T16:53:13+00:00 | Vulnerability · Source |
| CVE-2026-13878 | suse_vex | SUSE CVE CVE-2026-13878 | recommended: 6 | 2026-07-31T16:53:12+00:00 | Vulnerability · Source |
| CVE-2026-13912 | suse_vex | SUSE CVE CVE-2026-13912 | recommended: 6 | 2026-07-31T16:53:05+00:00 | Vulnerability · Source |
| CVE-2026-14001 | suse_vex | SUSE CVE CVE-2026-14001 | recommended: 6 | 2026-07-31T16:52:45+00:00 | Vulnerability · Source |
| CVE-2026-14025 | suse_vex | SUSE CVE CVE-2026-14025 | recommended: 6 | 2026-07-31T16:52:39+00:00 | Vulnerability · Source |
| CVE-2026-14033 | suse_vex | SUSE CVE CVE-2026-14033 | recommended: 6 | 2026-07-31T16:52:37+00:00 | Vulnerability · Source |
| CVE-2026-14060 | suse_vex | SUSE CVE CVE-2026-14060 | recommended: 6 | 2026-07-31T16:52:31+00:00 | Vulnerability · Source |
| CVE-2026-14063 | suse_vex | SUSE CVE CVE-2026-14063 | recommended: 6 | 2026-07-31T16:52:29+00:00 | Vulnerability · Source |
| CVE-2026-14066 | suse_vex | SUSE CVE CVE-2026-14066 | recommended: 6 | 2026-07-31T16:52:27+00:00 | Vulnerability · Source |
| CVE-2026-14089 | suse_vex | SUSE CVE CVE-2026-14089 | recommended: 6 | 2026-07-31T16:52:21+00:00 | Vulnerability · Source |
| CVE-2026-14094 | suse_vex | SUSE CVE CVE-2026-14094 | recommended: 6 | 2026-07-31T16:52:19+00:00 | Vulnerability · Source |
| CVE-2026-14389 | suse_vex | SUSE CVE CVE-2026-14389 | recommended: 6 | 2026-07-31T16:52:07+00:00 | Vulnerability · Source |
| CVE-2026-15370 | suse_vex | SUSE CVE CVE-2026-15370 | known affected: 12 known not affected: 136 recommended: 15 | 2026-07-31T16:51:36+00:00 | Vulnerability · Source |
| CVE-2026-15722 | suse_vex | SUSE CVE CVE-2026-15722 | No product status | 2026-07-31T16:51:31+00:00 | Vulnerability · Source |
| CVE-2026-15764 | suse_vex | SUSE CVE CVE-2026-15764 | recommended: 6 | 2026-07-31T16:51:30+00:00 | Vulnerability · Source |
| CVE-2026-15765 | suse_vex | SUSE CVE CVE-2026-15765 | recommended: 6 | 2026-07-31T16:51:28+00:00 | Vulnerability · Source |
| CVE-2026-15766 | suse_vex | SUSE CVE CVE-2026-15766 | recommended: 6 | 2026-07-31T16:51:27+00:00 | Vulnerability · Source |
| CVE-2026-15767 | suse_vex | SUSE CVE CVE-2026-15767 | recommended: 6 | 2026-07-31T16:51:24+00:00 | Vulnerability · Source |
| CVE-2026-15768 | suse_vex | SUSE CVE CVE-2026-15768 | recommended: 6 | 2026-07-31T16:51:22+00:00 | Vulnerability · Source |
| CVE-2026-15769 | suse_vex | SUSE CVE CVE-2026-15769 | recommended: 6 | 2026-07-31T16:51:20+00:00 | Vulnerability · Source |
| CVE-2026-15770 | suse_vex | SUSE CVE CVE-2026-15770 | recommended: 6 | 2026-07-31T16:51:18+00:00 | Vulnerability · Source |
| CVE-2026-15771 | suse_vex | SUSE CVE CVE-2026-15771 | recommended: 6 | 2026-07-31T16:51:16+00:00 | Vulnerability · Source |
| CVE-2026-15772 | suse_vex | SUSE CVE CVE-2026-15772 | recommended: 6 | 2026-07-31T16:51:14+00:00 | Vulnerability · Source |
| CVE-2026-15773 | suse_vex | SUSE CVE CVE-2026-15773 | recommended: 6 | 2026-07-31T16:51:12+00:00 | Vulnerability · Source |
| CVE-2026-15774 | suse_vex | SUSE CVE CVE-2026-15774 | recommended: 6 | 2026-07-31T16:51:10+00:00 | Vulnerability · Source |
| CVE-2026-15775 | suse_vex | SUSE CVE CVE-2026-15775 | recommended: 6 | 2026-07-31T16:51:08+00:00 | Vulnerability · Source |
| CVE-2026-15776 | suse_vex | SUSE CVE CVE-2026-15776 | recommended: 6 | 2026-07-31T16:51:07+00:00 | Vulnerability · Source |
| CVE-2026-15778 | suse_vex | SUSE CVE CVE-2026-15778 | recommended: 6 | 2026-07-31T16:51:05+00:00 | Vulnerability · Source |
| CVE-2026-15811 | suse_vex | SUSE CVE CVE-2026-15811 | known affected: 33 recommended: 30 | 2026-07-31T16:51:04+00:00 | Vulnerability · Source |
| CVE-2026-15812 | suse_vex | SUSE CVE CVE-2026-15812 | known affected: 33 recommended: 30 | 2026-07-31T16:51:03+00:00 | Vulnerability · Source |
| CVE-2026-15813 | suse_vex | SUSE CVE CVE-2026-15813 | known affected: 33 recommended: 30 | 2026-07-31T16:51:01+00:00 | Vulnerability · Source |
| CVE-2026-64516 | redhat_vex | kernel: drm/amdgpu/vce1: Fix VCE 1 firmware size and offsets | known affected: 184 known not affected: 90 | 2026-07-31T16:50:43+00:00 | Vulnerability · Source |
| CVE-2026-21932 | suse_vex | SUSE CVE CVE-2026-21932 | known affected: 394 known not affected: 88 recommended: 541 | 2026-07-31T16:47:31+00:00 | Vulnerability · Source |
| CVE-2026-21945 | suse_vex | SUSE CVE CVE-2026-21945 | known affected: 394 recommended: 830 | 2026-07-31T16:47:29+00:00 | Vulnerability · Source |
| CVE-2026-22039 | suse_vex | SUSE CVE CVE-2026-22039 | No product status | 2026-07-31T16:47:27+00:00 | Vulnerability · Source |
| CVE-2026-22703 | suse_vex | SUSE CVE CVE-2026-22703 | known affected: 14 known not affected: 3 recommended: 31 | 2026-07-31T16:47:25+00:00 | Vulnerability · Source |
| CVE-2026-22772 | suse_vex | SUSE CVE CVE-2026-22772 | first fixed: 2 known affected: 14 known not affected: 258 recommended: 36 | 2026-07-31T16:47:23+00:00 | Vulnerability · Source |
| CVE-2026-23831 | suse_vex | SUSE CVE CVE-2026-23831 | known affected: 21 known not affected: 281 recommended: 1 | 2026-07-31T16:46:43+00:00 | Vulnerability · Source |
| CVE-2026-23991 | suse_vex | SUSE CVE CVE-2026-23991 | known affected: 11 known not affected: 3 recommended: 31 | 2026-07-31T16:46:39+00:00 | Vulnerability · Source |
| CVE-2026-23992 | suse_vex | SUSE CVE CVE-2026-23992 | known affected: 11 known not affected: 3 recommended: 31 | 2026-07-31T16:46:37+00:00 | Vulnerability · Source |
| CVE-2026-24117 | suse_vex | SUSE CVE CVE-2026-24117 | known affected: 21 known not affected: 281 recommended: 1 | 2026-07-31T16:46:35+00:00 | Vulnerability · Source |
| CVE-2026-24122 | suse_vex | SUSE CVE CVE-2026-24122 | known affected: 15 recommended: 33 | 2026-07-31T16:46:33+00:00 | Vulnerability · Source |
| CVE-2026-24137 | suse_vex | SUSE CVE CVE-2026-24137 | first fixed: 2 known affected: 14 recommended: 48 | 2026-07-31T16:46:31+00:00 | Vulnerability · Source |
| CVE-2026-25934 | suse_vex | SUSE CVE CVE-2026-25934 | known affected: 400 known not affected: 296 recommended: 171 | 2026-07-31T16:46:11+00:00 | Vulnerability · Source |
| CVE-2026-26958 | suse_vex | SUSE CVE CVE-2026-26958 | known affected: 39 recommended: 131 | 2026-07-31T16:46:03+00:00 | Vulnerability · Source |