VEX records
Browse vendor VEX statements available in this Vulnerability-Lookup instance and pivot to the related vulnerability.
283041 VEX records
API response| Vulnerability | Source | Title | Product status | Imported | Links |
|---|---|---|---|---|---|
| CVE-2025-68227 | suse_vex | SUSE CVE CVE-2025-68227 | first fixed: 2 known affected: 602 known not affected: 152 recommended: 280 | 2026-07-21T13:18:59+00:00 | Vulnerability · Source |
| CVE-2025-68776 | suse_vex | SUSE CVE CVE-2025-68776 | first fixed: 2 known affected: 655 known not affected: 4 recommended: 307 | 2026-07-21T13:18:54+00:00 | Vulnerability · Source |
| CVE-2025-68778 | suse_vex | SUSE CVE CVE-2025-68778 | first fixed: 2 known affected: 665 recommended: 295 | 2026-07-21T13:18:53+00:00 | Vulnerability · Source |
| CVE-2025-71183 | suse_vex | SUSE CVE CVE-2025-71183 | first fixed: 2 known affected: 573 known not affected: 64 recommended: 298 | 2026-07-21T13:18:48+00:00 | Vulnerability · Source |
| CVE-2025-71274 | suse_vex | SUSE CVE CVE-2025-71274 | first fixed: 80 known affected: 144 known not affected: 147 | 2026-07-21T13:18:46+00:00 | Vulnerability · Source |
| CVE-2025-71286 | suse_vex | SUSE CVE CVE-2025-71286 | known affected: 20 known not affected: 207 | 2026-07-21T13:18:44+00:00 | Vulnerability · Source |
| CVE-2025-71294 | suse_vex | SUSE CVE CVE-2025-71294 | known affected: 30 known not affected: 194 recommended: 108 | 2026-07-21T13:18:43+00:00 | Vulnerability · Source |
| CVE-2025-71297 | suse_vex | SUSE CVE CVE-2025-71297 | known affected: 86 known not affected: 141 | 2026-07-21T13:18:37+00:00 | Vulnerability · Source |
| CVE-2025-71302 | suse_vex | SUSE CVE CVE-2025-71302 | first fixed: 82 known affected: 466 known not affected: 221 recommended: 172 | 2026-07-21T13:18:36+00:00 | Vulnerability · Source |
| CVE-2026-0672 | suse_vex | SUSE CVE CVE-2026-0672 | known affected: 420 known not affected: 30 recommended: 827 | 2026-07-21T13:18:32+00:00 | Vulnerability · Source |
| CVE-2026-1519 | suse_vex | SUSE CVE CVE-2026-1519 | known affected: 464 known not affected: 13 recommended: 300 | 2026-07-21T13:18:27+00:00 | Vulnerability · Source |
| CVE-2026-2100 | suse_vex | SUSE CVE CVE-2026-2100 | known not affected: 231 recommended: 19 | 2026-07-21T13:18:25+00:00 | Vulnerability · Source |
| CVE-2026-2291 | suse_vex | SUSE CVE CVE-2026-2291 | known affected: 10 recommended: 45 | 2026-07-21T13:18:23+00:00 | Vulnerability · Source |
| CVE-2026-16118 | redhat_vex | xdgmime: heap-based buffer overflow in _xdg_mime_magic_parse_magic_line() in xdgmimemagic.c | known affected: 30 | 2026-07-21T13:18:22+00:00 | Vulnerability · Source |
| CVE-2026-3184 | suse_vex | SUSE CVE CVE-2026-3184 | known affected: 756 recommended: 403 | 2026-07-21T13:18:20+00:00 | Vulnerability · Source |
| CVE-2026-3644 | suse_vex | SUSE CVE CVE-2026-3644 | known affected: 450 recommended: 846 | 2026-07-21T13:18:17+00:00 | Vulnerability · Source |
| CVE-2026-4224 | suse_vex | SUSE CVE CVE-2026-4224 | known affected: 450 recommended: 846 | 2026-07-21T13:18:13+00:00 | Vulnerability · Source |
| CVE-2026-4430 | suse_vex | SUSE CVE CVE-2026-4430 | known affected: 509 | 2026-07-21T13:18:11+00:00 | Vulnerability · Source |
| CVE-2026-4519 | suse_vex | SUSE CVE CVE-2026-4519 | known affected: 450 recommended: 890 | 2026-07-21T13:18:09+00:00 | Vulnerability · Source |
| CVE-2026-6039 | suse_vex | SUSE CVE CVE-2026-6039 | known affected: 509 | 2026-07-21T13:18:02+00:00 | Vulnerability · Source |
| CVE-2026-6040 | suse_vex | SUSE CVE CVE-2026-6040 | known affected: 509 | 2026-07-21T13:18:00+00:00 | Vulnerability · Source |
| CVE-2026-6045 | suse_vex | SUSE CVE CVE-2026-6045 | known affected: 509 | 2026-07-21T13:17:59+00:00 | Vulnerability · Source |
| CVE-2026-6047 | suse_vex | SUSE CVE CVE-2026-6047 | known affected: 509 | 2026-07-21T13:17:58+00:00 | Vulnerability · Source |
| CVE-2026-6429 | suse_vex | SUSE CVE CVE-2026-6429 | first fixed: 13 known affected: 441 recommended: 150 | 2026-07-21T13:17:55+00:00 | Vulnerability · Source |
| CVE-2026-8149 | suse_vex | SUSE CVE CVE-2026-8149 | known not affected: 78 | 2026-07-21T13:17:52+00:00 | Vulnerability · Source |
| CVE-2026-8356 | suse_vex | SUSE CVE CVE-2026-8356 | known affected: 509 | 2026-07-21T13:17:50+00:00 | Vulnerability · Source |
| CVE-2026-8357 | suse_vex | SUSE CVE CVE-2026-8357 | known affected: 509 | 2026-07-21T13:17:49+00:00 | Vulnerability · Source |
| CVE-2026-8358 | suse_vex | SUSE CVE CVE-2026-8358 | known affected: 509 | 2026-07-21T13:17:48+00:00 | Vulnerability · Source |
| CVE-2026-8376 | suse_vex | SUSE CVE CVE-2026-8376 | known not affected: 111 | 2026-07-21T13:17:46+00:00 | Vulnerability · Source |
| CVE-2026-9323 | suse_vex | SUSE CVE CVE-2026-9323 | known affected: 70 | 2026-07-21T13:17:42+00:00 | Vulnerability · Source |
| CVE-2026-9537 | suse_vex | SUSE CVE CVE-2026-9537 | No product status | 2026-07-21T13:17:41+00:00 | Vulnerability · Source |
| CVE-2026-10028 | suse_vex | SUSE CVE CVE-2026-10028 | first fixed: 4 known affected: 444 recommended: 29 | 2026-07-21T13:17:38+00:00 | Vulnerability · Source |
| CVE-2026-10649 | suse_vex | SUSE CVE CVE-2026-10649 | known affected: 419 recommended: 99 | 2026-07-21T13:17:36+00:00 | Vulnerability · Source |
| CVE-2026-11332 | suse_vex | SUSE CVE CVE-2026-11332 | known affected: 12 recommended: 16 | 2026-07-21T13:17:34+00:00 | Vulnerability · Source |
| CVE-2026-12080 | suse_vex | SUSE CVE CVE-2026-12080 | known affected: 867 known not affected: 212 | 2026-07-21T13:17:32+00:00 | Vulnerability · Source |
| CVE-2026-12478 | suse_vex | SUSE CVE CVE-2026-12478 | known affected: 227 | 2026-07-21T13:17:30+00:00 | Vulnerability · Source |
| CVE-2026-14474 | suse_vex | SUSE CVE CVE-2026-14474 | first fixed: 354 known affected: 481 recommended: 258 | 2026-07-21T13:17:27+00:00 | Vulnerability · Source |
| CVE-2026-14476 | suse_vex | SUSE CVE CVE-2026-14476 | first fixed: 354 known affected: 481 recommended: 258 | 2026-07-21T13:17:25+00:00 | Vulnerability · Source |
| CVE-2026-14741 | suse_vex | SUSE CVE CVE-2026-14741 | known affected: 29 | 2026-07-21T13:17:24+00:00 | Vulnerability · Source |
| CVE-2026-15043 | suse_vex | SUSE CVE CVE-2026-15043 | first fixed: 7 known affected: 31 | 2026-07-21T13:17:22+00:00 | Vulnerability · Source |
| CVE-2026-15146 | suse_vex | SUSE CVE CVE-2026-15146 | known affected: 36 | 2026-07-21T13:17:21+00:00 | Vulnerability · Source |
| CVE-2026-15392 | suse_vex | SUSE CVE CVE-2026-15392 | known affected: 31 | 2026-07-21T13:17:20+00:00 | Vulnerability · Source |
| CVE-2026-15809 | suse_vex | SUSE CVE CVE-2026-15809 | No product status | 2026-07-21T13:17:18+00:00 | Vulnerability · Source |
| CVE-2026-15811 | suse_vex | SUSE CVE CVE-2026-15811 | known affected: 49 | 2026-07-21T13:17:17+00:00 | Vulnerability · Source |
| CVE-2026-15812 | suse_vex | SUSE CVE CVE-2026-15812 | known affected: 49 | 2026-07-21T13:17:15+00:00 | Vulnerability · Source |
| CVE-2026-15813 | suse_vex | SUSE CVE CVE-2026-15813 | known affected: 49 | 2026-07-21T13:17:14+00:00 | Vulnerability · Source |
| CVE-2026-16207 | suse_vex | SUSE CVE CVE-2026-16207 | No product status | 2026-07-21T13:17:02+00:00 | Vulnerability · Source |
| CVE-2026-16208 | suse_vex | SUSE CVE CVE-2026-16208 | No product status | 2026-07-21T13:17:00+00:00 | Vulnerability · Source |
| CVE-2026-16221 | suse_vex | SUSE CVE CVE-2026-16221 | known affected: 75 known not affected: 41 | 2026-07-21T13:16:59+00:00 | Vulnerability · Source |
| CVE-2026-16277 | suse_vex | SUSE CVE CVE-2026-16277 | known affected: 36 | 2026-07-21T13:16:57+00:00 | Vulnerability · Source |