VEX records
Browse vendor VEX statements available in this Vulnerability-Lookup instance and pivot to the related vulnerability.
297693 VEX records
API response| Vulnerability | Source | Title | Product status | Imported | Links |
|---|---|---|---|---|---|
| CVE-2026-41046 | suse_vex | SUSE CVE CVE-2026-41046 | No product status | 2026-06-23T02:24:54+00:00 | Vulnerability · Source |
| CVE-2026-41047 | suse_vex | SUSE CVE CVE-2026-41047 | No product status | 2026-06-23T02:24:53+00:00 | Vulnerability · Source |
| CVE-2026-41417 | suse_vex | SUSE CVE CVE-2026-41417 | recommended: 22 | 2026-06-23T02:24:43+00:00 | Vulnerability · Source |
| CVE-2026-42583 | suse_vex | SUSE CVE CVE-2026-42583 | recommended: 22 | 2026-06-23T02:24:16+00:00 | Vulnerability · Source |
| CVE-2026-11526 | suse_vex | SUSE CVE CVE-2026-11526 | recommended: 2 | 2026-06-22T00:46:45+00:00 | Vulnerability · Source |
| CVE-2019-19061 | suse_vex | SUSE CVE CVE-2019-19061 | known affected: 310 known not affected: 268 recommended: 781 | 2026-06-21T02:32:26+00:00 | Vulnerability · Source |
| CVE-2010-1436 | suse_vex | SUSE CVE CVE-2010-1436 | known not affected: 468 recommended: 231 | 2026-06-20T03:15:51+00:00 | Vulnerability · Source |
| CVE-2017-9333 | suse_vex | SUSE CVE CVE-2017-9333 | No product status | 2026-06-20T03:15:02+00:00 | Vulnerability · Source |
| CVE-2018-9989 | suse_vex | SUSE CVE CVE-2018-9989 | recommended: 2 | 2026-06-20T03:14:48+00:00 | Vulnerability · Source |
| CVE-2024-38519 | suse_vex | SUSE CVE CVE-2024-38519 | recommended: 19 | 2026-06-20T03:00:49+00:00 | Vulnerability · Source |
| CVE-2026-6948 | suse_vex | SUSE CVE CVE-2026-6948 | known affected: 3 | 2026-06-20T02:36:10+00:00 | Vulnerability · Source |
| CVE-2026-9692 | suse_vex | SUSE CVE CVE-2026-9692 | No product status | 2026-06-20T02:36:04+00:00 | Vulnerability · Source |
| CVE-2026-11463 | suse_vex | SUSE CVE CVE-2026-11463 | known affected: 2 | 2026-06-20T02:36:02+00:00 | Vulnerability · Source |
| CVE-2026-12044 | suse_vex | SUSE CVE CVE-2026-12044 | known affected: 75 | 2026-06-20T02:35:32+00:00 | Vulnerability · Source |
| CVE-2026-12046 | suse_vex | SUSE CVE CVE-2026-12046 | known not affected: 75 | 2026-06-20T02:35:29+00:00 | Vulnerability · Source |
| CVE-2026-12047 | suse_vex | SUSE CVE CVE-2026-12047 | known not affected: 75 | 2026-06-20T02:35:27+00:00 | Vulnerability · Source |
| CVE-2026-12048 | suse_vex | SUSE CVE CVE-2026-12048 | known not affected: 75 | 2026-06-20T02:35:26+00:00 | Vulnerability · Source |
| CVE-2026-12049 | suse_vex | SUSE CVE CVE-2026-12049 | known not affected: 75 | 2026-06-20T02:35:24+00:00 | Vulnerability · Source |
| CVE-2026-12050 | suse_vex | SUSE CVE CVE-2026-12050 | known affected: 75 | 2026-06-20T02:35:23+00:00 | Vulnerability · Source |
| CVE-2026-23247 | suse_vex | SUSE CVE CVE-2026-23247 | known affected: 206 known not affected: 20 | 2026-06-20T02:34:38+00:00 | Vulnerability · Source |
| CVE-2026-23310 | suse_vex | SUSE CVE CVE-2026-23310 | known affected: 119 known not affected: 198 | 2026-06-20T02:34:16+00:00 | Vulnerability · Source |
| CVE-2026-43219 | suse_vex | SUSE CVE CVE-2026-43219 | known affected: 214 known not affected: 77 | 2026-06-20T02:30:31+00:00 | Vulnerability · Source |
| CVE-2026-43311 | suse_vex | SUSE CVE CVE-2026-43311 | known affected: 112 known not affected: 179 | 2026-06-20T02:30:25+00:00 | Vulnerability · Source |
| CVE-2026-43331 | suse_vex | SUSE CVE CVE-2026-43331 | known affected: 15 known not affected: 276 | 2026-06-20T02:30:22+00:00 | Vulnerability · Source |
| CVE-2026-43915 | suse_vex | SUSE CVE CVE-2026-43915 | No product status | 2026-06-20T02:30:08+00:00 | Vulnerability · Source |
| CVE-2026-44939 | suse_vex | SUSE CVE CVE-2026-44939 | No product status | 2026-06-20T02:30:02+00:00 | Vulnerability · Source |
| CVE-2026-48827 | suse_vex | SUSE CVE CVE-2026-48827 | known affected: 4 recommended: 34 | 2026-06-20T02:29:18+00:00 | Vulnerability · Source |
| CVE-2026-48990 | suse_vex | SUSE CVE CVE-2026-48990 | recommended: 3 | 2026-06-20T02:29:08+00:00 | Vulnerability · Source |
| CVE-2026-50141 | suse_vex | SUSE CVE CVE-2026-50141 | No product status | 2026-06-20T02:29:06+00:00 | Vulnerability · Source |
| CVE-2025-5791 | microsoft_vex | Users: `root` appended to group listings | fixed: 2 known affected: 8 known not affected: 2 | 2026-06-20T01:40:10+00:00 | Vulnerability · Source |
| CVE-2025-4574 | microsoft_vex | Crossbeam-channel: crossbeam-channel vulnerable to double free on drop | fixed: 5 known affected: 11 | 2026-06-20T01:39:58+00:00 | Vulnerability · Source |
| CVE-2026-9698 | microsoft_vex | DBI versions before 1.648 for Perl saved errors in a limited-sized buffer | fixed: 1 known affected: 1 | 2026-06-19T14:42:58+00:00 | Vulnerability · Source |
| CVE-2015-5400 | redhat_vex | squid: information disclosure due to incorrect handling of peer responses in tunnel.cc (SQUID-2015:2) | known affected: 7 | 2026-06-19T09:38:13+00:00 | Vulnerability · Source |
| CVE-2026-41149 | redhat_vex | mermaid: Mermaid: HTML injection via classDef directive in state diagrams | known affected: 2 | 2026-06-19T05:12:01+00:00 | Vulnerability · Source |
| CVE-2008-7316 | suse_vex | SUSE CVE CVE-2008-7316 | known not affected: 67 | 2026-06-19T02:12:36+00:00 | Vulnerability · Source |
| CVE-2011-4604 | suse_vex | SUSE CVE CVE-2011-4604 | known not affected: 468 recommended: 184 | 2026-06-19T02:12:24+00:00 | Vulnerability · Source |
| CVE-2015-4017 | suse_vex | SUSE CVE CVE-2015-4017 | No product status | 2026-06-19T02:12:07+00:00 | Vulnerability · Source |
| CVE-2019-17053 | suse_vex | SUSE CVE CVE-2019-17053 | known not affected: 270 recommended: 88 | 2026-06-19T02:10:15+00:00 | Vulnerability · Source |
| CVE-2022-0155 | suse_vex | SUSE CVE CVE-2022-0155 | recommended: 278 | 2026-06-19T02:08:51+00:00 | Vulnerability · Source |
| CVE-2024-24576 | suse_vex | SUSE CVE CVE-2024-24576 | known not affected: 691 recommended: 2 | 2026-06-19T02:05:50+00:00 | Vulnerability · Source |
| CVE-2026-43122 | suse_vex | SUSE CVE CVE-2026-43122 | known not affected: 291 | 2026-06-19T01:52:28+00:00 | Vulnerability · Source |
| CVE-2026-53537 | suse_vex | SUSE CVE CVE-2026-53537 | known affected: 5 | 2026-06-19T01:49:56+00:00 | Vulnerability · Source |
| CVE-2026-54387 | suse_vex | SUSE CVE CVE-2026-54387 | recommended: 1 | 2026-06-19T01:49:49+00:00 | Vulnerability · Source |
| CVE-2026-54388 | suse_vex | SUSE CVE CVE-2026-54388 | recommended: 1 | 2026-06-19T01:49:48+00:00 | Vulnerability · Source |
| CVE-2026-55202 | suse_vex | SUSE CVE CVE-2026-55202 | recommended: 1 | 2026-06-19T01:49:43+00:00 | Vulnerability · Source |
| CVE-2026-48855 | microsoft_vex | SFTP READLINK Leaks Absolute Backend Filesystem Path When Root Is Configured | fixed: 1 known affected: 1 | 2026-06-18T14:43:01+00:00 | Vulnerability · Source |
| CVE-2026-49759 | microsoft_vex | Stack buffer overflow in SCTP error cause parsing in inet_drv allows remote VM crash | fixed: 1 known affected: 1 | 2026-06-18T14:42:54+00:00 | Vulnerability · Source |
| CVE-2026-48860 | microsoft_vex | Distribution-over-TLS LAN allowlist silently bypassed due to sockname/peername confusion in inet_tls_dist | fixed: 1 known affected: 1 | 2026-06-18T14:42:46+00:00 | Vulnerability · Source |
| CVE-2026-48856 | microsoft_vex | httpc leaks Authorization header to cross-origin redirect targets | fixed: 1 known affected: 1 | 2026-06-18T14:42:39+00:00 | Vulnerability · Source |
| CVE-2026-48858 | microsoft_vex | ftp client PASV response IP not validated against control peer, enabling SSRF and FTP bounce attacks | fixed: 1 known affected: 1 | 2026-06-18T14:42:32+00:00 | Vulnerability · Source |