VEX records
Browse vendor VEX statements available in this Vulnerability-Lookup instance and pivot to the related vulnerability.
291704 VEX records
API response| Vulnerability | Source | Title | Product status | Imported | Links |
|---|---|---|---|---|---|
| CVE-2026-68146 | suse_vex | SUSE CVE CVE-2026-68146 | known affected: 296 | 2026-08-13T16:24:03+00:00 | Vulnerability · Source |
| CVE-2026-68161 | suse_vex | SUSE CVE CVE-2026-68161 | known affected: 292 known not affected: 4 | 2026-08-13T16:24:02+00:00 | Vulnerability · Source |
| CVE-2026-68162 | suse_vex | SUSE CVE CVE-2026-68162 | known affected: 292 known not affected: 4 | 2026-08-13T16:24:00+00:00 | Vulnerability · Source |
| CVE-2026-68163 | suse_vex | SUSE CVE CVE-2026-68163 | known affected: 29 known not affected: 267 | 2026-08-13T16:23:59+00:00 | Vulnerability · Source |
| CVE-2026-68164 | suse_vex | SUSE CVE CVE-2026-68164 | known affected: 234 known not affected: 62 | 2026-08-13T16:23:57+00:00 | Vulnerability · Source |
| CVE-2026-68165 | suse_vex | SUSE CVE CVE-2026-68165 | known affected: 129 known not affected: 167 | 2026-08-13T16:23:55+00:00 | Vulnerability · Source |
| CVE-2026-68166 | suse_vex | SUSE CVE CVE-2026-68166 | known not affected: 296 | 2026-08-13T16:23:53+00:00 | Vulnerability · Source |
| CVE-2026-68167 | suse_vex | SUSE CVE CVE-2026-68167 | known affected: 234 known not affected: 62 | 2026-08-13T16:23:52+00:00 | Vulnerability · Source |
| CVE-2026-68168 | suse_vex | SUSE CVE CVE-2026-68168 | known affected: 114 known not affected: 182 | 2026-08-13T16:23:50+00:00 | Vulnerability · Source |
| CVE-2026-68169 | suse_vex | SUSE CVE CVE-2026-68169 | known affected: 112 known not affected: 184 | 2026-08-13T16:23:48+00:00 | Vulnerability · Source |
| CVE-2026-68170 | suse_vex | SUSE CVE CVE-2026-68170 | known affected: 29 known not affected: 267 | 2026-08-13T16:23:46+00:00 | Vulnerability · Source |
| CVE-2026-68172 | suse_vex | SUSE CVE CVE-2026-68172 | known affected: 292 known not affected: 4 | 2026-08-13T16:23:44+00:00 | Vulnerability · Source |
| CVE-2026-68173 | suse_vex | SUSE CVE CVE-2026-68173 | known not affected: 296 | 2026-08-13T16:23:42+00:00 | Vulnerability · Source |
| CVE-2026-68174 | suse_vex | SUSE CVE CVE-2026-68174 | known affected: 292 known not affected: 4 | 2026-08-13T16:23:40+00:00 | Vulnerability · Source |
| CVE-2026-68175 | suse_vex | SUSE CVE CVE-2026-68175 | known affected: 296 | 2026-08-13T16:23:38+00:00 | Vulnerability · Source |
| CVE-2026-68176 | suse_vex | SUSE CVE CVE-2026-68176 | known affected: 296 | 2026-08-13T16:23:36+00:00 | Vulnerability · Source |
| CVE-2026-68178 | suse_vex | SUSE CVE CVE-2026-68178 | known not affected: 296 | 2026-08-13T16:23:32+00:00 | Vulnerability · Source |
| CVE-2026-68184 | suse_vex | SUSE CVE CVE-2026-68184 | known affected: 202 known not affected: 94 | 2026-08-13T16:23:22+00:00 | Vulnerability · Source |
| CVE-2026-68389 | suse_vex | SUSE CVE CVE-2026-68389 | known not affected: 296 | 2026-08-13T16:22:42+00:00 | Vulnerability · Source |
| CVE-2026-68390 | suse_vex | SUSE CVE CVE-2026-68390 | known not affected: 296 | 2026-08-13T16:22:40+00:00 | Vulnerability · Source |
| CVE-2026-68391 | suse_vex | SUSE CVE CVE-2026-68391 | known affected: 78 known not affected: 218 | 2026-08-13T16:22:38+00:00 | Vulnerability · Source |
| CVE-2026-68392 | suse_vex | SUSE CVE CVE-2026-68392 | known not affected: 296 | 2026-08-13T16:22:36+00:00 | Vulnerability · Source |
| CVE-2026-68393 | suse_vex | SUSE CVE CVE-2026-68393 | known affected: 17 known not affected: 279 | 2026-08-13T16:22:34+00:00 | Vulnerability · Source |
| CVE-2026-68394 | suse_vex | SUSE CVE CVE-2026-68394 | known not affected: 296 | 2026-08-13T16:22:32+00:00 | Vulnerability · Source |
| CVE-2026-68395 | suse_vex | SUSE CVE CVE-2026-68395 | known affected: 296 | 2026-08-13T16:22:30+00:00 | Vulnerability · Source |
| CVE-2026-68396 | suse_vex | SUSE CVE CVE-2026-68396 | known affected: 217 known not affected: 79 | 2026-08-13T16:22:28+00:00 | Vulnerability · Source |
| CVE-2026-68397 | suse_vex | SUSE CVE CVE-2026-68397 | known affected: 292 known not affected: 4 | 2026-08-13T16:22:26+00:00 | Vulnerability · Source |
| CVE-2026-68398 | suse_vex | SUSE CVE CVE-2026-68398 | known affected: 290 known not affected: 6 | 2026-08-13T16:22:24+00:00 | Vulnerability · Source |
| CVE-2026-68399 | suse_vex | SUSE CVE CVE-2026-68399 | known affected: 243 known not affected: 53 | 2026-08-13T16:22:22+00:00 | Vulnerability · Source |
| CVE-2026-68400 | suse_vex | SUSE CVE CVE-2026-68400 | known affected: 29 known not affected: 267 | 2026-08-13T16:22:20+00:00 | Vulnerability · Source |
| CVE-2026-68401 | suse_vex | SUSE CVE CVE-2026-68401 | known affected: 217 known not affected: 79 | 2026-08-13T16:22:18+00:00 | Vulnerability · Source |
| CVE-2026-68402 | suse_vex | SUSE CVE CVE-2026-68402 | known affected: 144 known not affected: 152 | 2026-08-13T16:22:16+00:00 | Vulnerability · Source |
| CVE-2026-68403 | suse_vex | SUSE CVE CVE-2026-68403 | known affected: 193 known not affected: 103 | 2026-08-13T16:22:14+00:00 | Vulnerability · Source |
| CVE-2026-68404 | suse_vex | SUSE CVE CVE-2026-68404 | known affected: 290 known not affected: 6 | 2026-08-13T16:22:12+00:00 | Vulnerability · Source |
| CVE-2026-68405 | suse_vex | SUSE CVE CVE-2026-68405 | known affected: 193 known not affected: 103 | 2026-08-13T16:22:10+00:00 | Vulnerability · Source |
| CVE-2026-68406 | suse_vex | SUSE CVE CVE-2026-68406 | known affected: 144 known not affected: 152 | 2026-08-13T16:22:08+00:00 | Vulnerability · Source |
| CVE-2026-68407 | suse_vex | SUSE CVE CVE-2026-68407 | known affected: 30 known not affected: 266 | 2026-08-13T16:22:06+00:00 | Vulnerability · Source |
| CVE-2026-68436 | suse_vex | SUSE CVE CVE-2026-68436 | No product status | 2026-08-13T16:22:04+00:00 | Vulnerability · Source |
| CVE-2026-73231 | suse_vex | SUSE CVE CVE-2026-73231 | known affected: 9 | 2026-08-13T16:21:58+00:00 | Vulnerability · Source |
| CVE-2026-73248 | suse_vex | SUSE CVE CVE-2026-73248 | No product status | 2026-08-13T16:21:56+00:00 | Vulnerability · Source |
| CVE-2026-73249 | suse_vex | SUSE CVE CVE-2026-73249 | No product status | 2026-08-13T16:21:55+00:00 | Vulnerability · Source |
| CVE-2026-73295 | suse_vex | SUSE CVE CVE-2026-73295 | No product status | 2026-08-13T16:21:53+00:00 | Vulnerability · Source |
| CVE-2026-73499 | suse_vex | SUSE CVE CVE-2026-73499 | No product status | 2026-08-13T16:21:46+00:00 | Vulnerability · Source |
| CVE-2026-73500 | suse_vex | SUSE CVE CVE-2026-73500 | No product status | 2026-08-13T16:21:44+00:00 | Vulnerability · Source |
| CVE-2026-73583 | suse_vex | SUSE CVE CVE-2026-73583 | known affected: 27 | 2026-08-13T16:21:42+00:00 | Vulnerability · Source |
| CVE-2026-73584 | suse_vex | SUSE CVE CVE-2026-73584 | known affected: 27 | 2026-08-13T16:21:40+00:00 | Vulnerability · Source |
| CVE-2026-73585 | suse_vex | SUSE CVE CVE-2026-73585 | known affected: 52 | 2026-08-13T16:21:39+00:00 | Vulnerability · Source |
| CVE-2026-73626 | suse_vex | SUSE CVE CVE-2026-73626 | No product status | 2026-08-13T16:21:37+00:00 | Vulnerability · Source |
| CVE-2026-73627 | suse_vex | SUSE CVE CVE-2026-73627 | No product status | 2026-08-13T16:21:35+00:00 | Vulnerability · Source |
| CVE-2026-73585 | redhat_vex | sblim-cmpi-base: Insecure temporary file creation in sblim-cmpi-base provider registration scripts allows local symlink attack | known affected: 9 | 2026-08-13T14:34:56+00:00 | Vulnerability · Source |