VEX records
Browse vendor VEX statements available in this Vulnerability-Lookup instance and pivot to the related vulnerability.
305789 VEX records
API response| Vulnerability | Source | Title | Product status | Imported | Links |
|---|---|---|---|---|---|
| CVE-2026-50261 | suse_vex | SUSE CVE CVE-2026-50261 | known affected: 44 recommended: 59 | 2026-10-08T17:14:35+00:00 | Vulnerability · Source |
| CVE-2026-50262 | suse_vex | SUSE CVE CVE-2026-50262 | known affected: 44 recommended: 59 | 2026-10-08T17:14:33+00:00 | Vulnerability · Source |
| CVE-2026-50263 | suse_vex | SUSE CVE CVE-2026-50263 | known affected: 44 recommended: 59 | 2026-10-08T17:14:30+00:00 | Vulnerability · Source |
| CVE-2026-50264 | suse_vex | SUSE CVE CVE-2026-50264 | known affected: 44 known not affected: 9 recommended: 59 | 2026-10-08T17:14:28+00:00 | Vulnerability · Source |
| CVE-2026-50524 | suse_vex | SUSE CVE CVE-2026-50524 | recommended: 148 | 2026-10-08T17:14:26+00:00 | Vulnerability · Source |
| CVE-2026-50525 | suse_vex | SUSE CVE CVE-2026-50525 | recommended: 148 | 2026-10-08T17:14:24+00:00 | Vulnerability · Source |
| CVE-2026-50526 | suse_vex | SUSE CVE CVE-2026-50526 | recommended: 148 | 2026-10-08T17:14:21+00:00 | Vulnerability · Source |
| CVE-2026-50527 | suse_vex | SUSE CVE CVE-2026-50527 | recommended: 148 | 2026-10-08T17:14:19+00:00 | Vulnerability · Source |
| CVE-2026-50528 | suse_vex | SUSE CVE CVE-2026-50528 | recommended: 148 | 2026-10-08T17:14:17+00:00 | Vulnerability · Source |
| CVE-2026-50646 | suse_vex | SUSE CVE CVE-2026-50646 | recommended: 148 | 2026-10-08T17:14:15+00:00 | Vulnerability · Source |
| CVE-2026-50648 | suse_vex | SUSE CVE CVE-2026-50648 | recommended: 148 | 2026-10-08T17:14:13+00:00 | Vulnerability · Source |
| CVE-2026-50649 | suse_vex | SUSE CVE CVE-2026-50649 | recommended: 148 | 2026-10-08T17:14:11+00:00 | Vulnerability · Source |
| CVE-2026-50650 | suse_vex | SUSE CVE CVE-2026-50650 | recommended: 148 | 2026-10-08T17:14:08+00:00 | Vulnerability · Source |
| CVE-2026-50651 | suse_vex | SUSE CVE CVE-2026-50651 | recommended: 148 | 2026-10-08T17:14:06+00:00 | Vulnerability · Source |
| CVE-2026-50659 | suse_vex | SUSE CVE CVE-2026-50659 | recommended: 148 | 2026-10-08T17:14:04+00:00 | Vulnerability · Source |
| CVE-2026-50721 | suse_vex | SUSE CVE CVE-2026-50721 | recommended: 5 | 2026-10-08T17:14:02+00:00 | Vulnerability · Source |
| CVE-2026-50722 | suse_vex | SUSE CVE CVE-2026-50722 | recommended: 5 | 2026-10-08T17:14:00+00:00 | Vulnerability · Source |
| CVE-2026-50812 | suse_vex | SUSE CVE CVE-2026-50812 | known not affected: 223 | 2026-10-08T17:13:58+00:00 | Vulnerability · Source |
| CVE-2026-51235 | suse_vex | SUSE CVE CVE-2026-51235 | recommended: 4 | 2026-10-08T17:13:56+00:00 | Vulnerability · Source |
| CVE-2026-52718 | suse_vex | SUSE CVE CVE-2026-52718 | known affected: 427 known not affected: 370 recommended: 403 | 2026-10-08T17:13:54+00:00 | Vulnerability · Source |
| CVE-2026-52719 | suse_vex | SUSE CVE CVE-2026-52719 | known affected: 88 known not affected: 423 recommended: 510 | 2026-10-08T17:13:51+00:00 | Vulnerability · Source |
| CVE-2026-52720 | suse_vex | SUSE CVE CVE-2026-52720 | known affected: 304 recommended: 790 | 2026-10-08T17:13:49+00:00 | Vulnerability · Source |
| CVE-2026-52722 | suse_vex | SUSE CVE CVE-2026-52722 | known affected: 304 recommended: 711 | 2026-10-08T17:13:46+00:00 | Vulnerability · Source |
| CVE-2026-52912 | suse_vex | SUSE CVE CVE-2026-52912 | known affected: 631 known not affected: 6 recommended: 401 | 2026-10-08T17:13:42+00:00 | Vulnerability · Source |
| CVE-2026-52929 | suse_vex | SUSE CVE CVE-2026-52929 | known affected: 500 known not affected: 125 recommended: 424 | 2026-10-08T17:13:40+00:00 | Vulnerability · Source |
| CVE-2026-52977 | suse_vex | SUSE CVE CVE-2026-52977 | known affected: 450 known not affected: 175 recommended: 465 | 2026-10-08T17:13:37+00:00 | Vulnerability · Source |
| CVE-2026-53059 | suse_vex | SUSE CVE CVE-2026-53059 | known affected: 567 recommended: 578 | 2026-10-08T17:13:34+00:00 | Vulnerability · Source |
| CVE-2026-53108 | suse_vex | SUSE CVE CVE-2026-53108 | known affected: 212 known not affected: 175 | 2026-10-08T17:13:31+00:00 | Vulnerability · Source |
| CVE-2026-53163 | suse_vex | SUSE CVE CVE-2026-53163 | known affected: 456 known not affected: 111 recommended: 462 | 2026-10-08T17:13:29+00:00 | Vulnerability · Source |
| CVE-2026-53166 | suse_vex | SUSE CVE CVE-2026-53166 | recommended: 169 | 2026-10-08T17:13:28+00:00 | Vulnerability · Source |
| CVE-2026-53260 | suse_vex | SUSE CVE CVE-2026-53260 | known affected: 425 known not affected: 183 recommended: 444 | 2026-10-08T17:13:25+00:00 | Vulnerability · Source |
| CVE-2026-53264 | suse_vex | SUSE CVE CVE-2026-53264 | known affected: 537 known not affected: 34 recommended: 530 | 2026-10-08T17:13:23+00:00 | Vulnerability · Source |
| CVE-2026-53384 | suse_vex | SUSE CVE CVE-2026-53384 | known affected: 261 known not affected: 147 recommended: 4 | 2026-10-08T17:13:18+00:00 | Vulnerability · Source |
| CVE-2026-53388 | suse_vex | SUSE CVE CVE-2026-53388 | known affected: 396 known not affected: 147 recommended: 471 | 2026-10-08T17:13:15+00:00 | Vulnerability · Source |
| CVE-2026-53404 | suse_vex | SUSE CVE CVE-2026-53404 | known affected: 324 known not affected: 69 recommended: 243 | 2026-10-08T17:13:12+00:00 | Vulnerability · Source |
| CVE-2026-53434 | suse_vex | SUSE CVE CVE-2026-53434 | known affected: 324 known not affected: 70 recommended: 243 | 2026-10-08T17:13:09+00:00 | Vulnerability · Source |
| CVE-2026-53587 | suse_vex | SUSE CVE CVE-2026-53587 | known affected: 112 recommended: 47 | 2026-10-08T17:13:06+00:00 | Vulnerability · Source |
| CVE-2026-53703 | suse_vex | SUSE CVE CVE-2026-53703 | known affected: 13 recommended: 3 | 2026-10-08T17:13:04+00:00 | Vulnerability · Source |
| CVE-2026-53704 | suse_vex | SUSE CVE CVE-2026-53704 | known affected: 13 recommended: 3 | 2026-10-08T17:13:01+00:00 | Vulnerability · Source |
| CVE-2026-53938 | suse_vex | SUSE CVE CVE-2026-53938 | known affected: 49 recommended: 40 | 2026-10-08T17:12:58+00:00 | Vulnerability · Source |
| CVE-2026-54369 | suse_vex | SUSE CVE CVE-2026-54369 | known affected: 449 recommended: 174 | 2026-10-08T17:12:56+00:00 | Vulnerability · Source |
| CVE-2026-54411 | suse_vex | SUSE CVE CVE-2026-54411 | known affected: 613 recommended: 88 | 2026-10-08T17:12:54+00:00 | Vulnerability · Source |
| CVE-2026-54512 | suse_vex | SUSE CVE CVE-2026-54512 | known affected: 12 recommended: 119 | 2026-10-08T17:12:52+00:00 | Vulnerability · Source |
| CVE-2026-54513 | suse_vex | SUSE CVE CVE-2026-54513 | known affected: 12 recommended: 149 | 2026-10-08T17:12:50+00:00 | Vulnerability · Source |
| CVE-2026-54789 | suse_vex | SUSE CVE CVE-2026-54789 | known affected: 12 recommended: 25 | 2026-10-08T17:12:48+00:00 | Vulnerability · Source |
| CVE-2026-55193 | suse_vex | SUSE CVE CVE-2026-55193 | known affected: 167 recommended: 36 | 2026-10-08T17:12:46+00:00 | Vulnerability · Source |
| CVE-2026-55194 | suse_vex | SUSE CVE CVE-2026-55194 | known affected: 167 recommended: 36 | 2026-10-08T17:12:44+00:00 | Vulnerability · Source |
| CVE-2026-55276 | suse_vex | SUSE CVE CVE-2026-55276 | known affected: 324 known not affected: 69 recommended: 243 | 2026-10-08T17:12:42+00:00 | Vulnerability · Source |
| CVE-2026-55677 | suse_vex | SUSE CVE CVE-2026-55677 | recommended: 6 | 2026-10-08T17:12:39+00:00 | Vulnerability · Source |
| CVE-2026-55955 | suse_vex | SUSE CVE CVE-2026-55955 | known affected: 325 known not affected: 69 recommended: 243 | 2026-10-08T17:12:36+00:00 | Vulnerability · Source |