VEX records
Browse vendor VEX statements available in this Vulnerability-Lookup instance and pivot to the related vulnerability.
290597 VEX records
API response| Vulnerability | Source | Title | Product status | Imported | Links |
|---|---|---|---|---|---|
| CVE-2026-64072 | suse_vex | SUSE CVE CVE-2026-64072 | known not affected: 296 | 2026-08-05T00:34:06+00:00 | Vulnerability · Source |
| CVE-2026-64073 | suse_vex | SUSE CVE CVE-2026-64073 | known affected: 217 known not affected: 79 | 2026-08-05T00:34:04+00:00 | Vulnerability · Source |
| CVE-2026-64074 | suse_vex | SUSE CVE CVE-2026-64074 | known not affected: 296 | 2026-08-05T00:34:03+00:00 | Vulnerability · Source |
| CVE-2026-64075 | suse_vex | SUSE CVE CVE-2026-64075 | known not affected: 296 | 2026-08-05T00:34:01+00:00 | Vulnerability · Source |
| CVE-2026-64076 | suse_vex | SUSE CVE CVE-2026-64076 | known affected: 217 known not affected: 79 | 2026-08-05T00:34:00+00:00 | Vulnerability · Source |
| CVE-2026-64077 | suse_vex | SUSE CVE CVE-2026-64077 | known affected: 129 known not affected: 167 | 2026-08-05T00:33:58+00:00 | Vulnerability · Source |
| CVE-2026-64078 | suse_vex | SUSE CVE CVE-2026-64078 | known affected: 129 known not affected: 167 | 2026-08-05T00:33:56+00:00 | Vulnerability · Source |
| CVE-2026-64079 | suse_vex | SUSE CVE CVE-2026-64079 | known affected: 217 known not affected: 79 | 2026-08-05T00:33:55+00:00 | Vulnerability · Source |
| CVE-2026-64081 | suse_vex | SUSE CVE CVE-2026-64081 | known not affected: 296 | 2026-08-05T00:33:53+00:00 | Vulnerability · Source |
| CVE-2026-64088 | suse_vex | SUSE CVE CVE-2026-64088 | known affected: 222 known not affected: 74 | 2026-08-05T00:33:44+00:00 | Vulnerability · Source |
| CVE-2026-64090 | suse_vex | SUSE CVE CVE-2026-64090 | known affected: 292 known not affected: 4 | 2026-08-05T00:33:42+00:00 | Vulnerability · Source |
| CVE-2026-64092 | suse_vex | SUSE CVE CVE-2026-64092 | known not affected: 296 | 2026-08-05T00:33:41+00:00 | Vulnerability · Source |
| CVE-2026-64095 | suse_vex | SUSE CVE CVE-2026-64095 | known affected: 292 known not affected: 4 | 2026-08-05T00:33:38+00:00 | Vulnerability · Source |
| CVE-2026-64097 | suse_vex | SUSE CVE CVE-2026-64097 | known affected: 191 known not affected: 105 | 2026-08-05T00:33:34+00:00 | Vulnerability · Source |
| CVE-2026-64098 | suse_vex | SUSE CVE CVE-2026-64098 | known affected: 118 known not affected: 178 | 2026-08-05T00:33:33+00:00 | Vulnerability · Source |
| CVE-2026-64099 | suse_vex | SUSE CVE CVE-2026-64099 | known affected: 84 known not affected: 212 | 2026-08-05T00:33:31+00:00 | Vulnerability · Source |
| CVE-2026-64100 | suse_vex | SUSE CVE CVE-2026-64100 | known not affected: 296 | 2026-08-05T00:33:30+00:00 | Vulnerability · Source |
| CVE-2026-64104 | suse_vex | SUSE CVE CVE-2026-64104 | known not affected: 296 | 2026-08-05T00:33:28+00:00 | Vulnerability · Source |
| CVE-2026-64110 | suse_vex | SUSE CVE CVE-2026-64110 | known not affected: 296 | 2026-08-05T00:33:25+00:00 | Vulnerability · Source |
| CVE-2026-64129 | suse_vex | SUSE CVE CVE-2026-64129 | known not affected: 296 | 2026-08-05T00:33:24+00:00 | Vulnerability · Source |
| CVE-2026-64139 | suse_vex | SUSE CVE CVE-2026-64139 | known not affected: 296 | 2026-08-05T00:33:22+00:00 | Vulnerability · Source |
| CVE-2026-64144 | suse_vex | SUSE CVE CVE-2026-64144 | known affected: 159 known not affected: 137 | 2026-08-05T00:33:20+00:00 | Vulnerability · Source |
| CVE-2026-64168 | suse_vex | SUSE CVE CVE-2026-64168 | known affected: 144 known not affected: 152 | 2026-08-05T00:33:17+00:00 | Vulnerability · Source |
| CVE-2026-64169 | suse_vex | SUSE CVE CVE-2026-64169 | known not affected: 296 | 2026-08-05T00:33:16+00:00 | Vulnerability · Source |
| CVE-2026-64518 | suse_vex | SUSE CVE CVE-2026-64518 | known affected: 29 known not affected: 269 | 2026-08-05T00:31:00+00:00 | Vulnerability · Source |
| CVE-2026-64524 | suse_vex | SUSE CVE CVE-2026-64524 | known affected: 40 known not affected: 258 | 2026-08-05T00:30:56+00:00 | Vulnerability · Source |
| CVE-2026-65898 | suse_vex | SUSE CVE CVE-2026-65898 | known affected: 14 | 2026-08-05T00:30:49+00:00 | Vulnerability · Source |
| CVE-2026-65899 | suse_vex | SUSE CVE CVE-2026-65899 | known affected: 14 | 2026-08-05T00:30:48+00:00 | Vulnerability · Source |
| CVE-2026-65900 | suse_vex | SUSE CVE CVE-2026-65900 | known affected: 14 | 2026-08-05T00:30:47+00:00 | Vulnerability · Source |
| CVE-2026-65901 | suse_vex | SUSE CVE CVE-2026-65901 | known affected: 14 | 2026-08-05T00:30:45+00:00 | Vulnerability · Source |
| CVE-2026-65902 | suse_vex | SUSE CVE CVE-2026-65902 | known affected: 14 | 2026-08-05T00:30:44+00:00 | Vulnerability · Source |
| CVE-2026-65903 | suse_vex | SUSE CVE CVE-2026-65903 | known affected: 14 | 2026-08-05T00:30:43+00:00 | Vulnerability · Source |
| CVE-2026-65904 | suse_vex | SUSE CVE CVE-2026-65904 | known affected: 14 | 2026-08-05T00:30:41+00:00 | Vulnerability · Source |
| CVE-2026-65911 | suse_vex | SUSE CVE CVE-2026-65911 | known affected: 14 | 2026-08-05T00:30:40+00:00 | Vulnerability · Source |
| CVE-2026-65912 | suse_vex | SUSE CVE CVE-2026-65912 | known affected: 14 | 2026-08-05T00:30:38+00:00 | Vulnerability · Source |
| CVE-2026-65913 | suse_vex | SUSE CVE CVE-2026-65913 | known affected: 14 | 2026-08-05T00:30:36+00:00 | Vulnerability · Source |
| CVE-2026-65914 | suse_vex | SUSE CVE CVE-2026-65914 | known affected: 14 | 2026-08-05T00:30:34+00:00 | Vulnerability · Source |
| CVE-2026-65981 | suse_vex | SUSE CVE CVE-2026-65981 | No product status | 2026-08-05T00:30:32+00:00 | Vulnerability · Source |
| CVE-2026-66010 | suse_vex | SUSE CVE CVE-2026-66010 | known affected: 14 | 2026-08-05T00:30:30+00:00 | Vulnerability · Source |
| CVE-2026-66063 | suse_vex | SUSE CVE CVE-2026-66063 | No product status | 2026-08-05T00:30:20+00:00 | Vulnerability · Source |
| CVE-2026-66064 | suse_vex | SUSE CVE CVE-2026-66064 | No product status | 2026-08-05T00:30:19+00:00 | Vulnerability · Source |
| CVE-2026-66759 | suse_vex | SUSE CVE CVE-2026-66759 | known not affected: 26 recommended: 18 | 2026-08-05T00:30:17+00:00 | Vulnerability · Source |
| CVE-2026-67295 | suse_vex | SUSE CVE CVE-2026-67295 | known affected: 140 | 2026-08-05T00:30:14+00:00 | Vulnerability · Source |
| CVE-2026-67300 | suse_vex | SUSE CVE CVE-2026-67300 | known affected: 140 | 2026-08-05T00:30:10+00:00 | Vulnerability · Source |
| CVE-2026-67301 | suse_vex | SUSE CVE CVE-2026-67301 | known affected: 140 | 2026-08-05T00:30:09+00:00 | Vulnerability · Source |
| CVE-2026-67302 | suse_vex | SUSE CVE CVE-2026-67302 | known affected: 49 known not affected: 91 | 2026-08-05T00:30:08+00:00 | Vulnerability · Source |
| CVE-2026-67303 | suse_vex | SUSE CVE CVE-2026-67303 | known affected: 93 known not affected: 47 | 2026-08-05T00:30:07+00:00 | Vulnerability · Source |
| CVE-2026-67304 | suse_vex | SUSE CVE CVE-2026-67304 | known affected: 49 known not affected: 91 | 2026-08-05T00:30:05+00:00 | Vulnerability · Source |
| CVE-2026-67306 | suse_vex | SUSE CVE CVE-2026-67306 | known affected: 49 known not affected: 91 | 2026-08-05T00:30:04+00:00 | Vulnerability · Source |
| CVE-2026-67309 | suse_vex | SUSE CVE CVE-2026-67309 | No product status | 2026-08-05T00:30:03+00:00 | Vulnerability · Source |