VEX records
Browse vendor VEX statements available in this Vulnerability-Lookup instance and pivot to the related vulnerability.
294458 VEX records
API response| Vulnerability | Source | Title | Product status | Imported | Links |
|---|---|---|---|---|---|
| CVE-2026-34378 | suse_vex | SUSE CVE CVE-2026-34378 | known not affected: 108 recommended: 18 | 2026-07-15T05:17:43+00:00 | Vulnerability · Source |
| CVE-2026-34379 | suse_vex | SUSE CVE CVE-2026-34379 | known not affected: 108 recommended: 55 | 2026-07-15T05:17:42+00:00 | Vulnerability · Source |
| CVE-2026-34380 | suse_vex | SUSE CVE CVE-2026-34380 | known not affected: 108 recommended: 55 | 2026-07-15T05:17:41+00:00 | Vulnerability · Source |
| CVE-2026-34441 | suse_vex | SUSE CVE CVE-2026-34441 | known affected: 5 recommended: 2 | 2026-07-15T05:17:39+00:00 | Vulnerability · Source |
| CVE-2026-34543 | suse_vex | SUSE CVE CVE-2026-34543 | known not affected: 108 recommended: 18 | 2026-07-15T05:17:24+00:00 | Vulnerability · Source |
| CVE-2026-34544 | suse_vex | SUSE CVE CVE-2026-34544 | known not affected: 108 recommended: 18 | 2026-07-15T05:17:23+00:00 | Vulnerability · Source |
| CVE-2026-34545 | suse_vex | SUSE CVE CVE-2026-34545 | known not affected: 108 recommended: 18 | 2026-07-15T05:17:22+00:00 | Vulnerability · Source |
| CVE-2026-34941 | suse_vex | SUSE CVE CVE-2026-34941 | recommended: 14 | 2026-07-15T05:17:11+00:00 | Vulnerability · Source |
| CVE-2026-34942 | suse_vex | SUSE CVE CVE-2026-34942 | recommended: 10 | 2026-07-15T05:17:10+00:00 | Vulnerability · Source |
| CVE-2026-34943 | suse_vex | SUSE CVE CVE-2026-34943 | recommended: 14 | 2026-07-15T05:17:09+00:00 | Vulnerability · Source |
| CVE-2026-34944 | suse_vex | SUSE CVE CVE-2026-34944 | recommended: 10 | 2026-07-15T05:17:08+00:00 | Vulnerability · Source |
| CVE-2026-34945 | suse_vex | SUSE CVE CVE-2026-34945 | recommended: 14 | 2026-07-15T05:17:07+00:00 | Vulnerability · Source |
| CVE-2026-34946 | suse_vex | SUSE CVE CVE-2026-34946 | recommended: 10 | 2026-07-15T05:17:06+00:00 | Vulnerability · Source |
| CVE-2026-34987 | suse_vex | SUSE CVE CVE-2026-34987 | recommended: 10 | 2026-07-15T05:17:03+00:00 | Vulnerability · Source |
| CVE-2026-34988 | suse_vex | SUSE CVE CVE-2026-34988 | recommended: 14 | 2026-07-15T05:17:01+00:00 | Vulnerability · Source |
| CVE-2026-35094 | suse_vex | SUSE CVE CVE-2026-35094 | known not affected: 129 recommended: 5 | 2026-07-15T05:16:57+00:00 | Vulnerability · Source |
| CVE-2026-35186 | suse_vex | SUSE CVE CVE-2026-35186 | recommended: 14 | 2026-07-15T05:16:56+00:00 | Vulnerability · Source |
| CVE-2026-35195 | suse_vex | SUSE CVE CVE-2026-35195 | recommended: 10 | 2026-07-15T05:16:55+00:00 | Vulnerability · Source |
| CVE-2026-39244 | suse_vex | SUSE CVE CVE-2026-39244 | known affected: 16 known not affected: 65 | 2026-07-15T05:16:33+00:00 | Vulnerability · Source |
| CVE-2026-39886 | suse_vex | SUSE CVE CVE-2026-39886 | known not affected: 133 recommended: 18 | 2026-07-15T05:16:08+00:00 | Vulnerability · Source |
| CVE-2026-40016 | suse_vex | SUSE CVE CVE-2026-40016 | known affected: 210 known not affected: 31 recommended: 30 | 2026-07-15T05:16:04+00:00 | Vulnerability · Source |
| CVE-2026-40020 | suse_vex | SUSE CVE CVE-2026-40020 | known affected: 198 known not affected: 31 recommended: 44 | 2026-07-15T05:16:03+00:00 | Vulnerability · Source |
| CVE-2026-40183 | suse_vex | SUSE CVE CVE-2026-40183 | known affected: 21 known not affected: 169 recommended: 141 | 2026-07-15T05:15:58+00:00 | Vulnerability · Source |
| CVE-2026-40310 | suse_vex | SUSE CVE CVE-2026-40310 | known affected: 75 known not affected: 42 recommended: 229 | 2026-07-15T05:15:51+00:00 | Vulnerability · Source |
| CVE-2026-40311 | suse_vex | SUSE CVE CVE-2026-40311 | known affected: 75 known not affected: 26 recommended: 245 | 2026-07-15T05:15:50+00:00 | Vulnerability · Source |
| CVE-2026-40312 | suse_vex | SUSE CVE CVE-2026-40312 | known affected: 21 known not affected: 169 recommended: 141 | 2026-07-15T05:15:49+00:00 | Vulnerability · Source |
| CVE-2026-41051 | suse_vex | SUSE CVE CVE-2026-41051 | known affected: 397 recommended: 8 | 2026-07-15T05:15:33+00:00 | Vulnerability · Source |
| CVE-2026-41401 | suse_vex | SUSE CVE CVE-2026-41401 | known not affected: 19 recommended: 22 | 2026-07-15T05:15:19+00:00 | Vulnerability · Source |
| CVE-2026-41425 | suse_vex | SUSE CVE CVE-2026-41425 | known affected: 6 recommended: 5 | 2026-07-15T05:15:18+00:00 | Vulnerability · Source |
| CVE-2026-42046 | suse_vex | SUSE CVE CVE-2026-42046 | known affected: 37 recommended: 86 | 2026-07-15T05:14:57+00:00 | Vulnerability · Source |
| CVE-2026-42311 | suse_vex | SUSE CVE CVE-2026-42311 | first fixed: 4 known affected: 7 known not affected: 51 recommended: 6 | 2026-07-15T05:14:38+00:00 | Vulnerability · Source |
| CVE-2026-43163 | suse_vex | SUSE CVE CVE-2026-43163 | known affected: 289 known not affected: 4 recommended: 116 | 2026-07-15T05:12:42+00:00 | Vulnerability · Source |
| 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 |