VEX records
Browse vendor VEX statements available in this Vulnerability-Lookup instance and pivot to the related vulnerability.
291890 VEX records
API response| Vulnerability | Source | Title | Product status | Imported | Links |
|---|---|---|---|---|---|
| CVE-2026-57437 | suse_vex | SUSE CVE CVE-2026-57437 | known affected: 103 known not affected: 5 | 2026-08-11T23:52:21+00:00 | Vulnerability · Source |
| CVE-2026-57438 | suse_vex | SUSE CVE CVE-2026-57438 | known affected: 103 known not affected: 5 | 2026-08-11T23:52:19+00:00 | Vulnerability · Source |
| CVE-2026-57965 | suse_vex | SUSE CVE CVE-2026-57965 | first fixed: 2 known affected: 8 known not affected: 3 recommended: 23 | 2026-08-11T23:52:16+00:00 | Vulnerability · Source |
| CVE-2026-57966 | suse_vex | SUSE CVE CVE-2026-57966 | first fixed: 2 known affected: 8 known not affected: 3 recommended: 23 | 2026-08-11T23:52:14+00:00 | Vulnerability · Source |
| CVE-2026-59881 | suse_vex | SUSE CVE CVE-2026-59881 | first fixed: 33 known affected: 66 recommended: 2 | 2026-08-11T23:51:08+00:00 | Vulnerability · Source |
| CVE-2026-63872 | suse_vex | SUSE CVE CVE-2026-63872 | known affected: 292 known not affected: 6 | 2026-08-11T23:50:34+00:00 | Vulnerability · Source |
| CVE-2026-64165 | suse_vex | SUSE CVE CVE-2026-64165 | known not affected: 298 | 2026-08-11T23:49:42+00:00 | Vulnerability · Source |
| CVE-2026-67215 | suse_vex | SUSE CVE CVE-2026-67215 | known affected: 17 | 2026-08-11T23:49:02+00:00 | Vulnerability · Source |
| CVE-2026-67216 | suse_vex | SUSE CVE CVE-2026-67216 | known affected: 17 | 2026-08-11T23:49:00+00:00 | Vulnerability · Source |
| CVE-2026-67217 | suse_vex | SUSE CVE CVE-2026-67217 | known affected: 17 | 2026-08-11T23:48:58+00:00 | Vulnerability · Source |
| CVE-2026-68083 | suse_vex | SUSE CVE CVE-2026-68083 | known affected: 80 known not affected: 88 | 2026-08-11T23:48:56+00:00 | Vulnerability · Source |
| CVE-2026-68084 | suse_vex | SUSE CVE CVE-2026-68084 | known affected: 117 known not affected: 179 | 2026-08-11T23:48:55+00:00 | Vulnerability · Source |
| CVE-2026-68085 | suse_vex | SUSE CVE CVE-2026-68085 | known affected: 209 known not affected: 87 | 2026-08-11T23:48:53+00:00 | Vulnerability · Source |
| CVE-2026-68086 | suse_vex | SUSE CVE CVE-2026-68086 | known affected: 80 known not affected: 216 | 2026-08-11T23:48:52+00:00 | Vulnerability · Source |
| CVE-2026-68088 | suse_vex | SUSE CVE CVE-2026-68088 | known affected: 193 known not affected: 103 | 2026-08-11T23:48:48+00:00 | Vulnerability · Source |
| CVE-2026-68089 | suse_vex | SUSE CVE CVE-2026-68089 | known not affected: 296 | 2026-08-11T23:48:46+00:00 | Vulnerability · Source |
| CVE-2026-68090 | suse_vex | SUSE CVE CVE-2026-68090 | known affected: 29 known not affected: 267 | 2026-08-11T23:48:44+00:00 | Vulnerability · Source |
| CVE-2026-68091 | suse_vex | SUSE CVE CVE-2026-68091 | known affected: 191 known not affected: 105 | 2026-08-11T23:48:42+00:00 | Vulnerability · Source |
| CVE-2026-68092 | suse_vex | SUSE CVE CVE-2026-68092 | known affected: 296 | 2026-08-11T23:48:40+00:00 | Vulnerability · Source |
| CVE-2026-68093 | suse_vex | SUSE CVE CVE-2026-68093 | known affected: 12 known not affected: 284 | 2026-08-11T23:48:38+00:00 | Vulnerability · Source |
| CVE-2026-68094 | suse_vex | SUSE CVE CVE-2026-68094 | known not affected: 296 | 2026-08-11T23:48:36+00:00 | Vulnerability · Source |
| CVE-2026-68095 | suse_vex | SUSE CVE CVE-2026-68095 | known not affected: 296 | 2026-08-11T23:48:34+00:00 | Vulnerability · Source |
| CVE-2026-68096 | suse_vex | SUSE CVE CVE-2026-68096 | known affected: 243 known not affected: 53 | 2026-08-11T23:48:32+00:00 | Vulnerability · Source |
| CVE-2026-68097 | suse_vex | SUSE CVE CVE-2026-68097 | known affected: 112 known not affected: 184 | 2026-08-11T23:48:30+00:00 | Vulnerability · Source |
| CVE-2026-68098 | suse_vex | SUSE CVE CVE-2026-68098 | known affected: 113 known not affected: 183 | 2026-08-11T23:48:28+00:00 | Vulnerability · Source |
| CVE-2026-68099 | suse_vex | SUSE CVE CVE-2026-68099 | known affected: 99 known not affected: 197 | 2026-08-11T23:48:26+00:00 | Vulnerability · Source |
| CVE-2026-68310 | suse_vex | SUSE CVE CVE-2026-68310 | known affected: 78 known not affected: 218 | 2026-08-11T23:48:24+00:00 | Vulnerability · Source |
| CVE-2026-68311 | suse_vex | SUSE CVE CVE-2026-68311 | known not affected: 296 | 2026-08-11T23:48:22+00:00 | Vulnerability · Source |
| CVE-2026-68312 | suse_vex | SUSE CVE CVE-2026-68312 | known affected: 217 known not affected: 79 | 2026-08-11T23:48:20+00:00 | Vulnerability · Source |
| CVE-2026-68313 | suse_vex | SUSE CVE CVE-2026-68313 | known affected: 292 known not affected: 4 | 2026-08-11T23:48:18+00:00 | Vulnerability · Source |
| CVE-2026-68314 | suse_vex | SUSE CVE CVE-2026-68314 | known affected: 29 known not affected: 267 | 2026-08-11T23:48:16+00:00 | Vulnerability · Source |
| CVE-2026-68315 | suse_vex | SUSE CVE CVE-2026-68315 | known affected: 290 known not affected: 6 | 2026-08-11T23:48:14+00:00 | Vulnerability · Source |
| CVE-2026-68316 | suse_vex | SUSE CVE CVE-2026-68316 | known not affected: 296 | 2026-08-11T23:48:11+00:00 | Vulnerability · Source |
| CVE-2026-68317 | suse_vex | SUSE CVE CVE-2026-68317 | known not affected: 296 | 2026-08-11T23:48:09+00:00 | Vulnerability · Source |
| CVE-2026-68318 | suse_vex | SUSE CVE CVE-2026-68318 | known affected: 129 known not affected: 167 | 2026-08-11T23:48:06+00:00 | Vulnerability · Source |
| CVE-2026-68319 | suse_vex | SUSE CVE CVE-2026-68319 | known affected: 29 known not affected: 267 | 2026-08-11T23:48:04+00:00 | Vulnerability · Source |
| CVE-2026-68320 | suse_vex | SUSE CVE CVE-2026-68320 | known affected: 296 | 2026-08-11T23:48:01+00:00 | Vulnerability · Source |
| CVE-2026-68321 | suse_vex | SUSE CVE CVE-2026-68321 | known affected: 29 known not affected: 267 | 2026-08-11T23:47:59+00:00 | Vulnerability · Source |
| CVE-2026-68322 | suse_vex | SUSE CVE CVE-2026-68322 | known affected: 243 known not affected: 53 | 2026-08-11T23:47:56+00:00 | Vulnerability · Source |
| CVE-2026-68323 | suse_vex | SUSE CVE CVE-2026-68323 | known affected: 290 known not affected: 6 | 2026-08-11T23:47:54+00:00 | Vulnerability · Source |
| CVE-2026-68324 | suse_vex | SUSE CVE CVE-2026-68324 | known affected: 217 known not affected: 79 | 2026-08-11T23:47:51+00:00 | Vulnerability · Source |
| CVE-2026-68325 | suse_vex | SUSE CVE CVE-2026-68325 | known affected: 292 known not affected: 4 | 2026-08-11T23:47:49+00:00 | Vulnerability · Source |
| CVE-2026-68326 | suse_vex | SUSE CVE CVE-2026-68326 | known affected: 193 known not affected: 103 | 2026-08-11T23:47:46+00:00 | Vulnerability · Source |
| CVE-2026-68328 | suse_vex | SUSE CVE CVE-2026-68328 | known affected: 290 known not affected: 6 | 2026-08-11T23:47:44+00:00 | Vulnerability · Source |
| CVE-2026-68329 | suse_vex | SUSE CVE CVE-2026-68329 | known affected: 296 | 2026-08-11T23:47:41+00:00 | Vulnerability · Source |
| CVE-2026-68330 | suse_vex | SUSE CVE CVE-2026-68330 | known not affected: 296 | 2026-08-11T23:47:39+00:00 | Vulnerability · Source |
| CVE-2026-68331 | suse_vex | SUSE CVE CVE-2026-68331 | known affected: 231 known not affected: 65 | 2026-08-11T23:47:36+00:00 | Vulnerability · Source |
| CVE-2026-68332 | suse_vex | SUSE CVE CVE-2026-68332 | known not affected: 296 | 2026-08-11T23:47:34+00:00 | Vulnerability · Source |
| CVE-2026-68333 | suse_vex | SUSE CVE CVE-2026-68333 | known affected: 129 known not affected: 167 | 2026-08-11T23:47:31+00:00 | Vulnerability · Source |
| CVE-2026-68334 | suse_vex | SUSE CVE CVE-2026-68334 | known not affected: 296 | 2026-08-11T23:47:29+00:00 | Vulnerability · Source |