VEX records
Browse vendor VEX statements available in this Vulnerability-Lookup instance and pivot to the related vulnerability.
297694 VEX records
API response| Vulnerability | Source | Title | Product status | Imported | Links |
|---|---|---|---|---|---|
| CVE-2026-5545 | microsoft_vex | wrong reuse of HTTP Negotiate connection | fixed: 2 known affected: 3 known not affected: 4 | 2026-06-15T01:40:49+00:00 | Vulnerability · Source |
| CVE-2026-6429 | microsoft_vex | netrc credential leak with reused proxy connection | fixed: 2 known affected: 3 known not affected: 4 | 2026-06-15T01:40:40+00:00 | Vulnerability · Source |
| CVE-2026-31574 | suse_vex | SUSE CVE CVE-2026-31574 | known not affected: 313 recommended: 4 | 2026-06-15T01:28:03+00:00 | Vulnerability · Source |
| CVE-2026-31577 | suse_vex | SUSE CVE CVE-2026-31577 | known not affected: 313 recommended: 4 | 2026-06-15T01:28:00+00:00 | Vulnerability · Source |
| CVE-2026-31594 | suse_vex | SUSE CVE CVE-2026-31594 | known affected: 129 known not affected: 184 recommended: 4 | 2026-06-15T01:27:44+00:00 | Vulnerability · Source |
| CVE-2026-31601 | suse_vex | SUSE CVE CVE-2026-31601 | known affected: 317 recommended: 4 | 2026-06-15T01:27:36+00:00 | Vulnerability · Source |
| CVE-2026-31621 | suse_vex | SUSE CVE CVE-2026-31621 | known not affected: 313 recommended: 4 | 2026-06-15T01:27:15+00:00 | Vulnerability · Source |
| CVE-2026-31686 | suse_vex | SUSE CVE CVE-2026-31686 | known affected: 248 known not affected: 65 recommended: 4 | 2026-06-15T01:27:05+00:00 | Vulnerability · Source |
| CVE-2026-31702 | suse_vex | SUSE CVE CVE-2026-31702 | known not affected: 289 recommended: 4 | 2026-06-15T01:26:58+00:00 | Vulnerability · Source |
| CVE-2026-31704 | suse_vex | SUSE CVE CVE-2026-31704 | known not affected: 289 recommended: 4 | 2026-06-15T01:26:57+00:00 | Vulnerability · Source |
| CVE-2026-31710 | suse_vex | SUSE CVE CVE-2026-31710 | known not affected: 289 recommended: 4 | 2026-06-15T01:26:49+00:00 | Vulnerability · Source |
| CVE-2026-31713 | suse_vex | SUSE CVE CVE-2026-31713 | known not affected: 289 recommended: 4 | 2026-06-15T01:26:46+00:00 | Vulnerability · Source |
| CVE-2026-31714 | suse_vex | SUSE CVE CVE-2026-31714 | known not affected: 291 recommended: 4 | 2026-06-15T01:26:45+00:00 | Vulnerability · Source |
| CVE-2026-31715 | suse_vex | SUSE CVE CVE-2026-31715 | known not affected: 291 recommended: 4 | 2026-06-15T01:26:44+00:00 | Vulnerability · Source |
| CVE-2026-43073 | suse_vex | SUSE CVE CVE-2026-43073 | known affected: 179 recommended: 4 | 2026-06-15T01:26:33+00:00 | Vulnerability · Source |
| CVE-2026-43349 | suse_vex | SUSE CVE CVE-2026-43349 | known not affected: 291 recommended: 4 | 2026-06-15T01:26:30+00:00 | Vulnerability · Source |
| CVE-2026-46087 | suse_vex | SUSE CVE CVE-2026-46087 | known not affected: 291 recommended: 4 | 2026-06-15T01:24:10+00:00 | Vulnerability · Source |
| CVE-2026-46095 | suse_vex | SUSE CVE CVE-2026-46095 | known not affected: 291 recommended: 4 | 2026-06-15T01:24:02+00:00 | Vulnerability · Source |
| CVE-2026-46097 | suse_vex | SUSE CVE CVE-2026-46097 | known not affected: 291 recommended: 4 | 2026-06-15T01:24:00+00:00 | Vulnerability · Source |
| CVE-2026-46134 | suse_vex | SUSE CVE CVE-2026-46134 | known not affected: 291 recommended: 4 | 2026-06-15T01:23:21+00:00 | Vulnerability · Source |
| CVE-2026-46139 | suse_vex | SUSE CVE CVE-2026-46139 | known not affected: 291 recommended: 4 | 2026-06-15T01:23:15+00:00 | Vulnerability · Source |
| CVE-2026-46141 | suse_vex | SUSE CVE CVE-2026-46141 | known not affected: 291 recommended: 4 | 2026-06-15T01:23:13+00:00 | Vulnerability · Source |
| CVE-2026-46142 | suse_vex | SUSE CVE CVE-2026-46142 | known not affected: 291 recommended: 4 | 2026-06-15T01:23:12+00:00 | Vulnerability · Source |
| CVE-2026-46148 | suse_vex | SUSE CVE CVE-2026-46148 | known affected: 112 known not affected: 179 recommended: 4 | 2026-06-15T01:23:06+00:00 | Vulnerability · Source |
| CVE-2026-46153 | suse_vex | SUSE CVE CVE-2026-46153 | known affected: 291 recommended: 4 | 2026-06-15T01:23:00+00:00 | Vulnerability · Source |
| CVE-2026-46156 | suse_vex | SUSE CVE CVE-2026-46156 | known not affected: 291 recommended: 4 | 2026-06-15T01:22:57+00:00 | Vulnerability · Source |
| CVE-2026-46171 | suse_vex | SUSE CVE CVE-2026-46171 | known affected: 15 known not affected: 276 recommended: 4 | 2026-06-15T01:22:41+00:00 | Vulnerability · Source |
| CVE-2026-46183 | suse_vex | SUSE CVE CVE-2026-46183 | known not affected: 291 recommended: 4 | 2026-06-15T01:22:29+00:00 | Vulnerability · Source |
| CVE-2026-46188 | suse_vex | SUSE CVE CVE-2026-46188 | known affected: 15 known not affected: 276 recommended: 4 | 2026-06-15T01:22:23+00:00 | Vulnerability · Source |
| CVE-2026-46192 | suse_vex | SUSE CVE CVE-2026-46192 | known not affected: 291 recommended: 4 | 2026-06-15T01:22:19+00:00 | Vulnerability · Source |
| CVE-2026-46196 | suse_vex | SUSE CVE CVE-2026-46196 | known affected: 285 known not affected: 6 recommended: 4 | 2026-06-15T01:22:15+00:00 | Vulnerability · Source |
| CVE-2026-46202 | suse_vex | SUSE CVE CVE-2026-46202 | known not affected: 291 recommended: 4 | 2026-06-15T01:22:09+00:00 | Vulnerability · Source |
| CVE-2026-46213 | suse_vex | SUSE CVE CVE-2026-46213 | known not affected: 291 recommended: 4 | 2026-06-15T01:21:57+00:00 | Vulnerability · Source |
| CVE-2026-46221 | suse_vex | SUSE CVE CVE-2026-46221 | known not affected: 291 recommended: 4 | 2026-06-15T01:21:49+00:00 | Vulnerability · Source |
| CVE-2026-46222 | suse_vex | SUSE CVE CVE-2026-46222 | known not affected: 291 recommended: 4 | 2026-06-15T01:21:48+00:00 | Vulnerability · Source |
| CVE-2026-46223 | suse_vex | SUSE CVE CVE-2026-46223 | known not affected: 291 recommended: 4 | 2026-06-15T01:21:47+00:00 | Vulnerability · Source |
| CVE-2026-46224 | suse_vex | SUSE CVE CVE-2026-46224 | known not affected: 291 recommended: 4 | 2026-06-15T01:21:46+00:00 | Vulnerability · Source |
| CVE-2026-46228 | suse_vex | SUSE CVE CVE-2026-46228 | known affected: 15 known not affected: 276 recommended: 4 | 2026-06-15T01:21:41+00:00 | Vulnerability · Source |
| CVE-2026-46239 | suse_vex | SUSE CVE CVE-2026-46239 | known not affected: 291 recommended: 4 | 2026-06-15T01:21:30+00:00 | Vulnerability · Source |
| CVE-2026-46278 | suse_vex | SUSE CVE CVE-2026-46278 | known not affected: 291 recommended: 4 | 2026-06-15T01:21:17+00:00 | Vulnerability · Source |
| CVE-2026-46279 | suse_vex | SUSE CVE CVE-2026-46279 | known affected: 15 known not affected: 276 recommended: 4 | 2026-06-15T01:21:15+00:00 | Vulnerability · Source |
| CVE-2026-46281 | suse_vex | SUSE CVE CVE-2026-46281 | known not affected: 291 recommended: 4 | 2026-06-15T01:21:13+00:00 | Vulnerability · Source |
| CVE-2026-46284 | suse_vex | SUSE CVE CVE-2026-46284 | known not affected: 291 recommended: 4 | 2026-06-15T01:21:10+00:00 | Vulnerability · Source |
| CVE-2026-46290 | suse_vex | SUSE CVE CVE-2026-46290 | known not affected: 291 recommended: 4 | 2026-06-15T01:21:04+00:00 | Vulnerability · Source |
| CVE-2026-46293 | suse_vex | SUSE CVE CVE-2026-46293 | known affected: 112 known not affected: 179 recommended: 4 | 2026-06-15T01:21:00+00:00 | Vulnerability · Source |
| CVE-2026-46295 | suse_vex | SUSE CVE CVE-2026-46295 | known not affected: 291 recommended: 4 | 2026-06-15T01:20:58+00:00 | Vulnerability · Source |
| CVE-2026-46297 | suse_vex | SUSE CVE CVE-2026-46297 | known not affected: 291 recommended: 4 | 2026-06-15T01:20:56+00:00 | Vulnerability · Source |
| CVE-2026-46305 | suse_vex | SUSE CVE CVE-2026-46305 | known not affected: 291 recommended: 4 | 2026-06-15T01:20:49+00:00 | Vulnerability · Source |
| CVE-2026-46308 | suse_vex | SUSE CVE CVE-2026-46308 | known not affected: 291 recommended: 4 | 2026-06-15T01:20:45+00:00 | Vulnerability · Source |
| CVE-2026-46309 | suse_vex | SUSE CVE CVE-2026-46309 | known not affected: 291 recommended: 4 | 2026-06-15T01:20:44+00:00 | Vulnerability · Source |