VEX records
Browse vendor VEX statements available in this Vulnerability-Lookup instance and pivot to the related vulnerability.
291348 VEX records
API response| Vulnerability | Source | Title | Product status | Imported | Links |
|---|---|---|---|---|---|
| CVE-2026-43964 | suse_vex | SUSE CVE CVE-2026-43964 | known affected: 95 recommended: 104 | 2026-08-07T00:05:43+00:00 | Vulnerability · Source |
| CVE-2026-44210 | suse_vex | SUSE CVE CVE-2026-44210 | No product status | 2026-08-07T00:05:41+00:00 | Vulnerability · Source |
| CVE-2026-54465 | suse_vex | SUSE CVE CVE-2026-54465 | known affected: 14 known not affected: 377 | 2026-08-07T00:02:56+00:00 | Vulnerability · Source |
| CVE-2026-54466 | suse_vex | SUSE CVE CVE-2026-54466 | known affected: 11 known not affected: 298 recommended: 1 | 2026-08-07T00:02:54+00:00 | Vulnerability · Source |
| CVE-2026-54513 | suse_vex | SUSE CVE CVE-2026-54513 | known affected: 6 recommended: 147 | 2026-08-07T00:02:52+00:00 | Vulnerability · Source |
| CVE-2026-54522 | suse_vex | SUSE CVE CVE-2026-54522 | No product status | 2026-08-07T00:02:50+00:00 | Vulnerability · Source |
| CVE-2026-54876 | suse_vex | SUSE CVE CVE-2026-54876 | known not affected: 486 | 2026-08-07T00:02:47+00:00 | Vulnerability · Source |
| CVE-2026-57062 | suse_vex | SUSE CVE CVE-2026-57062 | known affected: 411 known not affected: 56 recommended: 33 | 2026-08-07T00:02:18+00:00 | Vulnerability · Source |
| CVE-2026-59676 | suse_vex | SUSE CVE CVE-2026-59676 | known affected: 184 | 2026-08-07T00:01:37+00:00 | Vulnerability · Source |
| CVE-2026-59677 | suse_vex | SUSE CVE CVE-2026-59677 | known affected: 184 | 2026-08-07T00:01:35+00:00 | Vulnerability · Source |
| CVE-2026-59856 | suse_vex | SUSE CVE CVE-2026-59856 | first fixed: 2 known affected: 442 recommended: 150 | 2026-08-07T00:01:17+00:00 | Vulnerability · Source |
| CVE-2026-59857 | suse_vex | SUSE CVE CVE-2026-59857 | first fixed: 2 known affected: 442 recommended: 138 | 2026-08-07T00:01:15+00:00 | Vulnerability · Source |
| CVE-2026-59858 | suse_vex | SUSE CVE CVE-2026-59858 | first fixed: 2 known affected: 442 recommended: 155 | 2026-08-07T00:01:13+00:00 | Vulnerability · Source |
| CVE-2026-62423 | suse_vex | SUSE CVE CVE-2026-62423 | first fixed: 26 known affected: 456 recommended: 108 | 2026-08-07T00:00:57+00:00 | Vulnerability · Source |
| CVE-2026-62424 | suse_vex | SUSE CVE CVE-2026-62424 | first fixed: 26 known affected: 62 recommended: 101 | 2026-08-07T00:00:55+00:00 | Vulnerability · Source |
| CVE-2026-62425 | suse_vex | SUSE CVE CVE-2026-62425 | first fixed: 26 known affected: 62 recommended: 101 | 2026-08-07T00:00:53+00:00 | Vulnerability · Source |
| CVE-2026-62426 | suse_vex | SUSE CVE CVE-2026-62426 | first fixed: 26 known affected: 456 recommended: 108 | 2026-08-07T00:00:51+00:00 | Vulnerability · Source |
| CVE-2026-62427 | suse_vex | SUSE CVE CVE-2026-62427 | first fixed: 26 known affected: 62 recommended: 101 | 2026-08-07T00:00:49+00:00 | Vulnerability · Source |
| CVE-2026-62428 | suse_vex | SUSE CVE CVE-2026-62428 | first fixed: 26 known affected: 456 recommended: 108 | 2026-08-07T00:00:47+00:00 | Vulnerability · Source |
| CVE-2026-62429 | suse_vex | SUSE CVE CVE-2026-62429 | first fixed: 26 known affected: 456 recommended: 108 | 2026-08-07T00:00:45+00:00 | Vulnerability · Source |
| CVE-2026-62430 | suse_vex | SUSE CVE CVE-2026-62430 | first fixed: 26 known affected: 456 recommended: 108 | 2026-08-07T00:00:43+00:00 | Vulnerability · Source |
| CVE-2026-62431 | suse_vex | SUSE CVE CVE-2026-62431 | first fixed: 26 known affected: 446 known not affected: 26 recommended: 94 | 2026-08-07T00:00:42+00:00 | Vulnerability · Source |
| CVE-2026-62432 | suse_vex | SUSE CVE CVE-2026-62432 | first fixed: 26 known affected: 456 recommended: 108 | 2026-08-07T00:00:40+00:00 | Vulnerability · Source |
| CVE-2026-62433 | suse_vex | SUSE CVE CVE-2026-62433 | first fixed: 26 known affected: 456 recommended: 108 | 2026-08-07T00:00:38+00:00 | Vulnerability · Source |
| CVE-2026-62434 | suse_vex | SUSE CVE CVE-2026-62434 | first fixed: 26 known affected: 456 recommended: 108 | 2026-08-07T00:00:36+00:00 | Vulnerability · Source |
| CVE-2026-64127 | suse_vex | SUSE CVE CVE-2026-64127 | known not affected: 296 | 2026-08-07T00:00:22+00:00 | Vulnerability · Source |
| CVE-2026-64128 | suse_vex | SUSE CVE CVE-2026-64128 | known affected: 78 known not affected: 218 | 2026-08-07T00:00:20+00:00 | Vulnerability · Source |
| CVE-2026-64130 | suse_vex | SUSE CVE CVE-2026-64130 | known not affected: 296 | 2026-08-07T00:00:18+00:00 | Vulnerability · Source |
| CVE-2026-64131 | suse_vex | SUSE CVE CVE-2026-64131 | known affected: 129 known not affected: 167 | 2026-08-07T00:00:16+00:00 | Vulnerability · Source |
| CVE-2026-64133 | suse_vex | SUSE CVE CVE-2026-64133 | known affected: 197 known not affected: 99 | 2026-08-07T00:00:13+00:00 | Vulnerability · Source |
| CVE-2026-64134 | suse_vex | SUSE CVE CVE-2026-64134 | known not affected: 296 | 2026-08-07T00:00:11+00:00 | Vulnerability · Source |
| CVE-2026-64138 | suse_vex | SUSE CVE CVE-2026-64138 | known not affected: 298 | 2026-08-07T00:00:05+00:00 | Vulnerability · Source |
| CVE-2026-64143 | suse_vex | SUSE CVE CVE-2026-64143 | known not affected: 296 | 2026-08-07T00:00:03+00:00 | Vulnerability · Source |
| CVE-2026-64148 | suse_vex | SUSE CVE CVE-2026-64148 | known affected: 129 known not affected: 167 | 2026-08-07T00:00:01+00:00 | Vulnerability · Source |
| CVE-2026-64149 | suse_vex | SUSE CVE CVE-2026-64149 | known not affected: 296 | 2026-08-06T23:59:59+00:00 | Vulnerability · Source |
| CVE-2026-64151 | suse_vex | SUSE CVE CVE-2026-64151 | known not affected: 296 | 2026-08-06T23:59:56+00:00 | Vulnerability · Source |
| CVE-2026-64152 | suse_vex | SUSE CVE CVE-2026-64152 | known not affected: 296 | 2026-08-06T23:59:54+00:00 | Vulnerability · Source |
| CVE-2026-64153 | suse_vex | SUSE CVE CVE-2026-64153 | known affected: 177 known not affected: 119 | 2026-08-06T23:59:51+00:00 | Vulnerability · Source |
| CVE-2026-64164 | suse_vex | SUSE CVE CVE-2026-64164 | known affected: 99 known not affected: 197 | 2026-08-06T23:59:46+00:00 | Vulnerability · Source |
| CVE-2026-64167 | suse_vex | SUSE CVE CVE-2026-64167 | known not affected: 296 | 2026-08-06T23:59:44+00:00 | Vulnerability · Source |
| CVE-2026-64176 | suse_vex | SUSE CVE CVE-2026-64176 | known affected: 12 known not affected: 284 | 2026-08-06T23:59:41+00:00 | Vulnerability · Source |
| CVE-2026-64178 | suse_vex | SUSE CVE CVE-2026-64178 | known affected: 197 known not affected: 99 | 2026-08-06T23:59:39+00:00 | Vulnerability · Source |
| CVE-2026-64522 | suse_vex | SUSE CVE CVE-2026-64522 | known not affected: 298 | 2026-08-06T23:56:53+00:00 | Vulnerability · Source |
| CVE-2026-64526 | suse_vex | SUSE CVE CVE-2026-64526 | known affected: 29 known not affected: 269 | 2026-08-06T23:56:51+00:00 | Vulnerability · Source |
| CVE-2026-64565 | suse_vex | SUSE CVE CVE-2026-64565 | known affected: 193 known not affected: 103 | 2026-08-06T23:56:38+00:00 | Vulnerability · Source |
| CVE-2026-69240 | suse_vex | SUSE CVE CVE-2026-69240 | No product status | 2026-08-06T23:54:53+00:00 | Vulnerability · Source |
| CVE-2026-71225 | suse_vex | SUSE CVE CVE-2026-71225 | known affected: 26 known not affected: 102 | 2026-08-06T23:54:52+00:00 | Vulnerability · Source |
| CVE-2026-71226 | suse_vex | SUSE CVE CVE-2026-71226 | known affected: 26 known not affected: 102 | 2026-08-06T23:54:50+00:00 | Vulnerability · Source |
| CVE-2026-71227 | suse_vex | SUSE CVE CVE-2026-71227 | known affected: 26 known not affected: 102 | 2026-08-06T23:54:49+00:00 | Vulnerability · Source |
| CVE-2026-67589 | redhat_vex | org.apache.qpid/protonj2: Apache Qpid ProtonJ2: Denial of Service via excessive memory allocation | known affected: 1 | 2026-08-06T22:30:00+00:00 | Vulnerability · Source |