VEX records
Browse vendor VEX statements available in this Vulnerability-Lookup instance and pivot to the related vulnerability.
305846 VEX records
API response| Vulnerability | Source | Title | Product status | Imported | Links |
|---|---|---|---|---|---|
| CVE-2026-7573 | suse_vex | SUSE CVE CVE-2026-7573 | known affected: 3 | 2026-06-27T02:05:52+00:00 | Vulnerability · Source |
| CVE-2026-10532 | suse_vex | SUSE CVE CVE-2026-10532 | recommended: 4 | 2026-06-27T02:05:38+00:00 | Vulnerability · Source |
| CVE-2026-11625 | suse_vex | SUSE CVE CVE-2026-11625 | No product status | 2026-06-27T02:05:35+00:00 | Vulnerability · Source |
| CVE-2026-11702 | suse_vex | SUSE CVE CVE-2026-11702 | No product status | 2026-06-27T02:05:33+00:00 | Vulnerability · Source |
| CVE-2026-32936 | suse_vex | SUSE CVE CVE-2026-32936 | recommended: 2 | 2026-06-27T02:01:59+00:00 | Vulnerability · Source |
| CVE-2026-33489 | suse_vex | SUSE CVE CVE-2026-33489 | recommended: 2 | 2026-06-27T02:01:50+00:00 | Vulnerability · Source |
| CVE-2026-35051 | suse_vex | SUSE CVE CVE-2026-35051 | recommended: 2 | 2026-06-27T02:01:18+00:00 | Vulnerability · Source |
| CVE-2026-35392 | suse_vex | SUSE CVE CVE-2026-35392 | recommended: 1 | 2026-06-27T02:01:08+00:00 | Vulnerability · Source |
| CVE-2026-35393 | suse_vex | SUSE CVE CVE-2026-35393 | recommended: 1 | 2026-06-27T02:01:07+00:00 | Vulnerability · Source |
| CVE-2026-35471 | suse_vex | SUSE CVE CVE-2026-35471 | recommended: 1 | 2026-06-27T02:01:06+00:00 | Vulnerability · Source |
| CVE-2026-35579 | suse_vex | SUSE CVE CVE-2026-35579 | recommended: 2 | 2026-06-27T02:01:03+00:00 | Vulnerability · Source |
| CVE-2026-39388 | suse_vex | SUSE CVE CVE-2026-39388 | recommended: 8 | 2026-06-27T02:01:00+00:00 | Vulnerability · Source |
| CVE-2026-39396 | suse_vex | SUSE CVE CVE-2026-39396 | recommended: 8 | 2026-06-27T02:00:59+00:00 | Vulnerability · Source |
| CVE-2026-39858 | suse_vex | SUSE CVE CVE-2026-39858 | recommended: 2 | 2026-06-27T02:00:42+00:00 | Vulnerability · Source |
| CVE-2026-39946 | suse_vex | SUSE CVE CVE-2026-39946 | recommended: 8 | 2026-06-27T02:00:40+00:00 | Vulnerability · Source |
| CVE-2026-40012 | suse_vex | SUSE CVE CVE-2026-40012 | No product status | 2026-06-27T02:00:37+00:00 | Vulnerability · Source |
| CVE-2026-40264 | suse_vex | SUSE CVE CVE-2026-40264 | recommended: 8 | 2026-06-27T02:00:30+00:00 | Vulnerability · Source |
| CVE-2026-40912 | suse_vex | SUSE CVE CVE-2026-40912 | recommended: 2 | 2026-06-27T02:00:25+00:00 | Vulnerability · Source |
| CVE-2026-41174 | suse_vex | SUSE CVE CVE-2026-41174 | recommended: 2 | 2026-06-27T02:00:21+00:00 | Vulnerability · Source |
| CVE-2026-41263 | suse_vex | SUSE CVE CVE-2026-41263 | recommended: 2 | 2026-06-27T02:00:20+00:00 | Vulnerability · Source |
| CVE-2026-41564 | suse_vex | SUSE CVE CVE-2026-41564 | recommended: 3 | 2026-06-27T02:00:13+00:00 | Vulnerability · Source |
| CVE-2026-42387 | suse_vex | SUSE CVE CVE-2026-42387 | No product status | 2026-06-27T02:00:01+00:00 | Vulnerability · Source |
| CVE-2026-42388 | suse_vex | SUSE CVE CVE-2026-42388 | No product status | 2026-06-27T01:59:59+00:00 | Vulnerability · Source |
| CVE-2026-42389 | suse_vex | SUSE CVE CVE-2026-42389 | No product status | 2026-06-27T01:59:58+00:00 | Vulnerability · Source |
| CVE-2026-42390 | suse_vex | SUSE CVE CVE-2026-42390 | No product status | 2026-06-27T01:59:57+00:00 | Vulnerability · Source |
| CVE-2026-43195 | suse_vex | SUSE CVE CVE-2026-43195 | known not affected: 291 | 2026-06-27T01:58:53+00:00 | Vulnerability · Source |
| CVE-2026-43994 | suse_vex | SUSE CVE CVE-2026-43994 | No product status | 2026-06-27T01:57:54+00:00 | Vulnerability · Source |
| CVE-2026-44903 | suse_vex | SUSE CVE CVE-2026-44903 | known affected: 6 | 2026-06-27T01:57:48+00:00 | Vulnerability · Source |
| CVE-2026-48020 | suse_vex | SUSE CVE CVE-2026-48020 | recommended: 2 | 2026-06-27T01:56:03+00:00 | Vulnerability · Source |
| CVE-2026-48491 | suse_vex | SUSE CVE CVE-2026-48491 | recommended: 1 | 2026-06-27T01:56:02+00:00 | Vulnerability · Source |
| CVE-2026-52690 | suse_vex | SUSE CVE CVE-2026-52690 | No product status | 2026-06-27T01:55:16+00:00 | Vulnerability · Source |
| CVE-2026-52978 | suse_vex | SUSE CVE CVE-2026-52978 | known not affected: 291 | 2026-06-27T01:55:07+00:00 | Vulnerability · Source |
| CVE-2026-52979 | suse_vex | SUSE CVE CVE-2026-52979 | known not affected: 291 | 2026-06-27T01:55:05+00:00 | Vulnerability · Source |
| CVE-2026-53029 | suse_vex | SUSE CVE CVE-2026-53029 | known not affected: 291 | 2026-06-27T01:54:49+00:00 | Vulnerability · Source |
| CVE-2026-53067 | suse_vex | SUSE CVE CVE-2026-53067 | known not affected: 291 | 2026-06-27T01:54:27+00:00 | Vulnerability · Source |
| CVE-2026-53079 | suse_vex | SUSE CVE CVE-2026-53079 | known not affected: 291 | 2026-06-27T01:54:22+00:00 | Vulnerability · Source |
| CVE-2026-53124 | suse_vex | SUSE CVE CVE-2026-53124 | known not affected: 291 | 2026-06-27T01:54:14+00:00 | Vulnerability · Source |
| CVE-2026-53125 | suse_vex | SUSE CVE CVE-2026-53125 | known not affected: 291 | 2026-06-27T01:54:13+00:00 | Vulnerability · Source |
| CVE-2026-53169 | suse_vex | SUSE CVE CVE-2026-53169 | known not affected: 291 | 2026-06-27T01:53:44+00:00 | Vulnerability · Source |
| CVE-2026-53197 | suse_vex | SUSE CVE CVE-2026-53197 | known not affected: 291 | 2026-06-27T01:53:27+00:00 | Vulnerability · Source |
| CVE-2026-57520 | suse_vex | SUSE CVE CVE-2026-57520 | No product status | 2026-06-27T01:52:08+00:00 | Vulnerability · Source |
| CVE-2026-57521 | suse_vex | SUSE CVE CVE-2026-57521 | No product status | 2026-06-27T01:52:07+00:00 | Vulnerability · Source |
| CVE-2026-57522 | suse_vex | SUSE CVE CVE-2026-57522 | No product status | 2026-06-27T01:52:06+00:00 | Vulnerability · Source |
| CVE-2026-57918 | suse_vex | SUSE CVE CVE-2026-57918 | known not affected: 79 | 2026-06-27T01:52:04+00:00 | Vulnerability · Source |
| CVE-2018-4868 | redhat_vex | exiv2: Excessive memory allocation in Exiv2::Jp2Image::readMetadata function in jp2image.cpp | fixed: 164 known not affected: 3 | 2026-06-27T01:45:23+00:00 | Vulnerability · Source |
| CVE-2018-4121 | redhat_vex | webkitgtk: memory corruption processing maliciously crafted web content | fixed: 8618 known affected: 9 known not affected: 1 | 2026-06-27T01:45:06+00:00 | Vulnerability · Source |
| CVE-2018-3741 | redhat_vex | rubygem-rails-html-sanitizer: non-whitelisted attributes are present in sanitized output when input with specially-crafted HTML fragments leading to XSS vulnerability | fixed: 311 known affected: 4 | 2026-06-27T01:45:03+00:00 | Vulnerability · Source |
| CVE-2018-4200 | redhat_vex | webkitgtk: memory corruption processing maliciously crafted web content | fixed: 8618 known affected: 9 known not affected: 1 | 2026-06-27T01:44:59+00:00 | Vulnerability · Source |
| CVE-2018-4204 | redhat_vex | webkitgtk: memory corruption processing maliciously crafted web content | fixed: 8618 known affected: 9 known not affected: 1 | 2026-06-27T01:44:58+00:00 | Vulnerability · Source |
| CVE-2018-3640 | redhat_vex | hw: cpu: speculative register load | known not affected: 56 | 2026-06-27T01:44:39+00:00 | Vulnerability · Source |