VEX records
Browse vendor VEX statements available in this Vulnerability-Lookup instance and pivot to the related vulnerability.
287160 VEX records
API response| Vulnerability | Source | Title | Product status | Imported | Links |
|---|---|---|---|---|---|
| CVE-2026-64120 | suse_vex | SUSE CVE CVE-2026-64120 | known not affected: 296 | 2026-08-03T17:14:52+00:00 | Vulnerability · Source |
| CVE-2026-64140 | suse_vex | SUSE CVE CVE-2026-64140 | known not affected: 296 | 2026-08-03T17:14:50+00:00 | Vulnerability · Source |
| CVE-2026-64141 | suse_vex | SUSE CVE CVE-2026-64141 | known affected: 29 known not affected: 267 | 2026-08-03T17:14:49+00:00 | Vulnerability · Source |
| CVE-2026-64188 | suse_vex | SUSE CVE CVE-2026-64188 | known affected: 231 known not affected: 53 | 2026-08-03T17:14:47+00:00 | Vulnerability · Source |
| CVE-2026-64194 | suse_vex | SUSE CVE CVE-2026-64194 | known not affected: 6 recommended: 25 | 2026-08-03T17:14:45+00:00 | Vulnerability · Source |
| CVE-2026-64205 | suse_vex | SUSE CVE CVE-2026-64205 | known affected: 129 known not affected: 167 | 2026-08-03T17:14:43+00:00 | Vulnerability · Source |
| CVE-2026-64226 | suse_vex | SUSE CVE CVE-2026-64226 | known affected: 29 known not affected: 269 | 2026-08-03T17:14:42+00:00 | Vulnerability · Source |
| CVE-2026-64256 | suse_vex | SUSE CVE CVE-2026-64256 | known affected: 29 known not affected: 269 | 2026-08-03T17:14:40+00:00 | Vulnerability · Source |
| CVE-2026-64257 | suse_vex | SUSE CVE CVE-2026-64257 | known not affected: 298 | 2026-08-03T17:14:39+00:00 | Vulnerability · Source |
| CVE-2026-64259 | suse_vex | SUSE CVE CVE-2026-64259 | known not affected: 298 | 2026-08-03T17:14:37+00:00 | Vulnerability · Source |
| CVE-2026-64261 | suse_vex | SUSE CVE CVE-2026-64261 | known not affected: 298 | 2026-08-03T17:14:36+00:00 | Vulnerability · Source |
| CVE-2026-64268 | suse_vex | SUSE CVE CVE-2026-64268 | known affected: 245 known not affected: 53 | 2026-08-03T17:14:34+00:00 | Vulnerability · Source |
| CVE-2026-64281 | suse_vex | SUSE CVE CVE-2026-64281 | known not affected: 298 | 2026-08-03T17:14:31+00:00 | Vulnerability · Source |
| CVE-2026-64284 | suse_vex | SUSE CVE CVE-2026-64284 | known affected: 131 known not affected: 167 | 2026-08-03T17:14:29+00:00 | Vulnerability · Source |
| CVE-2026-64287 | suse_vex | SUSE CVE CVE-2026-64287 | known affected: 131 known not affected: 167 | 2026-08-03T17:14:28+00:00 | Vulnerability · Source |
| CVE-2026-64303 | suse_vex | SUSE CVE CVE-2026-64303 | known affected: 166 known not affected: 132 | 2026-08-03T17:14:26+00:00 | Vulnerability · Source |
| CVE-2026-64305 | suse_vex | SUSE CVE CVE-2026-64305 | known affected: 193 known not affected: 105 | 2026-08-03T17:14:24+00:00 | Vulnerability · Source |
| CVE-2026-64319 | suse_vex | SUSE CVE CVE-2026-64319 | known affected: 131 known not affected: 167 | 2026-08-03T17:14:23+00:00 | Vulnerability · Source |
| CVE-2026-64323 | suse_vex | SUSE CVE CVE-2026-64323 | known affected: 298 | 2026-08-03T17:14:21+00:00 | Vulnerability · Source |
| CVE-2026-64326 | suse_vex | SUSE CVE CVE-2026-64326 | known affected: 29 known not affected: 269 | 2026-08-03T17:14:20+00:00 | Vulnerability · Source |
| CVE-2026-64327 | suse_vex | SUSE CVE CVE-2026-64327 | known affected: 29 known not affected: 269 | 2026-08-03T17:14:19+00:00 | Vulnerability · Source |
| CVE-2026-64332 | suse_vex | SUSE CVE CVE-2026-64332 | known affected: 193 known not affected: 105 | 2026-08-03T17:14:17+00:00 | Vulnerability · Source |
| CVE-2026-64353 | suse_vex | SUSE CVE CVE-2026-64353 | known not affected: 298 | 2026-08-03T17:14:15+00:00 | Vulnerability · Source |
| CVE-2026-64360 | suse_vex | SUSE CVE CVE-2026-64360 | known affected: 102 known not affected: 196 | 2026-08-03T17:14:13+00:00 | Vulnerability · Source |
| CVE-2026-64363 | suse_vex | SUSE CVE CVE-2026-64363 | known affected: 294 known not affected: 4 | 2026-08-03T17:14:12+00:00 | Vulnerability · Source |
| CVE-2026-64365 | suse_vex | SUSE CVE CVE-2026-64365 | known affected: 30 known not affected: 268 | 2026-08-03T17:14:11+00:00 | Vulnerability · Source |
| CVE-2026-64377 | suse_vex | SUSE CVE CVE-2026-64377 | known affected: 131 known not affected: 167 | 2026-08-03T17:14:09+00:00 | Vulnerability · Source |
| CVE-2026-64382 | suse_vex | SUSE CVE CVE-2026-64382 | known affected: 131 known not affected: 167 | 2026-08-03T17:14:08+00:00 | Vulnerability · Source |
| CVE-2026-64391 | suse_vex | SUSE CVE CVE-2026-64391 | known affected: 131 known not affected: 167 | 2026-08-03T17:14:04+00:00 | Vulnerability · Source |
| CVE-2026-64402 | suse_vex | SUSE CVE CVE-2026-64402 | known affected: 131 known not affected: 167 | 2026-08-03T17:14:02+00:00 | Vulnerability · Source |
| CVE-2026-64407 | suse_vex | SUSE CVE CVE-2026-64407 | known affected: 47 known not affected: 251 | 2026-08-03T17:14:00+00:00 | Vulnerability · Source |
| CVE-2026-64414 | suse_vex | SUSE CVE CVE-2026-64414 | known affected: 29 known not affected: 269 | 2026-08-03T17:13:59+00:00 | Vulnerability · Source |
| CVE-2026-64415 | suse_vex | SUSE CVE CVE-2026-64415 | known affected: 29 known not affected: 269 | 2026-08-03T17:13:57+00:00 | Vulnerability · Source |
| CVE-2026-64416 | suse_vex | SUSE CVE CVE-2026-64416 | known affected: 29 known not affected: 269 | 2026-08-03T17:13:56+00:00 | Vulnerability · Source |
| CVE-2026-64420 | suse_vex | SUSE CVE CVE-2026-64420 | known affected: 191 known not affected: 107 | 2026-08-03T17:13:54+00:00 | Vulnerability · Source |
| CVE-2026-64422 | suse_vex | SUSE CVE CVE-2026-64422 | known affected: 298 | 2026-08-03T17:13:52+00:00 | Vulnerability · Source |
| CVE-2026-64427 | suse_vex | SUSE CVE CVE-2026-64427 | known not affected: 298 | 2026-08-03T17:13:51+00:00 | Vulnerability · Source |
| CVE-2026-64443 | suse_vex | SUSE CVE CVE-2026-64443 | known affected: 191 known not affected: 107 | 2026-08-03T17:13:49+00:00 | Vulnerability · Source |
| CVE-2026-64446 | suse_vex | SUSE CVE CVE-2026-64446 | known affected: 263 known not affected: 35 | 2026-08-03T17:13:47+00:00 | Vulnerability · Source |
| CVE-2026-64456 | suse_vex | SUSE CVE CVE-2026-64456 | known affected: 197 known not affected: 101 | 2026-08-03T17:13:46+00:00 | Vulnerability · Source |
| CVE-2026-64463 | suse_vex | SUSE CVE CVE-2026-64463 | known affected: 245 known not affected: 53 | 2026-08-03T17:13:44+00:00 | Vulnerability · Source |
| CVE-2026-64469 | suse_vex | SUSE CVE CVE-2026-64469 | known affected: 245 known not affected: 53 | 2026-08-03T17:13:42+00:00 | Vulnerability · Source |
| CVE-2026-64473 | suse_vex | SUSE CVE CVE-2026-64473 | known affected: 84 known not affected: 214 | 2026-08-03T17:13:41+00:00 | Vulnerability · Source |
| CVE-2026-64491 | suse_vex | SUSE CVE CVE-2026-64491 | known not affected: 298 | 2026-08-03T17:13:39+00:00 | Vulnerability · Source |
| CVE-2026-64493 | suse_vex | SUSE CVE CVE-2026-64493 | known affected: 131 known not affected: 167 | 2026-08-03T17:13:37+00:00 | Vulnerability · Source |
| CVE-2026-64508 | suse_vex | SUSE CVE CVE-2026-64508 | known affected: 179 known not affected: 119 | 2026-08-03T17:13:35+00:00 | Vulnerability · Source |
| CVE-2026-64513 | suse_vex | SUSE CVE CVE-2026-64513 | known affected: 191 known not affected: 107 | 2026-08-03T17:13:34+00:00 | Vulnerability · Source |
| CVE-2026-64532 | suse_vex | SUSE CVE CVE-2026-64532 | known affected: 131 known not affected: 167 | 2026-08-03T17:13:30+00:00 | Vulnerability · Source |
| CVE-2026-64533 | suse_vex | SUSE CVE CVE-2026-64533 | known affected: 131 known not affected: 167 | 2026-08-03T17:13:29+00:00 | Vulnerability · Source |
| CVE-2026-64536 | suse_vex | SUSE CVE CVE-2026-64536 | known affected: 191 known not affected: 107 | 2026-08-03T17:13:27+00:00 | Vulnerability · Source |