VEX records
Browse vendor VEX statements available in this Vulnerability-Lookup instance and pivot to the related vulnerability.
286947 VEX records
API response| Vulnerability | Source | Title | Product status | Imported | Links |
|---|---|---|---|---|---|
| CVE-2025-40356 | suse_vex | SUSE CVE CVE-2025-40356 | known not affected: 418 | 2026-07-31T01:01:30+00:00 | Vulnerability · Source |
| CVE-2025-40364 | suse_vex | SUSE CVE CVE-2025-40364 | first fixed: 2 known affected: 394 known not affected: 348 recommended: 235 | 2026-07-31T01:01:27+00:00 | Vulnerability · Source |
| CVE-2025-41436 | suse_vex | SUSE CVE CVE-2025-41436 | No product status | 2026-07-31T01:01:24+00:00 | Vulnerability · Source |
| CVE-2025-43240 | suse_vex | SUSE CVE CVE-2025-43240 | known affected: 99 known not affected: 52 recommended: 592 | 2026-07-31T01:01:21+00:00 | Vulnerability · Source |
| CVE-2025-45582 | suse_vex | SUSE CVE CVE-2025-45582 | known affected: 411 recommended: 142 | 2026-07-31T01:01:19+00:00 | Vulnerability · Source |
| CVE-2025-46809 | suse_vex | SUSE CVE CVE-2025-46809 | known affected: 394 known not affected: 3 recommended: 68 | 2026-07-31T01:01:15+00:00 | Vulnerability · Source |
| CVE-2025-47912 | suse_vex | SUSE CVE CVE-2025-47912 | known affected: 24 known not affected: 67 recommended: 314 | 2026-07-31T01:01:12+00:00 | Vulnerability · Source |
| CVE-2025-48924 | suse_vex | SUSE CVE CVE-2025-48924 | known affected: 434 recommended: 518 | 2026-07-31T01:01:09+00:00 | Vulnerability · Source |
| CVE-2025-49176 | suse_vex | SUSE CVE CVE-2025-49176 | known affected: 421 recommended: 184 | 2026-07-31T01:01:06+00:00 | Vulnerability · Source |
| CVE-2025-50327 | suse_vex | SUSE CVE CVE-2025-50327 | No product status | 2026-07-31T01:01:03+00:00 | Vulnerability · Source |
| CVE-2025-52473 | suse_vex | SUSE CVE CVE-2025-52473 | known affected: 27 recommended: 28 | 2026-07-31T01:00:59+00:00 | Vulnerability · Source |
| CVE-2025-52490 | suse_vex | SUSE CVE CVE-2025-52490 | No product status | 2026-07-31T01:00:57+00:00 | Vulnerability · Source |
| CVE-2025-55070 | suse_vex | SUSE CVE CVE-2025-55070 | No product status | 2026-07-31T01:00:47+00:00 | Vulnerability · Source |
| CVE-2025-55073 | suse_vex | SUSE CVE CVE-2025-55073 | No product status | 2026-07-31T01:00:45+00:00 | Vulnerability · Source |
| CVE-2025-58160 | suse_vex | SUSE CVE CVE-2025-58160 | known affected: 492 known not affected: 379 recommended: 137 | 2026-07-31T01:00:40+00:00 | Vulnerability · Source |
| CVE-2025-62718 | suse_vex | SUSE CVE CVE-2025-62718 | known not affected: 359 | 2026-07-31T01:00:17+00:00 | Vulnerability · Source |
| CVE-2025-63811 | suse_vex | SUSE CVE CVE-2025-63811 | No product status | 2026-07-31T01:00:13+00:00 | Vulnerability · Source |
| CVE-2025-63913 | suse_vex | SUSE CVE CVE-2025-63913 | No product status | 2026-07-31T01:00:10+00:00 | Vulnerability · Source |
| CVE-2025-64171 | suse_vex | SUSE CVE CVE-2025-64171 | No product status | 2026-07-31T01:00:07+00:00 | Vulnerability · Source |
| CVE-2025-64178 | suse_vex | SUSE CVE CVE-2025-64178 | No product status | 2026-07-31T01:00:05+00:00 | Vulnerability · Source |
| CVE-2025-64179 | suse_vex | SUSE CVE CVE-2025-64179 | No product status | 2026-07-31T01:00:02+00:00 | Vulnerability · Source |
| CVE-2025-64183 | suse_vex | SUSE CVE CVE-2025-64183 | known not affected: 143 recommended: 30 | 2026-07-31T00:59:59+00:00 | Vulnerability · Source |
| CVE-2025-64186 | suse_vex | SUSE CVE CVE-2025-64186 | No product status | 2026-07-31T00:59:57+00:00 | Vulnerability · Source |
| 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-64720 | suse_vex | SUSE CVE CVE-2025-64720 | first fixed: 28 known affected: 428 known not affected: 134 recommended: 502 | 2026-07-31T00:59:33+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 |