VEX records
Browse vendor VEX statements available in this Vulnerability-Lookup instance and pivot to the related vulnerability.
292285 VEX records
API response| Vulnerability | Source | Title | Product status | Imported | Links |
|---|---|---|---|---|---|
| CVE-2026-31428 | suse_vex | SUSE CVE CVE-2026-31428 | first fixed: 2 known affected: 208 recommended: 325 | 2026-07-24T02:34:09+00:00 | Vulnerability · Source |
| CVE-2026-31446 | suse_vex | SUSE CVE CVE-2026-31446 | first fixed: 2 known affected: 529 known not affected: 96 recommended: 267 | 2026-07-24T02:34:00+00:00 | Vulnerability · Source |
| CVE-2026-31454 | suse_vex | SUSE CVE CVE-2026-31454 | first fixed: 2 known affected: 529 known not affected: 96 recommended: 267 | 2026-07-24T02:33:50+00:00 | Vulnerability · Source |
| CVE-2026-31455 | suse_vex | SUSE CVE CVE-2026-31455 | first fixed: 2 known affected: 529 known not affected: 96 recommended: 267 | 2026-07-24T02:33:48+00:00 | Vulnerability · Source |
| CVE-2026-31694 | suse_vex | SUSE CVE CVE-2026-31694 | first fixed: 2 known affected: 420 known not affected: 63 recommended: 645 | 2026-07-24T02:32:23+00:00 | Vulnerability · Source |
| CVE-2026-31700 | suse_vex | SUSE CVE CVE-2026-31700 | first fixed: 2 known affected: 451 known not affected: 4 recommended: 487 | 2026-07-24T02:32:19+00:00 | Vulnerability · Source |
| CVE-2026-31703 | suse_vex | SUSE CVE CVE-2026-31703 | first fixed: 2 known affected: 424 known not affected: 177 recommended: 271 | 2026-07-24T02:32:16+00:00 | Vulnerability · Source |
| CVE-2026-31767 | suse_vex | SUSE CVE CVE-2026-31767 | known affected: 526 known not affected: 92 recommended: 122 | 2026-07-24T02:32:06+00:00 | Vulnerability · Source |
| CVE-2026-31788 | suse_vex | SUSE CVE CVE-2026-31788 | first fixed: 2 known affected: 394 known not affected: 185 recommended: 299 | 2026-07-24T02:32:01+00:00 | Vulnerability · Source |
| CVE-2026-34714 | suse_vex | SUSE CVE CVE-2026-34714 | first fixed: 2 known affected: 400 recommended: 187 | 2026-07-24T02:31:21+00:00 | Vulnerability · Source |
| CVE-2026-34978 | suse_vex | SUSE CVE CVE-2026-34978 | known affected: 619 recommended: 127 | 2026-07-24T02:31:15+00:00 | Vulnerability · Source |
| CVE-2026-34979 | suse_vex | SUSE CVE CVE-2026-34979 | known affected: 619 recommended: 127 | 2026-07-24T02:31:13+00:00 | Vulnerability · Source |
| CVE-2026-34990 | suse_vex | SUSE CVE CVE-2026-34990 | known affected: 468 recommended: 292 | 2026-07-24T02:31:05+00:00 | Vulnerability · Source |
| CVE-2026-39314 | suse_vex | SUSE CVE CVE-2026-39314 | known affected: 601 known not affected: 20 recommended: 118 | 2026-07-24T02:30:54+00:00 | Vulnerability · Source |
| CVE-2026-39316 | suse_vex | SUSE CVE CVE-2026-39316 | known affected: 619 recommended: 127 | 2026-07-24T02:30:52+00:00 | Vulnerability · Source |
| CVE-2026-39881 | suse_vex | SUSE CVE CVE-2026-39881 | first fixed: 2 known affected: 471 recommended: 121 | 2026-07-24T02:30:28+00:00 | Vulnerability · Source |
| CVE-2026-39892 | suse_vex | SUSE CVE CVE-2026-39892 | known not affected: 102 recommended: 3 | 2026-07-24T02:30:26+00:00 | Vulnerability · Source |
| CVE-2026-42307 | suse_vex | SUSE CVE CVE-2026-42307 | first fixed: 2 known affected: 411 known not affected: 8 recommended: 155 | 2026-07-24T02:29:43+00:00 | Vulnerability · Source |
| CVE-2026-43044 | suse_vex | SUSE CVE CVE-2026-43044 | known affected: 394 known not affected: 192 recommended: 154 | 2026-07-24T02:29:01+00:00 | Vulnerability · Source |
| CVE-2026-43052 | suse_vex | SUSE CVE CVE-2026-43052 | known affected: 569 known not affected: 19 recommended: 152 | 2026-07-24T02:28:58+00:00 | Vulnerability · Source |
| CVE-2026-43261 | suse_vex | SUSE CVE CVE-2026-43261 | known affected: 549 known not affected: 69 recommended: 122 | 2026-07-24T02:27:21+00:00 | Vulnerability · Source |
| CVE-2026-43296 | suse_vex | SUSE CVE CVE-2026-43296 | known affected: 512 known not affected: 106 recommended: 122 | 2026-07-24T02:27:16+00:00 | Vulnerability · Source |
| CVE-2026-43441 | suse_vex | SUSE CVE CVE-2026-43441 | first fixed: 2 known affected: 424 known not affected: 179 recommended: 268 | 2026-07-24T02:26:34+00:00 | Vulnerability · Source |
| CVE-2026-44656 | suse_vex | SUSE CVE CVE-2026-44656 | first fixed: 2 known affected: 419 recommended: 155 | 2026-07-24T02:25:37+00:00 | Vulnerability · Source |
| CVE-2026-45130 | suse_vex | SUSE CVE CVE-2026-45130 | first fixed: 2 known affected: 419 recommended: 155 | 2026-07-24T02:25:27+00:00 | Vulnerability · Source |
| CVE-2026-45232 | suse_vex | SUSE CVE CVE-2026-45232 | known affected: 404 recommended: 33 | 2026-07-24T02:25:25+00:00 | Vulnerability · Source |
| CVE-2026-45676 | suse_vex | SUSE CVE CVE-2026-45676 | known affected: 8 | 2026-07-24T02:25:21+00:00 | Vulnerability · Source |
| CVE-2026-45842 | suse_vex | SUSE CVE CVE-2026-45842 | first fixed: 2 known affected: 573 recommended: 301 | 2026-07-24T02:25:09+00:00 | Vulnerability · Source |
| CVE-2026-45843 | suse_vex | SUSE CVE CVE-2026-45843 | first fixed: 2 known affected: 573 recommended: 301 | 2026-07-24T02:25:07+00:00 | Vulnerability · Source |
| CVE-2026-45856 | suse_vex | SUSE CVE CVE-2026-45856 | first fixed: 2 known affected: 538 known not affected: 65 recommended: 267 | 2026-07-24T02:25:01+00:00 | Vulnerability · Source |
| CVE-2026-45878 | suse_vex | SUSE CVE CVE-2026-45878 | known affected: 394 known not affected: 202 recommended: 153 | 2026-07-24T02:24:49+00:00 | Vulnerability · Source |
| CVE-2026-45910 | suse_vex | SUSE CVE CVE-2026-45910 | first fixed: 2 known affected: 394 known not affected: 179 recommended: 298 | 2026-07-24T02:24:40+00:00 | Vulnerability · Source |
| CVE-2026-52962 | suse_vex | SUSE CVE CVE-2026-52962 | first fixed: 68 known affected: 175 known not affected: 23 recommended: 143 | 2026-07-24T02:19:36+00:00 | Vulnerability · Source |
| CVE-2026-54514 | suse_vex | SUSE CVE CVE-2026-54514 | known affected: 11 recommended: 103 | 2026-07-24T02:17:31+00:00 | Vulnerability · Source |
| CVE-2026-54515 | suse_vex | SUSE CVE CVE-2026-54515 | known affected: 11 recommended: 103 | 2026-07-24T02:17:29+00:00 | Vulnerability · Source |
| CVE-2026-56366 | suse_vex | SUSE CVE CVE-2026-56366 | known affected: 269 known not affected: 8 recommended: 15 | 2026-07-24T02:17:00+00:00 | Vulnerability · Source |
| CVE-2026-56367 | suse_vex | SUSE CVE CVE-2026-56367 | known affected: 85 known not affected: 8 recommended: 245 | 2026-07-24T02:16:58+00:00 | Vulnerability · Source |
| CVE-2026-56372 | suse_vex | SUSE CVE CVE-2026-56372 | known affected: 199 known not affected: 78 recommended: 15 | 2026-07-24T02:16:56+00:00 | Vulnerability · Source |
| CVE-2026-56373 | suse_vex | SUSE CVE CVE-2026-56373 | known affected: 85 known not affected: 8 | 2026-07-24T02:16:54+00:00 | Vulnerability · Source |
| CVE-2026-56377 | suse_vex | SUSE CVE CVE-2026-56377 | known affected: 269 known not affected: 8 recommended: 15 | 2026-07-24T02:16:50+00:00 | Vulnerability · Source |
| CVE-2026-59678 | suse_vex | SUSE CVE CVE-2026-59678 | No product status | 2026-07-24T02:16:11+00:00 | Vulnerability · Source |
| CVE-2026-63811 | suse_vex | SUSE CVE CVE-2026-63811 | No product status | 2026-07-24T02:14:19+00:00 | Vulnerability · Source |
| CVE-2026-63814 | suse_vex | SUSE CVE CVE-2026-63814 | No product status | 2026-07-24T02:14:17+00:00 | Vulnerability · Source |
| CVE-2026-63815 | suse_vex | SUSE CVE CVE-2026-63815 | No product status | 2026-07-24T02:14:15+00:00 | Vulnerability · Source |
| CVE-2026-63816 | suse_vex | SUSE CVE CVE-2026-63816 | No product status | 2026-07-24T02:14:13+00:00 | Vulnerability · Source |
| CVE-2026-63833 | suse_vex | SUSE CVE CVE-2026-63833 | No product status | 2026-07-24T02:14:07+00:00 | Vulnerability · Source |
| CVE-2026-63889 | suse_vex | SUSE CVE CVE-2026-63889 | No product status | 2026-07-24T02:12:59+00:00 | Vulnerability · Source |
| CVE-2026-63890 | suse_vex | SUSE CVE CVE-2026-63890 | No product status | 2026-07-24T02:12:56+00:00 | Vulnerability · Source |
| CVE-2026-64122 | suse_vex | SUSE CVE CVE-2026-64122 | No product status | 2026-07-24T02:12:03+00:00 | Vulnerability · Source |
| CVE-2026-64125 | suse_vex | SUSE CVE CVE-2026-64125 | No product status | 2026-07-24T02:12:00+00:00 | Vulnerability · Source |