VEX records
Browse vendor VEX statements available in this Vulnerability-Lookup instance and pivot to the related vulnerability.
293999 VEX records
API response| Vulnerability | Source | Title | Product status | Imported | Links |
|---|---|---|---|---|---|
| CVE-2026-12320 | suse_vex | SUSE CVE CVE-2026-12320 | known affected: 30 recommended: 9 | 2026-07-31T16:54:03+00:00 | Vulnerability · Source |
| CVE-2026-12321 | suse_vex | SUSE CVE CVE-2026-12321 | known affected: 30 recommended: 9 | 2026-07-31T16:54:02+00:00 | Vulnerability · Source |
| CVE-2026-12322 | suse_vex | SUSE CVE CVE-2026-12322 | known affected: 30 recommended: 9 | 2026-07-31T16:54:01+00:00 | Vulnerability · Source |
| CVE-2026-12323 | suse_vex | SUSE CVE CVE-2026-12323 | known affected: 30 recommended: 9 | 2026-07-31T16:54:00+00:00 | Vulnerability · Source |
| CVE-2026-12326 | suse_vex | SUSE CVE CVE-2026-12326 | known affected: 30 recommended: 9 | 2026-07-31T16:53:56+00:00 | Vulnerability · Source |
| CVE-2026-13122 | suse_vex | SUSE CVE CVE-2026-13122 | first fixed: 8 known affected: 9 known not affected: 50 recommended: 39 | 2026-07-31T16:53:42+00:00 | Vulnerability · Source |
| 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-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-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-26958 | suse_vex | SUSE CVE CVE-2026-26958 | known affected: 39 recommended: 131 | 2026-07-31T16:46:03+00:00 | Vulnerability · Source |
| CVE-2026-27138 | suse_vex | SUSE CVE CVE-2026-27138 | known not affected: 177 recommended: 133 | 2026-07-31T16:45:57+00:00 | Vulnerability · Source |
| CVE-2026-27139 | suse_vex | SUSE CVE CVE-2026-27139 | known affected: 12 known not affected: 27 recommended: 261 | 2026-07-31T16:45:55+00:00 | Vulnerability · Source |
| CVE-2026-27142 | suse_vex | SUSE CVE CVE-2026-27142 | known affected: 12 known not affected: 81 recommended: 261 | 2026-07-31T16:45:50+00:00 | Vulnerability · Source |
| CVE-2026-28691 | suse_vex | SUSE CVE CVE-2026-28691 | known affected: 74 recommended: 298 | 2026-07-31T16:45:35+00:00 | Vulnerability · Source |
| CVE-2026-28693 | suse_vex | SUSE CVE CVE-2026-28693 | known affected: 74 known not affected: 16 recommended: 282 | 2026-07-31T16:45:33+00:00 | Vulnerability · Source |
| CVE-2026-31553 | suse_vex | SUSE CVE CVE-2026-31553 | known not affected: 315 | 2026-07-31T16:44:58+00:00 | Vulnerability · Source |
| CVE-2026-33343 | suse_vex | SUSE CVE CVE-2026-33343 | known affected: 2 known not affected: 513 recommended: 6 | 2026-07-31T16:43:56+00:00 | Vulnerability · Source |
| CVE-2026-33413 | suse_vex | SUSE CVE CVE-2026-33413 | known affected: 2 known not affected: 513 recommended: 8 | 2026-07-31T16:43:53+00:00 | Vulnerability · Source |
| CVE-2026-33414 | suse_vex | SUSE CVE CVE-2026-33414 | known not affected: 173 recommended: 8 | 2026-07-31T16:43:51+00:00 | Vulnerability · Source |
| CVE-2026-33540 | suse_vex | SUSE CVE CVE-2026-33540 | known not affected: 67 recommended: 5 | 2026-07-31T16:43:47+00:00 | Vulnerability · Source |
| CVE-2026-33747 | suse_vex | SUSE CVE CVE-2026-33747 | known affected: 151 known not affected: 191 recommended: 81 | 2026-07-31T16:43:41+00:00 | Vulnerability · Source |
| CVE-2026-33748 | suse_vex | SUSE CVE CVE-2026-33748 | known affected: 321 known not affected: 34 recommended: 73 | 2026-07-31T16:43:39+00:00 | Vulnerability · Source |
| CVE-2026-33809 | suse_vex | SUSE CVE CVE-2026-33809 | recommended: 20 | 2026-07-31T16:43:38+00:00 | Vulnerability · Source |
| CVE-2026-34001 | suse_vex | SUSE CVE CVE-2026-34001 | known affected: 424 recommended: 148 | 2026-07-31T16:43:30+00:00 | Vulnerability · Source |
| CVE-2026-40197 | suse_vex | SUSE CVE CVE-2026-40197 | No product status | 2026-07-31T16:42:50+00:00 | Vulnerability · Source |
| CVE-2026-41082 | suse_vex | SUSE CVE CVE-2026-41082 | recommended: 11 | 2026-07-31T16:42:36+00:00 | Vulnerability · Source |
| CVE-2026-41176 | suse_vex | SUSE CVE CVE-2026-41176 | recommended: 15 | 2026-07-31T16:42:34+00:00 | Vulnerability · Source |
| CVE-2026-41874 | suse_vex | SUSE CVE CVE-2026-41874 | No product status | 2026-07-31T16:42:22+00:00 | Vulnerability · Source |
| CVE-2026-42448 | suse_vex | SUSE CVE CVE-2026-42448 | recommended: 6 | 2026-07-31T16:42:12+00:00 | Vulnerability · Source |
| CVE-2026-44660 | suse_vex | SUSE CVE CVE-2026-44660 | known affected: 52 | 2026-07-31T16:40:46+00:00 | Vulnerability · Source |
| CVE-2026-47089 | suse_vex | SUSE CVE CVE-2026-47089 | recommended: 10 | 2026-07-31T16:39:09+00:00 | Vulnerability · Source |
| CVE-2026-50642 | suse_vex | SUSE CVE CVE-2026-50642 | No product status | 2026-07-31T16:38:27+00:00 | Vulnerability · Source |
| CVE-2026-52863 | suse_vex | SUSE CVE CVE-2026-52863 | known not affected: 130 recommended: 6 | 2026-07-31T16:38:17+00:00 | Vulnerability · Source |
| CVE-2026-52949 | suse_vex | SUSE CVE CVE-2026-52949 | known not affected: 295 | 2026-07-31T16:38:13+00:00 | Vulnerability · Source |
| CVE-2026-54761 | suse_vex | SUSE CVE CVE-2026-54761 | No product status | 2026-07-31T16:37:43+00:00 | Vulnerability · Source |
| CVE-2026-54762 | suse_vex | SUSE CVE CVE-2026-54762 | No product status | 2026-07-31T16:37:42+00:00 | Vulnerability · Source |
| CVE-2026-63812 | suse_vex | SUSE CVE CVE-2026-63812 | known not affected: 286 | 2026-07-31T16:36:00+00:00 | Vulnerability · Source |
| CVE-2026-64016 | suse_vex | SUSE CVE CVE-2026-64016 | No product status | 2026-07-31T16:35:55+00:00 | Vulnerability · Source |