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-31708 | suse_vex | SUSE CVE CVE-2026-31708 | known affected: 289 known not affected: 4 recommended: 4 | 2026-08-06T01:23:35+00:00 | Vulnerability · Source |
| CVE-2026-31709 | suse_vex | SUSE CVE CVE-2026-31709 | known affected: 258 known not affected: 35 recommended: 107 | 2026-08-06T01:23:33+00:00 | Vulnerability · Source |
| CVE-2026-31711 | suse_vex | SUSE CVE CVE-2026-31711 | known not affected: 291 recommended: 4 | 2026-08-06T01:23:32+00:00 | Vulnerability · Source |
| CVE-2026-31712 | suse_vex | SUSE CVE CVE-2026-31712 | known not affected: 293 recommended: 4 | 2026-08-06T01:23:31+00:00 | Vulnerability · Source |
| CVE-2026-31717 | suse_vex | SUSE CVE CVE-2026-31717 | known not affected: 293 recommended: 4 | 2026-08-06T01:23:30+00:00 | Vulnerability · Source |
| CVE-2026-31718 | suse_vex | SUSE CVE CVE-2026-31718 | known not affected: 291 recommended: 4 | 2026-08-06T01:23:29+00:00 | Vulnerability · Source |
| CVE-2026-31719 | suse_vex | SUSE CVE CVE-2026-31719 | known not affected: 291 recommended: 4 | 2026-08-06T01:23:27+00:00 | Vulnerability · Source |
| CVE-2026-31731 | suse_vex | SUSE CVE CVE-2026-31731 | known affected: 17 known not affected: 278 | 2026-08-06T01:23:26+00:00 | Vulnerability · Source |
| CVE-2026-31735 | suse_vex | SUSE CVE CVE-2026-31735 | known not affected: 293 | 2026-08-06T01:23:24+00:00 | Vulnerability · Source |
| CVE-2026-31742 | suse_vex | SUSE CVE CVE-2026-31742 | known not affected: 293 | 2026-08-06T01:23:22+00:00 | Vulnerability · Source |
| CVE-2026-31743 | suse_vex | SUSE CVE CVE-2026-31743 | first fixed: 2 known affected: 17 known not affected: 278 recommended: 145 | 2026-08-06T01:23:21+00:00 | Vulnerability · Source |
| CVE-2026-31766 | suse_vex | SUSE CVE CVE-2026-31766 | known not affected: 293 recommended: 27 | 2026-08-06T01:23:19+00:00 | Vulnerability · Source |
| CVE-2026-31769 | suse_vex | SUSE CVE CVE-2026-31769 | known not affected: 293 | 2026-08-06T01:23:17+00:00 | Vulnerability · Source |
| CVE-2026-31774 | suse_vex | SUSE CVE CVE-2026-31774 | first fixed: 2 known affected: 411 known not affected: 221 recommended: 270 | 2026-08-06T01:23:15+00:00 | Vulnerability · Source |
| CVE-2026-31782 | suse_vex | SUSE CVE CVE-2026-31782 | known not affected: 291 | 2026-08-06T01:23:13+00:00 | Vulnerability · Source |
| CVE-2026-37458 | suse_vex | SUSE CVE CVE-2026-37458 | known affected: 169 known not affected: 21 recommended: 256 | 2026-08-06T01:22:56+00:00 | Vulnerability · Source |
| CVE-2026-40181 | suse_vex | SUSE CVE CVE-2026-40181 | known affected: 14 recommended: 1 | 2026-08-06T01:22:49+00:00 | Vulnerability · Source |
| CVE-2026-40208 | suse_vex | SUSE CVE CVE-2026-40208 | first fixed: 2 known not affected: 26 recommended: 2 | 2026-08-06T01:22:47+00:00 | Vulnerability · Source |
| CVE-2026-41140 | suse_vex | SUSE CVE CVE-2026-41140 | known not affected: 46 | 2026-08-06T01:22:40+00:00 | Vulnerability · Source |
| CVE-2026-42009 | suse_vex | SUSE CVE CVE-2026-42009 | known affected: 448 recommended: 251 | 2026-08-06T01:22:27+00:00 | Vulnerability · Source |
| CVE-2026-42257 | suse_vex | SUSE CVE CVE-2026-42257 | recommended: 54 | 2026-08-06T01:22:19+00:00 | Vulnerability · Source |
| CVE-2026-43006 | suse_vex | SUSE CVE CVE-2026-43006 | known not affected: 291 recommended: 42 | 2026-08-06T01:22:12+00:00 | Vulnerability · Source |
| CVE-2026-43029 | suse_vex | SUSE CVE CVE-2026-43029 | known not affected: 291 | 2026-08-06T01:22:04+00:00 | Vulnerability · Source |
| CVE-2026-43031 | suse_vex | SUSE CVE CVE-2026-43031 | known not affected: 291 | 2026-08-06T01:22:03+00:00 | Vulnerability · Source |
| CVE-2026-43039 | suse_vex | SUSE CVE CVE-2026-43039 | known not affected: 293 | 2026-08-06T01:21:59+00:00 | Vulnerability · Source |
| CVE-2026-43042 | suse_vex | SUSE CVE CVE-2026-43042 | known affected: 289 known not affected: 4 | 2026-08-06T01:21:57+00:00 | Vulnerability · Source |
| CVE-2026-43048 | suse_vex | SUSE CVE CVE-2026-43048 | known affected: 293 | 2026-08-06T01:21:56+00:00 | Vulnerability · Source |
| CVE-2026-43055 | suse_vex | SUSE CVE CVE-2026-43055 | known not affected: 291 | 2026-08-06T01:21:53+00:00 | Vulnerability · Source |
| CVE-2026-43063 | suse_vex | SUSE CVE CVE-2026-43063 | first fixed: 2 known affected: 411 known not affected: 278 recommended: 172 | 2026-08-06T01:21:50+00:00 | Vulnerability · Source |
| CVE-2026-43067 | suse_vex | SUSE CVE CVE-2026-43067 | known not affected: 293 | 2026-08-06T01:21:48+00:00 | Vulnerability · Source |
| CVE-2026-43070 | suse_vex | SUSE CVE CVE-2026-43070 | known not affected: 293 | 2026-08-06T01:21:46+00:00 | Vulnerability · Source |
| CVE-2026-43071 | suse_vex | SUSE CVE CVE-2026-43071 | known affected: 228 known not affected: 67 recommended: 4 | 2026-08-06T01:21:44+00:00 | Vulnerability · Source |
| CVE-2026-43075 | suse_vex | SUSE CVE CVE-2026-43075 | known not affected: 293 | 2026-08-06T01:21:43+00:00 | Vulnerability · Source |
| CVE-2026-43078 | suse_vex | SUSE CVE CVE-2026-43078 | known affected: 289 known not affected: 6 | 2026-08-06T01:21:41+00:00 | Vulnerability · Source |
| CVE-2026-43084 | suse_vex | SUSE CVE CVE-2026-43084 | known not affected: 293 | 2026-08-06T01:21:38+00:00 | Vulnerability · Source |
| CVE-2026-43091 | suse_vex | SUSE CVE CVE-2026-43091 | known affected: 289 known not affected: 6 | 2026-08-06T01:21:36+00:00 | Vulnerability · Source |
| CVE-2026-43099 | suse_vex | SUSE CVE CVE-2026-43099 | known affected: 202 known not affected: 93 | 2026-08-06T01:21:34+00:00 | Vulnerability · Source |
| CVE-2026-43106 | suse_vex | SUSE CVE CVE-2026-43106 | known not affected: 293 | 2026-08-06T01:21:32+00:00 | Vulnerability · Source |
| CVE-2026-43116 | suse_vex | SUSE CVE CVE-2026-43116 | known affected: 295 recommended: 103 | 2026-08-06T01:21:27+00:00 | Vulnerability · Source |
| CVE-2026-43119 | suse_vex | SUSE CVE CVE-2026-43119 | first fixed: 2 known affected: 538 known not affected: 84 recommended: 294 | 2026-08-06T01:21:25+00:00 | Vulnerability · Source |
| CVE-2026-43150 | suse_vex | SUSE CVE CVE-2026-43150 | first fixed: 2 known affected: 411 known not affected: 223 recommended: 270 | 2026-08-06T01:21:19+00:00 | Vulnerability · Source |
| CVE-2026-43153 | suse_vex | SUSE CVE CVE-2026-43153 | first fixed: 2 known affected: 596 known not affected: 93 recommended: 172 | 2026-08-06T01:21:18+00:00 | Vulnerability · Source |
| CVE-2026-43158 | suse_vex | SUSE CVE CVE-2026-43158 | first fixed: 2 known affected: 569 known not affected: 4 recommended: 447 | 2026-08-06T01:21:16+00:00 | Vulnerability · Source |
| CVE-2026-43164 | suse_vex | SUSE CVE CVE-2026-43164 | known not affected: 293 | 2026-08-06T01:21:14+00:00 | Vulnerability · Source |
| CVE-2026-43166 | suse_vex | SUSE CVE CVE-2026-43166 | known not affected: 293 | 2026-08-06T01:21:12+00:00 | Vulnerability · Source |
| CVE-2026-43178 | suse_vex | SUSE CVE CVE-2026-43178 | known not affected: 293 | 2026-08-06T01:21:10+00:00 | Vulnerability · Source |
| CVE-2026-43184 | suse_vex | SUSE CVE CVE-2026-43184 | first fixed: 2 known affected: 626 known not affected: 63 recommended: 172 | 2026-08-06T01:21:08+00:00 | Vulnerability · Source |
| CVE-2026-43186 | suse_vex | SUSE CVE CVE-2026-43186 | known not affected: 309 | 2026-08-06T01:21:07+00:00 | Vulnerability · Source |
| CVE-2026-43187 | suse_vex | SUSE CVE CVE-2026-43187 | first fixed: 2 known affected: 569 known not affected: 4 recommended: 331 | 2026-08-06T01:21:05+00:00 | Vulnerability · Source |
| CVE-2026-43197 | suse_vex | SUSE CVE CVE-2026-43197 | first fixed: 2 known affected: 411 known not affected: 278 recommended: 172 | 2026-08-06T01:21:03+00:00 | Vulnerability · Source |