VEX records
Browse vendor VEX statements available in this Vulnerability-Lookup instance and pivot to the related vulnerability.
287117 VEX records
API response| Vulnerability | Source | Title | Product status | Imported | Links |
|---|---|---|---|---|---|
| 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 |
| CVE-2026-64537 | suse_vex | SUSE CVE CVE-2026-64537 | known affected: 219 known not affected: 79 | 2026-08-03T17:13:25+00:00 | Vulnerability · Source |
| CVE-2026-64538 | suse_vex | SUSE CVE CVE-2026-64538 | known affected: 245 known not affected: 53 | 2026-08-03T17:13:23+00:00 | Vulnerability · Source |
| CVE-2026-64539 | suse_vex | SUSE CVE CVE-2026-64539 | known affected: 193 known not affected: 105 | 2026-08-03T17:13:21+00:00 | Vulnerability · Source |
| CVE-2026-64540 | suse_vex | SUSE CVE CVE-2026-64540 | known affected: 197 known not affected: 101 | 2026-08-03T17:13:20+00:00 | Vulnerability · Source |
| CVE-2026-64541 | suse_vex | SUSE CVE CVE-2026-64541 | known affected: 292 known not affected: 6 | 2026-08-03T17:13:17+00:00 | Vulnerability · Source |
| CVE-2026-64542 | suse_vex | SUSE CVE CVE-2026-64542 | known affected: 131 known not affected: 167 | 2026-08-03T17:13:15+00:00 | Vulnerability · Source |
| CVE-2026-64543 | suse_vex | SUSE CVE CVE-2026-64543 | known affected: 245 known not affected: 53 | 2026-08-03T17:13:13+00:00 | Vulnerability · Source |
| CVE-2026-64544 | suse_vex | SUSE CVE CVE-2026-64544 | known affected: 193 known not affected: 105 | 2026-08-03T17:13:10+00:00 | Vulnerability · Source |
| CVE-2026-64545 | suse_vex | SUSE CVE CVE-2026-64545 | known affected: 179 known not affected: 119 | 2026-08-03T17:13:09+00:00 | Vulnerability · Source |
| CVE-2026-64546 | suse_vex | SUSE CVE CVE-2026-64546 | known affected: 193 known not affected: 105 | 2026-08-03T17:13:07+00:00 | Vulnerability · Source |
| CVE-2026-64547 | suse_vex | SUSE CVE CVE-2026-64547 | known affected: 197 known not affected: 101 | 2026-08-03T17:13:04+00:00 | Vulnerability · Source |
| CVE-2026-64548 | suse_vex | SUSE CVE CVE-2026-64548 | known affected: 245 known not affected: 53 | 2026-08-03T17:13:02+00:00 | Vulnerability · Source |
| CVE-2026-64549 | suse_vex | SUSE CVE CVE-2026-64549 | known affected: 193 known not affected: 105 | 2026-08-03T17:12:59+00:00 | Vulnerability · Source |
| CVE-2026-64550 | suse_vex | SUSE CVE CVE-2026-64550 | known affected: 245 known not affected: 53 | 2026-08-03T17:12:57+00:00 | Vulnerability · Source |
| CVE-2026-64552 | suse_vex | SUSE CVE CVE-2026-64552 | known affected: 101 known not affected: 197 | 2026-08-03T17:12:54+00:00 | Vulnerability · Source |
| CVE-2026-64553 | suse_vex | SUSE CVE CVE-2026-64553 | known affected: 292 known not affected: 6 | 2026-08-03T17:12:52+00:00 | Vulnerability · Source |
| CVE-2026-64554 | suse_vex | SUSE CVE CVE-2026-64554 | known affected: 245 known not affected: 53 | 2026-08-03T17:12:50+00:00 | Vulnerability · Source |
| CVE-2026-64555 | suse_vex | SUSE CVE CVE-2026-64555 | known affected: 29 known not affected: 269 | 2026-08-03T17:12:47+00:00 | Vulnerability · Source |
| CVE-2026-64556 | suse_vex | SUSE CVE CVE-2026-64556 | known affected: 219 known not affected: 79 | 2026-08-03T17:12:45+00:00 | Vulnerability · Source |
| CVE-2026-64557 | suse_vex | SUSE CVE CVE-2026-64557 | known affected: 294 known not affected: 4 | 2026-08-03T17:12:42+00:00 | Vulnerability · Source |
| CVE-2026-65919 | suse_vex | SUSE CVE CVE-2026-65919 | No product status | 2026-08-03T17:12:40+00:00 | Vulnerability · Source |
| CVE-2026-66011 | suse_vex | SUSE CVE CVE-2026-66011 | known affected: 47 known not affected: 53 recommended: 75 | 2026-08-03T17:12:38+00:00 | Vulnerability · Source |
| CVE-2026-66066 | suse_vex | SUSE CVE CVE-2026-66066 | known affected: 5 known not affected: 77 | 2026-08-03T17:12:35+00:00 | Vulnerability · Source |
| CVE-2026-66401 | suse_vex | SUSE CVE CVE-2026-66401 | known affected: 49 known not affected: 91 | 2026-08-03T17:12:32+00:00 | Vulnerability · Source |
| CVE-2026-66402 | suse_vex | SUSE CVE CVE-2026-66402 | known affected: 140 | 2026-08-03T17:12:29+00:00 | Vulnerability · Source |
| CVE-2026-67288 | suse_vex | SUSE CVE CVE-2026-67288 | known affected: 93 known not affected: 47 | 2026-08-03T17:12:27+00:00 | Vulnerability · Source |
| CVE-2026-67289 | suse_vex | SUSE CVE CVE-2026-67289 | known affected: 140 | 2026-08-03T17:12:25+00:00 | Vulnerability · Source |
| CVE-2026-67290 | suse_vex | SUSE CVE CVE-2026-67290 | known affected: 140 | 2026-08-03T17:12:22+00:00 | Vulnerability · Source |
| CVE-2026-67291 | suse_vex | SUSE CVE CVE-2026-67291 | known affected: 140 | 2026-08-03T17:12:20+00:00 | Vulnerability · Source |
| CVE-2026-67292 | suse_vex | SUSE CVE CVE-2026-67292 | known affected: 93 known not affected: 47 | 2026-08-03T17:12:17+00:00 | Vulnerability · Source |
| CVE-2026-67293 | suse_vex | SUSE CVE CVE-2026-67293 | known affected: 140 | 2026-08-03T17:12:15+00:00 | Vulnerability · Source |
| CVE-2026-67294 | suse_vex | SUSE CVE CVE-2026-67294 | known affected: 93 known not affected: 47 | 2026-08-03T17:12:14+00:00 | Vulnerability · Source |
| CVE-2026-67296 | suse_vex | SUSE CVE CVE-2026-67296 | known affected: 140 | 2026-08-03T17:12:11+00:00 | Vulnerability · Source |