VEX records
Browse vendor VEX statements available in this Vulnerability-Lookup instance and pivot to the related vulnerability.
291704 VEX records
API response| Vulnerability | Source | Title | Product status | Imported | Links |
|---|---|---|---|---|---|
| CVE-2025-66866 | suse_vex | SUSE CVE CVE-2025-66866 | known affected: 214 | 2026-08-13T16:33:24+00:00 | Vulnerability · Source |
| CVE-2025-68368 | suse_vex | SUSE CVE CVE-2025-68368 | first fixed: 2 known affected: 5 known not affected: 431 recommended: 178 | 2026-08-13T16:33:15+00:00 | Vulnerability · Source |
| CVE-2025-68375 | suse_vex | SUSE CVE CVE-2025-68375 | known not affected: 453 recommended: 33 | 2026-08-13T16:33:13+00:00 | Vulnerability · Source |
| CVE-2025-68376 | suse_vex | SUSE CVE CVE-2025-68376 | first fixed: 2 known affected: 5 known not affected: 431 recommended: 178 | 2026-08-13T16:33:12+00:00 | Vulnerability · Source |
| CVE-2025-68731 | suse_vex | SUSE CVE CVE-2025-68731 | known not affected: 453 recommended: 6 | 2026-08-13T16:33:09+00:00 | Vulnerability · Source |
| CVE-2026-71287 | redhat_vex | cacti: Cacti: Blind SQL injection due to improper input sanitization | known not affected: 1 | 2026-08-13T16:33:00+00:00 | Vulnerability · Source |
| CVE-2025-71153 | suse_vex | SUSE CVE CVE-2025-71153 | known not affected: 332 | 2026-08-13T16:32:50+00:00 | Vulnerability · Source |
| CVE-2025-71156 | suse_vex | SUSE CVE CVE-2025-71156 | first fixed: 2 known affected: 399 known not affected: 259 recommended: 283 | 2026-08-13T16:32:48+00:00 | Vulnerability · Source |
| CVE-2026-65324 | redhat_vex | Apache Traffic Server: HTTP/2 and HTTP/3 dechunking removes per-stream buffer cap, allowing memory exhaustion | known not affected: 1 | 2026-08-13T16:32:45+00:00 | Vulnerability · Source |
| CVE-2025-71230 | suse_vex | SUSE CVE CVE-2025-71230 | known not affected: 336 recommended: 4 | 2026-08-13T16:32:45+00:00 | Vulnerability · Source |
| CVE-2025-71290 | suse_vex | SUSE CVE CVE-2025-71290 | known not affected: 293 | 2026-08-13T16:32:41+00:00 | Vulnerability · Source |
| CVE-2025-71296 | suse_vex | SUSE CVE CVE-2025-71296 | known not affected: 295 | 2026-08-13T16:32:38+00:00 | Vulnerability · Source |
| CVE-2026-2673 | suse_vex | SUSE CVE CVE-2026-2673 | first fixed: 61 known not affected: 521 recommended: 42 | 2026-08-13T16:32:31+00:00 | Vulnerability · Source |
| CVE-2026-5917 | suse_vex | SUSE CVE CVE-2026-5917 | known affected: 90 | 2026-08-13T16:32:17+00:00 | Vulnerability · Source |
| CVE-2026-9318 | suse_vex | SUSE CVE CVE-2026-9318 | known affected: 10 | 2026-08-13T16:32:00+00:00 | Vulnerability · Source |
| CVE-2026-13601 | suse_vex | SUSE CVE CVE-2026-13601 | known affected: 30 recommended: 94 | 2026-08-13T16:31:49+00:00 | Vulnerability · Source |
| CVE-2026-15028 | suse_vex | SUSE CVE CVE-2026-15028 | known affected: 151 | 2026-08-13T16:31:41+00:00 | Vulnerability · Source |
| CVE-2026-19404 | suse_vex | SUSE CVE CVE-2026-19404 | known affected: 108 | 2026-08-13T16:31:28+00:00 | Vulnerability · Source |
| CVE-2026-23204 | suse_vex | SUSE CVE CVE-2026-23204 | first fixed: 17 known affected: 453 recommended: 880 | 2026-08-13T16:31:13+00:00 | Vulnerability · Source |
| CVE-2026-28390 | suse_vex | SUSE CVE CVE-2026-28390 | first fixed: 61 known affected: 476 known not affected: 92 recommended: 401 | 2026-08-13T16:30:38+00:00 | Vulnerability · Source |
| CVE-2026-34182 | suse_vex | SUSE CVE CVE-2026-34182 | first fixed: 61 known affected: 443 known not affected: 388 recommended: 108 | 2026-08-13T16:29:47+00:00 | Vulnerability · Source |
| CVE-2026-41178 | suse_vex | SUSE CVE CVE-2026-41178 | recommended: 4 | 2026-08-13T16:29:27+00:00 | Vulnerability · Source |
| CVE-2026-42256 | suse_vex | SUSE CVE CVE-2026-42256 | first fixed: 12 known affected: 5 known not affected: 253 recommended: 96 | 2026-08-13T16:29:14+00:00 | Vulnerability · Source |
| CVE-2026-42764 | suse_vex | SUSE CVE CVE-2026-42764 | first fixed: 61 known affected: 49 known not affected: 443 recommended: 50 | 2026-08-13T16:29:09+00:00 | Vulnerability · Source |
| CVE-2026-43618 | suse_vex | SUSE CVE CVE-2026-43618 | first fixed: 2 known affected: 406 recommended: 42 | 2026-08-13T16:28:07+00:00 | Vulnerability · Source |
| CVE-2026-43870 | suse_vex | SUSE CVE CVE-2026-43870 | recommended: 1 | 2026-08-13T16:28:02+00:00 | Vulnerability · Source |
| CVE-2026-47013 | suse_vex | SUSE CVE CVE-2026-47013 | known not affected: 510 recommended: 2 | 2026-08-13T16:27:02+00:00 | Vulnerability · Source |
| CVE-2026-48702 | suse_vex | SUSE CVE CVE-2026-48702 | known affected: 252 known not affected: 154 recommended: 6 | 2026-08-13T16:26:57+00:00 | Vulnerability · Source |
| CVE-2026-53166 | suse_vex | SUSE CVE CVE-2026-53166 | recommended: 128 | 2026-08-13T16:26:33+00:00 | Vulnerability · Source |
| CVE-2026-56876 | suse_vex | SUSE CVE CVE-2026-56876 | known affected: 27 known not affected: 360 recommended: 1 | 2026-08-13T16:25:57+00:00 | Vulnerability · Source |
| CVE-2026-62420 | suse_vex | SUSE CVE CVE-2026-62420 | No product status | 2026-08-13T16:25:24+00:00 | Vulnerability · Source |
| CVE-2026-63293 | suse_vex | SUSE CVE CVE-2026-63293 | No product status | 2026-08-13T16:25:21+00:00 | Vulnerability · Source |
| CVE-2026-63294 | suse_vex | SUSE CVE CVE-2026-63294 | No product status | 2026-08-13T16:25:19+00:00 | Vulnerability · Source |
| CVE-2026-63295 | suse_vex | SUSE CVE CVE-2026-63295 | No product status | 2026-08-13T16:25:17+00:00 | Vulnerability · Source |
| CVE-2026-63296 | suse_vex | SUSE CVE CVE-2026-63296 | No product status | 2026-08-13T16:25:14+00:00 | Vulnerability · Source |
| CVE-2026-63297 | suse_vex | SUSE CVE CVE-2026-63297 | No product status | 2026-08-13T16:25:12+00:00 | Vulnerability · Source |
| CVE-2026-66486 | suse_vex | SUSE CVE CVE-2026-66486 | known affected: 93 | 2026-08-13T16:24:37+00:00 | Vulnerability · Source |
| CVE-2026-68107 | suse_vex | SUSE CVE CVE-2026-68107 | known affected: 42 known not affected: 254 | 2026-08-13T16:24:32+00:00 | Vulnerability · Source |
| CVE-2026-68108 | suse_vex | SUSE CVE CVE-2026-68108 | known affected: 203 known not affected: 93 | 2026-08-13T16:24:31+00:00 | Vulnerability · Source |
| CVE-2026-68109 | suse_vex | SUSE CVE CVE-2026-68109 | known not affected: 296 | 2026-08-13T16:24:29+00:00 | Vulnerability · Source |
| CVE-2026-68110 | suse_vex | SUSE CVE CVE-2026-68110 | known affected: 42 known not affected: 254 | 2026-08-13T16:24:27+00:00 | Vulnerability · Source |
| CVE-2026-68111 | suse_vex | SUSE CVE CVE-2026-68111 | known affected: 173 known not affected: 123 | 2026-08-13T16:24:26+00:00 | Vulnerability · Source |
| CVE-2026-68112 | suse_vex | SUSE CVE CVE-2026-68112 | known affected: 48 known not affected: 248 | 2026-08-13T16:24:24+00:00 | Vulnerability · Source |
| CVE-2026-68113 | suse_vex | SUSE CVE CVE-2026-68113 | known affected: 61 known not affected: 235 | 2026-08-13T16:24:22+00:00 | Vulnerability · Source |
| CVE-2026-68114 | suse_vex | SUSE CVE CVE-2026-68114 | known not affected: 296 | 2026-08-13T16:24:20+00:00 | Vulnerability · Source |
| CVE-2026-68115 | suse_vex | SUSE CVE CVE-2026-68115 | known affected: 208 known not affected: 88 | 2026-08-13T16:24:18+00:00 | Vulnerability · Source |
| CVE-2026-68116 | suse_vex | SUSE CVE CVE-2026-68116 | known affected: 129 known not affected: 167 | 2026-08-13T16:24:17+00:00 | Vulnerability · Source |
| CVE-2026-68117 | suse_vex | SUSE CVE CVE-2026-68117 | known affected: 161 known not affected: 135 | 2026-08-13T16:24:15+00:00 | Vulnerability · Source |
| CVE-2026-68118 | suse_vex | SUSE CVE CVE-2026-68118 | known affected: 296 | 2026-08-13T16:24:13+00:00 | Vulnerability · Source |
| CVE-2026-68120 | suse_vex | SUSE CVE CVE-2026-68120 | known affected: 29 known not affected: 267 | 2026-08-13T16:24:09+00:00 | Vulnerability · Source |