VEX records
Browse vendor VEX statements available in this Vulnerability-Lookup instance and pivot to the related vulnerability.
293841 VEX records
API response| Vulnerability | Source | Title | Product status | Imported | Links |
|---|---|---|---|---|---|
| CVE-2026-2923 | suse_vex | SUSE CVE CVE-2026-2923 | known affected: 744 known not affected: 26 recommended: 24 | 2026-07-01T03:39:23+00:00 | Vulnerability · Source |
| CVE-2026-3029 | suse_vex | SUSE CVE CVE-2026-3029 | recommended: 3 | 2026-07-01T03:39:22+00:00 | Vulnerability · Source |
| CVE-2026-3081 | suse_vex | SUSE CVE CVE-2026-3081 | known not affected: 770 | 2026-07-01T03:39:19+00:00 | Vulnerability · Source |
| CVE-2026-3082 | suse_vex | SUSE CVE CVE-2026-3082 | known affected: 744 known not affected: 26 recommended: 24 | 2026-07-01T03:39:18+00:00 | Vulnerability · Source |
| CVE-2026-3083 | suse_vex | SUSE CVE CVE-2026-3083 | known affected: 73 recommended: 24 | 2026-07-01T03:39:16+00:00 | Vulnerability · Source |
| CVE-2026-3084 | suse_vex | SUSE CVE CVE-2026-3084 | known not affected: 770 | 2026-07-01T03:39:15+00:00 | Vulnerability · Source |
| CVE-2026-3085 | suse_vex | SUSE CVE CVE-2026-3085 | known affected: 73 recommended: 24 | 2026-07-01T03:39:13+00:00 | Vulnerability · Source |
| CVE-2026-3086 | suse_vex | SUSE CVE CVE-2026-3086 | known not affected: 770 | 2026-07-01T03:39:12+00:00 | Vulnerability · Source |
| CVE-2026-3605 | suse_vex | SUSE CVE CVE-2026-3605 | recommended: 8 | 2026-07-01T03:39:00+00:00 | Vulnerability · Source |
| CVE-2026-4151 | suse_vex | SUSE CVE CVE-2026-4151 | known not affected: 34 recommended: 11 | 2026-07-01T03:38:54+00:00 | Vulnerability · Source |
| CVE-2026-4152 | suse_vex | SUSE CVE CVE-2026-4152 | known not affected: 34 recommended: 2 | 2026-07-01T03:38:53+00:00 | Vulnerability · Source |
| CVE-2026-5807 | suse_vex | SUSE CVE CVE-2026-5807 | recommended: 8 | 2026-07-01T03:38:15+00:00 | Vulnerability · Source |
| CVE-2026-6918 | suse_vex | SUSE CVE CVE-2026-6918 | known not affected: 499 | 2026-07-01T03:37:42+00:00 | Vulnerability · Source |
| CVE-2026-13593 | suse_vex | SUSE CVE CVE-2026-13593 | recommended: 1 | 2026-07-01T03:35:45+00:00 | Vulnerability · Source |
| CVE-2026-21884 | suse_vex | SUSE CVE CVE-2026-21884 | known affected: 8 known not affected: 13 | 2026-07-01T03:35:30+00:00 | Vulnerability · Source |
| CVE-2026-22775 | suse_vex | SUSE CVE CVE-2026-22775 | known not affected: 75 | 2026-07-01T03:35:25+00:00 | Vulnerability · Source |
| CVE-2026-23960 | suse_vex | SUSE CVE CVE-2026-23960 | No product status | 2026-07-01T03:33:41+00:00 | Vulnerability · Source |
| CVE-2026-26200 | suse_vex | SUSE CVE CVE-2026-26200 | known affected: 708 | 2026-07-01T03:33:13+00:00 | Vulnerability · Source |
| CVE-2026-26278 | suse_vex | SUSE CVE CVE-2026-26278 | known affected: 3 recommended: 2 | 2026-07-01T03:33:12+00:00 | Vulnerability · Source |
| CVE-2026-27623 | suse_vex | SUSE CVE CVE-2026-27623 | known not affected: 31 recommended: 3 | 2026-07-01T03:32:56+00:00 | Vulnerability · Source |
| CVE-2026-27727 | suse_vex | SUSE CVE CVE-2026-27727 | known not affected: 2 recommended: 13 | 2026-07-01T03:32:53+00:00 | Vulnerability · Source |
| CVE-2026-27830 | suse_vex | SUSE CVE CVE-2026-27830 | recommended: 9 | 2026-07-01T03:32:51+00:00 | Vulnerability · Source |
| CVE-2026-28364 | suse_vex | SUSE CVE CVE-2026-28364 | known affected: 32 recommended: 98 | 2026-07-01T03:32:39+00:00 | Vulnerability · Source |
| CVE-2026-28802 | suse_vex | SUSE CVE CVE-2026-28802 | known not affected: 18 | 2026-07-01T03:32:30+00:00 | Vulnerability · Source |
| CVE-2026-31892 | suse_vex | SUSE CVE CVE-2026-31892 | No product status | 2026-07-01T03:30:01+00:00 | Vulnerability · Source |
| CVE-2026-32305 | suse_vex | SUSE CVE CVE-2026-32305 | recommended: 2 | 2026-07-01T03:29:51+00:00 | Vulnerability · Source |
| CVE-2026-32640 | suse_vex | SUSE CVE CVE-2026-32640 | recommended: 6 | 2026-07-01T03:29:49+00:00 | Vulnerability · Source |
| CVE-2026-32748 | suse_vex | SUSE CVE CVE-2026-32748 | known affected: 34 recommended: 5 | 2026-07-01T03:29:44+00:00 | Vulnerability · Source |
| CVE-2026-32829 | suse_vex | SUSE CVE CVE-2026-32829 | known not affected: 471 | 2026-07-01T03:29:39+00:00 | Vulnerability · Source |
| CVE-2026-33150 | suse_vex | SUSE CVE CVE-2026-33150 | known not affected: 248 | 2026-07-01T03:29:33+00:00 | Vulnerability · Source |
| CVE-2026-33231 | suse_vex | SUSE CVE CVE-2026-33231 | recommended: 1 | 2026-07-01T03:29:26+00:00 | Vulnerability · Source |
| CVE-2026-33487 | suse_vex | SUSE CVE CVE-2026-33487 | recommended: 1 | 2026-07-01T03:29:23+00:00 | Vulnerability · Source |
| CVE-2026-33526 | suse_vex | SUSE CVE CVE-2026-33526 | known affected: 34 recommended: 5 | 2026-07-01T03:29:20+00:00 | Vulnerability · Source |
| CVE-2026-34580 | suse_vex | SUSE CVE CVE-2026-34580 | known not affected: 5 | 2026-07-01T03:28:50+00:00 | Vulnerability · Source |
| CVE-2026-34601 | suse_vex | SUSE CVE CVE-2026-34601 | known affected: 69 known not affected: 12 recommended: 5 | 2026-07-01T03:28:45+00:00 | Vulnerability · Source |
| CVE-2026-34734 | suse_vex | SUSE CVE CVE-2026-34734 | known affected: 708 | 2026-07-01T03:28:44+00:00 | Vulnerability · Source |
| CVE-2026-35093 | suse_vex | SUSE CVE CVE-2026-35093 | known not affected: 129 recommended: 5 | 2026-07-01T03:28:35+00:00 | Vulnerability · Source |
| CVE-2026-41053 | suse_vex | SUSE CVE CVE-2026-41053 | No product status | 2026-07-01T03:27:43+00:00 | Vulnerability · Source |
| CVE-2026-41674 | suse_vex | SUSE CVE CVE-2026-41674 | known affected: 75 | 2026-07-01T03:27:21+00:00 | Vulnerability · Source |
| CVE-2026-42027 | suse_vex | SUSE CVE CVE-2026-42027 | No product status | 2026-07-01T03:27:11+00:00 | Vulnerability · Source |
| CVE-2026-42573 | suse_vex | SUSE CVE CVE-2026-42573 | known affected: 75 | 2026-07-01T03:26:44+00:00 | Vulnerability · Source |
| CVE-2026-44727 | suse_vex | SUSE CVE CVE-2026-44727 | recommended: 6 | 2026-07-01T03:23:58+00:00 | Vulnerability · Source |
| CVE-2026-44947 | suse_vex | SUSE CVE CVE-2026-44947 | No product status | 2026-07-01T03:23:48+00:00 | Vulnerability · Source |
| CVE-2026-46625 | suse_vex | SUSE CVE CVE-2026-46625 | No product status | 2026-07-01T03:21:10+00:00 | Vulnerability · Source |
| CVE-2026-53115 | suse_vex | SUSE CVE CVE-2026-53115 | known affected: 214 known not affected: 77 | 2026-07-01T03:18:56+00:00 | Vulnerability · Source |
| CVE-2026-53116 | suse_vex | SUSE CVE CVE-2026-53116 | known affected: 226 known not affected: 65 | 2026-07-01T03:18:54+00:00 | Vulnerability · Source |
| CVE-2026-53117 | suse_vex | SUSE CVE CVE-2026-53117 | known affected: 226 known not affected: 65 | 2026-07-01T03:18:52+00:00 | Vulnerability · Source |
| CVE-2026-53119 | suse_vex | SUSE CVE CVE-2026-53119 | known affected: 15 known not affected: 276 | 2026-07-01T03:18:51+00:00 | Vulnerability · Source |
| CVE-2026-53120 | suse_vex | SUSE CVE CVE-2026-53120 | known affected: 287 known not affected: 4 | 2026-07-01T03:18:49+00:00 | Vulnerability · Source |
| CVE-2026-53126 | suse_vex | SUSE CVE CVE-2026-53126 | known affected: 112 known not affected: 179 | 2026-07-01T03:18:45+00:00 | Vulnerability · Source |