VEX records
Browse vendor VEX statements available in this Vulnerability-Lookup instance and pivot to the related vulnerability.
291935 VEX records
API response| Vulnerability | Source | Title | Product status | Imported | Links |
|---|---|---|---|---|---|
| CVE-2026-44185 | suse_vex | SUSE CVE CVE-2026-44185 | known affected: 445 recommended: 205 | 2026-07-28T17:15:54+00:00 | Vulnerability · Source |
| CVE-2026-44432 | suse_vex | SUSE CVE CVE-2026-44432 | known not affected: 134 recommended: 9 | 2026-07-28T17:15:51+00:00 | Vulnerability · Source |
| CVE-2026-45112 | suse_vex | SUSE CVE CVE-2026-45112 | No product status | 2026-07-28T17:15:44+00:00 | Vulnerability · Source |
| CVE-2026-45840 | suse_vex | SUSE CVE CVE-2026-45840 | first fixed: 2 known affected: 586 known not affected: 4 recommended: 335 | 2026-07-28T17:15:38+00:00 | Vulnerability · Source |
| CVE-2026-45841 | suse_vex | SUSE CVE CVE-2026-45841 | first fixed: 2 known affected: 590 recommended: 335 | 2026-07-28T17:15:36+00:00 | Vulnerability · Source |
| CVE-2026-45848 | suse_vex | SUSE CVE CVE-2026-45848 | first fixed: 2 known affected: 555 known not affected: 67 recommended: 292 | 2026-07-28T17:15:34+00:00 | Vulnerability · Source |
| CVE-2026-45862 | suse_vex | SUSE CVE CVE-2026-45862 | first fixed: 2 known affected: 489 known not affected: 133 recommended: 294 | 2026-07-28T17:15:30+00:00 | Vulnerability · Source |
| CVE-2026-45870 | suse_vex | SUSE CVE CVE-2026-45870 | first fixed: 2 known affected: 586 known not affected: 4 recommended: 331 | 2026-07-28T17:15:29+00:00 | Vulnerability · Source |
| CVE-2026-45891 | suse_vex | SUSE CVE CVE-2026-45891 | first fixed: 2 known affected: 529 known not affected: 93 recommended: 265 | 2026-07-28T17:15:27+00:00 | Vulnerability · Source |
| CVE-2026-45912 | suse_vex | SUSE CVE CVE-2026-45912 | first fixed: 2 known affected: 560 known not affected: 30 recommended: 329 | 2026-07-28T17:15:25+00:00 | Vulnerability · Source |
| CVE-2026-45940 | suse_vex | SUSE CVE CVE-2026-45940 | first fixed: 2 known affected: 529 known not affected: 93 recommended: 294 | 2026-07-28T17:15:21+00:00 | Vulnerability · Source |
| CVE-2026-45961 | suse_vex | SUSE CVE CVE-2026-45961 | first fixed: 2 known affected: 529 known not affected: 93 recommended: 294 | 2026-07-28T17:15:19+00:00 | Vulnerability · Source |
| CVE-2026-45964 | suse_vex | SUSE CVE CVE-2026-45964 | first fixed: 2 known affected: 555 known not affected: 67 recommended: 294 | 2026-07-28T17:15:18+00:00 | Vulnerability · Source |
| CVE-2026-45965 | suse_vex | SUSE CVE CVE-2026-45965 | first fixed: 2 known affected: 616 known not affected: 6 recommended: 294 | 2026-07-28T17:15:17+00:00 | Vulnerability · Source |
| CVE-2026-46005 | suse_vex | SUSE CVE CVE-2026-46005 | first fixed: 2 known affected: 441 known not affected: 181 recommended: 298 | 2026-07-28T17:15:12+00:00 | Vulnerability · Source |
| CVE-2026-46024 | suse_vex | SUSE CVE CVE-2026-46024 | first fixed: 2 known affected: 592 recommended: 321 | 2026-07-28T17:15:10+00:00 | Vulnerability · Source |
| CVE-2026-46046 | suse_vex | SUSE CVE CVE-2026-46046 | first fixed: 2 known affected: 529 known not affected: 93 recommended: 269 | 2026-07-28T17:15:06+00:00 | Vulnerability · Source |
| CVE-2026-46050 | suse_vex | SUSE CVE CVE-2026-46050 | first fixed: 2 known affected: 441 known not affected: 181 recommended: 269 | 2026-07-28T17:15:04+00:00 | Vulnerability · Source |
| CVE-2026-46053 | suse_vex | SUSE CVE CVE-2026-46053 | first fixed: 2 known affected: 529 known not affected: 93 recommended: 269 | 2026-07-28T17:15:01+00:00 | Vulnerability · Source |
| CVE-2026-46063 | suse_vex | SUSE CVE CVE-2026-46063 | first fixed: 2 known affected: 441 known not affected: 181 recommended: 269 | 2026-07-28T17:14:59+00:00 | Vulnerability · Source |
| CVE-2026-46065 | suse_vex | SUSE CVE CVE-2026-46065 | first fixed: 2 known affected: 590 recommended: 306 | 2026-07-28T17:14:57+00:00 | Vulnerability · Source |
| CVE-2026-46076 | suse_vex | SUSE CVE CVE-2026-46076 | first fixed: 2 known affected: 411 known not affected: 181 recommended: 327 | 2026-07-28T17:14:55+00:00 | Vulnerability · Source |
| CVE-2026-46079 | suse_vex | SUSE CVE CVE-2026-46079 | first fixed: 2 known affected: 489 known not affected: 133 recommended: 298 | 2026-07-28T17:14:53+00:00 | Vulnerability · Source |
| CVE-2026-46112 | suse_vex | SUSE CVE CVE-2026-46112 | first fixed: 2 known affected: 616 known not affected: 6 recommended: 296 | 2026-07-28T17:14:50+00:00 | Vulnerability · Source |
| CVE-2026-46160 | suse_vex | SUSE CVE CVE-2026-46160 | first fixed: 2 known affected: 590 recommended: 335 | 2026-07-28T17:14:42+00:00 | Vulnerability · Source |
| CVE-2026-46172 | suse_vex | SUSE CVE CVE-2026-46172 | first fixed: 2 known affected: 543 known not affected: 79 recommended: 298 | 2026-07-28T17:14:39+00:00 | Vulnerability · Source |
| CVE-2026-46185 | suse_vex | SUSE CVE CVE-2026-46185 | first fixed: 2 known affected: 529 known not affected: 93 recommended: 296 | 2026-07-28T17:14:35+00:00 | Vulnerability · Source |
| CVE-2026-46214 | suse_vex | SUSE CVE CVE-2026-46214 | first fixed: 2 known affected: 529 known not affected: 93 recommended: 269 | 2026-07-28T17:14:33+00:00 | Vulnerability · Source |
| CVE-2026-46254 | suse_vex | SUSE CVE CVE-2026-46254 | first fixed: 2 known affected: 586 known not affected: 6 recommended: 288 | 2026-07-28T17:14:26+00:00 | Vulnerability · Source |
| CVE-2026-46259 | suse_vex | SUSE CVE CVE-2026-46259 | first fixed: 2 known affected: 590 recommended: 414 | 2026-07-28T17:14:25+00:00 | Vulnerability · Source |
| CVE-2026-46314 | suse_vex | SUSE CVE CVE-2026-46314 | first fixed: 2 known affected: 489 known not affected: 133 recommended: 269 | 2026-07-28T17:14:22+00:00 | Vulnerability · Source |
| CVE-2026-46320 | suse_vex | SUSE CVE CVE-2026-46320 | first fixed: 2 known affected: 454 known not affected: 20 recommended: 484 | 2026-07-28T17:14:21+00:00 | Vulnerability · Source |
| CVE-2026-48144 | suse_vex | SUSE CVE CVE-2026-48144 | No product status | 2026-07-28T17:14:01+00:00 | Vulnerability · Source |
| CVE-2026-49158 | suse_vex | SUSE CVE CVE-2026-49158 | No product status | 2026-07-28T17:13:51+00:00 | Vulnerability · Source |
| CVE-2026-52954 | suse_vex | SUSE CVE CVE-2026-52954 | first fixed: 2 known affected: 569 known not affected: 4 recommended: 302 | 2026-07-28T17:13:32+00:00 | Vulnerability · Source |
| CVE-2026-52955 | suse_vex | SUSE CVE CVE-2026-52955 | first fixed: 2 known affected: 472 recommended: 494 | 2026-07-28T17:13:31+00:00 | Vulnerability · Source |
| CVE-2026-53040 | suse_vex | SUSE CVE CVE-2026-53040 | first fixed: 2 known affected: 569 known not affected: 4 recommended: 302 | 2026-07-28T17:13:21+00:00 | Vulnerability · Source |
| CVE-2026-53041 | suse_vex | SUSE CVE CVE-2026-53041 | first fixed: 2 known affected: 451 known not affected: 4 recommended: 494 | 2026-07-28T17:13:19+00:00 | Vulnerability · Source |
| CVE-2026-53049 | suse_vex | SUSE CVE CVE-2026-53049 | first fixed: 2 known affected: 573 known not affected: 32 recommended: 265 | 2026-07-28T17:13:17+00:00 | Vulnerability · Source |
| CVE-2026-53075 | suse_vex | SUSE CVE CVE-2026-53075 | first fixed: 2 known affected: 590 recommended: 302 | 2026-07-28T17:13:13+00:00 | Vulnerability · Source |
| CVE-2026-53078 | suse_vex | SUSE CVE CVE-2026-53078 | first fixed: 2 known affected: 602 known not affected: 20 recommended: 265 | 2026-07-28T17:13:11+00:00 | Vulnerability · Source |
| CVE-2026-53086 | suse_vex | SUSE CVE CVE-2026-53086 | first fixed: 2 known affected: 618 known not affected: 4 recommended: 265 | 2026-07-28T17:13:09+00:00 | Vulnerability · Source |
| CVE-2026-53090 | suse_vex | SUSE CVE CVE-2026-53090 | first fixed: 2 known affected: 529 known not affected: 93 recommended: 265 | 2026-07-28T17:13:07+00:00 | Vulnerability · Source |
| CVE-2026-53122 | suse_vex | SUSE CVE CVE-2026-53122 | first fixed: 2 known affected: 555 known not affected: 67 recommended: 265 | 2026-07-28T17:13:06+00:00 | Vulnerability · Source |
| CVE-2026-53139 | suse_vex | SUSE CVE CVE-2026-53139 | first fixed: 2 known affected: 555 known not affected: 67 recommended: 265 | 2026-07-28T17:13:01+00:00 | Vulnerability · Source |
| CVE-2026-53168 | suse_vex | SUSE CVE CVE-2026-53168 | first fixed: 2 known affected: 555 known not affected: 67 recommended: 265 | 2026-07-28T17:12:58+00:00 | Vulnerability · Source |
| CVE-2026-53178 | suse_vex | SUSE CVE CVE-2026-53178 | first fixed: 2 known affected: 411 known not affected: 181 recommended: 296 | 2026-07-28T17:12:55+00:00 | Vulnerability · Source |
| CVE-2026-53215 | suse_vex | SUSE CVE CVE-2026-53215 | first fixed: 2 known affected: 529 known not affected: 93 recommended: 265 | 2026-07-28T17:12:52+00:00 | Vulnerability · Source |
| CVE-2026-53216 | suse_vex | SUSE CVE CVE-2026-53216 | first fixed: 2 known affected: 529 known not affected: 93 recommended: 265 | 2026-07-28T17:12:51+00:00 | Vulnerability · Source |
| CVE-2026-53229 | suse_vex | SUSE CVE CVE-2026-53229 | first fixed: 2 known affected: 555 known not affected: 67 recommended: 265 | 2026-07-28T17:12:49+00:00 | Vulnerability · Source |