VEX records
Browse vendor VEX statements available in this Vulnerability-Lookup instance and pivot to the related vulnerability.
294135 VEX records
API response| Vulnerability | Source | Title | Product status | Imported | Links |
|---|---|---|---|---|---|
| CVE-2026-44024 | suse_vex | SUSE CVE CVE-2026-44024 | No product status | 2026-07-15T05:10:26+00:00 | Vulnerability · Source |
| CVE-2026-44243 | suse_vex | SUSE CVE CVE-2026-44243 | known affected: 38 recommended: 6 | 2026-07-15T05:10:16+00:00 | Vulnerability · Source |
| CVE-2026-44244 | suse_vex | SUSE CVE CVE-2026-44244 | known affected: 38 recommended: 6 | 2026-07-15T05:10:15+00:00 | Vulnerability · Source |
| CVE-2026-44681 | suse_vex | SUSE CVE CVE-2026-44681 | known affected: 6 recommended: 8 | 2026-07-15T05:10:05+00:00 | Vulnerability · Source |
| CVE-2026-45678 | suse_vex | SUSE CVE CVE-2026-45678 | known affected: 3 recommended: 9 | 2026-07-15T05:09:39+00:00 | Vulnerability · Source |
| CVE-2026-45682 | suse_vex | SUSE CVE CVE-2026-45682 | known affected: 3 recommended: 9 | 2026-07-15T05:09:38+00:00 | Vulnerability · Source |
| CVE-2026-45685 | suse_vex | SUSE CVE CVE-2026-45685 | known affected: 3 recommended: 9 | 2026-07-15T05:09:37+00:00 | Vulnerability · Source |
| CVE-2026-45686 | suse_vex | SUSE CVE CVE-2026-45686 | known affected: 3 recommended: 9 | 2026-07-15T05:09:36+00:00 | Vulnerability · Source |
| CVE-2026-47734 | suse_vex | SUSE CVE CVE-2026-47734 | first fixed: 10 known affected: 21 recommended: 6 | 2026-07-15T05:06:39+00:00 | Vulnerability · Source |
| CVE-2026-47784 | suse_vex | SUSE CVE CVE-2026-47784 | known affected: 14 recommended: 50 | 2026-07-15T05:06:37+00:00 | Vulnerability · Source |
| CVE-2026-47828 | suse_vex | SUSE CVE CVE-2026-47828 | known affected: 6 | 2026-07-15T05:06:36+00:00 | Vulnerability · Source |
| CVE-2026-48095 | suse_vex | SUSE CVE CVE-2026-48095 | known affected: 49 recommended: 20 | 2026-07-15T05:06:32+00:00 | Vulnerability · Source |
| CVE-2026-48101 | suse_vex | SUSE CVE CVE-2026-48101 | known affected: 3 recommended: 19 | 2026-07-15T05:06:31+00:00 | Vulnerability · Source |
| CVE-2026-48102 | suse_vex | SUSE CVE CVE-2026-48102 | known affected: 3 recommended: 19 | 2026-07-15T05:06:30+00:00 | Vulnerability · Source |
| CVE-2026-48103 | suse_vex | SUSE CVE CVE-2026-48103 | known affected: 3 recommended: 19 | 2026-07-15T05:06:29+00:00 | Vulnerability · Source |
| CVE-2026-48104 | suse_vex | SUSE CVE CVE-2026-48104 | known affected: 3 recommended: 19 | 2026-07-15T05:06:28+00:00 | Vulnerability · Source |
| CVE-2026-48111 | suse_vex | SUSE CVE CVE-2026-48111 | known affected: 3 recommended: 19 | 2026-07-15T05:06:26+00:00 | Vulnerability · Source |
| CVE-2026-48112 | suse_vex | SUSE CVE CVE-2026-48112 | known affected: 3 recommended: 19 | 2026-07-15T05:06:25+00:00 | Vulnerability · Source |
| CVE-2026-48817 | suse_vex | SUSE CVE CVE-2026-48817 | known affected: 5 recommended: 3 | 2026-07-15T05:06:13+00:00 | Vulnerability · Source |
| CVE-2026-52985 | suse_vex | SUSE CVE CVE-2026-52985 | known affected: 228 known not affected: 65 | 2026-07-15T05:05:08+00:00 | Vulnerability · Source |
| CVE-2026-53320 | suse_vex | SUSE CVE CVE-2026-53320 | known affected: 293 | 2026-07-15T05:03:58+00:00 | Vulnerability · Source |
| CVE-2026-53448 | suse_vex | SUSE CVE CVE-2026-53448 | No product status | 2026-07-15T05:03:44+00:00 | Vulnerability · Source |
| CVE-2026-53449 | suse_vex | SUSE CVE CVE-2026-53449 | No product status | 2026-07-15T05:03:43+00:00 | Vulnerability · Source |
| CVE-2026-53450 | suse_vex | SUSE CVE CVE-2026-53450 | No product status | 2026-07-15T05:03:42+00:00 | Vulnerability · Source |
| CVE-2026-53538 | suse_vex | SUSE CVE CVE-2026-53538 | known affected: 5 recommended: 6 | 2026-07-15T05:03:33+00:00 | Vulnerability · Source |
| CVE-2026-53539 | suse_vex | SUSE CVE CVE-2026-53539 | known affected: 5 recommended: 3 | 2026-07-15T05:03:32+00:00 | Vulnerability · Source |
| CVE-2026-53540 | suse_vex | SUSE CVE CVE-2026-53540 | known affected: 5 recommended: 6 | 2026-07-15T05:03:32+00:00 | Vulnerability · Source |
| CVE-2026-54063 | suse_vex | SUSE CVE CVE-2026-54063 | known affected: 3 | 2026-07-15T05:03:26+00:00 | Vulnerability · Source |
| CVE-2026-54282 | suse_vex | SUSE CVE CVE-2026-54282 | known affected: 5 recommended: 6 | 2026-07-15T05:03:22+00:00 | Vulnerability · Source |
| CVE-2026-54283 | suse_vex | SUSE CVE CVE-2026-54283 | known affected: 5 recommended: 3 | 2026-07-15T05:03:21+00:00 | Vulnerability · Source |
| CVE-2026-54736 | suse_vex | SUSE CVE CVE-2026-54736 | No product status | 2026-07-15T05:03:17+00:00 | Vulnerability · Source |
| CVE-2026-54911 | suse_vex | SUSE CVE CVE-2026-54911 | known affected: 52 | 2026-07-15T05:03:16+00:00 | Vulnerability · Source |
| CVE-2026-54919 | suse_vex | SUSE CVE CVE-2026-54919 | known not affected: 31 | 2026-07-15T05:03:15+00:00 | Vulnerability · Source |
| CVE-2026-57212 | suse_vex | SUSE CVE CVE-2026-57212 | known affected: 98 | 2026-07-15T05:02:25+00:00 | Vulnerability · Source |
| CVE-2026-57213 | suse_vex | SUSE CVE CVE-2026-57213 | known affected: 98 | 2026-07-15T05:02:24+00:00 | Vulnerability · Source |
| CVE-2026-57214 | suse_vex | SUSE CVE CVE-2026-57214 | known affected: 98 | 2026-07-15T05:02:23+00:00 | Vulnerability · Source |
| CVE-2026-57215 | suse_vex | SUSE CVE CVE-2026-57215 | known affected: 11 known not affected: 87 | 2026-07-15T05:02:22+00:00 | Vulnerability · Source |
| CVE-2026-57216 | suse_vex | SUSE CVE CVE-2026-57216 | known affected: 98 | 2026-07-15T05:02:21+00:00 | Vulnerability · Source |
| CVE-2026-57217 | suse_vex | SUSE CVE CVE-2026-57217 | known affected: 40 known not affected: 58 | 2026-07-15T05:02:20+00:00 | Vulnerability · Source |
| CVE-2026-57218 | suse_vex | SUSE CVE CVE-2026-57218 | known affected: 98 | 2026-07-15T05:02:19+00:00 | Vulnerability · Source |
| CVE-2026-57219 | suse_vex | SUSE CVE CVE-2026-57219 | known affected: 98 | 2026-07-15T05:02:18+00:00 | Vulnerability · Source |
| CVE-2026-57220 | suse_vex | SUSE CVE CVE-2026-57220 | known affected: 98 | 2026-07-15T05:02:17+00:00 | Vulnerability · Source |
| CVE-2026-57221 | suse_vex | SUSE CVE CVE-2026-57221 | known affected: 98 | 2026-07-15T05:02:16+00:00 | Vulnerability · Source |
| CVE-2026-57584 | suse_vex | SUSE CVE CVE-2026-57584 | No product status | 2026-07-15T05:02:04+00:00 | Vulnerability · Source |
| CVE-2026-57850 | suse_vex | SUSE CVE CVE-2026-57850 | No product status | 2026-07-15T05:02:02+00:00 | Vulnerability · Source |
| CVE-2026-58208 | suse_vex | SUSE CVE CVE-2026-58208 | No product status | 2026-07-15T05:01:59+00:00 | Vulnerability · Source |
| CVE-2026-58250 | suse_vex | SUSE CVE CVE-2026-58250 | No product status | 2026-07-15T05:01:58+00:00 | Vulnerability · Source |
| CVE-2026-58251 | suse_vex | SUSE CVE CVE-2026-58251 | No product status | 2026-07-15T05:01:57+00:00 | Vulnerability · Source |
| CVE-2026-58252 | suse_vex | SUSE CVE CVE-2026-58252 | No product status | 2026-07-15T05:01:56+00:00 | Vulnerability · Source |
| CVE-2026-58253 | suse_vex | SUSE CVE CVE-2026-58253 | No product status | 2026-07-15T05:01:55+00:00 | Vulnerability · Source |