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-5657 | suse_vex | SUSE CVE CVE-2026-5657 | known affected: 96 known not affected: 60 recommended: 120 | 2026-10-16T00:48:00+00:00 | Vulnerability · Source |
| CVE-2026-5704 | suse_vex | SUSE CVE CVE-2026-5704 | known affected: 453 recommended: 88 | 2026-10-16T00:47:57+00:00 | Vulnerability · Source |
| CVE-2026-5713 | suse_vex | SUSE CVE CVE-2026-5713 | known not affected: 411 recommended: 56 | 2026-10-16T00:47:54+00:00 | Vulnerability · Source |
| CVE-2026-5773 | suse_vex | SUSE CVE CVE-2026-5773 | known affected: 524 known not affected: 2 recommended: 71 | 2026-10-16T00:47:52+00:00 | Vulnerability · Source |
| CVE-2026-5958 | suse_vex | SUSE CVE CVE-2026-5958 | known affected: 420 recommended: 73 | 2026-10-16T00:47:49+00:00 | Vulnerability · Source |
| CVE-2026-6100 | suse_vex | SUSE CVE CVE-2026-6100 | known affected: 529 known not affected: 44 recommended: 943 | 2026-10-16T00:47:43+00:00 | Vulnerability · Source |
| CVE-2026-6103 | suse_vex | SUSE CVE CVE-2026-6103 | known affected: 2257 recommended: 307 | 2026-10-16T00:47:40+00:00 | Vulnerability · Source |
| CVE-2026-6244 | suse_vex | SUSE CVE CVE-2026-6244 | known affected: 445 recommended: 55 | 2026-10-16T00:47:36+00:00 | Vulnerability · Source |
| CVE-2026-6253 | suse_vex | SUSE CVE CVE-2026-6253 | first fixed: 13 known affected: 446 recommended: 166 | 2026-10-16T00:47:33+00:00 | Vulnerability · Source |
| CVE-2026-6276 | suse_vex | SUSE CVE CVE-2026-6276 | first fixed: 13 known affected: 416 known not affected: 30 recommended: 166 | 2026-10-16T00:47:30+00:00 | Vulnerability · Source |
| CVE-2026-6321 | suse_vex | SUSE CVE CVE-2026-6321 | known not affected: 117 recommended: 70 | 2026-10-16T00:47:28+00:00 | Vulnerability · Source |
| CVE-2026-6322 | suse_vex | SUSE CVE CVE-2026-6322 | known affected: 109 known not affected: 8 | 2026-10-16T00:47:26+00:00 | Vulnerability · Source |
| CVE-2026-6368 | suse_vex | SUSE CVE CVE-2026-6368 | known affected: 594 recommended: 1017 | 2026-10-16T00:47:22+00:00 | Vulnerability · Source |
| CVE-2026-6429 | suse_vex | SUSE CVE CVE-2026-6429 | first fixed: 13 known affected: 446 recommended: 166 | 2026-10-16T00:47:20+00:00 | Vulnerability · Source |
| CVE-2026-6519 | suse_vex | SUSE CVE CVE-2026-6519 | known affected: 96 known not affected: 60 recommended: 120 | 2026-10-16T00:47:17+00:00 | Vulnerability · Source |
| CVE-2026-6520 | suse_vex | SUSE CVE CVE-2026-6520 | known affected: 96 known not affected: 60 recommended: 120 | 2026-10-16T00:47:15+00:00 | Vulnerability · Source |
| CVE-2026-6521 | suse_vex | SUSE CVE CVE-2026-6521 | known affected: 148 recommended: 139 | 2026-10-16T00:47:12+00:00 | Vulnerability · Source |
| CVE-2026-6522 | suse_vex | SUSE CVE CVE-2026-6522 | known affected: 148 recommended: 139 | 2026-10-16T00:47:10+00:00 | Vulnerability · Source |
| CVE-2026-6523 | suse_vex | SUSE CVE CVE-2026-6523 | known affected: 96 known not affected: 60 recommended: 120 | 2026-10-16T00:47:08+00:00 | Vulnerability · Source |
| CVE-2026-6524 | suse_vex | SUSE CVE CVE-2026-6524 | known not affected: 237 recommended: 54 | 2026-10-16T00:47:06+00:00 | Vulnerability · Source |
| CVE-2026-6527 | suse_vex | SUSE CVE CVE-2026-6527 | known affected: 148 recommended: 139 | 2026-10-16T00:47:03+00:00 | Vulnerability · Source |
| CVE-2026-6529 | suse_vex | SUSE CVE CVE-2026-6529 | known affected: 96 known not affected: 60 recommended: 120 | 2026-10-16T00:47:00+00:00 | Vulnerability · Source |
| CVE-2026-6530 | suse_vex | SUSE CVE CVE-2026-6530 | known affected: 96 known not affected: 60 recommended: 120 | 2026-10-16T00:46:58+00:00 | Vulnerability · Source |
| CVE-2026-6531 | suse_vex | SUSE CVE CVE-2026-6531 | known not affected: 237 recommended: 54 | 2026-10-16T00:46:56+00:00 | Vulnerability · Source |
| CVE-2026-6532 | suse_vex | SUSE CVE CVE-2026-6532 | known affected: 148 recommended: 139 | 2026-10-16T00:46:54+00:00 | Vulnerability · Source |
| CVE-2026-6533 | suse_vex | SUSE CVE CVE-2026-6533 | known affected: 24 known not affected: 213 recommended: 54 | 2026-10-16T00:46:53+00:00 | Vulnerability · Source |
| CVE-2026-6534 | suse_vex | SUSE CVE CVE-2026-6534 | known affected: 96 known not affected: 60 recommended: 120 | 2026-10-16T00:46:51+00:00 | Vulnerability · Source |
| CVE-2026-6535 | suse_vex | SUSE CVE CVE-2026-6535 | known affected: 148 recommended: 139 | 2026-10-16T00:46:49+00:00 | Vulnerability · Source |
| CVE-2026-6537 | suse_vex | SUSE CVE CVE-2026-6537 | known affected: 24 known not affected: 213 recommended: 54 | 2026-10-16T00:46:48+00:00 | Vulnerability · Source |
| CVE-2026-6538 | suse_vex | SUSE CVE CVE-2026-6538 | known affected: 148 recommended: 139 | 2026-10-16T00:46:46+00:00 | Vulnerability · Source |
| CVE-2026-6554 | suse_vex | SUSE CVE CVE-2026-6554 | known affected: 445 recommended: 55 | 2026-10-16T00:46:43+00:00 | Vulnerability · Source |
| CVE-2026-6791 | suse_vex | SUSE CVE CVE-2026-6791 | known affected: 594 recommended: 1017 | 2026-10-16T00:46:40+00:00 | Vulnerability · Source |
| CVE-2026-6868 | suse_vex | SUSE CVE CVE-2026-6868 | known affected: 96 known not affected: 60 recommended: 120 | 2026-10-16T00:46:38+00:00 | Vulnerability · Source |
| CVE-2026-6869 | suse_vex | SUSE CVE CVE-2026-6869 | known affected: 96 known not affected: 60 recommended: 120 | 2026-10-16T00:46:35+00:00 | Vulnerability · Source |
| CVE-2026-6893 | suse_vex | SUSE CVE CVE-2026-6893 | known affected: 413 known not affected: 23 recommended: 147 | 2026-10-16T00:46:30+00:00 | Vulnerability · Source |
| CVE-2026-7009 | suse_vex | SUSE CVE CVE-2026-7009 | known not affected: 193 | 2026-10-16T00:46:26+00:00 | Vulnerability · Source |
| CVE-2026-7168 | suse_vex | SUSE CVE CVE-2026-7168 | known affected: 509 recommended: 72 | 2026-10-16T00:46:24+00:00 | Vulnerability · Source |
| CVE-2026-7320 | suse_vex | SUSE CVE CVE-2026-7320 | known affected: 48 recommended: 124 | 2026-10-16T00:46:20+00:00 | Vulnerability · Source |
| CVE-2026-7321 | suse_vex | SUSE CVE CVE-2026-7321 | known affected: 48 recommended: 119 | 2026-10-16T00:46:17+00:00 | Vulnerability · Source |
| CVE-2026-7322 | suse_vex | SUSE CVE CVE-2026-7322 | known affected: 48 recommended: 124 | 2026-10-16T00:46:15+00:00 | Vulnerability · Source |
| CVE-2026-7323 | suse_vex | SUSE CVE CVE-2026-7323 | known affected: 48 recommended: 124 | 2026-10-16T00:46:13+00:00 | Vulnerability · Source |
| CVE-2026-7383 | suse_vex | SUSE CVE CVE-2026-7383 | known affected: 568 known not affected: 104 recommended: 347 | 2026-10-16T00:46:11+00:00 | Vulnerability · Source |
| CVE-2026-8286 | suse_vex | SUSE CVE CVE-2026-8286 | first fixed: 13 known affected: 466 known not affected: 13 recommended: 149 | 2026-10-16T00:46:05+00:00 | Vulnerability · Source |
| CVE-2026-8376 | suse_vex | SUSE CVE CVE-2026-8376 | known affected: 394 known not affected: 77 recommended: 125 | 2026-10-16T00:46:01+00:00 | Vulnerability · Source |
| CVE-2026-8458 | suse_vex | SUSE CVE CVE-2026-8458 | first fixed: 13 known affected: 466 known not affected: 2 recommended: 139 | 2026-10-16T00:45:59+00:00 | Vulnerability · Source |
| CVE-2026-8863 | suse_vex | SUSE CVE CVE-2026-8863 | known not affected: 30 | 2026-10-16T00:45:56+00:00 | Vulnerability · Source |
| CVE-2026-8924 | suse_vex | SUSE CVE CVE-2026-8924 | first fixed: 13 known affected: 466 known not affected: 15 recommended: 138 | 2026-10-16T00:45:54+00:00 | Vulnerability · Source |
| CVE-2026-8925 | suse_vex | SUSE CVE CVE-2026-8925 | known not affected: 186 recommended: 9 | 2026-10-16T00:45:52+00:00 | Vulnerability · Source |
| CVE-2026-8926 | suse_vex | SUSE CVE CVE-2026-8926 | known affected: 478 known not affected: 50 recommended: 71 | 2026-10-16T00:45:49+00:00 | Vulnerability · Source |
| CVE-2026-8927 | suse_vex | SUSE CVE CVE-2026-8927 | first fixed: 13 known affected: 490 recommended: 131 | 2026-10-16T00:45:46+00:00 | Vulnerability · Source |