VEX records
Browse vendor VEX statements available in this Vulnerability-Lookup instance and pivot to the related vulnerability.
291709 VEX records
API response| Vulnerability | Source | Title | Product status | Imported | Links |
|---|---|---|---|---|---|
| CVE-2026-63799 | suse_vex | SUSE CVE CVE-2026-63799 | known not affected: 286 recommended: 4 | 2026-08-06T01:11:36+00:00 | Vulnerability · Source |
| CVE-2026-63801 | suse_vex | SUSE CVE CVE-2026-63801 | known affected: 217 known not affected: 79 recommended: 4 | 2026-08-06T01:11:35+00:00 | Vulnerability · Source |
| CVE-2026-63813 | suse_vex | SUSE CVE CVE-2026-63813 | known not affected: 286 recommended: 4 | 2026-08-06T01:11:28+00:00 | Vulnerability · Source |
| CVE-2026-63819 | suse_vex | SUSE CVE CVE-2026-63819 | known affected: 292 known not affected: 4 recommended: 4 | 2026-08-06T01:11:26+00:00 | Vulnerability · Source |
| CVE-2026-63825 | suse_vex | SUSE CVE CVE-2026-63825 | known affected: 296 recommended: 4 | 2026-08-06T01:11:22+00:00 | Vulnerability · Source |
| CVE-2026-63830 | suse_vex | SUSE CVE CVE-2026-63830 | known affected: 290 known not affected: 6 recommended: 4 | 2026-08-06T01:11:18+00:00 | Vulnerability · Source |
| CVE-2026-63832 | suse_vex | SUSE CVE CVE-2026-63832 | known affected: 29 known not affected: 267 recommended: 4 | 2026-08-06T01:11:17+00:00 | Vulnerability · Source |
| CVE-2026-64000 | suse_vex | SUSE CVE CVE-2026-64000 | known affected: 129 known not affected: 167 | 2026-08-06T01:10:35+00:00 | Vulnerability · Source |
| CVE-2026-64001 | suse_vex | SUSE CVE CVE-2026-64001 | known affected: 210 known not affected: 88 | 2026-08-06T01:10:34+00:00 | Vulnerability · Source |
| CVE-2026-64003 | suse_vex | SUSE CVE CVE-2026-64003 | known affected: 298 | 2026-08-06T01:10:32+00:00 | Vulnerability · Source |
| CVE-2026-64004 | suse_vex | SUSE CVE CVE-2026-64004 | known affected: 298 | 2026-08-06T01:10:31+00:00 | Vulnerability · Source |
| CVE-2026-64005 | suse_vex | SUSE CVE CVE-2026-64005 | known affected: 298 | 2026-08-06T01:10:29+00:00 | Vulnerability · Source |
| CVE-2026-64006 | suse_vex | SUSE CVE CVE-2026-64006 | known affected: 235 known not affected: 63 | 2026-08-06T01:10:28+00:00 | Vulnerability · Source |
| CVE-2026-64008 | suse_vex | SUSE CVE CVE-2026-64008 | known not affected: 298 | 2026-08-06T01:10:27+00:00 | Vulnerability · Source |
| CVE-2026-64009 | suse_vex | SUSE CVE CVE-2026-64009 | known affected: 245 known not affected: 53 | 2026-08-06T01:10:25+00:00 | Vulnerability · Source |
| CVE-2026-64010 | suse_vex | SUSE CVE CVE-2026-64010 | known affected: 193 known not affected: 105 | 2026-08-06T01:10:24+00:00 | Vulnerability · Source |
| CVE-2026-64011 | suse_vex | SUSE CVE CVE-2026-64011 | known affected: 209 known not affected: 89 | 2026-08-06T01:10:23+00:00 | Vulnerability · Source |
| CVE-2026-64012 | suse_vex | SUSE CVE CVE-2026-64012 | known affected: 296 | 2026-08-06T01:10:22+00:00 | Vulnerability · Source |
| CVE-2026-64014 | suse_vex | SUSE CVE CVE-2026-64014 | known affected: 197 known not affected: 99 | 2026-08-06T01:10:20+00:00 | Vulnerability · Source |
| CVE-2026-64015 | suse_vex | SUSE CVE CVE-2026-64015 | known affected: 193 known not affected: 103 | 2026-08-06T01:10:19+00:00 | Vulnerability · Source |
| CVE-2026-64017 | suse_vex | SUSE CVE CVE-2026-64017 | known affected: 177 known not affected: 119 recommended: 41 | 2026-08-06T01:10:18+00:00 | Vulnerability · Source |
| CVE-2026-64026 | suse_vex | SUSE CVE CVE-2026-64026 | known affected: 243 known not affected: 53 | 2026-08-06T01:10:14+00:00 | Vulnerability · Source |
| CVE-2026-64027 | suse_vex | SUSE CVE CVE-2026-64027 | known affected: 29 known not affected: 267 | 2026-08-06T01:10:12+00:00 | Vulnerability · Source |
| CVE-2026-64029 | suse_vex | SUSE CVE CVE-2026-64029 | known affected: 45 known not affected: 251 | 2026-08-06T01:10:10+00:00 | Vulnerability · Source |
| CVE-2026-64030 | suse_vex | SUSE CVE CVE-2026-64030 | known not affected: 296 | 2026-08-06T01:10:08+00:00 | Vulnerability · Source |
| CVE-2026-64032 | suse_vex | SUSE CVE CVE-2026-64032 | known not affected: 296 | 2026-08-06T01:10:07+00:00 | Vulnerability · Source |
| CVE-2026-64035 | suse_vex | SUSE CVE CVE-2026-64035 | known not affected: 298 | 2026-08-06T01:10:05+00:00 | Vulnerability · Source |
| CVE-2026-64037 | suse_vex | SUSE CVE CVE-2026-64037 | known not affected: 298 | 2026-08-06T01:10:03+00:00 | Vulnerability · Source |
| CVE-2026-64038 | suse_vex | SUSE CVE CVE-2026-64038 | known affected: 129 known not affected: 167 | 2026-08-06T01:10:01+00:00 | Vulnerability · Source |
| CVE-2026-64040 | suse_vex | SUSE CVE CVE-2026-64040 | known not affected: 296 | 2026-08-06T01:09:59+00:00 | Vulnerability · Source |
| CVE-2026-64041 | suse_vex | SUSE CVE CVE-2026-64041 | known not affected: 296 | 2026-08-06T01:09:57+00:00 | Vulnerability · Source |
| CVE-2026-64047 | suse_vex | SUSE CVE CVE-2026-64047 | known affected: 245 known not affected: 53 | 2026-08-06T01:09:54+00:00 | Vulnerability · Source |
| CVE-2026-64101 | suse_vex | SUSE CVE CVE-2026-64101 | known not affected: 296 | 2026-08-06T01:09:43+00:00 | Vulnerability · Source |
| CVE-2026-64103 | suse_vex | SUSE CVE CVE-2026-64103 | known affected: 296 | 2026-08-06T01:09:42+00:00 | Vulnerability · Source |
| CVE-2026-64105 | suse_vex | SUSE CVE CVE-2026-64105 | known not affected: 296 | 2026-08-06T01:09:40+00:00 | Vulnerability · Source |
| CVE-2026-64108 | suse_vex | SUSE CVE CVE-2026-64108 | known not affected: 296 | 2026-08-06T01:09:37+00:00 | Vulnerability · Source |
| CVE-2026-64109 | suse_vex | SUSE CVE CVE-2026-64109 | known affected: 292 known not affected: 4 | 2026-08-06T01:09:36+00:00 | Vulnerability · Source |
| CVE-2026-64112 | suse_vex | SUSE CVE CVE-2026-64112 | known affected: 290 known not affected: 6 | 2026-08-06T01:09:33+00:00 | Vulnerability · Source |
| CVE-2026-64113 | suse_vex | SUSE CVE CVE-2026-64113 | known affected: 292 known not affected: 4 | 2026-08-06T01:09:32+00:00 | Vulnerability · Source |
| CVE-2026-64115 | suse_vex | SUSE CVE CVE-2026-64115 | known affected: 292 known not affected: 4 | 2026-08-06T01:09:30+00:00 | Vulnerability · Source |
| CVE-2026-64116 | suse_vex | SUSE CVE CVE-2026-64116 | known affected: 129 known not affected: 167 | 2026-08-06T01:09:29+00:00 | Vulnerability · Source |
| CVE-2026-64117 | suse_vex | SUSE CVE CVE-2026-64117 | known affected: 129 known not affected: 167 | 2026-08-06T01:09:28+00:00 | Vulnerability · Source |
| CVE-2026-64118 | suse_vex | SUSE CVE CVE-2026-64118 | known affected: 292 known not affected: 4 | 2026-08-06T01:09:27+00:00 | Vulnerability · Source |
| CVE-2026-64119 | suse_vex | SUSE CVE CVE-2026-64119 | known affected: 29 known not affected: 267 | 2026-08-06T01:09:25+00:00 | Vulnerability · Source |
| CVE-2026-64124 | suse_vex | SUSE CVE CVE-2026-64124 | known not affected: 296 | 2026-08-06T01:09:20+00:00 | Vulnerability · Source |
| CVE-2026-64126 | suse_vex | SUSE CVE CVE-2026-64126 | known affected: 118 known not affected: 178 | 2026-08-06T01:09:18+00:00 | Vulnerability · Source |
| CVE-2026-64145 | suse_vex | SUSE CVE CVE-2026-64145 | known not affected: 296 | 2026-08-06T01:09:15+00:00 | Vulnerability · Source |
| CVE-2026-64155 | suse_vex | SUSE CVE CVE-2026-64155 | known affected: 118 known not affected: 178 | 2026-08-06T01:09:11+00:00 | Vulnerability · Source |
| CVE-2026-64161 | suse_vex | SUSE CVE CVE-2026-64161 | known not affected: 296 | 2026-08-06T01:09:10+00:00 | Vulnerability · Source |
| CVE-2026-64166 | suse_vex | SUSE CVE CVE-2026-64166 | known affected: 118 known not affected: 178 | 2026-08-06T01:09:08+00:00 | Vulnerability · Source |