VEX records
Browse vendor VEX statements available in this Vulnerability-Lookup instance and pivot to the related vulnerability.
288586 VEX records
API response| Vulnerability | Source | Title | Product status | Imported | Links |
|---|---|---|---|---|---|
| CVE-2026-64379 | suse_vex | SUSE CVE CVE-2026-64379 | known affected: 292 known not affected: 6 | 2026-08-06T01:07:41+00:00 | Vulnerability · Source |
| CVE-2026-64381 | suse_vex | SUSE CVE CVE-2026-64381 | known affected: 292 known not affected: 6 | 2026-08-06T01:07:39+00:00 | Vulnerability · Source |
| CVE-2026-64396 | suse_vex | SUSE CVE CVE-2026-64396 | known affected: 131 known not affected: 167 | 2026-08-06T01:07:30+00:00 | Vulnerability · Source |
| CVE-2026-64401 | suse_vex | SUSE CVE CVE-2026-64401 | known affected: 245 known not affected: 53 | 2026-08-06T01:07:27+00:00 | Vulnerability · Source |
| CVE-2026-64408 | suse_vex | SUSE CVE CVE-2026-64408 | known affected: 197 known not affected: 101 | 2026-08-06T01:07:25+00:00 | Vulnerability · Source |
| CVE-2026-64409 | suse_vex | SUSE CVE CVE-2026-64409 | known affected: 78 known not affected: 220 | 2026-08-06T01:07:24+00:00 | Vulnerability · Source |
| CVE-2026-64412 | suse_vex | SUSE CVE CVE-2026-64412 | known affected: 292 known not affected: 6 | 2026-08-06T01:07:22+00:00 | Vulnerability · Source |
| CVE-2026-64418 | suse_vex | SUSE CVE CVE-2026-64418 | known affected: 29 known not affected: 269 | 2026-08-06T01:07:20+00:00 | Vulnerability · Source |
| CVE-2026-64426 | suse_vex | SUSE CVE CVE-2026-64426 | known not affected: 298 | 2026-08-06T01:07:18+00:00 | Vulnerability · Source |
| CVE-2026-64434 | suse_vex | SUSE CVE CVE-2026-64434 | known affected: 101 known not affected: 197 | 2026-08-06T01:07:17+00:00 | Vulnerability · Source |
| CVE-2026-64442 | suse_vex | SUSE CVE CVE-2026-64442 | known affected: 191 known not affected: 107 | 2026-08-06T01:07:14+00:00 | Vulnerability · Source |
| CVE-2026-64451 | suse_vex | SUSE CVE CVE-2026-64451 | known not affected: 298 | 2026-08-06T01:07:10+00:00 | Vulnerability · Source |
| CVE-2026-64455 | suse_vex | SUSE CVE CVE-2026-64455 | known affected: 193 known not affected: 105 | 2026-08-06T01:07:08+00:00 | Vulnerability · Source |
| CVE-2026-64458 | suse_vex | SUSE CVE CVE-2026-64458 | known affected: 131 known not affected: 167 | 2026-08-06T01:07:07+00:00 | Vulnerability · Source |
| CVE-2026-64461 | suse_vex | SUSE CVE CVE-2026-64461 | known affected: 245 known not affected: 53 | 2026-08-06T01:07:05+00:00 | Vulnerability · Source |
| CVE-2026-64462 | suse_vex | SUSE CVE CVE-2026-64462 | known affected: 233 known not affected: 65 | 2026-08-06T01:07:03+00:00 | Vulnerability · Source |
| CVE-2026-64464 | suse_vex | SUSE CVE CVE-2026-64464 | known not affected: 298 | 2026-08-06T01:07:01+00:00 | Vulnerability · Source |
| CVE-2026-64470 | suse_vex | SUSE CVE CVE-2026-64470 | known affected: 191 known not affected: 107 | 2026-08-06T01:06:59+00:00 | Vulnerability · Source |
| CVE-2026-64479 | suse_vex | SUSE CVE CVE-2026-64479 | known affected: 30 known not affected: 268 | 2026-08-06T01:06:57+00:00 | Vulnerability · Source |
| CVE-2026-64482 | suse_vex | SUSE CVE CVE-2026-64482 | known affected: 30 known not affected: 268 | 2026-08-06T01:06:56+00:00 | Vulnerability · Source |
| CVE-2026-64485 | suse_vex | SUSE CVE CVE-2026-64485 | known not affected: 298 | 2026-08-06T01:06:55+00:00 | Vulnerability · Source |
| CVE-2026-64498 | suse_vex | SUSE CVE CVE-2026-64498 | known not affected: 298 | 2026-08-06T01:06:52+00:00 | Vulnerability · Source |
| CVE-2026-64499 | suse_vex | SUSE CVE CVE-2026-64499 | known not affected: 298 | 2026-08-06T01:06:51+00:00 | Vulnerability · Source |
| CVE-2026-64501 | suse_vex | SUSE CVE CVE-2026-64501 | known not affected: 298 | 2026-08-06T01:06:50+00:00 | Vulnerability · Source |
| CVE-2026-64511 | suse_vex | SUSE CVE CVE-2026-64511 | known affected: 30 known not affected: 268 | 2026-08-06T01:06:48+00:00 | Vulnerability · Source |
| CVE-2026-64515 | suse_vex | SUSE CVE CVE-2026-64515 | known affected: 55 known not affected: 243 | 2026-08-06T01:06:47+00:00 | Vulnerability · Source |
| CVE-2026-64535 | suse_vex | SUSE CVE CVE-2026-64535 | known affected: 219 known not affected: 79 | 2026-08-06T01:06:42+00:00 | Vulnerability · Source |
| CVE-2026-64551 | suse_vex | SUSE CVE CVE-2026-64551 | known affected: 245 known not affected: 53 | 2026-08-06T01:06:38+00:00 | Vulnerability · Source |
| CVE-2026-64558 | suse_vex | SUSE CVE CVE-2026-64558 | known affected: 29 known not affected: 267 | 2026-08-06T01:06:36+00:00 | Vulnerability · Source |
| CVE-2026-64559 | suse_vex | SUSE CVE CVE-2026-64559 | known affected: 29 known not affected: 267 | 2026-08-06T01:06:35+00:00 | Vulnerability · Source |
| CVE-2026-66140 | suse_vex | SUSE CVE CVE-2026-66140 | No product status | 2026-08-06T01:06:01+00:00 | Vulnerability · Source |
| CVE-2026-66141 | suse_vex | SUSE CVE CVE-2026-66141 | No product status | 2026-08-06T01:06:00+00:00 | Vulnerability · Source |
| CVE-2026-66746 | suse_vex | SUSE CVE CVE-2026-66746 | known affected: 16 known not affected: 8 | 2026-08-06T01:05:59+00:00 | Vulnerability · Source |
| CVE-2026-66754 | suse_vex | SUSE CVE CVE-2026-66754 | known affected: 16 known not affected: 8 | 2026-08-06T01:05:57+00:00 | Vulnerability · Source |
| CVE-2026-66758 | suse_vex | SUSE CVE CVE-2026-66758 | known not affected: 26 recommended: 18 | 2026-08-06T01:05:56+00:00 | Vulnerability · Source |
| CVE-2026-67181 | suse_vex | SUSE CVE CVE-2026-67181 | known affected: 16 known not affected: 8 | 2026-08-06T01:05:55+00:00 | Vulnerability · Source |
| CVE-2026-67182 | suse_vex | SUSE CVE CVE-2026-67182 | known affected: 16 known not affected: 8 | 2026-08-06T01:05:53+00:00 | Vulnerability · Source |
| CVE-2026-67313 | suse_vex | SUSE CVE CVE-2026-67313 | known affected: 26 known not affected: 63 | 2026-08-06T01:05:51+00:00 | Vulnerability · Source |
| CVE-2026-67314 | suse_vex | SUSE CVE CVE-2026-67314 | known affected: 9 | 2026-08-06T01:05:50+00:00 | Vulnerability · Source |
| CVE-2026-67315 | suse_vex | SUSE CVE CVE-2026-67315 | known affected: 9 | 2026-08-06T01:05:49+00:00 | Vulnerability · Source |
| CVE-2026-67316 | suse_vex | SUSE CVE CVE-2026-67316 | known affected: 26 known not affected: 63 | 2026-08-06T01:05:48+00:00 | Vulnerability · Source |
| CVE-2026-67317 | suse_vex | SUSE CVE CVE-2026-67317 | known affected: 14 known not affected: 75 | 2026-08-06T01:05:47+00:00 | Vulnerability · Source |
| CVE-2026-67318 | suse_vex | SUSE CVE CVE-2026-67318 | known affected: 9 | 2026-08-06T01:05:46+00:00 | Vulnerability · Source |
| CVE-2026-67319 | suse_vex | SUSE CVE CVE-2026-67319 | known affected: 28 known not affected: 308 | 2026-08-06T01:05:45+00:00 | Vulnerability · Source |
| CVE-2026-67320 | suse_vex | SUSE CVE CVE-2026-67320 | known affected: 9 | 2026-08-06T01:05:43+00:00 | Vulnerability · Source |
| CVE-2026-67321 | suse_vex | SUSE CVE CVE-2026-67321 | known affected: 9 | 2026-08-06T01:05:42+00:00 | Vulnerability · Source |
| CVE-2026-68494 | suse_vex | SUSE CVE CVE-2026-68494 | known not affected: 32 | 2026-08-06T01:05:40+00:00 | Vulnerability · Source |
| CVE-2026-44210 | redhat_vex | kata-containers: Kata Containers: Privilege escalation and information disclosure via command-line argument injection | known affected: 3 | 2026-08-06T01:03:20+00:00 | Vulnerability · Source |
| CVE-2026-31788 | redhat_vex | kernel: xen/privcmd: restrict usage in unprivileged domU | known affected: 260 known not affected: 14 | 2026-08-06T00:35:24+00:00 | Vulnerability · Source |
| CVE-2026-18739 | redhat_vex | popt-devel: popt-static: Off-by-one in poptStuffArgs | known affected: 13 under investigation: 1 | 2026-08-05T21:49:04+00:00 | Vulnerability · Source |