VEX records
Browse vendor VEX statements available in this Vulnerability-Lookup instance and pivot to the related vulnerability.
291904 VEX records
API response| Vulnerability | Source | Title | Product status | Imported | Links |
|---|---|---|---|---|---|
| CVE-2026-48113 | suse_vex | SUSE CVE CVE-2026-48113 | No product status | 2026-08-05T00:36:56+00:00 | Vulnerability · Source |
| CVE-2026-49834 | suse_vex | SUSE CVE CVE-2026-49834 | known not affected: 167 | 2026-08-05T00:36:51+00:00 | Vulnerability · Source |
| CVE-2026-52746 | suse_vex | SUSE CVE CVE-2026-52746 | No product status | 2026-08-05T00:36:38+00:00 | Vulnerability · Source |
| CVE-2026-53095 | suse_vex | SUSE CVE CVE-2026-53095 | known affected: 118 known not affected: 177 | 2026-08-05T00:36:19+00:00 | Vulnerability · Source |
| CVE-2026-54448 | suse_vex | SUSE CVE CVE-2026-54448 | recommended: 3 | 2026-08-05T00:36:04+00:00 | Vulnerability · Source |
| CVE-2026-54787 | suse_vex | SUSE CVE CVE-2026-54787 | known affected: 134 known not affected: 241 | 2026-08-05T00:36:02+00:00 | Vulnerability · Source |
| CVE-2026-55831 | suse_vex | SUSE CVE CVE-2026-55831 | known not affected: 42 recommended: 22 | 2026-08-05T00:35:58+00:00 | Vulnerability · Source |
| CVE-2026-55833 | suse_vex | SUSE CVE CVE-2026-55833 | known not affected: 42 recommended: 22 | 2026-08-05T00:35:57+00:00 | Vulnerability · Source |
| CVE-2026-55851 | suse_vex | SUSE CVE CVE-2026-55851 | known not affected: 42 recommended: 22 | 2026-08-05T00:35:55+00:00 | Vulnerability · Source |
| CVE-2026-56109 | suse_vex | SUSE CVE CVE-2026-56109 | known affected: 513 recommended: 53 | 2026-08-05T00:35:52+00:00 | Vulnerability · Source |
| CVE-2026-56745 | suse_vex | SUSE CVE CVE-2026-56745 | known not affected: 42 recommended: 22 | 2026-08-05T00:35:47+00:00 | Vulnerability · Source |
| CVE-2026-56746 | suse_vex | SUSE CVE CVE-2026-56746 | known not affected: 42 recommended: 22 | 2026-08-05T00:35:45+00:00 | Vulnerability · Source |
| CVE-2026-56817 | suse_vex | SUSE CVE CVE-2026-56817 | known not affected: 42 recommended: 22 | 2026-08-05T00:35:43+00:00 | Vulnerability · Source |
| CVE-2026-56819 | suse_vex | SUSE CVE CVE-2026-56819 | known not affected: 42 recommended: 22 | 2026-08-05T00:35:39+00:00 | Vulnerability · Source |
| CVE-2026-56820 | suse_vex | SUSE CVE CVE-2026-56820 | known not affected: 42 recommended: 22 | 2026-08-05T00:35:37+00:00 | Vulnerability · Source |
| CVE-2026-56821 | suse_vex | SUSE CVE CVE-2026-56821 | known not affected: 42 recommended: 22 | 2026-08-05T00:35:35+00:00 | Vulnerability · Source |
| CVE-2026-56822 | suse_vex | SUSE CVE CVE-2026-56822 | known not affected: 42 recommended: 22 | 2026-08-05T00:35:34+00:00 | Vulnerability · Source |
| CVE-2026-59898 | suse_vex | SUSE CVE CVE-2026-59898 | known not affected: 42 recommended: 22 | 2026-08-05T00:34:44+00:00 | Vulnerability · Source |
| CVE-2026-59899 | suse_vex | SUSE CVE CVE-2026-59899 | known not affected: 42 recommended: 22 | 2026-08-05T00:34:42+00:00 | Vulnerability · Source |
| CVE-2026-59900 | suse_vex | SUSE CVE CVE-2026-59900 | known not affected: 42 recommended: 22 | 2026-08-05T00:34:40+00:00 | Vulnerability · Source |
| CVE-2026-59901 | suse_vex | SUSE CVE CVE-2026-59901 | known not affected: 42 recommended: 22 | 2026-08-05T00:34:39+00:00 | Vulnerability · Source |
| CVE-2026-59919 | suse_vex | SUSE CVE CVE-2026-59919 | known not affected: 42 recommended: 22 | 2026-08-05T00:34:37+00:00 | Vulnerability · Source |
| CVE-2026-59920 | suse_vex | SUSE CVE CVE-2026-59920 | known not affected: 42 recommended: 22 | 2026-08-05T00:34:35+00:00 | Vulnerability · Source |
| CVE-2026-59921 | suse_vex | SUSE CVE CVE-2026-59921 | known not affected: 42 recommended: 22 | 2026-08-05T00:34:34+00:00 | Vulnerability · Source |
| CVE-2026-64013 | suse_vex | SUSE CVE CVE-2026-64013 | known not affected: 296 | 2026-08-05T00:34:19+00:00 | Vulnerability · Source |
| CVE-2026-64042 | suse_vex | SUSE CVE CVE-2026-64042 | known not affected: 296 | 2026-08-05T00:34:16+00:00 | Vulnerability · Source |
| CVE-2026-64043 | suse_vex | SUSE CVE CVE-2026-64043 | known not affected: 298 | 2026-08-05T00:34:15+00:00 | Vulnerability · Source |
| CVE-2026-64044 | suse_vex | SUSE CVE CVE-2026-64044 | known not affected: 298 | 2026-08-05T00:34:14+00:00 | Vulnerability · Source |
| CVE-2026-64045 | suse_vex | SUSE CVE CVE-2026-64045 | known not affected: 298 | 2026-08-05T00:34:13+00:00 | Vulnerability · Source |
| CVE-2026-64057 | suse_vex | SUSE CVE CVE-2026-64057 | known not affected: 298 | 2026-08-05T00:34:08+00:00 | Vulnerability · Source |
| CVE-2026-64071 | suse_vex | SUSE CVE CVE-2026-64071 | known affected: 29 known not affected: 267 | 2026-08-05T00:34:07+00:00 | Vulnerability · Source |
| CVE-2026-64072 | suse_vex | SUSE CVE CVE-2026-64072 | known not affected: 296 | 2026-08-05T00:34:06+00:00 | Vulnerability · Source |
| CVE-2026-64073 | suse_vex | SUSE CVE CVE-2026-64073 | known affected: 217 known not affected: 79 | 2026-08-05T00:34:04+00:00 | Vulnerability · Source |
| CVE-2026-64074 | suse_vex | SUSE CVE CVE-2026-64074 | known not affected: 296 | 2026-08-05T00:34:03+00:00 | Vulnerability · Source |
| CVE-2026-64075 | suse_vex | SUSE CVE CVE-2026-64075 | known not affected: 296 | 2026-08-05T00:34:01+00:00 | Vulnerability · Source |
| CVE-2026-64076 | suse_vex | SUSE CVE CVE-2026-64076 | known affected: 217 known not affected: 79 | 2026-08-05T00:34:00+00:00 | Vulnerability · Source |
| CVE-2026-64077 | suse_vex | SUSE CVE CVE-2026-64077 | known affected: 129 known not affected: 167 | 2026-08-05T00:33:58+00:00 | Vulnerability · Source |
| CVE-2026-64078 | suse_vex | SUSE CVE CVE-2026-64078 | known affected: 129 known not affected: 167 | 2026-08-05T00:33:56+00:00 | Vulnerability · Source |
| CVE-2026-64079 | suse_vex | SUSE CVE CVE-2026-64079 | known affected: 217 known not affected: 79 | 2026-08-05T00:33:55+00:00 | Vulnerability · Source |
| CVE-2026-64081 | suse_vex | SUSE CVE CVE-2026-64081 | known not affected: 296 | 2026-08-05T00:33:53+00:00 | Vulnerability · Source |
| CVE-2026-64088 | suse_vex | SUSE CVE CVE-2026-64088 | known affected: 222 known not affected: 74 | 2026-08-05T00:33:44+00:00 | Vulnerability · Source |
| CVE-2026-64090 | suse_vex | SUSE CVE CVE-2026-64090 | known affected: 292 known not affected: 4 | 2026-08-05T00:33:42+00:00 | Vulnerability · Source |
| CVE-2026-64092 | suse_vex | SUSE CVE CVE-2026-64092 | known not affected: 296 | 2026-08-05T00:33:41+00:00 | Vulnerability · Source |
| CVE-2026-64095 | suse_vex | SUSE CVE CVE-2026-64095 | known affected: 292 known not affected: 4 | 2026-08-05T00:33:38+00:00 | Vulnerability · Source |
| CVE-2026-64097 | suse_vex | SUSE CVE CVE-2026-64097 | known affected: 191 known not affected: 105 | 2026-08-05T00:33:34+00:00 | Vulnerability · Source |
| CVE-2026-64098 | suse_vex | SUSE CVE CVE-2026-64098 | known affected: 118 known not affected: 178 | 2026-08-05T00:33:33+00:00 | Vulnerability · Source |
| CVE-2026-64099 | suse_vex | SUSE CVE CVE-2026-64099 | known affected: 84 known not affected: 212 | 2026-08-05T00:33:31+00:00 | Vulnerability · Source |
| CVE-2026-64100 | suse_vex | SUSE CVE CVE-2026-64100 | known not affected: 296 | 2026-08-05T00:33:30+00:00 | Vulnerability · Source |
| CVE-2026-64104 | suse_vex | SUSE CVE CVE-2026-64104 | known not affected: 296 | 2026-08-05T00:33:28+00:00 | Vulnerability · Source |
| CVE-2026-64110 | suse_vex | SUSE CVE CVE-2026-64110 | known not affected: 296 | 2026-08-05T00:33:25+00:00 | Vulnerability · Source |