VEX records
Browse vendor VEX statements available in this Vulnerability-Lookup instance and pivot to the related vulnerability.
291897 VEX records
API response| Vulnerability | Source | Title | Product status | Imported | Links |
|---|---|---|---|---|---|
| CVE-2026-68324 | suse_vex | SUSE CVE CVE-2026-68324 | known affected: 217 known not affected: 79 | 2026-08-11T23:47:51+00:00 | Vulnerability · Source |
| CVE-2026-68325 | suse_vex | SUSE CVE CVE-2026-68325 | known affected: 292 known not affected: 4 | 2026-08-11T23:47:49+00:00 | Vulnerability · Source |
| CVE-2026-68326 | suse_vex | SUSE CVE CVE-2026-68326 | known affected: 193 known not affected: 103 | 2026-08-11T23:47:46+00:00 | Vulnerability · Source |
| CVE-2026-68328 | suse_vex | SUSE CVE CVE-2026-68328 | known affected: 290 known not affected: 6 | 2026-08-11T23:47:44+00:00 | Vulnerability · Source |
| CVE-2026-68329 | suse_vex | SUSE CVE CVE-2026-68329 | known affected: 296 | 2026-08-11T23:47:41+00:00 | Vulnerability · Source |
| CVE-2026-68330 | suse_vex | SUSE CVE CVE-2026-68330 | known not affected: 296 | 2026-08-11T23:47:39+00:00 | Vulnerability · Source |
| CVE-2026-68331 | suse_vex | SUSE CVE CVE-2026-68331 | known affected: 231 known not affected: 65 | 2026-08-11T23:47:36+00:00 | Vulnerability · Source |
| CVE-2026-68332 | suse_vex | SUSE CVE CVE-2026-68332 | known not affected: 296 | 2026-08-11T23:47:34+00:00 | Vulnerability · Source |
| CVE-2026-68333 | suse_vex | SUSE CVE CVE-2026-68333 | known affected: 129 known not affected: 167 | 2026-08-11T23:47:31+00:00 | Vulnerability · Source |
| CVE-2026-68334 | suse_vex | SUSE CVE CVE-2026-68334 | known not affected: 296 | 2026-08-11T23:47:29+00:00 | Vulnerability · Source |
| CVE-2026-68335 | suse_vex | SUSE CVE CVE-2026-68335 | known affected: 243 known not affected: 53 | 2026-08-11T23:47:26+00:00 | Vulnerability · Source |
| CVE-2026-68336 | suse_vex | SUSE CVE CVE-2026-68336 | known affected: 129 known not affected: 167 | 2026-08-11T23:47:24+00:00 | Vulnerability · Source |
| CVE-2026-68337 | suse_vex | SUSE CVE CVE-2026-68337 | known affected: 231 known not affected: 65 | 2026-08-11T23:47:22+00:00 | Vulnerability · Source |
| CVE-2026-68338 | suse_vex | SUSE CVE CVE-2026-68338 | known affected: 292 known not affected: 4 | 2026-08-11T23:47:20+00:00 | Vulnerability · Source |
| CVE-2026-68339 | suse_vex | SUSE CVE CVE-2026-68339 | known affected: 30 known not affected: 266 | 2026-08-11T23:47:17+00:00 | Vulnerability · Source |
| CVE-2026-68340 | suse_vex | SUSE CVE CVE-2026-68340 | known affected: 144 known not affected: 152 | 2026-08-11T23:47:15+00:00 | Vulnerability · Source |
| CVE-2026-68341 | suse_vex | SUSE CVE CVE-2026-68341 | known not affected: 296 | 2026-08-11T23:47:12+00:00 | Vulnerability · Source |
| CVE-2026-68342 | suse_vex | SUSE CVE CVE-2026-68342 | known not affected: 296 | 2026-08-11T23:47:09+00:00 | Vulnerability · Source |
| CVE-2026-68343 | suse_vex | SUSE CVE CVE-2026-68343 | known affected: 292 known not affected: 4 | 2026-08-11T23:47:07+00:00 | Vulnerability · Source |
| CVE-2026-68344 | suse_vex | SUSE CVE CVE-2026-68344 | known not affected: 296 | 2026-08-11T23:47:04+00:00 | Vulnerability · Source |
| CVE-2026-68345 | suse_vex | SUSE CVE CVE-2026-68345 | known not affected: 296 | 2026-08-11T23:47:02+00:00 | Vulnerability · Source |
| CVE-2026-68346 | suse_vex | SUSE CVE CVE-2026-68346 | known affected: 30 known not affected: 266 | 2026-08-11T23:46:59+00:00 | Vulnerability · Source |
| CVE-2026-68347 | suse_vex | SUSE CVE CVE-2026-68347 | known not affected: 296 | 2026-08-11T23:46:56+00:00 | Vulnerability · Source |
| CVE-2026-68348 | suse_vex | SUSE CVE CVE-2026-68348 | known affected: 30 known not affected: 266 | 2026-08-11T23:46:54+00:00 | Vulnerability · Source |
| CVE-2026-68349 | suse_vex | SUSE CVE CVE-2026-68349 | known affected: 197 known not affected: 99 | 2026-08-11T23:46:51+00:00 | Vulnerability · Source |
| CVE-2026-68350 | suse_vex | SUSE CVE CVE-2026-68350 | known affected: 197 known not affected: 99 | 2026-08-11T23:46:49+00:00 | Vulnerability · Source |
| CVE-2026-68351 | suse_vex | SUSE CVE CVE-2026-68351 | known affected: 197 known not affected: 99 | 2026-08-11T23:46:46+00:00 | Vulnerability · Source |
| CVE-2026-68352 | suse_vex | SUSE CVE CVE-2026-68352 | known affected: 193 known not affected: 103 | 2026-08-11T23:46:43+00:00 | Vulnerability · Source |
| CVE-2026-68353 | suse_vex | SUSE CVE CVE-2026-68353 | known affected: 193 known not affected: 103 | 2026-08-11T23:46:41+00:00 | Vulnerability · Source |
| CVE-2026-68354 | suse_vex | SUSE CVE CVE-2026-68354 | known affected: 197 known not affected: 99 | 2026-08-11T23:46:38+00:00 | Vulnerability · Source |
| CVE-2026-68355 | suse_vex | SUSE CVE CVE-2026-68355 | known affected: 118 known not affected: 178 | 2026-08-11T23:46:35+00:00 | Vulnerability · Source |
| CVE-2026-68356 | suse_vex | SUSE CVE CVE-2026-68356 | known not affected: 296 | 2026-08-11T23:46:33+00:00 | Vulnerability · Source |
| CVE-2026-68357 | suse_vex | SUSE CVE CVE-2026-68357 | known affected: 191 known not affected: 105 | 2026-08-11T23:46:30+00:00 | Vulnerability · Source |
| CVE-2026-68358 | suse_vex | SUSE CVE CVE-2026-68358 | known not affected: 296 | 2026-08-11T23:46:28+00:00 | Vulnerability · Source |
| CVE-2026-68359 | suse_vex | SUSE CVE CVE-2026-68359 | known affected: 30 known not affected: 266 | 2026-08-11T23:46:25+00:00 | Vulnerability · Source |
| CVE-2026-68408 | suse_vex | SUSE CVE CVE-2026-68408 | known affected: 99 known not affected: 197 | 2026-08-11T23:46:22+00:00 | Vulnerability · Source |
| CVE-2026-68409 | suse_vex | SUSE CVE CVE-2026-68409 | known affected: 117 known not affected: 179 | 2026-08-11T23:46:20+00:00 | Vulnerability · Source |
| CVE-2026-68410 | suse_vex | SUSE CVE CVE-2026-68410 | known affected: 193 known not affected: 103 | 2026-08-11T23:46:17+00:00 | Vulnerability · Source |
| CVE-2026-68411 | suse_vex | SUSE CVE CVE-2026-68411 | known affected: 231 known not affected: 65 | 2026-08-11T23:46:14+00:00 | Vulnerability · Source |
| CVE-2026-68412 | suse_vex | SUSE CVE CVE-2026-68412 | known affected: 284 known not affected: 12 | 2026-08-11T23:46:12+00:00 | Vulnerability · Source |
| CVE-2026-68413 | suse_vex | SUSE CVE CVE-2026-68413 | known affected: 197 known not affected: 99 | 2026-08-11T23:46:09+00:00 | Vulnerability · Source |
| CVE-2026-68414 | suse_vex | SUSE CVE CVE-2026-68414 | known affected: 197 known not affected: 99 | 2026-08-11T23:46:07+00:00 | Vulnerability · Source |
| CVE-2026-68415 | suse_vex | SUSE CVE CVE-2026-68415 | known not affected: 296 | 2026-08-11T23:46:04+00:00 | Vulnerability · Source |
| CVE-2026-68416 | suse_vex | SUSE CVE CVE-2026-68416 | known affected: 12 known not affected: 284 | 2026-08-11T23:46:02+00:00 | Vulnerability · Source |
| CVE-2026-68417 | suse_vex | SUSE CVE CVE-2026-68417 | known affected: 243 known not affected: 53 | 2026-08-11T23:45:59+00:00 | Vulnerability · Source |
| CVE-2026-68418 | suse_vex | SUSE CVE CVE-2026-68418 | known affected: 217 known not affected: 79 | 2026-08-11T23:45:57+00:00 | Vulnerability · Source |
| CVE-2026-68419 | suse_vex | SUSE CVE CVE-2026-68419 | known affected: 129 known not affected: 167 | 2026-08-11T23:45:54+00:00 | Vulnerability · Source |
| CVE-2026-68420 | suse_vex | SUSE CVE CVE-2026-68420 | known affected: 12 known not affected: 284 | 2026-08-11T23:45:52+00:00 | Vulnerability · Source |
| CVE-2026-68421 | suse_vex | SUSE CVE CVE-2026-68421 | known affected: 29 known not affected: 267 | 2026-08-11T23:45:49+00:00 | Vulnerability · Source |
| CVE-2026-68422 | suse_vex | SUSE CVE CVE-2026-68422 | known affected: 247 known not affected: 49 | 2026-08-11T23:45:47+00:00 | Vulnerability · Source |