VEX records
Browse vendor VEX statements available in this Vulnerability-Lookup instance and pivot to the related vulnerability.
286444 VEX records
API response| Vulnerability | Source | Title | Product status | Imported | Links |
|---|---|---|---|---|---|
| CVE-2026-57585 | suse_vex | SUSE CVE CVE-2026-57585 | first fixed: 7 known affected: 33 recommended: 27 | 2026-07-28T17:11:53+00:00 | Vulnerability · Source |
| CVE-2026-58023 | suse_vex | SUSE CVE CVE-2026-58023 | No product status | 2026-07-28T17:11:43+00:00 | Vulnerability · Source |
| CVE-2026-58389 | suse_vex | SUSE CVE CVE-2026-58389 | No product status | 2026-07-28T17:11:22+00:00 | Vulnerability · Source |
| CVE-2026-58459 | suse_vex | SUSE CVE CVE-2026-58459 | recommended: 7 | 2026-07-28T17:11:20+00:00 | Vulnerability · Source |
| CVE-2026-58586 | suse_vex | SUSE CVE CVE-2026-58586 | No product status | 2026-07-28T17:11:19+00:00 | Vulnerability · Source |
| CVE-2026-58624 | suse_vex | SUSE CVE CVE-2026-58624 | known affected: 4 recommended: 18 | 2026-07-28T17:11:17+00:00 | Vulnerability · Source |
| CVE-2026-58662 | suse_vex | SUSE CVE CVE-2026-58662 | No product status | 2026-07-28T17:11:16+00:00 | Vulnerability · Source |
| CVE-2026-61859 | suse_vex | SUSE CVE CVE-2026-61859 | known affected: 126 known not affected: 25 recommended: 155 | 2026-07-28T17:10:28+00:00 | Vulnerability · Source |
| CVE-2026-61860 | suse_vex | SUSE CVE CVE-2026-61860 | known not affected: 152 recommended: 141 | 2026-07-28T17:10:27+00:00 | Vulnerability · Source |
| CVE-2026-61862 | suse_vex | SUSE CVE CVE-2026-61862 | known affected: 140 known not affected: 8 recommended: 169 | 2026-07-28T17:10:25+00:00 | Vulnerability · Source |
| CVE-2026-61863 | suse_vex | SUSE CVE CVE-2026-61863 | known affected: 140 known not affected: 8 recommended: 169 | 2026-07-28T17:10:24+00:00 | Vulnerability · Source |
| CVE-2026-61864 | suse_vex | SUSE CVE CVE-2026-61864 | known affected: 126 known not affected: 25 recommended: 155 | 2026-07-28T17:10:23+00:00 | Vulnerability · Source |
| CVE-2026-61865 | suse_vex | SUSE CVE CVE-2026-61865 | known affected: 126 known not affected: 25 recommended: 155 | 2026-07-28T17:10:21+00:00 | Vulnerability · Source |
| CVE-2026-61867 | suse_vex | SUSE CVE CVE-2026-61867 | known affected: 126 known not affected: 25 recommended: 155 | 2026-07-28T17:10:19+00:00 | Vulnerability · Source |
| CVE-2026-61868 | suse_vex | SUSE CVE CVE-2026-61868 | known affected: 140 known not affected: 8 recommended: 169 | 2026-07-28T17:10:17+00:00 | Vulnerability · Source |
| CVE-2026-61869 | suse_vex | SUSE CVE CVE-2026-61869 | known affected: 140 known not affected: 8 recommended: 169 | 2026-07-28T17:10:16+00:00 | Vulnerability · Source |
| CVE-2026-61871 | suse_vex | SUSE CVE CVE-2026-61871 | known not affected: 191 recommended: 117 | 2026-07-28T17:10:14+00:00 | Vulnerability · Source |
| CVE-2026-61872 | suse_vex | SUSE CVE CVE-2026-61872 | known affected: 140 known not affected: 8 recommended: 169 | 2026-07-28T17:10:12+00:00 | Vulnerability · Source |
| CVE-2026-62423 | suse_vex | SUSE CVE CVE-2026-62423 | first fixed: 87 known affected: 151 | 2026-07-28T17:10:08+00:00 | Vulnerability · Source |
| CVE-2026-62424 | suse_vex | SUSE CVE CVE-2026-62424 | first fixed: 87 known affected: 151 | 2026-07-28T17:10:06+00:00 | Vulnerability · Source |
| CVE-2026-62425 | suse_vex | SUSE CVE CVE-2026-62425 | first fixed: 87 known affected: 151 | 2026-07-28T17:10:04+00:00 | Vulnerability · Source |
| CVE-2026-62427 | suse_vex | SUSE CVE CVE-2026-62427 | first fixed: 87 known affected: 151 | 2026-07-28T17:10:03+00:00 | Vulnerability · Source |
| CVE-2026-62436 | suse_vex | SUSE CVE CVE-2026-62436 | known affected: 151 | 2026-07-28T17:10:01+00:00 | Vulnerability · Source |
| CVE-2026-63891 | suse_vex | SUSE CVE CVE-2026-63891 | known affected: 292 known not affected: 6 | 2026-07-28T17:09:57+00:00 | Vulnerability · Source |
| CVE-2026-63897 | suse_vex | SUSE CVE CVE-2026-63897 | known affected: 197 known not affected: 101 | 2026-07-28T17:09:55+00:00 | Vulnerability · Source |
| CVE-2026-63898 | suse_vex | SUSE CVE CVE-2026-63898 | known affected: 294 known not affected: 4 | 2026-07-28T17:09:53+00:00 | Vulnerability · Source |
| CVE-2026-63906 | suse_vex | SUSE CVE CVE-2026-63906 | known not affected: 298 | 2026-07-28T17:09:52+00:00 | Vulnerability · Source |
| CVE-2026-63908 | suse_vex | SUSE CVE CVE-2026-63908 | known affected: 144 known not affected: 154 | 2026-07-28T17:09:50+00:00 | Vulnerability · Source |
| CVE-2026-63938 | suse_vex | SUSE CVE CVE-2026-63938 | known affected: 55 known not affected: 241 | 2026-07-28T17:09:46+00:00 | Vulnerability · Source |
| CVE-2026-63939 | suse_vex | SUSE CVE CVE-2026-63939 | known affected: 55 known not affected: 241 | 2026-07-28T17:09:44+00:00 | Vulnerability · Source |
| CVE-2026-63940 | suse_vex | SUSE CVE CVE-2026-63940 | known affected: 118 known not affected: 178 | 2026-07-28T17:09:42+00:00 | Vulnerability · Source |
| CVE-2026-63944 | suse_vex | SUSE CVE CVE-2026-63944 | known affected: 47 known not affected: 251 | 2026-07-28T17:09:40+00:00 | Vulnerability · Source |
| CVE-2026-63945 | suse_vex | SUSE CVE CVE-2026-63945 | known affected: 78 known not affected: 220 | 2026-07-28T17:09:39+00:00 | Vulnerability · Source |
| CVE-2026-63946 | suse_vex | SUSE CVE CVE-2026-63946 | known affected: 78 known not affected: 220 | 2026-07-28T17:09:37+00:00 | Vulnerability · Source |
| CVE-2026-63947 | suse_vex | SUSE CVE CVE-2026-63947 | known affected: 197 known not affected: 101 | 2026-07-28T17:09:35+00:00 | Vulnerability · Source |
| CVE-2026-63948 | suse_vex | SUSE CVE CVE-2026-63948 | known affected: 110 known not affected: 188 | 2026-07-28T17:09:33+00:00 | Vulnerability · Source |
| CVE-2026-63949 | suse_vex | SUSE CVE CVE-2026-63949 | known affected: 30 known not affected: 268 | 2026-07-28T17:09:31+00:00 | Vulnerability · Source |
| CVE-2026-63970 | suse_vex | SUSE CVE CVE-2026-63970 | known affected: 131 known not affected: 167 | 2026-07-28T17:09:29+00:00 | Vulnerability · Source |
| CVE-2026-63971 | suse_vex | SUSE CVE CVE-2026-63971 | known affected: 298 | 2026-07-28T17:09:27+00:00 | Vulnerability · Source |
| CVE-2026-63972 | suse_vex | SUSE CVE CVE-2026-63972 | known affected: 115 known not affected: 183 | 2026-07-28T17:09:26+00:00 | Vulnerability · Source |
| CVE-2026-63973 | suse_vex | SUSE CVE CVE-2026-63973 | known affected: 115 known not affected: 183 | 2026-07-28T17:09:24+00:00 | Vulnerability · Source |
| CVE-2026-63974 | suse_vex | SUSE CVE CVE-2026-63974 | known affected: 150 known not affected: 144 | 2026-07-28T17:09:22+00:00 | Vulnerability · Source |
| CVE-2026-63975 | suse_vex | SUSE CVE CVE-2026-63975 | known affected: 102 known not affected: 196 | 2026-07-28T17:09:20+00:00 | Vulnerability · Source |
| CVE-2026-63976 | suse_vex | SUSE CVE CVE-2026-63976 | known affected: 132 known not affected: 166 | 2026-07-28T17:09:18+00:00 | Vulnerability · Source |
| CVE-2026-64213 | suse_vex | SUSE CVE CVE-2026-64213 | known affected: 245 known not affected: 53 | 2026-07-28T17:09:15+00:00 | Vulnerability · Source |
| CVE-2026-64214 | suse_vex | SUSE CVE CVE-2026-64214 | known affected: 131 known not affected: 167 | 2026-07-28T17:09:14+00:00 | Vulnerability · Source |
| CVE-2026-64220 | suse_vex | SUSE CVE CVE-2026-64220 | known affected: 118 known not affected: 180 | 2026-07-28T17:09:08+00:00 | Vulnerability · Source |
| CVE-2026-64224 | suse_vex | SUSE CVE CVE-2026-64224 | known affected: 84 known not affected: 214 | 2026-07-28T17:09:02+00:00 | Vulnerability · Source |
| CVE-2026-64225 | suse_vex | SUSE CVE CVE-2026-64225 | known affected: 245 known not affected: 53 | 2026-07-28T17:09:00+00:00 | Vulnerability · Source |
| CVE-2026-64227 | suse_vex | SUSE CVE CVE-2026-64227 | known affected: 84 known not affected: 214 | 2026-07-28T17:08:57+00:00 | Vulnerability · Source |