VEX records
Browse vendor VEX statements available in this Vulnerability-Lookup instance and pivot to the related vulnerability.
286610 VEX records
API response| Vulnerability | Source | Title | Product status | Imported | Links |
|---|---|---|---|---|---|
| CVE-2026-53229 | suse_vex | SUSE CVE CVE-2026-53229 | first fixed: 2 known affected: 555 known not affected: 67 recommended: 265 | 2026-07-28T17:12:49+00:00 | Vulnerability · Source |
| CVE-2026-53245 | suse_vex | SUSE CVE CVE-2026-53245 | known affected: 618 known not affected: 4 recommended: 120 | 2026-07-28T17:12:48+00:00 | Vulnerability · Source |
| CVE-2026-53249 | suse_vex | SUSE CVE CVE-2026-53249 | first fixed: 2 known affected: 622 recommended: 265 | 2026-07-28T17:12:46+00:00 | Vulnerability · Source |
| CVE-2026-53258 | suse_vex | SUSE CVE CVE-2026-53258 | first fixed: 2 known affected: 529 known not affected: 93 recommended: 265 | 2026-07-28T17:12:44+00:00 | Vulnerability · Source |
| CVE-2026-53266 | suse_vex | SUSE CVE CVE-2026-53266 | first fixed: 2 known affected: 529 known not affected: 93 recommended: 326 | 2026-07-28T17:12:43+00:00 | Vulnerability · Source |
| CVE-2026-53274 | suse_vex | SUSE CVE CVE-2026-53274 | first fixed: 2 known affected: 489 known not affected: 133 recommended: 265 | 2026-07-28T17:12:41+00:00 | Vulnerability · Source |
| CVE-2026-53285 | suse_vex | SUSE CVE CVE-2026-53285 | first fixed: 2 known affected: 489 known not affected: 133 recommended: 265 | 2026-07-28T17:12:38+00:00 | Vulnerability · Source |
| CVE-2026-53287 | suse_vex | SUSE CVE CVE-2026-53287 | first fixed: 2 known affected: 590 recommended: 302 | 2026-07-28T17:12:36+00:00 | Vulnerability · Source |
| CVE-2026-53306 | suse_vex | SUSE CVE CVE-2026-53306 | first fixed: 2 known affected: 622 recommended: 265 | 2026-07-28T17:12:35+00:00 | Vulnerability · Source |
| CVE-2026-53342 | suse_vex | SUSE CVE CVE-2026-53342 | known affected: 135 known not affected: 146 | 2026-07-28T17:12:33+00:00 | Vulnerability · Source |
| CVE-2026-53357 | suse_vex | SUSE CVE CVE-2026-53357 | known affected: 557 known not affected: 33 recommended: 151 | 2026-07-28T17:12:31+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-54369 | suse_vex | SUSE CVE CVE-2026-54369 | known affected: 194 recommended: 14 | 2026-07-28T17:12:20+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-56391 | suse_vex | SUSE CVE CVE-2026-56391 | known affected: 89 | 2026-07-28T17:12:05+00:00 | Vulnerability · Source |
| CVE-2026-56392 | suse_vex | SUSE CVE CVE-2026-56392 | known affected: 89 | 2026-07-28T17:12:04+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-57062 | suse_vex | SUSE CVE CVE-2026-57062 | known affected: 17 known not affected: 56 recommended: 33 | 2026-07-28T17:11:56+00:00 | Vulnerability · Source |
| 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-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 |