VEX records
Browse vendor VEX statements available in this Vulnerability-Lookup instance and pivot to the related vulnerability.
104719 VEX records
API response| Vulnerability | Source | Title | Product status | Imported | Links |
|---|---|---|---|---|---|
| CVE-2026-47563 | suse_vex | SUSE CVE CVE-2026-47563 | known affected: 152 recommended: 4 | 2026-10-16T00:20:06+00:00 | Vulnerability · Source |
| CVE-2026-47565 | suse_vex | SUSE CVE CVE-2026-47565 | known affected: 152 recommended: 4 | 2026-10-16T00:20:01+00:00 | Vulnerability · Source |
| CVE-2026-47566 | suse_vex | SUSE CVE CVE-2026-47566 | known affected: 152 recommended: 4 | 2026-10-16T00:19:59+00:00 | Vulnerability · Source |
| CVE-2026-47567 | suse_vex | SUSE CVE CVE-2026-47567 | known affected: 152 recommended: 4 | 2026-10-16T00:19:56+00:00 | Vulnerability · Source |
| CVE-2026-47568 | suse_vex | SUSE CVE CVE-2026-47568 | known affected: 152 recommended: 4 | 2026-10-16T00:19:54+00:00 | Vulnerability · Source |
| CVE-2026-47569 | suse_vex | SUSE CVE CVE-2026-47569 | known affected: 152 recommended: 9 | 2026-10-16T00:19:52+00:00 | Vulnerability · Source |
| CVE-2026-47572 | suse_vex | SUSE CVE CVE-2026-47572 | known affected: 152 recommended: 9 | 2026-10-16T00:19:49+00:00 | Vulnerability · Source |
| CVE-2026-47586 | suse_vex | SUSE CVE CVE-2026-47586 | known affected: 152 recommended: 4 | 2026-10-16T00:19:47+00:00 | Vulnerability · Source |
| CVE-2026-47587 | suse_vex | SUSE CVE CVE-2026-47587 | known affected: 152 recommended: 9 | 2026-10-16T00:19:45+00:00 | Vulnerability · Source |
| CVE-2026-47588 | suse_vex | SUSE CVE CVE-2026-47588 | known affected: 152 recommended: 4 | 2026-10-16T00:19:42+00:00 | Vulnerability · Source |
| CVE-2026-47589 | suse_vex | SUSE CVE CVE-2026-47589 | known affected: 152 recommended: 4 | 2026-10-16T00:19:40+00:00 | Vulnerability · Source |
| CVE-2026-47590 | suse_vex | SUSE CVE CVE-2026-47590 | known affected: 152 recommended: 4 | 2026-10-16T00:19:38+00:00 | Vulnerability · Source |
| CVE-2026-47591 | suse_vex | SUSE CVE CVE-2026-47591 | known affected: 152 recommended: 9 | 2026-10-16T00:19:36+00:00 | Vulnerability · Source |
| CVE-2026-47592 | suse_vex | SUSE CVE CVE-2026-47592 | known affected: 152 recommended: 9 | 2026-10-16T00:19:33+00:00 | Vulnerability · Source |
| CVE-2026-47594 | suse_vex | SUSE CVE CVE-2026-47594 | known affected: 152 recommended: 4 | 2026-10-16T00:19:31+00:00 | Vulnerability · Source |
| CVE-2026-47595 | suse_vex | SUSE CVE CVE-2026-47595 | known affected: 152 recommended: 4 | 2026-10-16T00:19:29+00:00 | Vulnerability · Source |
| CVE-2026-47596 | suse_vex | SUSE CVE CVE-2026-47596 | known affected: 152 recommended: 9 | 2026-10-16T00:19:27+00:00 | Vulnerability · Source |
| CVE-2026-47597 | suse_vex | SUSE CVE CVE-2026-47597 | known affected: 152 recommended: 9 | 2026-10-16T00:19:25+00:00 | Vulnerability · Source |
| CVE-2026-47598 | suse_vex | SUSE CVE CVE-2026-47598 | known affected: 152 recommended: 4 | 2026-10-16T00:19:24+00:00 | Vulnerability · Source |
| CVE-2026-47599 | suse_vex | SUSE CVE CVE-2026-47599 | known affected: 152 recommended: 9 | 2026-10-16T00:19:22+00:00 | Vulnerability · Source |
| CVE-2026-47600 | suse_vex | SUSE CVE CVE-2026-47600 | known affected: 152 recommended: 4 | 2026-10-16T00:19:20+00:00 | Vulnerability · Source |
| CVE-2026-47601 | suse_vex | SUSE CVE CVE-2026-47601 | known affected: 152 recommended: 4 | 2026-10-16T00:19:18+00:00 | Vulnerability · Source |
| CVE-2026-47602 | suse_vex | SUSE CVE CVE-2026-47602 | known affected: 152 recommended: 9 | 2026-10-16T00:19:16+00:00 | Vulnerability · Source |
| CVE-2026-47603 | suse_vex | SUSE CVE CVE-2026-47603 | known affected: 152 recommended: 4 | 2026-10-16T00:19:15+00:00 | Vulnerability · Source |
| CVE-2026-47604 | suse_vex | SUSE CVE CVE-2026-47604 | known affected: 152 recommended: 4 | 2026-10-16T00:19:13+00:00 | Vulnerability · Source |
| CVE-2026-48142 | suse_vex | SUSE CVE CVE-2026-48142 | known affected: 24 recommended: 42 | 2026-10-16T00:19:11+00:00 | Vulnerability · Source |
| CVE-2026-48496 | suse_vex | SUSE CVE CVE-2026-48496 | known affected: 7 recommended: 1 | 2026-10-16T00:19:09+00:00 | Vulnerability · Source |
| CVE-2026-48856 | suse_vex | SUSE CVE CVE-2026-48856 | known affected: 16 recommended: 84 | 2026-10-16T00:19:01+00:00 | Vulnerability · Source |
| CVE-2026-49356 | suse_vex | SUSE CVE CVE-2026-49356 | known affected: 118 known not affected: 441 recommended: 2 | 2026-10-16T00:18:59+00:00 | Vulnerability · Source |
| CVE-2026-49478 | suse_vex | SUSE CVE CVE-2026-49478 | known affected: 89 known not affected: 214 | 2026-10-16T00:18:56+00:00 | Vulnerability · Source |
| CVE-2026-49982 | suse_vex | SUSE CVE CVE-2026-49982 | known not affected: 513 | 2026-10-16T00:18:54+00:00 | Vulnerability · Source |
| CVE-2026-52791 | suse_vex | SUSE CVE CVE-2026-52791 | known affected: 420 recommended: 14 | 2026-10-16T00:18:49+00:00 | Vulnerability · Source |
| CVE-2026-52865 | suse_vex | SUSE CVE CVE-2026-52865 | known affected: 61 | 2026-10-16T00:18:47+00:00 | Vulnerability · Source |
| CVE-2026-53017 | suse_vex | SUSE CVE CVE-2026-53017 | known affected: 287 known not affected: 4 | 2026-10-16T00:18:29+00:00 | Vulnerability · Source |
| CVE-2026-53292 | suse_vex | SUSE CVE CVE-2026-53292 | known affected: 291 | 2026-10-16T00:18:01+00:00 | Vulnerability · Source |
| CVE-2026-53550 | suse_vex | SUSE CVE CVE-2026-53550 | known affected: 428 known not affected: 111 recommended: 10 | 2026-10-16T00:17:45+00:00 | Vulnerability · Source |
| CVE-2026-53910 | suse_vex | SUSE CVE CVE-2026-53910 | known affected: 76 | 2026-10-16T00:17:32+00:00 | Vulnerability · Source |
| CVE-2026-54465 | suse_vex | SUSE CVE CVE-2026-54465 | known affected: 14 known not affected: 498 | 2026-10-16T00:17:23+00:00 | Vulnerability · Source |
| CVE-2026-54876 | suse_vex | SUSE CVE CVE-2026-54876 | known not affected: 619 | 2026-10-16T00:17:18+00:00 | Vulnerability · Source |
| CVE-2026-54904 | suse_vex | SUSE CVE CVE-2026-54904 | known affected: 86 known not affected: 5 | 2026-10-16T00:17:16+00:00 | Vulnerability · Source |
| CVE-2026-54905 | suse_vex | SUSE CVE CVE-2026-54905 | known affected: 86 known not affected: 5 | 2026-10-16T00:17:14+00:00 | Vulnerability · Source |
| CVE-2026-54906 | suse_vex | SUSE CVE CVE-2026-54906 | known affected: 86 known not affected: 5 | 2026-10-16T00:17:13+00:00 | Vulnerability · Source |
| CVE-2026-55686 | suse_vex | SUSE CVE CVE-2026-55686 | known affected: 423 known not affected: 16 recommended: 64 | 2026-10-16T00:17:05+00:00 | Vulnerability · Source |
| CVE-2026-55723 | suse_vex | SUSE CVE CVE-2026-55723 | known affected: 61 | 2026-10-16T00:17:03+00:00 | Vulnerability · Source |
| CVE-2026-56391 | suse_vex | SUSE CVE CVE-2026-56391 | known affected: 14 known not affected: 96 recommended: 6 | 2026-10-16T00:17:00+00:00 | Vulnerability · Source |
| CVE-2026-56392 | suse_vex | SUSE CVE CVE-2026-56392 | known not affected: 110 recommended: 12 | 2026-10-16T00:16:58+00:00 | Vulnerability · Source |
| CVE-2026-56434 | suse_vex | SUSE CVE CVE-2026-56434 | known affected: 61 recommended: 31 | 2026-10-16T00:16:50+00:00 | Vulnerability · Source |
| CVE-2026-57231 | suse_vex | SUSE CVE CVE-2026-57231 | known affected: 45 recommended: 111 | 2026-10-16T00:16:42+00:00 | Vulnerability · Source |
| CVE-2026-57235 | suse_vex | SUSE CVE CVE-2026-57235 | known affected: 124 known not affected: 5 | 2026-10-16T00:16:38+00:00 | Vulnerability · Source |
| CVE-2026-58374 | suse_vex | SUSE CVE CVE-2026-58374 | known affected: 397 known not affected: 33 recommended: 15 | 2026-10-16T00:16:20+00:00 | Vulnerability · Source |