VEX records
Browse vendor VEX statements available in this Vulnerability-Lookup instance and pivot to the related vulnerability.
292268 VEX records
API response| Vulnerability | Source | Title | Product status | Imported | Links |
|---|---|---|---|---|---|
| CVE-2026-66339 | redhat_vex | libsoup: libsoup: Proxy credentials leak to destination server via Proxy-Authorization header in CONNECT tunnels | known affected: 16 | 2026-07-25T00:06:04+00:00 | Vulnerability · Source |
| CVE-2026-10609 | redhat_vex | openshift/cluster-logging-operator: Cluster Logging Operator creates and forwards ServiceAccount tokens without verifying CLF creator authorization | known affected: 1 | 2026-07-24T20:06:57+00:00 | Vulnerability · Source |
| CVE-2024-53846 | redhat_vex | erlang: ssl fails to validate incorrect extened key usage | known not affected: 41 | 2026-07-24T18:36:17+00:00 | Vulnerability · Source |
| CVE-2025-68801 | suse_vex | SUSE CVE CVE-2025-68801 | first fixed: 2 known affected: 549 known not affected: 20 recommended: 307 | 2026-07-24T16:35:57+00:00 | Vulnerability · Source |
| CVE-2025-68803 | suse_vex | SUSE CVE CVE-2025-68803 | first fixed: 2 known affected: 509 known not affected: 152 recommended: 307 | 2026-07-24T16:35:55+00:00 | Vulnerability · Source |
| CVE-2025-68808 | suse_vex | SUSE CVE CVE-2025-68808 | first fixed: 2 known affected: 482 known not affected: 142 recommended: 402 | 2026-07-24T16:35:53+00:00 | Vulnerability · Source |
| CVE-2025-68810 | suse_vex | SUSE CVE CVE-2025-68810 | first fixed: 2 known affected: 465 known not affected: 200 recommended: 295 | 2026-07-24T16:35:51+00:00 | Vulnerability · Source |
| CVE-2025-68813 | suse_vex | SUSE CVE CVE-2025-68813 | first fixed: 2 known affected: 439 known not affected: 20 recommended: 750 | 2026-07-24T16:35:49+00:00 | Vulnerability · Source |
| CVE-2025-68814 | suse_vex | SUSE CVE CVE-2025-68814 | first fixed: 2 known affected: 509 known not affected: 152 recommended: 307 | 2026-07-24T16:35:47+00:00 | Vulnerability · Source |
| CVE-2025-68815 | suse_vex | SUSE CVE CVE-2025-68815 | first fixed: 2 known affected: 568 known not affected: 93 recommended: 307 | 2026-07-24T16:35:45+00:00 | Vulnerability · Source |
| CVE-2025-68817 | suse_vex | SUSE CVE CVE-2025-68817 | known not affected: 353 | 2026-07-24T16:35:43+00:00 | Vulnerability · Source |
| CVE-2025-68819 | suse_vex | SUSE CVE CVE-2025-68819 | first fixed: 2 known affected: 451 known not affected: 30 recommended: 402 | 2026-07-24T16:35:41+00:00 | Vulnerability · Source |
| CVE-2025-68820 | suse_vex | SUSE CVE CVE-2025-68820 | first fixed: 2 known affected: 549 known not affected: 112 recommended: 307 | 2026-07-24T16:35:39+00:00 | Vulnerability · Source |
| CVE-2025-68920 | suse_vex | SUSE CVE CVE-2025-68920 | known affected: 47 recommended: 2 | 2026-07-24T16:35:37+00:00 | Vulnerability · Source |
| CVE-2025-69645 | suse_vex | SUSE CVE CVE-2025-69645 | known affected: 157 | 2026-07-24T16:35:32+00:00 | Vulnerability · Source |
| CVE-2025-69651 | suse_vex | SUSE CVE CVE-2025-69651 | known not affected: 154 | 2026-07-24T16:35:29+00:00 | Vulnerability · Source |
| CVE-2025-70071 | suse_vex | SUSE CVE CVE-2025-70071 | known affected: 736 | 2026-07-24T16:35:25+00:00 | Vulnerability · Source |
| CVE-2025-71064 | suse_vex | SUSE CVE CVE-2025-71064 | first fixed: 2 known affected: 611 known not affected: 20 recommended: 330 | 2026-07-24T16:35:23+00:00 | Vulnerability · Source |
| CVE-2025-71065 | suse_vex | SUSE CVE CVE-2025-71065 | known not affected: 336 | 2026-07-24T16:35:21+00:00 | Vulnerability · Source |
| CVE-2025-71067 | suse_vex | SUSE CVE CVE-2025-71067 | known not affected: 357 | 2026-07-24T16:35:18+00:00 | Vulnerability · Source |
| CVE-2025-71068 | suse_vex | SUSE CVE CVE-2025-71068 | known affected: 243 known not affected: 112 | 2026-07-24T16:35:16+00:00 | Vulnerability · Source |
| CVE-2025-71071 | suse_vex | SUSE CVE CVE-2025-71071 | first fixed: 2 known affected: 513 known not affected: 152 recommended: 295 | 2026-07-24T16:35:14+00:00 | Vulnerability · Source |
| CVE-2025-71073 | suse_vex | SUSE CVE CVE-2025-71073 | first fixed: 2 known not affected: 340 recommended: 172 | 2026-07-24T16:35:13+00:00 | Vulnerability · Source |
| CVE-2025-71075 | suse_vex | SUSE CVE CVE-2025-71075 | known affected: 717 recommended: 37 | 2026-07-24T16:35:11+00:00 | Vulnerability · Source |
| CVE-2025-71076 | suse_vex | SUSE CVE CVE-2025-71076 | first fixed: 2 known affected: 394 known not affected: 262 recommended: 283 | 2026-07-24T16:35:09+00:00 | Vulnerability · Source |
| CVE-2025-71078 | suse_vex | SUSE CVE CVE-2025-71078 | first fixed: 2 known affected: 513 known not affected: 111 recommended: 402 | 2026-07-24T16:35:06+00:00 | Vulnerability · Source |
| CVE-2025-71081 | suse_vex | SUSE CVE CVE-2025-71081 | first fixed: 2 known affected: 394 known not affected: 230 recommended: 402 | 2026-07-24T16:35:03+00:00 | Vulnerability · Source |
| CVE-2025-71083 | suse_vex | SUSE CVE CVE-2025-71083 | first fixed: 2 known affected: 530 known not affected: 94 recommended: 402 | 2026-07-24T16:35:01+00:00 | Vulnerability · Source |
| CVE-2025-71084 | suse_vex | SUSE CVE CVE-2025-71084 | first fixed: 2 known affected: 568 known not affected: 93 recommended: 307 | 2026-07-24T16:34:59+00:00 | Vulnerability · Source |
| CVE-2025-71086 | suse_vex | SUSE CVE CVE-2025-71086 | first fixed: 2 known affected: 394 known not affected: 205 recommended: 307 | 2026-07-24T16:34:55+00:00 | Vulnerability · Source |
| CVE-2025-71088 | suse_vex | SUSE CVE CVE-2025-71088 | first fixed: 2 known affected: 461 known not affected: 200 recommended: 307 | 2026-07-24T16:34:53+00:00 | Vulnerability · Source |
| CVE-2025-71090 | suse_vex | SUSE CVE CVE-2025-71090 | known not affected: 336 | 2026-07-24T16:34:49+00:00 | Vulnerability · Source |
| CVE-2025-71091 | suse_vex | SUSE CVE CVE-2025-71091 | first fixed: 2 known affected: 625 known not affected: 4 recommended: 344 | 2026-07-24T16:34:47+00:00 | Vulnerability · Source |
| CVE-2025-71093 | suse_vex | SUSE CVE CVE-2025-71093 | first fixed: 2 known affected: 629 recommended: 344 | 2026-07-24T16:34:45+00:00 | Vulnerability · Source |
| CVE-2025-71094 | suse_vex | SUSE CVE CVE-2025-71094 | first fixed: 2 known affected: 487 known not affected: 112 recommended: 307 | 2026-07-24T16:34:44+00:00 | Vulnerability · Source |
| CVE-2025-71098 | suse_vex | SUSE CVE CVE-2025-71098 | first fixed: 2 known affected: 558 known not affected: 30 recommended: 344 | 2026-07-24T16:34:41+00:00 | Vulnerability · Source |
| CVE-2025-71103 | suse_vex | SUSE CVE CVE-2025-71103 | known not affected: 321 | 2026-07-24T16:34:38+00:00 | Vulnerability · Source |
| CVE-2025-71104 | suse_vex | SUSE CVE CVE-2025-71104 | first fixed: 2 known affected: 600 known not affected: 20 recommended: 318 | 2026-07-24T16:34:37+00:00 | Vulnerability · Source |
| CVE-2025-71106 | suse_vex | SUSE CVE CVE-2025-71106 | known not affected: 321 | 2026-07-24T16:34:35+00:00 | Vulnerability · Source |
| CVE-2025-71108 | suse_vex | SUSE CVE CVE-2025-71108 | first fixed: 2 known affected: 596 known not affected: 20 recommended: 330 | 2026-07-24T16:34:33+00:00 | Vulnerability · Source |
| CVE-2025-71111 | suse_vex | SUSE CVE CVE-2025-71111 | first fixed: 2 known affected: 394 known not affected: 205 recommended: 402 | 2026-07-24T16:34:31+00:00 | Vulnerability · Source |
| CVE-2025-71112 | suse_vex | SUSE CVE CVE-2025-71112 | first fixed: 2 known affected: 400 known not affected: 34 recommended: 625 | 2026-07-24T16:34:29+00:00 | Vulnerability · Source |
| CVE-2025-71114 | suse_vex | SUSE CVE CVE-2025-71114 | first fixed: 2 known affected: 451 known not affected: 41 recommended: 307 | 2026-07-24T16:34:26+00:00 | Vulnerability · Source |
| CVE-2025-71116 | suse_vex | SUSE CVE CVE-2025-71116 | first fixed: 2 known affected: 486 recommended: 601 | 2026-07-24T16:34:24+00:00 | Vulnerability · Source |
| CVE-2025-71117 | suse_vex | SUSE CVE CVE-2025-71117 | known not affected: 316 recommended: 27 | 2026-07-24T16:34:22+00:00 | Vulnerability · Source |
| CVE-2025-71118 | suse_vex | SUSE CVE CVE-2025-71118 | first fixed: 2 known affected: 553 known not affected: 61 recommended: 344 | 2026-07-24T16:34:20+00:00 | Vulnerability · Source |
| CVE-2025-71119 | suse_vex | SUSE CVE CVE-2025-71119 | first fixed: 2 known affected: 482 known not affected: 134 recommended: 330 | 2026-07-24T16:34:18+00:00 | Vulnerability · Source |
| CVE-2025-71120 | suse_vex | SUSE CVE CVE-2025-71120 | first fixed: 2 known affected: 400 known not affected: 34 recommended: 749 | 2026-07-24T16:34:16+00:00 | Vulnerability · Source |
| CVE-2025-71123 | suse_vex | SUSE CVE CVE-2025-71123 | first fixed: 2 known affected: 399 known not affected: 168 recommended: 344 | 2026-07-24T16:34:15+00:00 | Vulnerability · Source |
| CVE-2025-71125 | suse_vex | SUSE CVE CVE-2025-71125 | first fixed: 2 known affected: 569 known not affected: 81 recommended: 295 | 2026-07-24T16:34:13+00:00 | Vulnerability · Source |