VEX records
Browse vendor VEX statements available in this Vulnerability-Lookup instance and pivot to the related vulnerability.
292431 VEX records
API response| Vulnerability | Source | Title | Product status | Imported | Links |
|---|---|---|---|---|---|
| CVE-2025-14009 | suse_vex | SUSE CVE CVE-2025-14009 | recommended: 6 | 2026-07-01T03:47:40+00:00 | Vulnerability · Source |
| CVE-2025-24965 | suse_vex | SUSE CVE CVE-2025-24965 | known affected: 390 recommended: 4 | 2026-07-01T03:45:48+00:00 | Vulnerability · Source |
| CVE-2025-47917 | suse_vex | SUSE CVE CVE-2025-47917 | recommended: 11 | 2026-07-01T03:42:03+00:00 | Vulnerability · Source |
| CVE-2025-48965 | suse_vex | SUSE CVE CVE-2025-48965 | recommended: 11 | 2026-07-01T03:41:58+00:00 | Vulnerability · Source |
| CVE-2025-49600 | suse_vex | SUSE CVE CVE-2025-49600 | recommended: 27 | 2026-07-01T03:41:52+00:00 | Vulnerability · Source |
| CVE-2025-52496 | suse_vex | SUSE CVE CVE-2025-52496 | recommended: 27 | 2026-07-01T03:41:47+00:00 | Vulnerability · Source |
| CVE-2025-54386 | suse_vex | SUSE CVE CVE-2025-54386 | recommended: 3 | 2026-07-01T03:41:40+00:00 | Vulnerability · Source |
| CVE-2025-59343 | suse_vex | SUSE CVE CVE-2025-59343 | known affected: 75 known not affected: 312 recommended: 4 | 2026-07-01T03:41:26+00:00 | Vulnerability · Source |
| CVE-2025-62507 | suse_vex | SUSE CVE CVE-2025-62507 | known not affected: 62 recommended: 2 | 2026-07-01T03:41:17+00:00 | Vulnerability · Source |
| CVE-2025-67269 | suse_vex | SUSE CVE CVE-2025-67269 | recommended: 12 | 2026-07-01T03:41:01+00:00 | Vulnerability · Source |
| CVE-2025-68463 | suse_vex | SUSE CVE CVE-2025-68463 | recommended: 5 | 2026-07-01T03:40:39+00:00 | Vulnerability · Source |
| CVE-2025-68616 | suse_vex | SUSE CVE CVE-2025-68616 | recommended: 7 | 2026-07-01T03:40:37+00:00 | Vulnerability · Source |
| CVE-2026-0847 | suse_vex | SUSE CVE CVE-2026-0847 | recommended: 3 | 2026-07-01T03:40:04+00:00 | Vulnerability · Source |
| CVE-2026-1801 | suse_vex | SUSE CVE CVE-2026-1801 | known affected: 163 known not affected: 13 recommended: 81 | 2026-07-01T03:39:50+00:00 | Vulnerability · Source |
| CVE-2026-2047 | suse_vex | SUSE CVE CVE-2026-2047 | known not affected: 34 recommended: 2 | 2026-07-01T03:39:44+00:00 | Vulnerability · Source |
| CVE-2026-2492 | suse_vex | SUSE CVE CVE-2026-2492 | No product status | 2026-07-01T03:39:37+00:00 | Vulnerability · Source |
| CVE-2026-2921 | suse_vex | SUSE CVE CVE-2026-2921 | known affected: 809 recommended: 24 | 2026-07-01T03:39:26+00:00 | Vulnerability · Source |
| 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-10701 | suse_vex | SUSE CVE CVE-2026-10701 | known affected: 112 recommended: 5 | 2026-07-01T03:36:49+00:00 | Vulnerability · Source |
| CVE-2026-10702 | suse_vex | SUSE CVE CVE-2026-10702 | known not affected: 112 recommended: 5 | 2026-07-01T03:36:47+00:00 | Vulnerability · Source |
| CVE-2026-13281 | suse_vex | SUSE CVE CVE-2026-13281 | recommended: 4 | 2026-07-01T03:35:54+00:00 | Vulnerability · Source |
| CVE-2026-13282 | suse_vex | SUSE CVE CVE-2026-13282 | recommended: 4 | 2026-07-01T03:35:52+00:00 | Vulnerability · Source |
| CVE-2026-13283 | suse_vex | SUSE CVE CVE-2026-13283 | recommended: 4 | 2026-07-01T03:35:51+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-24869 | suse_vex | SUSE CVE CVE-2026-24869 | known not affected: 124 recommended: 5 | 2026-07-01T03:33:33+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 |