VEX records
Browse vendor VEX statements available in this Vulnerability-Lookup instance and pivot to the related vulnerability.
294114 VEX records
API response| Vulnerability | Source | Title | Product status | Imported | Links |
|---|---|---|---|---|---|
| CVE-2026-16806 | suse_vex | SUSE CVE CVE-2026-16806 | recommended: 6 | 2026-07-28T17:20:23+00:00 | Vulnerability · Source |
| CVE-2026-16807 | suse_vex | SUSE CVE CVE-2026-16807 | recommended: 6 | 2026-07-28T17:20:22+00:00 | Vulnerability · Source |
| CVE-2026-17500 | suse_vex | SUSE CVE CVE-2026-17500 | No product status | 2026-07-28T17:20:21+00:00 | Vulnerability · Source |
| CVE-2026-20031 | suse_vex | SUSE CVE CVE-2026-20031 | known not affected: 20 recommended: 203 | 2026-07-28T17:20:13+00:00 | Vulnerability · Source |
| CVE-2026-27904 | suse_vex | SUSE CVE CVE-2026-27904 | known affected: 531 known not affected: 310 recommended: 170 | 2026-07-28T17:19:33+00:00 | Vulnerability · Source |
| CVE-2026-31402 | suse_vex | SUSE CVE CVE-2026-31402 | first fixed: 2 known affected: 477 recommended: 852 | 2026-07-28T17:19:28+00:00 | Vulnerability · Source |
| CVE-2026-31613 | suse_vex | SUSE CVE CVE-2026-31613 | first fixed: 2 known affected: 411 known not affected: 98 recommended: 593 | 2026-07-28T17:19:02+00:00 | Vulnerability · Source |
| CVE-2026-31684 | suse_vex | SUSE CVE CVE-2026-31684 | first fixed: 2 known affected: 577 known not affected: 67 recommended: 411 | 2026-07-28T17:18:52+00:00 | Vulnerability · Source |
| CVE-2026-35480 | suse_vex | SUSE CVE CVE-2026-35480 | recommended: 2 | 2026-07-28T17:18:32+00:00 | Vulnerability · Source |
| CVE-2026-41608 | suse_vex | SUSE CVE CVE-2026-41608 | No product status | 2026-07-28T17:18:12+00:00 | Vulnerability · Source |
| CVE-2026-43871 | suse_vex | SUSE CVE CVE-2026-43871 | No product status | 2026-07-28T17:15:57+00:00 | Vulnerability · Source |
| CVE-2026-45112 | suse_vex | SUSE CVE CVE-2026-45112 | No product status | 2026-07-28T17:15:44+00:00 | Vulnerability · Source |
| CVE-2026-48144 | suse_vex | SUSE CVE CVE-2026-48144 | No product status | 2026-07-28T17:14:01+00:00 | Vulnerability · Source |
| CVE-2026-49158 | suse_vex | SUSE CVE CVE-2026-49158 | No product status | 2026-07-28T17:13:51+00:00 | Vulnerability · Source |
| CVE-2026-53384 | suse_vex | SUSE CVE CVE-2026-53384 | known affected: 217 known not affected: 79 recommended: 4 | 2026-07-28T17:12:24+00:00 | Vulnerability · Source |
| CVE-2026-53705 | suse_vex | SUSE CVE CVE-2026-53705 | known affected: 45 recommended: 72 | 2026-07-28T17:12:22+00:00 | Vulnerability · Source |
| CVE-2026-55380 | suse_vex | SUSE CVE CVE-2026-55380 | known not affected: 7 recommended: 47 | 2026-07-28T17:12:17+00:00 | Vulnerability · Source |
| CVE-2026-55968 | suse_vex | SUSE CVE CVE-2026-55968 | No product status | 2026-07-28T17:12:15+00:00 | Vulnerability · Source |
| CVE-2026-55969 | suse_vex | SUSE CVE CVE-2026-55969 | No product status | 2026-07-28T17:12:14+00:00 | Vulnerability · Source |
| CVE-2026-55970 | suse_vex | SUSE CVE CVE-2026-55970 | No product status | 2026-07-28T17:12:12+00:00 | Vulnerability · Source |
| CVE-2026-56375 | suse_vex | SUSE CVE CVE-2026-56375 | known affected: 72 known not affected: 79 recommended: 155 | 2026-07-28T17:12:06+00:00 | Vulnerability · Source |
| CVE-2026-56452 | suse_vex | SUSE CVE CVE-2026-56452 | known affected: 4 recommended: 18 | 2026-07-28T17:12:02+00:00 | Vulnerability · Source |
| CVE-2026-56623 | suse_vex | SUSE CVE CVE-2026-56623 | known affected: 4 recommended: 18 | 2026-07-28T17:12:01+00:00 | Vulnerability · Source |
| CVE-2026-56624 | suse_vex | SUSE CVE CVE-2026-56624 | known affected: 4 recommended: 18 | 2026-07-28T17:11:59+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-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-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-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-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-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 |
| CVE-2026-64228 | suse_vex | SUSE CVE CVE-2026-64228 | known not affected: 298 | 2026-07-28T17:08:55+00:00 | Vulnerability · Source |
| CVE-2026-64229 | suse_vex | SUSE CVE CVE-2026-64229 | known not affected: 298 | 2026-07-28T17:08:53+00:00 | Vulnerability · Source |
| CVE-2026-64230 | suse_vex | SUSE CVE CVE-2026-64230 | known not affected: 298 | 2026-07-28T17:08:51+00:00 | Vulnerability · Source |