VEX records
Browse vendor VEX statements available in this Vulnerability-Lookup instance and pivot to the related vulnerability.
288585 VEX records
API response| Vulnerability | Source | Title | Product status | Imported | Links |
|---|---|---|---|---|---|
| CVE-2026-6529 | suse_vex | SUSE CVE CVE-2026-6529 | known affected: 104 known not affected: 28 recommended: 90 | 2026-07-31T16:55:40+00:00 | Vulnerability · Source |
| CVE-2026-6530 | suse_vex | SUSE CVE CVE-2026-6530 | known affected: 132 recommended: 90 | 2026-07-31T16:55:39+00:00 | Vulnerability · Source |
| CVE-2026-6531 | suse_vex | SUSE CVE CVE-2026-6531 | known affected: 44 known not affected: 153 recommended: 24 | 2026-07-31T16:55:38+00:00 | Vulnerability · Source |
| CVE-2026-6532 | suse_vex | SUSE CVE CVE-2026-6532 | known affected: 130 recommended: 103 | 2026-07-31T16:55:37+00:00 | Vulnerability · Source |
| CVE-2026-6533 | suse_vex | SUSE CVE CVE-2026-6533 | known affected: 169 known not affected: 28 recommended: 24 | 2026-07-31T16:55:35+00:00 | Vulnerability · Source |
| CVE-2026-6534 | suse_vex | SUSE CVE CVE-2026-6534 | known affected: 104 known not affected: 28 recommended: 90 | 2026-07-31T16:55:34+00:00 | Vulnerability · Source |
| CVE-2026-6535 | suse_vex | SUSE CVE CVE-2026-6535 | known affected: 130 recommended: 103 | 2026-07-31T16:55:33+00:00 | Vulnerability · Source |
| CVE-2026-6537 | suse_vex | SUSE CVE CVE-2026-6537 | known affected: 68 known not affected: 129 recommended: 24 | 2026-07-31T16:55:30+00:00 | Vulnerability · Source |
| CVE-2026-6538 | suse_vex | SUSE CVE CVE-2026-6538 | known affected: 130 recommended: 103 | 2026-07-31T16:55:28+00:00 | Vulnerability · Source |
| CVE-2026-6868 | suse_vex | SUSE CVE CVE-2026-6868 | known affected: 104 known not affected: 28 recommended: 90 | 2026-07-31T16:55:25+00:00 | Vulnerability · Source |
| CVE-2026-6869 | suse_vex | SUSE CVE CVE-2026-6869 | known affected: 104 known not affected: 28 recommended: 90 | 2026-07-31T16:55:23+00:00 | Vulnerability · Source |
| CVE-2026-6870 | suse_vex | SUSE CVE CVE-2026-6870 | known affected: 130 recommended: 85 | 2026-07-31T16:55:22+00:00 | Vulnerability · Source |
| CVE-2026-10294 | suse_vex | SUSE CVE CVE-2026-10294 | first fixed: 7 known affected: 161 recommended: 98 | 2026-07-31T16:55:03+00:00 | Vulnerability · Source |
| CVE-2026-11605 | suse_vex | SUSE CVE CVE-2026-11605 | first fixed: 16 known not affected: 192 recommended: 31 | 2026-07-31T16:54:55+00:00 | Vulnerability · Source |
| CVE-2026-11770 | suse_vex | SUSE CVE CVE-2026-11770 | No product status | 2026-07-31T16:54:51+00:00 | Vulnerability · Source |
| CVE-2026-12293 | suse_vex | SUSE CVE CVE-2026-12293 | known affected: 30 recommended: 9 | 2026-07-31T16:54:41+00:00 | Vulnerability · Source |
| CVE-2026-12300 | suse_vex | SUSE CVE CVE-2026-12300 | known affected: 30 recommended: 9 | 2026-07-31T16:54:31+00:00 | Vulnerability · Source |
| CVE-2026-12301 | suse_vex | SUSE CVE CVE-2026-12301 | known affected: 30 recommended: 9 | 2026-07-31T16:54:29+00:00 | Vulnerability · Source |
| CVE-2026-12303 | suse_vex | SUSE CVE CVE-2026-12303 | known affected: 30 recommended: 9 | 2026-07-31T16:54:27+00:00 | Vulnerability · Source |
| CVE-2026-12316 | suse_vex | SUSE CVE CVE-2026-12316 | known affected: 30 recommended: 9 | 2026-07-31T16:54:08+00:00 | Vulnerability · Source |
| CVE-2026-12317 | suse_vex | SUSE CVE CVE-2026-12317 | known affected: 30 recommended: 9 | 2026-07-31T16:54:07+00:00 | Vulnerability · Source |
| CVE-2026-12318 | suse_vex | SUSE CVE CVE-2026-12318 | known affected: 30 recommended: 9 | 2026-07-31T16:54:06+00:00 | Vulnerability · Source |
| CVE-2026-12319 | suse_vex | SUSE CVE CVE-2026-12319 | known affected: 30 recommended: 9 | 2026-07-31T16:54:05+00:00 | Vulnerability · Source |
| 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-13221 | suse_vex | SUSE CVE CVE-2026-13221 | known affected: 9 known not affected: 127 recommended: 11 | 2026-07-31T16:53:40+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-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 |