VEX records
Browse vendor VEX statements available in this Vulnerability-Lookup instance and pivot to the related vulnerability.
292260 VEX records
API response| Vulnerability | Source | Title | Product status | Imported | Links |
|---|---|---|---|---|---|
| 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-35406 | suse_vex | SUSE CVE CVE-2026-35406 | known not affected: 27 recommended: 3 | 2026-07-15T05:16:44+00:00 | Vulnerability · Source |
| CVE-2026-35549 | suse_vex | SUSE CVE CVE-2026-35549 | known not affected: 152 recommended: 59 | 2026-07-15T05:16:41+00:00 | Vulnerability · Source |
| CVE-2026-37457 | suse_vex | SUSE CVE CVE-2026-37457 | known affected: 43 recommended: 253 | 2026-07-15T05:16:39+00:00 | Vulnerability · Source |
| CVE-2026-38969 | suse_vex | SUSE CVE CVE-2026-38969 | known affected: 121 known not affected: 65 | 2026-07-15T05:16:35+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-39373 | suse_vex | SUSE CVE CVE-2026-39373 | recommended: 11 | 2026-07-15T05:16:32+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-40170 | suse_vex | SUSE CVE CVE-2026-40170 | known affected: 122 known not affected: 910 recommended: 195 | 2026-07-15T05:16:00+00:00 | Vulnerability · Source |
| CVE-2026-40176 | suse_vex | SUSE CVE CVE-2026-40176 | recommended: 20 | 2026-07-15T05:15:59+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-40244 | suse_vex | SUSE CVE CVE-2026-40244 | known affected: 56 known not affected: 12 recommended: 103 | 2026-07-15T05:15:56+00:00 | Vulnerability · Source |
| CVE-2026-40250 | suse_vex | SUSE CVE CVE-2026-40250 | known affected: 56 known not affected: 12 recommended: 103 | 2026-07-15T05:15:55+00:00 | Vulnerability · Source |
| CVE-2026-40253 | suse_vex | SUSE CVE CVE-2026-40253 | known affected: 54 known not affected: 13 recommended: 52 | 2026-07-15T05:15:54+00:00 | Vulnerability · Source |
| CVE-2026-40261 | suse_vex | SUSE CVE CVE-2026-40261 | recommended: 20 | 2026-07-15T05:15:52+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-40347 | suse_vex | SUSE CVE CVE-2026-40347 | recommended: 6 | 2026-07-15T05:15:48+00:00 | Vulnerability · Source |
| CVE-2026-40393 | suse_vex | SUSE CVE CVE-2026-40393 | known affected: 872 recommended: 455 | 2026-07-15T05:15:45+00:00 | Vulnerability · Source |
| CVE-2026-40469 | suse_vex | SUSE CVE CVE-2026-40469 | known affected: 36 | 2026-07-15T05:15:42+00:00 | Vulnerability · Source |
| CVE-2026-40489 | suse_vex | SUSE CVE CVE-2026-40489 | known affected: 13 recommended: 15 | 2026-07-15T05:15:41+00:00 | Vulnerability · Source |
| CVE-2026-40701 | suse_vex | SUSE CVE CVE-2026-40701 | known affected: 398 known not affected: 8 recommended: 44 | 2026-07-15T05:15:37+00:00 | Vulnerability · Source |
| CVE-2026-40706 | suse_vex | SUSE CVE CVE-2026-40706 | known affected: 24 recommended: 48 | 2026-07-15T05:15:36+00:00 | Vulnerability · Source |
| CVE-2026-40962 | suse_vex | SUSE CVE CVE-2026-40962 | known not affected: 336 recommended: 162 | 2026-07-15T05:15:34+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-41069 | suse_vex | SUSE CVE CVE-2026-41069 | known not affected: 44 recommended: 69 | 2026-07-15T05:15:32+00:00 | Vulnerability · Source |
| CVE-2026-41071 | suse_vex | SUSE CVE CVE-2026-41071 | known not affected: 44 recommended: 69 | 2026-07-15T05:15:31+00:00 | Vulnerability · Source |
| CVE-2026-41080 | suse_vex | SUSE CVE CVE-2026-41080 | known affected: 131 known not affected: 291 recommended: 5 | 2026-07-15T05:15:29+00:00 | Vulnerability · Source |
| CVE-2026-41142 | suse_vex | SUSE CVE CVE-2026-41142 | known affected: 24 known not affected: 12 recommended: 109 | 2026-07-15T05:15:28+00:00 | Vulnerability · Source |
| CVE-2026-41163 | suse_vex | SUSE CVE CVE-2026-41163 | known affected: 7 known not affected: 14 recommended: 30 | 2026-07-15T05:15:27+00:00 | Vulnerability · Source |
| CVE-2026-41205 | suse_vex | SUSE CVE CVE-2026-41205 | known affected: 17 recommended: 25 | 2026-07-15T05:15:26+00:00 | Vulnerability · Source |
| CVE-2026-41284 | suse_vex | SUSE CVE CVE-2026-41284 | known affected: 524 recommended: 374 | 2026-07-15T05:15:21+00:00 | Vulnerability · Source |
| CVE-2026-41293 | suse_vex | SUSE CVE CVE-2026-41293 | known affected: 524 recommended: 374 | 2026-07-15T05:15:20+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-41889 | suse_vex | SUSE CVE CVE-2026-41889 | known affected: 33 recommended: 10 | 2026-07-15T05:15:07+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-42216 | suse_vex | SUSE CVE CVE-2026-42216 | known not affected: 101 recommended: 61 | 2026-07-15T05:14:51+00:00 | Vulnerability · Source |