VEX records
Browse vendor VEX statements available in this Vulnerability-Lookup instance and pivot to the related vulnerability.
291925 VEX records
API response| Vulnerability | Source | Title | Product status | Imported | Links |
|---|---|---|---|---|---|
| CVE-2026-17755 | suse_vex | SUSE CVE CVE-2026-17755 | recommended: 6 | 2026-08-05T00:42:12+00:00 | Vulnerability · Source |
| CVE-2026-17756 | suse_vex | SUSE CVE CVE-2026-17756 | recommended: 6 | 2026-08-05T00:42:10+00:00 | Vulnerability · Source |
| CVE-2026-17787 | suse_vex | SUSE CVE CVE-2026-17787 | recommended: 6 | 2026-08-05T00:42:09+00:00 | Vulnerability · Source |
| CVE-2026-17841 | suse_vex | SUSE CVE CVE-2026-17841 | recommended: 6 | 2026-08-05T00:42:07+00:00 | Vulnerability · Source |
| CVE-2026-18654 | suse_vex | SUSE CVE CVE-2026-18654 | known affected: 31 | 2026-08-05T00:42:05+00:00 | Vulnerability · Source |
| CVE-2026-18739 | suse_vex | SUSE CVE CVE-2026-18739 | known affected: 129 | 2026-08-05T00:42:04+00:00 | Vulnerability · Source |
| CVE-2026-23199 | suse_vex | SUSE CVE CVE-2026-23199 | known affected: 22 known not affected: 318 recommended: 42 | 2026-08-05T00:41:54+00:00 | Vulnerability · Source |
| CVE-2026-29146 | suse_vex | SUSE CVE CVE-2026-29146 | known affected: 82 known not affected: 1 recommended: 439 | 2026-08-05T00:41:10+00:00 | Vulnerability · Source |
| CVE-2026-32274 | suse_vex | SUSE CVE CVE-2026-32274 | recommended: 7 | 2026-08-05T00:40:33+00:00 | Vulnerability · Source |
| CVE-2026-34486 | suse_vex | SUSE CVE CVE-2026-34486 | known affected: 82 known not affected: 1 recommended: 439 | 2026-08-05T00:40:21+00:00 | Vulnerability · Source |
| CVE-2026-35204 | suse_vex | SUSE CVE CVE-2026-35204 | known not affected: 67 recommended: 8 | 2026-08-05T00:40:17+00:00 | Vulnerability · Source |
| CVE-2026-35205 | suse_vex | SUSE CVE CVE-2026-35205 | known not affected: 67 recommended: 8 | 2026-08-05T00:40:16+00:00 | Vulnerability · Source |
| CVE-2026-35206 | suse_vex | SUSE CVE CVE-2026-35206 | known affected: 43 recommended: 48 | 2026-08-05T00:40:15+00:00 | Vulnerability · Source |
| CVE-2026-41506 | suse_vex | SUSE CVE CVE-2026-41506 | known affected: 404 known not affected: 301 recommended: 191 | 2026-08-05T00:39:47+00:00 | Vulnerability · Source |
| CVE-2026-41602 | suse_vex | SUSE CVE CVE-2026-41602 | known affected: 34 known not affected: 396 recommended: 268 | 2026-08-05T00:39:44+00:00 | Vulnerability · Source |
| CVE-2026-41604 | suse_vex | SUSE CVE CVE-2026-41604 | known affected: 30 known not affected: 408 recommended: 150 | 2026-08-05T00:39:42+00:00 | Vulnerability · Source |
| CVE-2026-41605 | suse_vex | SUSE CVE CVE-2026-41605 | known affected: 30 known not affected: 408 recommended: 150 | 2026-08-05T00:39:41+00:00 | Vulnerability · Source |
| CVE-2026-41606 | suse_vex | SUSE CVE CVE-2026-41606 | known affected: 42 known not affected: 396 recommended: 151 | 2026-08-05T00:39:40+00:00 | Vulnerability · Source |
| CVE-2026-42215 | suse_vex | SUSE CVE CVE-2026-42215 | known affected: 38 recommended: 7 | 2026-08-05T00:39:28+00:00 | Vulnerability · Source |
| CVE-2026-42284 | suse_vex | SUSE CVE CVE-2026-42284 | known affected: 38 recommended: 4 | 2026-08-05T00:39:27+00:00 | Vulnerability · Source |
| CVE-2026-42533 | suse_vex | SUSE CVE CVE-2026-42533 | first fixed: 4 known affected: 12 recommended: 38 | 2026-08-05T00:39:19+00:00 | Vulnerability · Source |
| CVE-2026-43227 | suse_vex | SUSE CVE CVE-2026-43227 | known affected: 295 | 2026-08-05T00:38:53+00:00 | Vulnerability · Source |
| CVE-2026-43617 | suse_vex | SUSE CVE CVE-2026-43617 | known affected: 404 known not affected: 2 recommended: 34 | 2026-08-05T00:38:30+00:00 | Vulnerability · Source |
| CVE-2026-43620 | suse_vex | SUSE CVE CVE-2026-43620 | known affected: 406 recommended: 34 | 2026-08-05T00:38:28+00:00 | Vulnerability · Source |
| CVE-2026-43958 | suse_vex | SUSE CVE CVE-2026-43958 | first fixed: 20 known affected: 22 known not affected: 34 recommended: 111 | 2026-08-05T00:38:17+00:00 | Vulnerability · Source |
| CVE-2026-44673 | suse_vex | SUSE CVE CVE-2026-44673 | known affected: 6 recommended: 46 | 2026-08-05T00:37:58+00:00 | Vulnerability · Source |
| CVE-2026-44891 | suse_vex | SUSE CVE CVE-2026-44891 | known not affected: 42 recommended: 22 | 2026-08-05T00:37:54+00:00 | Vulnerability · Source |
| CVE-2026-46150 | suse_vex | SUSE CVE CVE-2026-46150 | first fixed: 2 known affected: 463 known not affected: 6 recommended: 621 | 2026-08-05T00:37:24+00:00 | Vulnerability · Source |
| CVE-2026-47763 | suse_vex | SUSE CVE CVE-2026-47763 | recommended: 4 | 2026-08-05T00:37:00+00:00 | Vulnerability · Source |
| CVE-2026-47764 | suse_vex | SUSE CVE CVE-2026-47764 | recommended: 4 | 2026-08-05T00:36:59+00:00 | Vulnerability · Source |
| CVE-2026-48031 | suse_vex | SUSE CVE CVE-2026-48031 | No product status | 2026-08-05T00:36:57+00:00 | Vulnerability · Source |
| CVE-2026-48113 | suse_vex | SUSE CVE CVE-2026-48113 | No product status | 2026-08-05T00:36:56+00:00 | Vulnerability · Source |
| CVE-2026-49834 | suse_vex | SUSE CVE CVE-2026-49834 | known not affected: 167 | 2026-08-05T00:36:51+00:00 | Vulnerability · Source |
| CVE-2026-52746 | suse_vex | SUSE CVE CVE-2026-52746 | No product status | 2026-08-05T00:36:38+00:00 | Vulnerability · Source |
| CVE-2026-53095 | suse_vex | SUSE CVE CVE-2026-53095 | known affected: 118 known not affected: 177 | 2026-08-05T00:36:19+00:00 | Vulnerability · Source |
| CVE-2026-54448 | suse_vex | SUSE CVE CVE-2026-54448 | recommended: 3 | 2026-08-05T00:36:04+00:00 | Vulnerability · Source |
| CVE-2026-54787 | suse_vex | SUSE CVE CVE-2026-54787 | known affected: 134 known not affected: 241 | 2026-08-05T00:36:02+00:00 | Vulnerability · Source |
| CVE-2026-55831 | suse_vex | SUSE CVE CVE-2026-55831 | known not affected: 42 recommended: 22 | 2026-08-05T00:35:58+00:00 | Vulnerability · Source |
| CVE-2026-55833 | suse_vex | SUSE CVE CVE-2026-55833 | known not affected: 42 recommended: 22 | 2026-08-05T00:35:57+00:00 | Vulnerability · Source |
| CVE-2026-55851 | suse_vex | SUSE CVE CVE-2026-55851 | known not affected: 42 recommended: 22 | 2026-08-05T00:35:55+00:00 | Vulnerability · Source |
| CVE-2026-56109 | suse_vex | SUSE CVE CVE-2026-56109 | known affected: 513 recommended: 53 | 2026-08-05T00:35:52+00:00 | Vulnerability · Source |
| CVE-2026-56745 | suse_vex | SUSE CVE CVE-2026-56745 | known not affected: 42 recommended: 22 | 2026-08-05T00:35:47+00:00 | Vulnerability · Source |
| CVE-2026-56746 | suse_vex | SUSE CVE CVE-2026-56746 | known not affected: 42 recommended: 22 | 2026-08-05T00:35:45+00:00 | Vulnerability · Source |
| CVE-2026-56817 | suse_vex | SUSE CVE CVE-2026-56817 | known not affected: 42 recommended: 22 | 2026-08-05T00:35:43+00:00 | Vulnerability · Source |
| CVE-2026-56819 | suse_vex | SUSE CVE CVE-2026-56819 | known not affected: 42 recommended: 22 | 2026-08-05T00:35:39+00:00 | Vulnerability · Source |
| CVE-2026-56820 | suse_vex | SUSE CVE CVE-2026-56820 | known not affected: 42 recommended: 22 | 2026-08-05T00:35:37+00:00 | Vulnerability · Source |
| CVE-2026-56821 | suse_vex | SUSE CVE CVE-2026-56821 | known not affected: 42 recommended: 22 | 2026-08-05T00:35:35+00:00 | Vulnerability · Source |
| CVE-2026-56822 | suse_vex | SUSE CVE CVE-2026-56822 | known not affected: 42 recommended: 22 | 2026-08-05T00:35:34+00:00 | Vulnerability · Source |
| CVE-2026-59898 | suse_vex | SUSE CVE CVE-2026-59898 | known not affected: 42 recommended: 22 | 2026-08-05T00:34:44+00:00 | Vulnerability · Source |
| CVE-2026-59899 | suse_vex | SUSE CVE CVE-2026-59899 | known not affected: 42 recommended: 22 | 2026-08-05T00:34:42+00:00 | Vulnerability · Source |