VEX records
Browse vendor VEX statements available in this Vulnerability-Lookup instance and pivot to the related vulnerability.
288112 VEX records
API response| Vulnerability | Source | Title | Product status | Imported | Links |
|---|---|---|---|---|---|
| CVE-2025-64323 | suse_vex | SUSE CVE CVE-2025-64323 | No product status | 2026-07-31T00:59:54+00:00 | Vulnerability · Source |
| CVE-2025-64431 | suse_vex | SUSE CVE CVE-2025-64431 | No product status | 2026-07-31T00:59:51+00:00 | Vulnerability · Source |
| CVE-2025-64484 | suse_vex | SUSE CVE CVE-2025-64484 | No product status | 2026-07-31T00:59:48+00:00 | Vulnerability · Source |
| CVE-2025-64494 | suse_vex | SUSE CVE CVE-2025-64494 | No product status | 2026-07-31T00:59:46+00:00 | Vulnerability · Source |
| CVE-2025-64503 | suse_vex | SUSE CVE CVE-2025-64503 | known affected: 69 recommended: 36 | 2026-07-31T00:59:45+00:00 | Vulnerability · Source |
| CVE-2025-64513 | suse_vex | SUSE CVE CVE-2025-64513 | No product status | 2026-07-31T00:59:43+00:00 | Vulnerability · Source |
| CVE-2025-64522 | suse_vex | SUSE CVE CVE-2025-64522 | No product status | 2026-07-31T00:59:41+00:00 | Vulnerability · Source |
| CVE-2025-64523 | suse_vex | SUSE CVE CVE-2025-64523 | No product status | 2026-07-31T00:59:40+00:00 | Vulnerability · Source |
| CVE-2025-64529 | suse_vex | SUSE CVE CVE-2025-64529 | No product status | 2026-07-31T00:59:38+00:00 | Vulnerability · Source |
| CVE-2025-64717 | suse_vex | SUSE CVE CVE-2025-64717 | No product status | 2026-07-31T00:59:36+00:00 | Vulnerability · Source |
| CVE-2025-64719 | suse_vex | SUSE CVE CVE-2025-64719 | No product status | 2026-07-31T00:59:34+00:00 | Vulnerability · Source |
| CVE-2025-66418 | suse_vex | SUSE CVE CVE-2025-66418 | known affected: 437 known not affected: 6 recommended: 222 | 2026-07-31T00:59:25+00:00 | Vulnerability · Source |
| CVE-2025-66471 | suse_vex | SUSE CVE CVE-2025-66471 | known affected: 443 recommended: 234 | 2026-07-31T00:59:22+00:00 | Vulnerability · Source |
| CVE-2025-66719 | suse_vex | SUSE CVE CVE-2025-66719 | No product status | 2026-07-31T00:59:17+00:00 | Vulnerability · Source |
| CVE-2025-67860 | suse_vex | SUSE CVE CVE-2025-67860 | No product status | 2026-07-31T00:59:12+00:00 | Vulnerability · Source |
| CVE-2025-67873 | suse_vex | SUSE CVE CVE-2025-67873 | known affected: 37 recommended: 24 | 2026-07-31T00:59:10+00:00 | Vulnerability · Source |
| CVE-2025-68152 | suse_vex | SUSE CVE CVE-2025-68152 | No product status | 2026-07-31T00:59:08+00:00 | Vulnerability · Source |
| CVE-2025-68153 | suse_vex | SUSE CVE CVE-2025-68153 | No product status | 2026-07-31T00:59:07+00:00 | Vulnerability · Source |
| CVE-2025-68167 | suse_vex | SUSE CVE CVE-2025-68167 | first fixed: 2 known affected: 394 known not affected: 415 recommended: 172 | 2026-07-31T00:59:05+00:00 | Vulnerability · Source |
| CVE-2025-68179 | suse_vex | SUSE CVE CVE-2025-68179 | known affected: 184 known not affected: 266 recommended: 43 | 2026-07-31T00:59:01+00:00 | Vulnerability · Source |
| CVE-2025-68183 | suse_vex | SUSE CVE CVE-2025-68183 | first fixed: 2 known affected: 354 known not affected: 275 recommended: 701 | 2026-07-31T00:58:59+00:00 | Vulnerability · Source |
| CVE-2025-68184 | suse_vex | SUSE CVE CVE-2025-68184 | first fixed: 2 known affected: 484 known not affected: 266 recommended: 283 | 2026-07-31T00:58:58+00:00 | Vulnerability · Source |
| CVE-2025-68207 | suse_vex | SUSE CVE CVE-2025-68207 | first fixed: 2 known affected: 394 known not affected: 358 recommended: 283 | 2026-07-31T00:58:54+00:00 | Vulnerability · Source |
| CVE-2025-68215 | suse_vex | SUSE CVE CVE-2025-68215 | first fixed: 2 known affected: 394 known not affected: 374 recommended: 283 | 2026-07-31T00:58:52+00:00 | Vulnerability · Source |
| CVE-2025-68232 | suse_vex | SUSE CVE CVE-2025-68232 | known not affected: 418 | 2026-07-31T00:58:49+00:00 | Vulnerability · Source |
| CVE-2025-68234 | suse_vex | SUSE CVE CVE-2025-68234 | known affected: 394 known not affected: 386 recommended: 37 | 2026-07-31T00:58:47+00:00 | Vulnerability · Source |
| CVE-2025-68246 | suse_vex | SUSE CVE CVE-2025-68246 | known not affected: 432 | 2026-07-31T00:58:44+00:00 | Vulnerability · Source |
| CVE-2025-68260 | suse_vex | SUSE CVE CVE-2025-68260 | known not affected: 418 recommended: 6 | 2026-07-31T00:58:41+00:00 | Vulnerability · Source |
| CVE-2025-68294 | suse_vex | SUSE CVE CVE-2025-68294 | known not affected: 418 | 2026-07-31T00:58:36+00:00 | Vulnerability · Source |
| CVE-2025-68301 | suse_vex | SUSE CVE CVE-2025-68301 | first fixed: 2 known affected: 547 known not affected: 209 recommended: 410 | 2026-07-31T00:58:35+00:00 | Vulnerability · Source |
| CVE-2025-68302 | suse_vex | SUSE CVE CVE-2025-68302 | first fixed: 2 known affected: 762 known not affected: 6 recommended: 283 | 2026-07-31T00:58:33+00:00 | Vulnerability · Source |
| CVE-2025-68315 | suse_vex | SUSE CVE CVE-2025-68315 | known affected: 10 known not affected: 430 | 2026-07-31T00:58:30+00:00 | Vulnerability · Source |
| CVE-2025-68321 | suse_vex | SUSE CVE CVE-2025-68321 | known affected: 284 known not affected: 52 | 2026-07-31T00:58:27+00:00 | Vulnerability · Source |
| CVE-2025-68336 | suse_vex | SUSE CVE CVE-2025-68336 | known affected: 301 known not affected: 154 recommended: 6 | 2026-07-31T00:58:24+00:00 | Vulnerability · Source |
| CVE-2025-68341 | suse_vex | SUSE CVE CVE-2025-68341 | first fixed: 2 known not affected: 431 recommended: 172 | 2026-07-31T00:58:21+00:00 | Vulnerability · Source |
| CVE-2025-68349 | suse_vex | SUSE CVE CVE-2025-68349 | first fixed: 2 known affected: 709 known not affected: 22 recommended: 452 | 2026-07-31T00:58:17+00:00 | Vulnerability · Source |
| CVE-2025-68360 | suse_vex | SUSE CVE CVE-2025-68360 | first fixed: 2 known affected: 5 known not affected: 431 recommended: 178 | 2026-07-31T00:58:13+00:00 | Vulnerability · Source |
| CVE-2025-68724 | suse_vex | SUSE CVE CVE-2025-68724 | first fixed: 2 known affected: 622 known not affected: 66 recommended: 548 | 2026-07-31T00:58:07+00:00 | Vulnerability · Source |
| CVE-2025-68726 | suse_vex | SUSE CVE CVE-2025-68726 | known not affected: 453 recommended: 6 | 2026-07-31T00:58:05+00:00 | Vulnerability · Source |
| CVE-2025-68730 | suse_vex | SUSE CVE CVE-2025-68730 | known affected: 81 known not affected: 374 recommended: 6 | 2026-07-31T00:58:02+00:00 | Vulnerability · Source |
| CVE-2025-68745 | suse_vex | SUSE CVE CVE-2025-68745 | first fixed: 2 known affected: 382 known not affected: 22 recommended: 178 | 2026-07-31T00:57:56+00:00 | Vulnerability · Source |
| CVE-2025-68748 | suse_vex | SUSE CVE CVE-2025-68748 | first fixed: 2 known affected: 453 known not affected: 379 recommended: 178 | 2026-07-31T00:57:52+00:00 | Vulnerability · Source |
| CVE-2025-68761 | suse_vex | SUSE CVE CVE-2025-68761 | known not affected: 353 recommended: 6 | 2026-07-31T00:57:48+00:00 | Vulnerability · Source |
| CVE-2025-68774 | suse_vex | SUSE CVE CVE-2025-68774 | known affected: 562 known not affected: 79 recommended: 37 | 2026-07-31T00:57:43+00:00 | Vulnerability · Source |
| CVE-2025-68782 | suse_vex | SUSE CVE CVE-2025-68782 | known affected: 355 | 2026-07-31T00:57:39+00:00 | Vulnerability · Source |
| CVE-2025-68793 | suse_vex | SUSE CVE CVE-2025-68793 | known not affected: 336 | 2026-07-31T00:57:35+00:00 | Vulnerability · Source |
| CVE-2025-68799 | suse_vex | SUSE CVE CVE-2025-68799 | first fixed: 2 known not affected: 146 recommended: 172 | 2026-07-31T00:57:31+00:00 | Vulnerability · Source |
| CVE-2025-68800 | suse_vex | SUSE CVE CVE-2025-68800 | first fixed: 2 known affected: 549 known not affected: 93 recommended: 410 | 2026-07-31T00:57:29+00:00 | Vulnerability · Source |
| CVE-2025-68805 | suse_vex | SUSE CVE CVE-2025-68805 | known not affected: 336 | 2026-07-31T00:57:24+00:00 | Vulnerability · Source |
| CVE-2025-68811 | suse_vex | SUSE CVE CVE-2025-68811 | first fixed: 2 known affected: 5 known not affected: 331 recommended: 255 | 2026-07-31T00:57:20+00:00 | Vulnerability · Source |