VEX records
Browse vendor VEX statements available in this Vulnerability-Lookup instance and pivot to the related vulnerability.
291704 VEX records
API response| Vulnerability | Source | Title | Product status | Imported | Links |
|---|---|---|---|---|---|
| CVE-2026-45942 | suse_vex | SUSE CVE CVE-2026-45942 | first fixed: 2 known affected: 411 known not affected: 278 recommended: 172 | 2026-08-06T01:18:53+00:00 | Vulnerability · Source |
| CVE-2026-45945 | suse_vex | SUSE CVE CVE-2026-45945 | known not affected: 293 | 2026-08-06T01:18:51+00:00 | Vulnerability · Source |
| CVE-2026-45955 | suse_vex | SUSE CVE CVE-2026-45955 | known not affected: 293 | 2026-08-06T01:18:50+00:00 | Vulnerability · Source |
| CVE-2026-45956 | suse_vex | SUSE CVE CVE-2026-45956 | known affected: 291 known not affected: 4 | 2026-08-06T01:18:49+00:00 | Vulnerability · Source |
| CVE-2026-45959 | suse_vex | SUSE CVE CVE-2026-45959 | known not affected: 293 | 2026-08-06T01:18:46+00:00 | Vulnerability · Source |
| CVE-2026-45972 | suse_vex | SUSE CVE CVE-2026-45972 | known not affected: 293 | 2026-08-06T01:18:43+00:00 | Vulnerability · Source |
| CVE-2026-45980 | suse_vex | SUSE CVE CVE-2026-45980 | known not affected: 293 recommended: 27 | 2026-08-06T01:18:42+00:00 | Vulnerability · Source |
| CVE-2026-45988 | suse_vex | SUSE CVE CVE-2026-45988 | known affected: 295 recommended: 4 | 2026-08-06T01:18:39+00:00 | Vulnerability · Source |
| CVE-2026-45991 | suse_vex | SUSE CVE CVE-2026-45991 | known affected: 228 known not affected: 67 recommended: 4 | 2026-08-06T01:18:38+00:00 | Vulnerability · Source |
| CVE-2026-45999 | suse_vex | SUSE CVE CVE-2026-45999 | first fixed: 2 known affected: 202 known not affected: 93 recommended: 176 | 2026-08-06T01:18:36+00:00 | Vulnerability · Source |
| CVE-2026-46010 | suse_vex | SUSE CVE CVE-2026-46010 | known not affected: 293 recommended: 4 | 2026-08-06T01:18:34+00:00 | Vulnerability · Source |
| CVE-2026-46029 | suse_vex | SUSE CVE CVE-2026-46029 | known not affected: 293 recommended: 4 | 2026-08-06T01:18:31+00:00 | Vulnerability · Source |
| CVE-2026-46031 | suse_vex | SUSE CVE CVE-2026-46031 | known affected: 118 known not affected: 93 recommended: 4 | 2026-08-06T01:18:29+00:00 | Vulnerability · Source |
| CVE-2026-46039 | suse_vex | SUSE CVE CVE-2026-46039 | known not affected: 293 recommended: 4 | 2026-08-06T01:18:28+00:00 | Vulnerability · Source |
| CVE-2026-46054 | suse_vex | SUSE CVE CVE-2026-46054 | known affected: 228 known not affected: 67 recommended: 66 | 2026-08-06T01:18:23+00:00 | Vulnerability · Source |
| CVE-2026-46055 | suse_vex | SUSE CVE CVE-2026-46055 | known not affected: 293 recommended: 4 | 2026-08-06T01:18:22+00:00 | Vulnerability · Source |
| CVE-2026-46062 | suse_vex | SUSE CVE CVE-2026-46062 | known not affected: 293 recommended: 4 | 2026-08-06T01:18:20+00:00 | Vulnerability · Source |
| CVE-2026-46070 | suse_vex | SUSE CVE CVE-2026-46070 | known affected: 291 known not affected: 4 recommended: 4 | 2026-08-06T01:18:18+00:00 | Vulnerability · Source |
| CVE-2026-46078 | suse_vex | SUSE CVE CVE-2026-46078 | first fixed: 2 known affected: 118 known not affected: 175 recommended: 176 | 2026-08-06T01:18:16+00:00 | Vulnerability · Source |
| CVE-2026-46081 | suse_vex | SUSE CVE CVE-2026-46081 | known not affected: 293 recommended: 4 | 2026-08-06T01:18:14+00:00 | Vulnerability · Source |
| CVE-2026-46085 | suse_vex | SUSE CVE CVE-2026-46085 | known not affected: 293 recommended: 4 | 2026-08-06T01:18:13+00:00 | Vulnerability · Source |
| CVE-2026-46093 | suse_vex | SUSE CVE CVE-2026-46093 | first fixed: 2 known not affected: 278 recommended: 149 | 2026-08-06T01:18:10+00:00 | Vulnerability · Source |
| CVE-2026-46100 | suse_vex | SUSE CVE CVE-2026-46100 | known not affected: 293 recommended: 4 | 2026-08-06T01:18:08+00:00 | Vulnerability · Source |
| CVE-2026-46105 | suse_vex | SUSE CVE CVE-2026-46105 | known not affected: 293 recommended: 4 | 2026-08-06T01:18:06+00:00 | Vulnerability · Source |
| CVE-2026-46107 | suse_vex | SUSE CVE CVE-2026-46107 | known affected: 295 recommended: 4 | 2026-08-06T01:18:05+00:00 | Vulnerability · Source |
| CVE-2026-46111 | suse_vex | SUSE CVE CVE-2026-46111 | first fixed: 2 known affected: 472 known not affected: 133 recommended: 298 | 2026-08-06T01:18:03+00:00 | Vulnerability · Source |
| CVE-2026-46115 | suse_vex | SUSE CVE CVE-2026-46115 | known affected: 114 known not affected: 181 recommended: 4 | 2026-08-06T01:18:01+00:00 | Vulnerability · Source |
| CVE-2026-46129 | suse_vex | SUSE CVE CVE-2026-46129 | known not affected: 293 recommended: 4 | 2026-08-06T01:17:56+00:00 | Vulnerability · Source |
| CVE-2026-46135 | suse_vex | SUSE CVE CVE-2026-46135 | known affected: 295 recommended: 107 | 2026-08-06T01:17:55+00:00 | Vulnerability · Source |
| CVE-2026-46154 | suse_vex | SUSE CVE CVE-2026-46154 | known not affected: 293 recommended: 4 | 2026-08-06T01:17:49+00:00 | Vulnerability · Source |
| CVE-2026-46155 | suse_vex | SUSE CVE CVE-2026-46155 | known affected: 114 known not affected: 181 recommended: 87 | 2026-08-06T01:17:47+00:00 | Vulnerability · Source |
| CVE-2026-46164 | suse_vex | SUSE CVE CVE-2026-46164 | known not affected: 293 recommended: 4 | 2026-08-06T01:17:44+00:00 | Vulnerability · Source |
| CVE-2026-46175 | suse_vex | SUSE CVE CVE-2026-46175 | known affected: 289 known not affected: 6 recommended: 4 | 2026-08-06T01:17:39+00:00 | Vulnerability · Source |
| CVE-2026-46195 | suse_vex | SUSE CVE CVE-2026-46195 | known affected: 258 known not affected: 37 recommended: 65 | 2026-08-06T01:17:35+00:00 | Vulnerability · Source |
| CVE-2026-46208 | suse_vex | SUSE CVE CVE-2026-46208 | known affected: 289 known not affected: 6 recommended: 4 | 2026-08-06T01:17:31+00:00 | Vulnerability · Source |
| CVE-2026-46210 | suse_vex | SUSE CVE CVE-2026-46210 | known not affected: 293 recommended: 4 | 2026-08-06T01:17:29+00:00 | Vulnerability · Source |
| CVE-2026-46215 | suse_vex | SUSE CVE CVE-2026-46215 | known not affected: 293 recommended: 87 | 2026-08-06T01:17:27+00:00 | Vulnerability · Source |
| CVE-2026-46240 | suse_vex | SUSE CVE CVE-2026-46240 | known not affected: 293 recommended: 4 | 2026-08-06T01:17:24+00:00 | Vulnerability · Source |
| CVE-2026-46250 | suse_vex | SUSE CVE CVE-2026-46250 | known not affected: 293 | 2026-08-06T01:17:20+00:00 | Vulnerability · Source |
| CVE-2026-46251 | suse_vex | SUSE CVE CVE-2026-46251 | known affected: 114 known not affected: 181 | 2026-08-06T01:17:18+00:00 | Vulnerability · Source |
| CVE-2026-46260 | suse_vex | SUSE CVE CVE-2026-46260 | known not affected: 293 | 2026-08-06T01:17:16+00:00 | Vulnerability · Source |
| CVE-2026-46264 | suse_vex | SUSE CVE CVE-2026-46264 | known not affected: 293 | 2026-08-06T01:17:13+00:00 | Vulnerability · Source |
| CVE-2026-46277 | suse_vex | SUSE CVE CVE-2026-46277 | known not affected: 293 recommended: 4 | 2026-08-06T01:17:10+00:00 | Vulnerability · Source |
| CVE-2026-46280 | suse_vex | SUSE CVE CVE-2026-46280 | known affected: 216 known not affected: 79 recommended: 4 | 2026-08-06T01:17:09+00:00 | Vulnerability · Source |
| CVE-2026-46288 | suse_vex | SUSE CVE CVE-2026-46288 | known affected: 17 known not affected: 278 recommended: 4 | 2026-08-06T01:17:07+00:00 | Vulnerability · Source |
| CVE-2026-46299 | suse_vex | SUSE CVE CVE-2026-46299 | known affected: 259 known not affected: 4 recommended: 41 | 2026-08-06T01:17:05+00:00 | Vulnerability · Source |
| CVE-2026-46304 | suse_vex | SUSE CVE CVE-2026-46304 | known affected: 291 known not affected: 4 recommended: 4 | 2026-08-06T01:17:04+00:00 | Vulnerability · Source |
| CVE-2026-46311 | suse_vex | SUSE CVE CVE-2026-46311 | known not affected: 293 recommended: 4 | 2026-08-06T01:17:02+00:00 | Vulnerability · Source |
| CVE-2026-46328 | suse_vex | SUSE CVE CVE-2026-46328 | first fixed: 2 known affected: 555 known not affected: 35 recommended: 288 | 2026-08-06T01:16:55+00:00 | Vulnerability · Source |
| CVE-2026-46332 | suse_vex | SUSE CVE CVE-2026-46332 | known not affected: 293 recommended: 4 | 2026-08-06T01:16:53+00:00 | Vulnerability · Source |