VEX records
Browse vendor VEX statements available in this Vulnerability-Lookup instance and pivot to the related vulnerability.
283483 VEX records
API response| Vulnerability | Source | Title | Product status | Imported | Links |
|---|---|---|---|---|---|
| CVE-2025-14104 | suse_vex | SUSE CVE CVE-2025-14104 | known affected: 908 known not affected: 1 recommended: 459 | 2026-07-25T16:51:38+00:00 | Vulnerability · Source |
| CVE-2025-15281 | suse_vex | SUSE CVE CVE-2025-15281 | first fixed: 1 known affected: 492 known not affected: 64 recommended: 778 | 2026-07-25T16:51:35+00:00 | Vulnerability · Source |
| CVE-2025-20012 | suse_vex | SUSE CVE CVE-2025-20012 | known affected: 10 recommended: 46 | 2026-07-25T16:51:33+00:00 | Vulnerability · Source |
| CVE-2025-21777 | suse_vex | SUSE CVE CVE-2025-21777 | known affected: 59 known not affected: 346 recommended: 95 | 2026-07-25T16:51:29+00:00 | Vulnerability · Source |
| CVE-2025-21816 | suse_vex | SUSE CVE CVE-2025-21816 | first fixed: 2 known affected: 453 known not affected: 331 recommended: 154 | 2026-07-25T16:51:28+00:00 | Vulnerability · Source |
| CVE-2025-22068 | suse_vex | SUSE CVE CVE-2025-22068 | known not affected: 344 recommended: 95 | 2026-07-25T16:51:25+00:00 | Vulnerability · Source |
| CVE-2025-22134 | suse_vex | SUSE CVE CVE-2025-22134 | known affected: 474 known not affected: 3 recommended: 162 | 2026-07-25T16:51:23+00:00 | Vulnerability · Source |
| CVE-2025-23085 | suse_vex | SUSE CVE CVE-2025-23085 | known affected: 116 known not affected: 41 recommended: 160 | 2026-07-25T16:51:21+00:00 | Vulnerability · Source |
| CVE-2025-24216 | suse_vex | SUSE CVE CVE-2025-24216 | known affected: 88 recommended: 592 | 2026-07-25T16:51:19+00:00 | Vulnerability · Source |
| CVE-2025-32906 | suse_vex | SUSE CVE CVE-2025-32906 | known affected: 21 recommended: 246 | 2026-07-25T16:51:15+00:00 | Vulnerability · Source |
| CVE-2025-32988 | suse_vex | SUSE CVE CVE-2025-32988 | known affected: 423 known not affected: 38 recommended: 310 | 2026-07-25T16:51:14+00:00 | Vulnerability · Source |
| CVE-2025-37762 | suse_vex | SUSE CVE CVE-2025-37762 | known not affected: 397 | 2026-07-25T16:51:12+00:00 | Vulnerability · Source |
| CVE-2025-37834 | suse_vex | SUSE CVE CVE-2025-37834 | known not affected: 398 | 2026-07-25T16:51:10+00:00 | Vulnerability · Source |
| CVE-2025-37878 | suse_vex | SUSE CVE CVE-2025-37878 | known not affected: 442 recommended: 53 | 2026-07-25T16:51:08+00:00 | Vulnerability · Source |
| CVE-2025-37999 | suse_vex | SUSE CVE CVE-2025-37999 | known not affected: 397 recommended: 53 | 2026-07-25T16:51:05+00:00 | Vulnerability · Source |
| CVE-2025-38048 | suse_vex | SUSE CVE CVE-2025-38048 | known affected: 127 known not affected: 150 | 2026-07-25T16:51:04+00:00 | Vulnerability · Source |
| CVE-2025-38071 | suse_vex | SUSE CVE CVE-2025-38071 | known not affected: 205 | 2026-07-25T16:51:02+00:00 | Vulnerability · Source |
| CVE-2025-38196 | suse_vex | SUSE CVE CVE-2025-38196 | known not affected: 416 | 2026-07-25T16:50:59+00:00 | Vulnerability · Source |
| CVE-2025-38309 | suse_vex | SUSE CVE CVE-2025-38309 | known not affected: 416 | 2026-07-25T16:50:56+00:00 | Vulnerability · Source |
| CVE-2025-38368 | suse_vex | SUSE CVE CVE-2025-38368 | first fixed: 2 known not affected: 416 recommended: 154 | 2026-07-25T16:50:54+00:00 | Vulnerability · Source |
| CVE-2025-38381 | suse_vex | SUSE CVE CVE-2025-38381 | first fixed: 2 known not affected: 416 recommended: 154 | 2026-07-25T16:50:52+00:00 | Vulnerability · Source |
| CVE-2025-38508 | suse_vex | SUSE CVE CVE-2025-38508 | first fixed: 2 known affected: 5 known not affected: 448 recommended: 154 | 2026-07-25T16:50:49+00:00 | Vulnerability · Source |
| CVE-2025-38598 | suse_vex | SUSE CVE CVE-2025-38598 | known not affected: 416 | 2026-07-25T16:50:47+00:00 | Vulnerability · Source |
| CVE-2025-38711 | suse_vex | SUSE CVE CVE-2025-38711 | known not affected: 416 | 2026-07-25T16:50:45+00:00 | Vulnerability · Source |
| CVE-2025-38723 | suse_vex | SUSE CVE CVE-2025-38723 | known affected: 196 known not affected: 205 | 2026-07-25T16:50:43+00:00 | Vulnerability · Source |
| CVE-2025-39712 | suse_vex | SUSE CVE CVE-2025-39712 | first fixed: 2 known affected: 57 known not affected: 353 recommended: 154 | 2026-07-25T16:50:42+00:00 | Vulnerability · Source |
| CVE-2025-39734 | suse_vex | SUSE CVE CVE-2025-39734 | known not affected: 416 | 2026-07-25T16:50:40+00:00 | Vulnerability · Source |
| CVE-2025-39736 | suse_vex | SUSE CVE CVE-2025-39736 | known not affected: 453 | 2026-07-25T16:50:39+00:00 | Vulnerability · Source |
| CVE-2025-39745 | suse_vex | SUSE CVE CVE-2025-39745 | known affected: 24 known not affected: 433 | 2026-07-25T16:50:37+00:00 | Vulnerability · Source |
| CVE-2025-39755 | suse_vex | SUSE CVE CVE-2025-39755 | known not affected: 348 | 2026-07-25T16:50:36+00:00 | Vulnerability · Source |
| CVE-2025-39896 | suse_vex | SUSE CVE CVE-2025-39896 | first fixed: 2 known affected: 64 known not affected: 376 recommended: 154 | 2026-07-25T16:50:33+00:00 | Vulnerability · Source |
| CVE-2025-39933 | suse_vex | SUSE CVE CVE-2025-39933 | known not affected: 416 recommended: 103 | 2026-07-25T16:50:32+00:00 | Vulnerability · Source |
| CVE-2025-40047 | suse_vex | SUSE CVE CVE-2025-40047 | first fixed: 2 known affected: 394 known not affected: 376 recommended: 354 | 2026-07-25T16:50:29+00:00 | Vulnerability · Source |
| CVE-2025-40050 | suse_vex | SUSE CVE CVE-2025-40050 | known not affected: 407 recommended: 6 | 2026-07-25T16:50:27+00:00 | Vulnerability · Source |
| CVE-2025-40068 | suse_vex | SUSE CVE CVE-2025-40068 | known not affected: 407 recommended: 6 | 2026-07-25T16:50:26+00:00 | Vulnerability · Source |
| CVE-2025-40084 | suse_vex | SUSE CVE CVE-2025-40084 | known not affected: 407 recommended: 6 | 2026-07-25T16:50:24+00:00 | Vulnerability · Source |
| CVE-2025-40093 | suse_vex | SUSE CVE CVE-2025-40093 | known affected: 26 known not affected: 403 recommended: 6 | 2026-07-25T16:50:23+00:00 | Vulnerability · Source |
| CVE-2025-40161 | suse_vex | SUSE CVE CVE-2025-40161 | first fixed: 2 known not affected: 405 recommended: 154 | 2026-07-25T16:50:21+00:00 | Vulnerability · Source |
| CVE-2025-40182 | suse_vex | SUSE CVE CVE-2025-40182 | known not affected: 408 | 2026-07-25T16:50:19+00:00 | Vulnerability · Source |
| CVE-2025-40295 | suse_vex | SUSE CVE CVE-2025-40295 | known not affected: 414 | 2026-07-25T16:50:17+00:00 | Vulnerability · Source |
| CVE-2025-40354 | suse_vex | SUSE CVE CVE-2025-40354 | first fixed: 2 known affected: 394 known not affected: 372 recommended: 283 | 2026-07-25T16:50:15+00:00 | Vulnerability · Source |
| CVE-2025-43265 | suse_vex | SUSE CVE CVE-2025-43265 | known affected: 99 known not affected: 52 recommended: 592 | 2026-07-25T16:50:13+00:00 | Vulnerability · Source |
| CVE-2025-43531 | suse_vex | SUSE CVE CVE-2025-43531 | known affected: 133 recommended: 624 | 2026-07-25T16:50:11+00:00 | Vulnerability · Source |
| CVE-2025-43921 | suse_vex | SUSE CVE CVE-2025-43921 | known not affected: 10 | 2026-07-25T16:50:10+00:00 | Vulnerability · Source |
| CVE-2025-48384 | suse_vex | SUSE CVE CVE-2025-48384 | known affected: 110 recommended: 461 | 2026-07-25T16:50:08+00:00 | Vulnerability · Source |
| CVE-2025-48734 | suse_vex | SUSE CVE CVE-2025-48734 | known affected: 400 recommended: 550 | 2026-07-25T16:50:06+00:00 | Vulnerability · Source |
| CVE-2025-49794 | suse_vex | SUSE CVE CVE-2025-49794 | known affected: 423 known not affected: 63 recommended: 285 | 2026-07-25T16:50:05+00:00 | Vulnerability · Source |
| CVE-2025-49812 | suse_vex | SUSE CVE CVE-2025-49812 | known affected: 474 recommended: 310 | 2026-07-25T16:50:03+00:00 | Vulnerability · Source |
| CVE-2025-54571 | suse_vex | SUSE CVE CVE-2025-54571 | known affected: 33 recommended: 16 | 2026-07-25T16:50:01+00:00 | Vulnerability · Source |
| CVE-2025-64506 | suse_vex | SUSE CVE CVE-2025-64506 | known affected: 416 known not affected: 149 recommended: 208 | 2026-07-25T16:49:58+00:00 | Vulnerability · Source |