VEX records
Browse vendor VEX statements available in this Vulnerability-Lookup instance and pivot to the related vulnerability.
104719 VEX records
API response| Vulnerability | Source | Title | Product status | Imported | Links |
|---|---|---|---|---|---|
| CVE-2026-33987 | suse_vex | SUSE CVE CVE-2026-33987 | known not affected: 46 recommended: 123 | 2026-10-16T00:27:38+00:00 | Vulnerability · Source |
| CVE-2026-33995 | suse_vex | SUSE CVE CVE-2026-33995 | known affected: 75 recommended: 117 | 2026-10-16T00:27:36+00:00 | Vulnerability · Source |
| CVE-2026-33997 | suse_vex | SUSE CVE CVE-2026-33997 | known affected: 290 recommended: 67 | 2026-10-16T00:27:34+00:00 | Vulnerability · Source |
| CVE-2026-33999 | suse_vex | SUSE CVE CVE-2026-33999 | known affected: 450 recommended: 144 | 2026-10-16T00:27:33+00:00 | Vulnerability · Source |
| CVE-2026-34000 | suse_vex | SUSE CVE CVE-2026-34000 | known affected: 442 known not affected: 8 recommended: 116 | 2026-10-16T00:27:31+00:00 | Vulnerability · Source |
| CVE-2026-34001 | suse_vex | SUSE CVE CVE-2026-34001 | known affected: 450 recommended: 144 | 2026-10-16T00:27:28+00:00 | Vulnerability · Source |
| CVE-2026-34002 | suse_vex | SUSE CVE CVE-2026-34002 | known affected: 450 recommended: 116 | 2026-10-16T00:27:26+00:00 | Vulnerability · Source |
| CVE-2026-34003 | suse_vex | SUSE CVE CVE-2026-34003 | known affected: 450 recommended: 144 | 2026-10-16T00:27:24+00:00 | Vulnerability · Source |
| CVE-2026-34040 | suse_vex | SUSE CVE CVE-2026-34040 | known affected: 290 recommended: 67 | 2026-10-16T00:27:22+00:00 | Vulnerability · Source |
| CVE-2026-34180 | suse_vex | SUSE CVE CVE-2026-34180 | known affected: 568 known not affected: 104 recommended: 347 | 2026-10-16T00:27:19+00:00 | Vulnerability · Source |
| CVE-2026-34181 | suse_vex | SUSE CVE CVE-2026-34181 | known affected: 394 known not affected: 608 recommended: 67 | 2026-10-16T00:27:16+00:00 | Vulnerability · Source |
| CVE-2026-34230 | suse_vex | SUSE CVE CVE-2026-34230 | known affected: 41 known not affected: 10 recommended: 63 | 2026-10-16T00:27:09+00:00 | Vulnerability · Source |
| CVE-2026-34268 | suse_vex | SUSE CVE CVE-2026-34268 | known affected: 608 known not affected: 70 recommended: 870 | 2026-10-16T00:27:06+00:00 | Vulnerability · Source |
| CVE-2026-34282 | suse_vex | SUSE CVE CVE-2026-34282 | known affected: 458 known not affected: 391 recommended: 634 | 2026-10-16T00:27:03+00:00 | Vulnerability · Source |
| CVE-2026-34352 | suse_vex | SUSE CVE CVE-2026-34352 | known affected: 442 recommended: 171 | 2026-10-16T00:27:00+00:00 | Vulnerability · Source |
| CVE-2026-34483 | suse_vex | SUSE CVE CVE-2026-34483 | known affected: 142 known not affected: 1 recommended: 402 | 2026-10-16T00:26:57+00:00 | Vulnerability · Source |
| CVE-2026-34486 | suse_vex | SUSE CVE CVE-2026-34486 | known affected: 142 known not affected: 1 recommended: 459 | 2026-10-16T00:26:54+00:00 | Vulnerability · Source |
| CVE-2026-34487 | suse_vex | SUSE CVE CVE-2026-34487 | known affected: 142 known not affected: 1 recommended: 402 | 2026-10-16T00:26:51+00:00 | Vulnerability · Source |
| CVE-2026-34500 | suse_vex | SUSE CVE CVE-2026-34500 | known affected: 142 known not affected: 1 recommended: 402 | 2026-10-16T00:26:50+00:00 | Vulnerability · Source |
| CVE-2026-34714 | suse_vex | SUSE CVE CVE-2026-34714 | first fixed: 2 known affected: 446 recommended: 192 | 2026-10-16T00:26:45+00:00 | Vulnerability · Source |
| CVE-2026-34743 | suse_vex | SUSE CVE CVE-2026-34743 | known affected: 464 recommended: 189 | 2026-10-16T00:26:43+00:00 | Vulnerability · Source |
| CVE-2026-34763 | suse_vex | SUSE CVE CVE-2026-34763 | known affected: 14 known not affected: 37 recommended: 63 | 2026-10-16T00:26:41+00:00 | Vulnerability · Source |
| CVE-2026-34785 | suse_vex | SUSE CVE CVE-2026-34785 | known affected: 14 known not affected: 37 recommended: 63 | 2026-10-16T00:26:39+00:00 | Vulnerability · Source |
| CVE-2026-34786 | suse_vex | SUSE CVE CVE-2026-34786 | known affected: 14 known not affected: 37 recommended: 63 | 2026-10-16T00:26:38+00:00 | Vulnerability · Source |
| CVE-2026-34826 | suse_vex | SUSE CVE CVE-2026-34826 | known affected: 14 known not affected: 37 recommended: 63 | 2026-10-16T00:26:36+00:00 | Vulnerability · Source |
| CVE-2026-34829 | suse_vex | SUSE CVE CVE-2026-34829 | known affected: 14 known not affected: 37 recommended: 63 | 2026-10-16T00:26:35+00:00 | Vulnerability · Source |
| CVE-2026-34830 | suse_vex | SUSE CVE CVE-2026-34830 | known affected: 14 known not affected: 37 recommended: 63 | 2026-10-16T00:26:33+00:00 | Vulnerability · Source |
| CVE-2026-34831 | suse_vex | SUSE CVE CVE-2026-34831 | known affected: 14 known not affected: 37 recommended: 63 | 2026-10-16T00:26:32+00:00 | Vulnerability · Source |
| CVE-2026-34933 | suse_vex | SUSE CVE CVE-2026-34933 | known affected: 843 recommended: 284 | 2026-10-16T00:26:30+00:00 | Vulnerability · Source |
| CVE-2026-34982 | suse_vex | SUSE CVE CVE-2026-34982 | known affected: 436 recommended: 219 | 2026-10-16T00:26:28+00:00 | Vulnerability · Source |
| CVE-2026-35172 | suse_vex | SUSE CVE CVE-2026-35172 | first fixed: 14 known not affected: 80 recommended: 5 | 2026-10-16T00:26:25+00:00 | Vulnerability · Source |
| CVE-2026-35406 | suse_vex | SUSE CVE CVE-2026-35406 | known not affected: 30 recommended: 4 | 2026-10-16T00:26:06+00:00 | Vulnerability · Source |
| CVE-2026-35535 | suse_vex | SUSE CVE CVE-2026-35535 | known affected: 367 known not affected: 31 recommended: 156 | 2026-10-16T00:26:04+00:00 | Vulnerability · Source |
| CVE-2026-37236 | suse_vex | SUSE CVE CVE-2026-37236 | known affected: 499 known not affected: 319 recommended: 104 | 2026-10-16T00:26:01+00:00 | Vulnerability · Source |
| CVE-2026-38752 | suse_vex | SUSE CVE CVE-2026-38752 | known affected: 42 recommended: 18 | 2026-10-16T00:25:59+00:00 | Vulnerability · Source |
| CVE-2026-38753 | suse_vex | SUSE CVE CVE-2026-38753 | known affected: 42 recommended: 18 | 2026-10-16T00:25:58+00:00 | Vulnerability · Source |
| CVE-2026-38754 | suse_vex | SUSE CVE CVE-2026-38754 | known affected: 42 recommended: 18 | 2026-10-16T00:25:56+00:00 | Vulnerability · Source |
| CVE-2026-38755 | suse_vex | SUSE CVE CVE-2026-38755 | known affected: 42 recommended: 18 | 2026-10-16T00:25:54+00:00 | Vulnerability · Source |
| CVE-2026-39324 | suse_vex | SUSE CVE CVE-2026-39324 | known not affected: 100 recommended: 1 | 2026-10-16T00:25:52+00:00 | Vulnerability · Source |
| CVE-2026-40192 | suse_vex | SUSE CVE CVE-2026-40192 | known not affected: 57 recommended: 14 | 2026-10-16T00:25:43+00:00 | Vulnerability · Source |
| CVE-2026-40223 | suse_vex | SUSE CVE CVE-2026-40223 | known not affected: 643 | 2026-10-16T00:25:40+00:00 | Vulnerability · Source |
| CVE-2026-40224 | suse_vex | SUSE CVE CVE-2026-40224 | known not affected: 581 recommended: 21 | 2026-10-16T00:25:37+00:00 | Vulnerability · Source |
| CVE-2026-40227 | suse_vex | SUSE CVE CVE-2026-40227 | known not affected: 581 | 2026-10-16T00:25:34+00:00 | Vulnerability · Source |
| CVE-2026-40228 | suse_vex | SUSE CVE CVE-2026-40228 | known not affected: 581 | 2026-10-16T00:25:33+00:00 | Vulnerability · Source |
| CVE-2026-40253 | suse_vex | SUSE CVE CVE-2026-40253 | known affected: 64 known not affected: 25 recommended: 62 | 2026-10-16T00:25:31+00:00 | Vulnerability · Source |
| CVE-2026-40393 | suse_vex | SUSE CVE CVE-2026-40393 | known affected: 1122 recommended: 425 | 2026-10-16T00:25:28+00:00 | Vulnerability · Source |
| CVE-2026-40706 | suse_vex | SUSE CVE CVE-2026-40706 | known affected: 16 recommended: 49 | 2026-10-16T00:25:22+00:00 | Vulnerability · Source |
| CVE-2026-41035 | suse_vex | SUSE CVE CVE-2026-41035 | known affected: 411 recommended: 42 | 2026-10-16T00:25:21+00:00 | Vulnerability · Source |
| CVE-2026-41205 | suse_vex | SUSE CVE CVE-2026-41205 | known affected: 24 recommended: 25 | 2026-10-16T00:25:16+00:00 | Vulnerability · Source |
| CVE-2026-41316 | suse_vex | SUSE CVE CVE-2026-41316 | known affected: 641 known not affected: 38 recommended: 131 | 2026-10-16T00:25:13+00:00 | Vulnerability · Source |