VEX records
Browse vendor VEX statements available in this Vulnerability-Lookup instance and pivot to the related vulnerability.
294458 VEX records
API response| Vulnerability | Source | Title | Product status | Imported | Links |
|---|---|---|---|---|---|
| CVE-2026-48817 | suse_vex | SUSE CVE CVE-2026-48817 | known affected: 5 recommended: 3 | 2026-07-15T05:06:13+00:00 | Vulnerability · Source |
| CVE-2026-52985 | suse_vex | SUSE CVE CVE-2026-52985 | known affected: 228 known not affected: 65 | 2026-07-15T05:05:08+00:00 | Vulnerability · Source |
| CVE-2026-53320 | suse_vex | SUSE CVE CVE-2026-53320 | known affected: 293 | 2026-07-15T05:03:58+00:00 | Vulnerability · Source |
| CVE-2026-53448 | suse_vex | SUSE CVE CVE-2026-53448 | No product status | 2026-07-15T05:03:44+00:00 | Vulnerability · Source |
| CVE-2026-53449 | suse_vex | SUSE CVE CVE-2026-53449 | No product status | 2026-07-15T05:03:43+00:00 | Vulnerability · Source |
| CVE-2026-53450 | suse_vex | SUSE CVE CVE-2026-53450 | No product status | 2026-07-15T05:03:42+00:00 | Vulnerability · Source |
| CVE-2026-53538 | suse_vex | SUSE CVE CVE-2026-53538 | known affected: 5 recommended: 6 | 2026-07-15T05:03:33+00:00 | Vulnerability · Source |
| CVE-2026-53539 | suse_vex | SUSE CVE CVE-2026-53539 | known affected: 5 recommended: 3 | 2026-07-15T05:03:32+00:00 | Vulnerability · Source |
| CVE-2026-53540 | suse_vex | SUSE CVE CVE-2026-53540 | known affected: 5 recommended: 6 | 2026-07-15T05:03:32+00:00 | Vulnerability · Source |
| CVE-2026-54063 | suse_vex | SUSE CVE CVE-2026-54063 | known affected: 3 | 2026-07-15T05:03:26+00:00 | Vulnerability · Source |
| CVE-2026-54282 | suse_vex | SUSE CVE CVE-2026-54282 | known affected: 5 recommended: 6 | 2026-07-15T05:03:22+00:00 | Vulnerability · Source |
| CVE-2026-54283 | suse_vex | SUSE CVE CVE-2026-54283 | known affected: 5 recommended: 3 | 2026-07-15T05:03:21+00:00 | Vulnerability · Source |
| CVE-2026-54736 | suse_vex | SUSE CVE CVE-2026-54736 | No product status | 2026-07-15T05:03:17+00:00 | Vulnerability · Source |
| CVE-2026-54911 | suse_vex | SUSE CVE CVE-2026-54911 | known affected: 52 | 2026-07-15T05:03:16+00:00 | Vulnerability · Source |
| CVE-2026-54919 | suse_vex | SUSE CVE CVE-2026-54919 | known not affected: 31 | 2026-07-15T05:03:15+00:00 | Vulnerability · Source |
| CVE-2026-57212 | suse_vex | SUSE CVE CVE-2026-57212 | known affected: 98 | 2026-07-15T05:02:25+00:00 | Vulnerability · Source |
| CVE-2026-57213 | suse_vex | SUSE CVE CVE-2026-57213 | known affected: 98 | 2026-07-15T05:02:24+00:00 | Vulnerability · Source |
| CVE-2026-57214 | suse_vex | SUSE CVE CVE-2026-57214 | known affected: 98 | 2026-07-15T05:02:23+00:00 | Vulnerability · Source |
| CVE-2026-57215 | suse_vex | SUSE CVE CVE-2026-57215 | known affected: 11 known not affected: 87 | 2026-07-15T05:02:22+00:00 | Vulnerability · Source |
| CVE-2026-57216 | suse_vex | SUSE CVE CVE-2026-57216 | known affected: 98 | 2026-07-15T05:02:21+00:00 | Vulnerability · Source |
| CVE-2026-57217 | suse_vex | SUSE CVE CVE-2026-57217 | known affected: 40 known not affected: 58 | 2026-07-15T05:02:20+00:00 | Vulnerability · Source |
| CVE-2026-57218 | suse_vex | SUSE CVE CVE-2026-57218 | known affected: 98 | 2026-07-15T05:02:19+00:00 | Vulnerability · Source |
| CVE-2026-57219 | suse_vex | SUSE CVE CVE-2026-57219 | known affected: 98 | 2026-07-15T05:02:18+00:00 | Vulnerability · Source |
| CVE-2026-57220 | suse_vex | SUSE CVE CVE-2026-57220 | known affected: 98 | 2026-07-15T05:02:17+00:00 | Vulnerability · Source |
| CVE-2026-57221 | suse_vex | SUSE CVE CVE-2026-57221 | known affected: 98 | 2026-07-15T05:02:16+00:00 | Vulnerability · Source |
| CVE-2026-57584 | suse_vex | SUSE CVE CVE-2026-57584 | No product status | 2026-07-15T05:02:04+00:00 | Vulnerability · Source |
| CVE-2026-57850 | suse_vex | SUSE CVE CVE-2026-57850 | No product status | 2026-07-15T05:02:02+00:00 | Vulnerability · Source |
| CVE-2026-58208 | suse_vex | SUSE CVE CVE-2026-58208 | No product status | 2026-07-15T05:01:59+00:00 | Vulnerability · Source |
| CVE-2026-58250 | suse_vex | SUSE CVE CVE-2026-58250 | No product status | 2026-07-15T05:01:58+00:00 | Vulnerability · Source |
| CVE-2026-58251 | suse_vex | SUSE CVE CVE-2026-58251 | No product status | 2026-07-15T05:01:57+00:00 | Vulnerability · Source |
| CVE-2026-58252 | suse_vex | SUSE CVE CVE-2026-58252 | No product status | 2026-07-15T05:01:56+00:00 | Vulnerability · Source |
| CVE-2026-58253 | suse_vex | SUSE CVE CVE-2026-58253 | No product status | 2026-07-15T05:01:55+00:00 | Vulnerability · Source |
| CVE-2026-59161 | suse_vex | SUSE CVE CVE-2026-59161 | known affected: 3 | 2026-07-15T05:01:50+00:00 | Vulnerability · Source |
| CVE-2026-59162 | suse_vex | SUSE CVE CVE-2026-59162 | known affected: 3 | 2026-07-15T05:01:49+00:00 | Vulnerability · Source |
| CVE-2026-59180 | suse_vex | SUSE CVE CVE-2026-59180 | No product status | 2026-07-15T05:01:48+00:00 | Vulnerability · Source |
| CVE-2026-59922 | suse_vex | SUSE CVE CVE-2026-59922 | first fixed: 2 known affected: 5 known not affected: 35 | 2026-07-15T05:01:43+00:00 | Vulnerability · Source |
| CVE-2026-59923 | suse_vex | SUSE CVE CVE-2026-59923 | first fixed: 2 known affected: 5 known not affected: 35 | 2026-07-15T05:01:42+00:00 | Vulnerability · Source |
| CVE-2026-59924 | suse_vex | SUSE CVE CVE-2026-59924 | first fixed: 2 known affected: 5 known not affected: 35 | 2026-07-15T05:01:41+00:00 | Vulnerability · Source |
| CVE-2026-59925 | suse_vex | SUSE CVE CVE-2026-59925 | first fixed: 2 known affected: 5 known not affected: 35 | 2026-07-15T05:01:40+00:00 | Vulnerability · Source |
| CVE-2026-59926 | suse_vex | SUSE CVE CVE-2026-59926 | first fixed: 2 known not affected: 40 | 2026-07-15T05:01:39+00:00 | Vulnerability · Source |
| CVE-2026-59927 | suse_vex | SUSE CVE CVE-2026-59927 | first fixed: 2 known affected: 5 known not affected: 35 | 2026-07-15T05:01:38+00:00 | Vulnerability · Source |
| CVE-2026-59928 | suse_vex | SUSE CVE CVE-2026-59928 | first fixed: 2 known affected: 5 known not affected: 35 | 2026-07-15T05:01:37+00:00 | Vulnerability · Source |
| CVE-2026-59929 | suse_vex | SUSE CVE CVE-2026-59929 | first fixed: 2 known affected: 5 known not affected: 35 | 2026-07-15T05:01:36+00:00 | Vulnerability · Source |
| CVE-2026-59930 | suse_vex | SUSE CVE CVE-2026-59930 | first fixed: 2 known affected: 40 | 2026-07-15T05:01:35+00:00 | Vulnerability · Source |
| CVE-2025-43213 | redhat_vex | webkitgtk: Processing maliciously crafted web content may lead to an unexpected Safari crash | fixed: 509 known affected: 4 known not affected: 5 | 2026-07-15T03:16:38+00:00 | Vulnerability · Source |
| CVE-2021-47952 | redhat_vex | python-jsonpickle: python-jsonpickle: Arbitrary Code Execution via Malicious JSON Deserialization | known not affected: 2 | 2026-07-15T03:16:31+00:00 | Vulnerability · Source |
| CVE-2026-1207 | redhat_vex | Django: Django: SQL Injection via RasterField band index parameter | fixed: 122 known affected: 6 known not affected: 4552 | 2026-07-15T03:13:09+00:00 | Vulnerability · Source |
| CVE-2026-0877 | redhat_vex | firefox: thunderbird: Mitigation bypass in the DOM: Security component | fixed: 320 known affected: 7 | 2026-07-15T03:13:07+00:00 | Vulnerability · Source |
| CVE-2025-70974 | redhat_vex | fastjson: Fastjson: Remote Code Execution via JNDI Injection due to autoType mishandling | known not affected: 14 | 2026-07-15T03:13:03+00:00 | Vulnerability · Source |
| CVE-2026-8946 | redhat_vex | firefox: thunderbird: Incorrect boundary conditions in the Audio/Video: Web Codecs component | fixed: 260 known affected: 8 | 2026-07-15T03:00:00+00:00 | Vulnerability · Source |