VEX records
Browse vendor VEX statements available in this Vulnerability-Lookup instance and pivot to the related vulnerability.
288029 VEX records
API response| Vulnerability | Source | Title | Product status | Imported | Links |
|---|---|---|---|---|---|
| CVE-2026-56209 | suse_vex | SUSE CVE CVE-2026-56209 | known affected: 7 known not affected: 8 recommended: 129 | 2026-07-30T16:38:29+00:00 | Vulnerability · Source |
| CVE-2026-56210 | suse_vex | SUSE CVE CVE-2026-56210 | known affected: 7 known not affected: 8 recommended: 129 | 2026-07-30T16:38:27+00:00 | Vulnerability · Source |
| CVE-2026-56211 | suse_vex | SUSE CVE CVE-2026-56211 | known affected: 7 known not affected: 8 recommended: 129 | 2026-07-30T16:38:26+00:00 | Vulnerability · Source |
| CVE-2026-56362 | suse_vex | SUSE CVE CVE-2026-56362 | known affected: 140 known not affected: 8 recommended: 169 | 2026-07-30T16:38:24+00:00 | Vulnerability · Source |
| CVE-2026-56389 | suse_vex | SUSE CVE CVE-2026-56389 | known affected: 9 known not affected: 75 | 2026-07-30T16:38:22+00:00 | Vulnerability · Source |
| CVE-2026-56390 | suse_vex | SUSE CVE CVE-2026-56390 | known affected: 77 known not affected: 7 | 2026-07-30T16:38:21+00:00 | Vulnerability · Source |
| CVE-2026-56740 | suse_vex | SUSE CVE CVE-2026-56740 | recommended: 65 | 2026-07-30T16:37:57+00:00 | Vulnerability · Source |
| CVE-2026-57074 | suse_vex | SUSE CVE CVE-2026-57074 | known affected: 17 recommended: 8 | 2026-07-30T16:37:44+00:00 | Vulnerability · Source |
| CVE-2026-58058 | suse_vex | SUSE CVE CVE-2026-58058 | first fixed: 1 known affected: 26 recommended: 14 | 2026-07-30T16:37:14+00:00 | Vulnerability · Source |
| CVE-2026-58379 | suse_vex | SUSE CVE CVE-2026-58379 | recommended: 46 | 2026-07-30T16:37:05+00:00 | Vulnerability · Source |
| CVE-2026-58380 | suse_vex | SUSE CVE CVE-2026-58380 | recommended: 37 | 2026-07-30T16:37:03+00:00 | Vulnerability · Source |
| CVE-2026-58381 | suse_vex | SUSE CVE CVE-2026-58381 | recommended: 35 | 2026-07-30T16:37:02+00:00 | Vulnerability · Source |
| CVE-2026-58419 | suse_vex | SUSE CVE CVE-2026-58419 | No product status | 2026-07-30T16:36:59+00:00 | Vulnerability · Source |
| CVE-2026-58422 | suse_vex | SUSE CVE CVE-2026-58422 | No product status | 2026-07-30T16:36:56+00:00 | Vulnerability · Source |
| CVE-2026-58423 | suse_vex | SUSE CVE CVE-2026-58423 | No product status | 2026-07-30T16:36:55+00:00 | Vulnerability · Source |
| CVE-2026-58424 | suse_vex | SUSE CVE CVE-2026-58424 | No product status | 2026-07-30T16:36:53+00:00 | Vulnerability · Source |
| CVE-2026-59247 | suse_vex | SUSE CVE CVE-2026-59247 | No product status | 2026-07-30T16:36:41+00:00 | Vulnerability · Source |
| CVE-2026-59733 | suse_vex | SUSE CVE CVE-2026-59733 | recommended: 9 | 2026-07-30T16:36:32+00:00 | Vulnerability · Source |
| CVE-2026-59873 | suse_vex | SUSE CVE CVE-2026-59873 | recommended: 33 | 2026-07-30T16:36:21+00:00 | Vulnerability · Source |
| CVE-2026-59874 | suse_vex | SUSE CVE CVE-2026-59874 | recommended: 33 | 2026-07-30T16:36:20+00:00 | Vulnerability · Source |
| CVE-2026-62685 | suse_vex | SUSE CVE CVE-2026-62685 | No product status | 2026-07-30T16:35:40+00:00 | Vulnerability · Source |
| CVE-2026-62843 | suse_vex | SUSE CVE CVE-2026-62843 | No product status | 2026-07-30T16:35:38+00:00 | Vulnerability · Source |
| CVE-2026-62995 | suse_vex | SUSE CVE CVE-2026-62995 | No product status | 2026-07-30T16:35:34+00:00 | Vulnerability · Source |
| CVE-2026-63720 | suse_vex | SUSE CVE CVE-2026-63720 | No product status | 2026-07-30T16:35:30+00:00 | Vulnerability · Source |
| CVE-2026-63907 | suse_vex | SUSE CVE CVE-2026-63907 | known not affected: 298 | 2026-07-30T16:35:24+00:00 | Vulnerability · Source |
| CVE-2026-63909 | suse_vex | SUSE CVE CVE-2026-63909 | known not affected: 298 | 2026-07-30T16:35:22+00:00 | Vulnerability · Source |
| CVE-2026-63913 | suse_vex | SUSE CVE CVE-2026-63913 | known affected: 294 known not affected: 4 | 2026-07-30T16:35:18+00:00 | Vulnerability · Source |
| CVE-2026-63914 | suse_vex | SUSE CVE CVE-2026-63914 | known affected: 294 known not affected: 4 | 2026-07-30T16:35:16+00:00 | Vulnerability · Source |
| CVE-2026-63918 | suse_vex | SUSE CVE CVE-2026-63918 | known affected: 292 known not affected: 6 | 2026-07-30T16:35:08+00:00 | Vulnerability · Source |
| CVE-2026-63920 | suse_vex | SUSE CVE CVE-2026-63920 | known affected: 298 | 2026-07-30T16:35:03+00:00 | Vulnerability · Source |
| CVE-2026-63925 | suse_vex | SUSE CVE CVE-2026-63925 | known affected: 219 known not affected: 79 | 2026-07-30T16:34:55+00:00 | Vulnerability · Source |
| CVE-2026-63926 | suse_vex | SUSE CVE CVE-2026-63926 | known affected: 245 known not affected: 53 | 2026-07-30T16:34:54+00:00 | Vulnerability · Source |
| CVE-2026-63932 | suse_vex | SUSE CVE CVE-2026-63932 | known not affected: 296 | 2026-07-30T16:34:43+00:00 | Vulnerability · Source |
| CVE-2026-63935 | suse_vex | SUSE CVE CVE-2026-63935 | known not affected: 296 | 2026-07-30T16:34:37+00:00 | Vulnerability · Source |
| CVE-2026-63941 | suse_vex | SUSE CVE CVE-2026-63941 | known affected: 29 known not affected: 267 | 2026-07-30T16:34:33+00:00 | Vulnerability · Source |
| CVE-2026-63977 | suse_vex | SUSE CVE CVE-2026-63977 | known not affected: 298 | 2026-07-30T16:34:27+00:00 | Vulnerability · Source |
| CVE-2026-63981 | suse_vex | SUSE CVE CVE-2026-63981 | known not affected: 296 | 2026-07-30T16:34:19+00:00 | Vulnerability · Source |
| CVE-2026-63982 | suse_vex | SUSE CVE CVE-2026-63982 | known not affected: 296 | 2026-07-30T16:34:17+00:00 | Vulnerability · Source |
| CVE-2026-63983 | suse_vex | SUSE CVE CVE-2026-63983 | known affected: 296 | 2026-07-30T16:34:15+00:00 | Vulnerability · Source |
| CVE-2021-20322 | redhat_vex | kernel: new DNS Cache Poisoning Attack based on ICMP fragment needed packets replies | fixed: 300 known affected: 43 known not affected: 106 | 2026-07-30T16:34:14+00:00 | Vulnerability · Source |
| CVE-2026-63985 | suse_vex | SUSE CVE CVE-2026-63985 | known affected: 217 known not affected: 79 | 2026-07-30T16:34:12+00:00 | Vulnerability · Source |
| CVE-2026-63986 | suse_vex | SUSE CVE CVE-2026-63986 | known affected: 29 known not affected: 267 | 2026-07-30T16:34:10+00:00 | Vulnerability · Source |
| CVE-2026-63987 | suse_vex | SUSE CVE CVE-2026-63987 | known affected: 129 known not affected: 167 | 2026-07-30T16:34:08+00:00 | Vulnerability · Source |
| CVE-2026-63988 | suse_vex | SUSE CVE CVE-2026-63988 | known not affected: 296 | 2026-07-30T16:34:05+00:00 | Vulnerability · Source |
| CVE-2026-63989 | suse_vex | SUSE CVE CVE-2026-63989 | known not affected: 296 | 2026-07-30T16:34:04+00:00 | Vulnerability · Source |
| CVE-2026-63990 | suse_vex | SUSE CVE CVE-2026-63990 | known affected: 296 | 2026-07-30T16:34:02+00:00 | Vulnerability · Source |
| CVE-2026-63992 | suse_vex | SUSE CVE CVE-2026-63992 | known affected: 233 known not affected: 65 | 2026-07-30T16:33:57+00:00 | Vulnerability · Source |
| CVE-2026-63993 | suse_vex | SUSE CVE CVE-2026-63993 | No product status | 2026-07-30T16:33:55+00:00 | Vulnerability · Source |
| CVE-2026-63997 | suse_vex | SUSE CVE CVE-2026-63997 | known affected: 84 known not affected: 212 | 2026-07-30T16:33:46+00:00 | Vulnerability · Source |
| CVE-2026-63998 | suse_vex | SUSE CVE CVE-2026-63998 | known affected: 84 known not affected: 212 | 2026-07-30T16:33:44+00:00 | Vulnerability · Source |