VEX records
Browse vendor VEX statements available in this Vulnerability-Lookup instance and pivot to the related vulnerability.
286733 VEX records
API response| Vulnerability | Source | Title | Product status | Imported | Links |
|---|---|---|---|---|---|
| CVE-2026-46119 | suse_vex | SUSE CVE CVE-2026-46119 | first fixed: 2 known affected: 512 known not affected: 93 recommended: 298 | 2026-07-30T16:46:16+00:00 | Vulnerability · Source |
| CVE-2026-46152 | suse_vex | SUSE CVE CVE-2026-46152 | known affected: 424 known not affected: 208 recommended: 205 | 2026-07-30T16:46:13+00:00 | Vulnerability · Source |
| CVE-2026-46189 | suse_vex | SUSE CVE CVE-2026-46189 | known affected: 289 known not affected: 6 recommended: 46 | 2026-07-30T16:46:07+00:00 | Vulnerability · Source |
| CVE-2026-46300 | suse_vex | SUSE CVE CVE-2026-46300 | first fixed: 2 known affected: 421 known not affected: 4 recommended: 836 | 2026-07-30T16:45:59+00:00 | Vulnerability · Source |
| CVE-2026-46316 | suse_vex | SUSE CVE CVE-2026-46316 | first fixed: 2 known affected: 411 known not affected: 278 recommended: 259 | 2026-07-30T16:45:57+00:00 | Vulnerability · Source |
| CVE-2026-46317 | suse_vex | SUSE CVE CVE-2026-46317 | first fixed: 2 known affected: 394 known not affected: 278 recommended: 176 | 2026-07-30T16:45:55+00:00 | Vulnerability · Source |
| CVE-2026-46323 | suse_vex | SUSE CVE CVE-2026-46323 | known not affected: 293 recommended: 284 | 2026-07-30T16:45:52+00:00 | Vulnerability · Source |
| CVE-2026-46354 | suse_vex | SUSE CVE CVE-2026-46354 | No product status | 2026-07-30T16:45:49+00:00 | Vulnerability · Source |
| CVE-2026-46356 | suse_vex | SUSE CVE CVE-2026-46356 | No product status | 2026-07-30T16:45:48+00:00 | Vulnerability · Source |
| CVE-2026-46377 | suse_vex | SUSE CVE CVE-2026-46377 | No product status | 2026-07-30T16:45:44+00:00 | Vulnerability · Source |
| CVE-2026-46378 | suse_vex | SUSE CVE CVE-2026-46378 | No product status | 2026-07-30T16:45:42+00:00 | Vulnerability · Source |
| CVE-2026-46403 | suse_vex | SUSE CVE CVE-2026-46403 | No product status | 2026-07-30T16:45:41+00:00 | Vulnerability · Source |
| CVE-2026-46410 | suse_vex | SUSE CVE CVE-2026-46410 | No product status | 2026-07-30T16:45:39+00:00 | Vulnerability · Source |
| CVE-2026-46415 | suse_vex | SUSE CVE CVE-2026-46415 | No product status | 2026-07-30T16:45:37+00:00 | Vulnerability · Source |
| CVE-2026-46430 | suse_vex | SUSE CVE CVE-2026-46430 | No product status | 2026-07-30T16:45:35+00:00 | Vulnerability · Source |
| CVE-2026-46431 | suse_vex | SUSE CVE CVE-2026-46431 | No product status | 2026-07-30T16:45:34+00:00 | Vulnerability · Source |
| CVE-2026-46599 | suse_vex | SUSE CVE CVE-2026-46599 | No product status | 2026-07-30T16:45:30+00:00 | Vulnerability · Source |
| CVE-2026-46602 | suse_vex | SUSE CVE CVE-2026-46602 | No product status | 2026-07-30T16:45:28+00:00 | Vulnerability · Source |
| CVE-2026-46612 | suse_vex | SUSE CVE CVE-2026-46612 | No product status | 2026-07-30T16:45:26+00:00 | Vulnerability · Source |
| CVE-2026-46614 | suse_vex | SUSE CVE CVE-2026-46614 | No product status | 2026-07-30T16:45:24+00:00 | Vulnerability · Source |
| CVE-2026-46617 | suse_vex | SUSE CVE CVE-2026-46617 | No product status | 2026-07-30T16:45:22+00:00 | Vulnerability · Source |
| CVE-2026-46618 | suse_vex | SUSE CVE CVE-2026-46618 | No product status | 2026-07-30T16:45:20+00:00 | Vulnerability · Source |
| CVE-2026-46668 | suse_vex | SUSE CVE CVE-2026-46668 | No product status | 2026-07-30T16:45:18+00:00 | Vulnerability · Source |
| CVE-2026-46695 | suse_vex | SUSE CVE CVE-2026-46695 | No product status | 2026-07-30T16:45:16+00:00 | Vulnerability · Source |
| CVE-2026-46703 | suse_vex | SUSE CVE CVE-2026-46703 | No product status | 2026-07-30T16:45:14+00:00 | Vulnerability · Source |
| CVE-2026-46716 | suse_vex | SUSE CVE CVE-2026-46716 | No product status | 2026-07-30T16:45:13+00:00 | Vulnerability · Source |
| CVE-2026-46717 | suse_vex | SUSE CVE CVE-2026-46717 | No product status | 2026-07-30T16:45:11+00:00 | Vulnerability · Source |
| CVE-2026-47120 | suse_vex | SUSE CVE CVE-2026-47120 | No product status | 2026-07-30T16:45:06+00:00 | Vulnerability · Source |
| CVE-2026-47124 | suse_vex | SUSE CVE CVE-2026-47124 | No product status | 2026-07-30T16:45:04+00:00 | Vulnerability · Source |
| CVE-2026-47125 | suse_vex | SUSE CVE CVE-2026-47125 | No product status | 2026-07-30T16:45:03+00:00 | Vulnerability · Source |
| CVE-2026-47179 | suse_vex | SUSE CVE CVE-2026-47179 | No product status | 2026-07-30T16:45:02+00:00 | Vulnerability · Source |
| CVE-2026-47190 | suse_vex | SUSE CVE CVE-2026-47190 | No product status | 2026-07-30T16:45:00+00:00 | Vulnerability · Source |
| CVE-2026-47203 | suse_vex | SUSE CVE CVE-2026-47203 | No product status | 2026-07-30T16:44:59+00:00 | Vulnerability · Source |
| CVE-2026-59849 | redhat_vex | libssh: libssh: denial of service via automatic certificate authentication loop | fixed: 4 known affected: 4 known not affected: 8 | 2026-07-30T16:44:50+00:00 | Vulnerability · Source |
| CVE-2026-47267 | suse_vex | SUSE CVE CVE-2026-47267 | No product status | 2026-07-30T16:44:49+00:00 | Vulnerability · Source |
| CVE-2026-47268 | suse_vex | SUSE CVE CVE-2026-47268 | No product status | 2026-07-30T16:44:48+00:00 | Vulnerability · Source |
| CVE-2026-47671 | suse_vex | SUSE CVE CVE-2026-47671 | No product status | 2026-07-30T16:44:46+00:00 | Vulnerability · Source |
| CVE-2026-47703 | suse_vex | SUSE CVE CVE-2026-47703 | No product status | 2026-07-30T16:44:41+00:00 | Vulnerability · Source |
| CVE-2026-47724 | suse_vex | SUSE CVE CVE-2026-47724 | No product status | 2026-07-30T16:44:37+00:00 | Vulnerability · Source |
| CVE-2026-47768 | suse_vex | SUSE CVE CVE-2026-47768 | No product status | 2026-07-30T16:44:31+00:00 | Vulnerability · Source |
| CVE-2026-48025 | suse_vex | SUSE CVE CVE-2026-48025 | No product status | 2026-07-30T16:44:28+00:00 | Vulnerability · Source |
| CVE-2026-48089 | suse_vex | SUSE CVE CVE-2026-48089 | No product status | 2026-07-30T16:44:23+00:00 | Vulnerability · Source |
| CVE-2026-48096 | suse_vex | SUSE CVE CVE-2026-48096 | No product status | 2026-07-30T16:44:21+00:00 | Vulnerability · Source |
| CVE-2026-48126 | suse_vex | SUSE CVE CVE-2026-48126 | No product status | 2026-07-30T16:44:18+00:00 | Vulnerability · Source |
| CVE-2026-48529 | suse_vex | SUSE CVE CVE-2026-48529 | No product status | 2026-07-30T16:44:15+00:00 | Vulnerability · Source |
| CVE-2026-48708 | suse_vex | SUSE CVE CVE-2026-48708 | No product status | 2026-07-30T16:44:13+00:00 | Vulnerability · Source |
| CVE-2026-48709 | suse_vex | SUSE CVE CVE-2026-48709 | No product status | 2026-07-30T16:44:11+00:00 | Vulnerability · Source |
| CVE-2026-48777 | suse_vex | SUSE CVE CVE-2026-48777 | No product status | 2026-07-30T16:44:09+00:00 | Vulnerability · Source |
| CVE-2026-48779 | suse_vex | SUSE CVE CVE-2026-48779 | known affected: 92 known not affected: 326 recommended: 21 | 2026-07-30T16:44:08+00:00 | Vulnerability · Source |
| CVE-2026-48788 | suse_vex | SUSE CVE CVE-2026-48788 | No product status | 2026-07-30T16:44:07+00:00 | Vulnerability · Source |