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-100775 | suse_vex | SUSE CVE CVE-2026-100775 | known affected: 164 recommended: 83 | 2026-10-15T23:45:52+00:00 | Vulnerability · Source |
| CVE-2026-100776 | suse_vex | SUSE CVE CVE-2026-100776 | known affected: 164 recommended: 83 | 2026-10-15T23:45:50+00:00 | Vulnerability · Source |
| CVE-2026-100777 | suse_vex | SUSE CVE CVE-2026-100777 | known affected: 80 recommended: 83 | 2026-10-15T23:45:48+00:00 | Vulnerability · Source |
| CVE-2026-100778 | suse_vex | SUSE CVE CVE-2026-100778 | known affected: 80 recommended: 83 | 2026-10-15T23:45:45+00:00 | Vulnerability · Source |
| CVE-2026-100779 | suse_vex | SUSE CVE CVE-2026-100779 | known affected: 164 recommended: 83 | 2026-10-15T23:45:43+00:00 | Vulnerability · Source |
| CVE-2026-100780 | suse_vex | SUSE CVE CVE-2026-100780 | known affected: 80 recommended: 83 | 2026-10-15T23:45:41+00:00 | Vulnerability · Source |
| CVE-2026-100781 | suse_vex | SUSE CVE CVE-2026-100781 | known affected: 80 recommended: 83 | 2026-10-15T23:45:38+00:00 | Vulnerability · Source |
| CVE-2026-100782 | suse_vex | SUSE CVE CVE-2026-100782 | known affected: 80 recommended: 83 | 2026-10-15T23:45:36+00:00 | Vulnerability · Source |
| CVE-2026-100783 | suse_vex | SUSE CVE CVE-2026-100783 | known affected: 80 recommended: 83 | 2026-10-15T23:45:34+00:00 | Vulnerability · Source |
| CVE-2026-100784 | suse_vex | SUSE CVE CVE-2026-100784 | known affected: 80 recommended: 83 | 2026-10-15T23:45:31+00:00 | Vulnerability · Source |
| CVE-2026-100785 | suse_vex | SUSE CVE CVE-2026-100785 | known affected: 80 recommended: 83 | 2026-10-15T23:45:28+00:00 | Vulnerability · Source |
| CVE-2026-100786 | suse_vex | SUSE CVE CVE-2026-100786 | known affected: 80 recommended: 83 | 2026-10-15T23:45:26+00:00 | Vulnerability · Source |
| CVE-2026-100788 | suse_vex | SUSE CVE CVE-2026-100788 | known affected: 80 recommended: 83 | 2026-10-15T23:45:24+00:00 | Vulnerability · Source |
| CVE-2026-100789 | suse_vex | SUSE CVE CVE-2026-100789 | known affected: 164 recommended: 83 | 2026-10-15T23:45:22+00:00 | Vulnerability · Source |
| CVE-2026-100790 | suse_vex | SUSE CVE CVE-2026-100790 | known affected: 164 recommended: 83 | 2026-10-15T23:45:20+00:00 | Vulnerability · Source |
| CVE-2026-100791 | suse_vex | SUSE CVE CVE-2026-100791 | known affected: 80 recommended: 83 | 2026-10-15T23:45:17+00:00 | Vulnerability · Source |
| CVE-2026-100792 | suse_vex | SUSE CVE CVE-2026-100792 | known affected: 80 recommended: 83 | 2026-10-15T23:45:15+00:00 | Vulnerability · Source |
| CVE-2026-100794 | suse_vex | SUSE CVE CVE-2026-100794 | known affected: 164 recommended: 83 | 2026-10-15T23:45:13+00:00 | Vulnerability · Source |
| CVE-2026-100797 | suse_vex | SUSE CVE CVE-2026-100797 | known affected: 80 recommended: 83 | 2026-10-15T23:45:10+00:00 | Vulnerability · Source |
| CVE-2026-100801 | suse_vex | SUSE CVE CVE-2026-100801 | known affected: 80 recommended: 83 | 2026-10-15T23:45:08+00:00 | Vulnerability · Source |
| CVE-2026-100803 | suse_vex | SUSE CVE CVE-2026-100803 | known affected: 80 recommended: 83 | 2026-10-15T23:45:06+00:00 | Vulnerability · Source |
| CVE-2026-100807 | suse_vex | SUSE CVE CVE-2026-100807 | known affected: 80 recommended: 83 | 2026-10-15T23:45:04+00:00 | Vulnerability · Source |
| CVE-2026-100811 | suse_vex | SUSE CVE CVE-2026-100811 | known affected: 80 recommended: 83 | 2026-10-15T23:45:02+00:00 | Vulnerability · Source |
| CVE-2026-100818 | suse_vex | SUSE CVE CVE-2026-100818 | known affected: 164 recommended: 83 | 2026-10-15T23:44:59+00:00 | Vulnerability · Source |
| CVE-2026-100819 | suse_vex | SUSE CVE CVE-2026-100819 | known affected: 80 recommended: 83 | 2026-10-15T23:44:57+00:00 | Vulnerability · Source |
| CVE-2026-100820 | suse_vex | SUSE CVE CVE-2026-100820 | known affected: 80 recommended: 83 | 2026-10-15T23:44:54+00:00 | Vulnerability · Source |
| CVE-2026-100821 | suse_vex | SUSE CVE CVE-2026-100821 | known affected: 80 recommended: 83 | 2026-10-15T23:44:52+00:00 | Vulnerability · Source |
| CVE-2026-100832 | suse_vex | SUSE CVE CVE-2026-100832 | known affected: 80 recommended: 83 | 2026-10-15T23:44:50+00:00 | Vulnerability · Source |
| CVE-2026-101276 | suse_vex | SUSE CVE CVE-2026-101276 | known affected: 22 | 2026-10-15T23:44:44+00:00 | Vulnerability · Source |
| CVE-2026-101283 | suse_vex | SUSE CVE CVE-2026-101283 | known affected: 22 | 2026-10-15T23:44:41+00:00 | Vulnerability · Source |
| CVE-2026-102276 | suse_vex | SUSE CVE CVE-2026-102276 | known affected: 261 known not affected: 328 | 2026-10-15T23:44:37+00:00 | Vulnerability · Source |
| CVE-2026-102278 | suse_vex | SUSE CVE CVE-2026-102278 | known affected: 260 known not affected: 328 | 2026-10-15T23:44:32+00:00 | Vulnerability · Source |
| CVE-2026-102633 | suse_vex | SUSE CVE CVE-2026-102633 | known affected: 163 recommended: 5 | 2026-10-15T23:44:13+00:00 | Vulnerability · Source |
| CVE-2026-102635 | suse_vex | SUSE CVE CVE-2026-102635 | known affected: 368 known not affected: 8 | 2026-10-15T23:44:11+00:00 | Vulnerability · Source |
| CVE-2026-103242 | suse_vex | SUSE CVE CVE-2026-103242 | known affected: 36 known not affected: 155 | 2026-10-15T23:43:58+00:00 | Vulnerability · Source |
| CVE-2026-103500 | suse_vex | SUSE CVE CVE-2026-103500 | known affected: 164 | 2026-10-15T23:43:46+00:00 | Vulnerability · Source |
| CVE-2026-103923 | suse_vex | SUSE CVE CVE-2026-103923 | No product status | 2026-10-15T23:43:44+00:00 | Vulnerability · Source |
| CVE-2026-104029 | suse_vex | SUSE CVE CVE-2026-104029 | known affected: 558 known not affected: 381 | 2026-10-15T23:43:38+00:00 | Vulnerability · Source |
| CVE-2026-104844 | suse_vex | SUSE CVE CVE-2026-104844 | known affected: 251 known not affected: 328 recommended: 4 | 2026-10-15T23:43:35+00:00 | Vulnerability · Source |
| CVE-2026-105712 | suse_vex | SUSE CVE CVE-2026-105712 | known affected: 114 | 2026-10-15T23:43:29+00:00 | Vulnerability · Source |
| CVE-2026-106061 | suse_vex | SUSE CVE CVE-2026-106061 | known affected: 26 | 2026-10-15T23:43:27+00:00 | Vulnerability · Source |
| CVE-2026-106062 | suse_vex | SUSE CVE CVE-2026-106062 | known affected: 26 | 2026-10-15T23:43:25+00:00 | Vulnerability · Source |
| CVE-2026-106063 | suse_vex | SUSE CVE CVE-2026-106063 | known affected: 26 | 2026-10-15T23:43:23+00:00 | Vulnerability · Source |
| CVE-2026-106552 | suse_vex | SUSE CVE CVE-2026-106552 | known affected: 269 | 2026-10-15T23:43:21+00:00 | Vulnerability · Source |
| CVE-2026-106553 | suse_vex | SUSE CVE CVE-2026-106553 | known affected: 269 | 2026-10-15T23:43:19+00:00 | Vulnerability · Source |
| CVE-2026-106555 | suse_vex | SUSE CVE CVE-2026-106555 | known affected: 269 | 2026-10-15T23:43:18+00:00 | Vulnerability · Source |
| CVE-2026-106582 | suse_vex | SUSE CVE CVE-2026-106582 | known affected: 269 | 2026-10-15T23:43:16+00:00 | Vulnerability · Source |
| CVE-2026-106583 | suse_vex | SUSE CVE CVE-2026-106583 | known affected: 269 | 2026-10-15T23:43:14+00:00 | Vulnerability · Source |
| CVE-2026-106584 | suse_vex | SUSE CVE CVE-2026-106584 | known affected: 269 | 2026-10-15T23:43:12+00:00 | Vulnerability · Source |
| CVE-2026-106585 | suse_vex | SUSE CVE CVE-2026-106585 | known affected: 269 | 2026-10-15T23:43:10+00:00 | Vulnerability · Source |