VEX records
Browse vendor VEX statements available in this Vulnerability-Lookup instance and pivot to the related vulnerability.
286687 VEX records
API response| Vulnerability | Source | Title | Product status | Imported | Links |
|---|---|---|---|---|---|
| CVE-2026-45090 | suse_vex | SUSE CVE CVE-2026-45090 | No product status | 2026-07-30T16:47:48+00:00 | Vulnerability · Source |
| CVE-2026-45147 | suse_vex | SUSE CVE CVE-2026-45147 | No product status | 2026-07-30T16:47:46+00:00 | Vulnerability · Source |
| CVE-2026-45148 | suse_vex | SUSE CVE CVE-2026-45148 | No product status | 2026-07-30T16:47:44+00:00 | Vulnerability · Source |
| CVE-2026-45152 | suse_vex | SUSE CVE CVE-2026-45152 | No product status | 2026-07-30T16:47:42+00:00 | Vulnerability · Source |
| CVE-2026-45224 | suse_vex | SUSE CVE CVE-2026-45224 | No product status | 2026-07-30T16:47:40+00:00 | Vulnerability · Source |
| CVE-2026-45287 | suse_vex | SUSE CVE CVE-2026-45287 | No product status | 2026-07-30T16:47:38+00:00 | Vulnerability · Source |
| CVE-2026-45298 | suse_vex | SUSE CVE CVE-2026-45298 | No product status | 2026-07-30T16:47:36+00:00 | Vulnerability · Source |
| CVE-2026-45327 | suse_vex | SUSE CVE CVE-2026-45327 | No product status | 2026-07-30T16:47:34+00:00 | Vulnerability · Source |
| CVE-2026-45371 | suse_vex | SUSE CVE CVE-2026-45371 | No product status | 2026-07-30T16:47:32+00:00 | Vulnerability · Source |
| CVE-2026-45375 | suse_vex | SUSE CVE CVE-2026-45375 | No product status | 2026-07-30T16:47:30+00:00 | Vulnerability · Source |
| CVE-2026-45491 | suse_vex | SUSE CVE CVE-2026-45491 | recommended: 121 | 2026-07-30T16:47:26+00:00 | Vulnerability · Source |
| CVE-2026-45576 | suse_vex | SUSE CVE CVE-2026-45576 | No product status | 2026-07-30T16:47:24+00:00 | Vulnerability · Source |
| CVE-2026-45591 | suse_vex | SUSE CVE CVE-2026-45591 | recommended: 121 | 2026-07-30T16:47:22+00:00 | Vulnerability · Source |
| CVE-2026-45625 | suse_vex | SUSE CVE CVE-2026-45625 | No product status | 2026-07-30T16:47:19+00:00 | Vulnerability · Source |
| CVE-2026-45626 | suse_vex | SUSE CVE CVE-2026-45626 | No product status | 2026-07-30T16:47:17+00:00 | Vulnerability · Source |
| CVE-2026-45627 | suse_vex | SUSE CVE CVE-2026-45627 | No product status | 2026-07-30T16:47:15+00:00 | Vulnerability · Source |
| CVE-2026-45692 | suse_vex | SUSE CVE CVE-2026-45692 | known not affected: 245 | 2026-07-30T16:47:12+00:00 | Vulnerability · Source |
| CVE-2026-45709 | suse_vex | SUSE CVE CVE-2026-45709 | No product status | 2026-07-30T16:47:11+00:00 | Vulnerability · Source |
| CVE-2026-45712 | suse_vex | SUSE CVE CVE-2026-45712 | No product status | 2026-07-30T16:47:08+00:00 | Vulnerability · Source |
| CVE-2026-45713 | suse_vex | SUSE CVE CVE-2026-45713 | No product status | 2026-07-30T16:47:07+00:00 | Vulnerability · Source |
| CVE-2026-45721 | suse_vex | SUSE CVE CVE-2026-45721 | No product status | 2026-07-30T16:47:04+00:00 | Vulnerability · Source |
| CVE-2026-45728 | suse_vex | SUSE CVE CVE-2026-45728 | No product status | 2026-07-30T16:47:00+00:00 | Vulnerability · Source |
| CVE-2026-45737 | suse_vex | SUSE CVE CVE-2026-45737 | No product status | 2026-07-30T16:46:58+00:00 | Vulnerability · Source |
| CVE-2026-45738 | suse_vex | SUSE CVE CVE-2026-45738 | No product status | 2026-07-30T16:46:56+00:00 | Vulnerability · Source |
| CVE-2026-45760 | suse_vex | SUSE CVE CVE-2026-45760 | No product status | 2026-07-30T16:46:53+00:00 | Vulnerability · Source |
| CVE-2026-45781 | suse_vex | SUSE CVE CVE-2026-45781 | No product status | 2026-07-30T16:46:52+00:00 | Vulnerability · Source |
| CVE-2026-45796 | suse_vex | SUSE CVE CVE-2026-45796 | No product status | 2026-07-30T16:46:49+00:00 | Vulnerability · Source |
| CVE-2026-45837 | suse_vex | SUSE CVE CVE-2026-45837 | first fixed: 2 known not affected: 278 recommended: 149 | 2026-07-30T16:46:48+00:00 | Vulnerability · Source |
| CVE-2026-45882 | suse_vex | SUSE CVE CVE-2026-45882 | known not affected: 293 | 2026-07-30T16:46:44+00:00 | Vulnerability · Source |
| CVE-2026-45899 | suse_vex | SUSE CVE CVE-2026-45899 | first fixed: 2 known affected: 424 known not affected: 181 recommended: 265 | 2026-07-30T16:46:41+00:00 | Vulnerability · Source |
| CVE-2026-45917 | suse_vex | SUSE CVE CVE-2026-45917 | known affected: 295 | 2026-07-30T16:46:39+00:00 | Vulnerability · Source |
| CVE-2026-45949 | suse_vex | SUSE CVE CVE-2026-45949 | known affected: 291 known not affected: 4 | 2026-07-30T16:46:35+00:00 | Vulnerability · Source |
| CVE-2026-46119 | suse_vex | SUSE CVE CVE-2026-46119 | first fixed: 2 known affected: 512 known not affected: 93 recommended: 298 | 2026-07-30T16:46:16+00:00 | Vulnerability · Source |
| CVE-2026-46152 | suse_vex | SUSE CVE CVE-2026-46152 | known affected: 424 known not affected: 208 recommended: 205 | 2026-07-30T16:46:13+00:00 | Vulnerability · Source |
| CVE-2026-46189 | suse_vex | SUSE CVE CVE-2026-46189 | known affected: 289 known not affected: 6 recommended: 46 | 2026-07-30T16:46:07+00:00 | Vulnerability · Source |
| CVE-2026-46300 | suse_vex | SUSE CVE CVE-2026-46300 | first fixed: 2 known affected: 421 known not affected: 4 recommended: 836 | 2026-07-30T16:45:59+00:00 | Vulnerability · Source |
| CVE-2026-46316 | suse_vex | SUSE CVE CVE-2026-46316 | first fixed: 2 known affected: 411 known not affected: 278 recommended: 259 | 2026-07-30T16:45:57+00:00 | Vulnerability · Source |
| CVE-2026-46317 | suse_vex | SUSE CVE CVE-2026-46317 | first fixed: 2 known affected: 394 known not affected: 278 recommended: 176 | 2026-07-30T16:45:55+00:00 | Vulnerability · Source |
| CVE-2026-46323 | suse_vex | SUSE CVE CVE-2026-46323 | known not affected: 293 recommended: 284 | 2026-07-30T16:45:52+00:00 | Vulnerability · Source |
| CVE-2026-46354 | suse_vex | SUSE CVE CVE-2026-46354 | No product status | 2026-07-30T16:45:49+00:00 | Vulnerability · Source |
| CVE-2026-46356 | suse_vex | SUSE CVE CVE-2026-46356 | No product status | 2026-07-30T16:45:48+00:00 | Vulnerability · Source |
| CVE-2026-46377 | suse_vex | SUSE CVE CVE-2026-46377 | No product status | 2026-07-30T16:45:44+00:00 | Vulnerability · Source |
| CVE-2026-46378 | suse_vex | SUSE CVE CVE-2026-46378 | No product status | 2026-07-30T16:45:42+00:00 | Vulnerability · Source |
| CVE-2026-46403 | suse_vex | SUSE CVE CVE-2026-46403 | No product status | 2026-07-30T16:45:41+00:00 | Vulnerability · Source |
| CVE-2026-46410 | suse_vex | SUSE CVE CVE-2026-46410 | No product status | 2026-07-30T16:45:39+00:00 | Vulnerability · Source |
| CVE-2026-46415 | suse_vex | SUSE CVE CVE-2026-46415 | No product status | 2026-07-30T16:45:37+00:00 | Vulnerability · Source |
| CVE-2026-46430 | suse_vex | SUSE CVE CVE-2026-46430 | No product status | 2026-07-30T16:45:35+00:00 | Vulnerability · Source |
| CVE-2026-46431 | suse_vex | SUSE CVE CVE-2026-46431 | No product status | 2026-07-30T16:45:34+00:00 | Vulnerability · Source |
| CVE-2026-46599 | suse_vex | SUSE CVE CVE-2026-46599 | No product status | 2026-07-30T16:45:30+00:00 | Vulnerability · Source |
| CVE-2026-46602 | suse_vex | SUSE CVE CVE-2026-46602 | No product status | 2026-07-30T16:45:28+00:00 | Vulnerability · Source |