VEX records
Browse vendor VEX statements available in this Vulnerability-Lookup instance and pivot to the related vulnerability.
304407 VEX records
API response| Vulnerability | Source | Title | Product status | Imported | Links |
|---|---|---|---|---|---|
| CVE-2026-6879 | suse_vex | SUSE CVE CVE-2026-6879 | known affected: 563 recommended: 55 | 2026-10-02T16:54:49+00:00 | Vulnerability · Source |
| CVE-2026-7210 | suse_vex | SUSE CVE CVE-2026-7210 | known affected: 859 recommended: 436 | 2026-10-02T16:54:46+00:00 | Vulnerability · Source |
| CVE-2026-96659 | redhat_vex | foreman: Excessive Permissions for Viewer Role on Preview | fixed: 147 known not affected: 178 | 2026-10-02T16:54:44+00:00 | Vulnerability · Source |
| CVE-2026-7774 | suse_vex | SUSE CVE CVE-2026-7774 | known affected: 856 recommended: 380 | 2026-10-02T16:54:43+00:00 | Vulnerability · Source |
| CVE-2026-96658 | redhat_vex | foreman: Safemode Bypass leading to RCE | fixed: 91 known not affected: 234 | 2026-10-02T16:54:41+00:00 | Vulnerability · Source |
| CVE-2026-8328 | suse_vex | SUSE CVE CVE-2026-8328 | known affected: 746 recommended: 493 | 2026-10-02T16:54:41+00:00 | Vulnerability · Source |
| CVE-2026-8643 | suse_vex | SUSE CVE CVE-2026-8643 | known affected: 983 recommended: 160 | 2026-10-02T16:54:39+00:00 | Vulnerability · Source |
| CVE-2026-8674 | suse_vex | SUSE CVE CVE-2026-8674 | known affected: 500 known not affected: 78 recommended: 48 | 2026-10-02T16:54:36+00:00 | Vulnerability · Source |
| CVE-2026-9669 | suse_vex | SUSE CVE CVE-2026-9669 | known affected: 703 known not affected: 327 recommended: 215 | 2026-10-02T16:54:33+00:00 | Vulnerability · Source |
| CVE-2026-87817 | redhat_vex | GitPython: GitPython: Remote Code Execution via Git directory impersonation | fixed: 52 known affected: 47 known not affected: 816 | 2026-10-02T16:54:32+00:00 | Vulnerability · Source |
| CVE-2026-10118 | suse_vex | SUSE CVE CVE-2026-10118 | recommended: 30 | 2026-10-02T16:54:31+00:00 | Vulnerability · Source |
| CVE-2026-11940 | suse_vex | SUSE CVE CVE-2026-11940 | known affected: 746 known not affected: 107 recommended: 493 | 2026-10-02T16:54:29+00:00 | Vulnerability · Source |
| CVE-2026-11972 | suse_vex | SUSE CVE CVE-2026-11972 | known affected: 802 recommended: 502 | 2026-10-02T16:54:27+00:00 | Vulnerability · Source |
| CVE-2026-59893 | redhat_vex | sqlparse: sqlparse: Denial of Service via inefficient SQL parsing | fixed: 97 known affected: 186 known not affected: 1233 | 2026-10-02T16:54:25+00:00 | Vulnerability · Source |
| CVE-2026-13149 | suse_vex | SUSE CVE CVE-2026-13149 | known affected: 215 known not affected: 318 recommended: 54 | 2026-10-02T16:54:24+00:00 | Vulnerability · Source |
| CVE-2026-13346 | suse_vex | SUSE CVE CVE-2026-13346 | known affected: 1060 known not affected: 38 recommended: 132 | 2026-10-02T16:54:22+00:00 | Vulnerability · Source |
| CVE-2026-15055 | suse_vex | SUSE CVE CVE-2026-15055 | known affected: 32 recommended: 92 | 2026-10-02T16:54:19+00:00 | Vulnerability · Source |
| CVE-2026-15308 | suse_vex | SUSE CVE CVE-2026-15308 | known affected: 766 recommended: 568 | 2026-10-02T16:54:17+00:00 | Vulnerability · Source |
| CVE-2026-15911 | suse_vex | SUSE CVE CVE-2026-15911 | No product status | 2026-10-02T16:54:14+00:00 | Vulnerability · Source |
| CVE-2026-16756 | suse_vex | SUSE CVE CVE-2026-16756 | known affected: 63 known not affected: 33 | 2026-10-02T16:54:09+00:00 | Vulnerability · Source |
| CVE-2026-17507 | suse_vex | SUSE CVE CVE-2026-17507 | known affected: 134 | 2026-10-02T16:54:06+00:00 | Vulnerability · Source |
| CVE-2026-54284 | redhat_vex | sqlparse: sqlparse: Denial of Service via quadratic CPU consumption in SQL parsing | fixed: 103 known affected: 188 known not affected: 5139 | 2026-10-02T16:54:05+00:00 | Vulnerability · Source |
| CVE-2026-17508 | suse_vex | SUSE CVE CVE-2026-17508 | known affected: 134 | 2026-10-02T16:54:04+00:00 | Vulnerability · Source |
| CVE-2026-18036 | suse_vex | SUSE CVE CVE-2026-18036 | known affected: 134 | 2026-10-02T16:54:01+00:00 | Vulnerability · Source |
| CVE-2026-18174 | suse_vex | SUSE CVE CVE-2026-18174 | known affected: 234 known not affected: 204 | 2026-10-02T16:53:58+00:00 | Vulnerability · Source |
| CVE-2026-18374 | suse_vex | SUSE CVE CVE-2026-18374 | known affected: 814 recommended: 220 | 2026-10-02T16:53:56+00:00 | Vulnerability · Source |
| CVE-2026-18503 | suse_vex | SUSE CVE CVE-2026-18503 | known affected: 563 recommended: 55 | 2026-10-02T16:53:54+00:00 | Vulnerability · Source |
| CVE-2026-18917 | suse_vex | SUSE CVE CVE-2026-18917 | known affected: 782 recommended: 980 | 2026-10-02T16:53:51+00:00 | Vulnerability · Source |
| CVE-2026-19499 | suse_vex | SUSE CVE CVE-2026-19499 | known affected: 815 recommended: 170 | 2026-10-02T16:53:48+00:00 | Vulnerability · Source |
| CVE-2026-19542 | suse_vex | SUSE CVE CVE-2026-19542 | known affected: 814 known not affected: 4 recommended: 220 | 2026-10-02T16:53:46+00:00 | Vulnerability · Source |
| CVE-2026-19953 | suse_vex | SUSE CVE CVE-2026-19953 | known affected: 423 recommended: 12 | 2026-10-02T16:53:42+00:00 | Vulnerability · Source |
| CVE-2026-25500 | suse_vex | SUSE CVE CVE-2026-25500 | known affected: 17 known not affected: 86 recommended: 1 | 2026-10-02T16:53:35+00:00 | Vulnerability · Source |
| CVE-2026-33244 | suse_vex | SUSE CVE CVE-2026-33244 | known not affected: 92 recommended: 13 | 2026-10-02T16:53:25+00:00 | Vulnerability · Source |
| CVE-2026-33814 | suse_vex | SUSE CVE CVE-2026-33814 | known affected: 954 known not affected: 177 recommended: 1182 | 2026-10-02T16:53:23+00:00 | Vulnerability · Source |
| CVE-2026-33818 | suse_vex | SUSE CVE CVE-2026-33818 | known affected: 12 known not affected: 139 recommended: 379 | 2026-10-02T16:53:21+00:00 | Vulnerability · Source |
| CVE-2026-33845 | suse_vex | SUSE CVE CVE-2026-33845 | known affected: 493 recommended: 245 | 2026-10-02T16:53:19+00:00 | Vulnerability · Source |
| CVE-2026-33846 | suse_vex | SUSE CVE CVE-2026-33846 | known affected: 493 recommended: 245 | 2026-10-02T16:53:17+00:00 | Vulnerability · Source |
| CVE-2026-35191 | suse_vex | SUSE CVE CVE-2026-35191 | known affected: 40 known not affected: 553 recommended: 24 | 2026-10-02T16:53:13+00:00 | Vulnerability · Source |
| CVE-2026-39821 | suse_vex | SUSE CVE CVE-2026-39821 | known affected: 1129 known not affected: 665 recommended: 1349 | 2026-10-02T16:53:10+00:00 | Vulnerability · Source |
| CVE-2026-40034 | suse_vex | SUSE CVE CVE-2026-40034 | known affected: 110 known not affected: 124 recommended: 14 | 2026-10-02T16:53:07+00:00 | Vulnerability · Source |
| CVE-2026-40510 | suse_vex | SUSE CVE CVE-2026-40510 | known affected: 33 recommended: 18 | 2026-10-02T16:53:05+00:00 | Vulnerability · Source |
| CVE-2026-42009 | suse_vex | SUSE CVE CVE-2026-42009 | known affected: 493 recommended: 245 | 2026-10-02T16:52:53+00:00 | Vulnerability · Source |
| CVE-2026-42011 | suse_vex | SUSE CVE CVE-2026-42011 | known affected: 529 recommended: 236 | 2026-10-02T16:52:50+00:00 | Vulnerability · Source |
| CVE-2026-42012 | suse_vex | SUSE CVE CVE-2026-42012 | known affected: 477 known not affected: 45 recommended: 219 | 2026-10-02T16:52:49+00:00 | Vulnerability · Source |
| CVE-2026-42013 | suse_vex | SUSE CVE CVE-2026-42013 | known affected: 529 recommended: 236 | 2026-10-02T16:52:47+00:00 | Vulnerability · Source |
| CVE-2026-42014 | suse_vex | SUSE CVE CVE-2026-42014 | known affected: 529 recommended: 236 | 2026-10-02T16:52:45+00:00 | Vulnerability · Source |
| CVE-2026-42015 | suse_vex | SUSE CVE CVE-2026-42015 | known affected: 529 recommended: 236 | 2026-10-02T16:52:43+00:00 | Vulnerability · Source |
| CVE-2026-42258 | suse_vex | SUSE CVE CVE-2026-42258 | known affected: 278 known not affected: 104 recommended: 139 | 2026-10-02T16:52:40+00:00 | Vulnerability · Source |
| CVE-2026-42356 | suse_vex | SUSE CVE CVE-2026-42356 | known affected: 183 | 2026-10-02T16:52:37+00:00 | Vulnerability · Source |
| CVE-2026-42504 | suse_vex | SUSE CVE CVE-2026-42504 | known affected: 24 known not affected: 93 recommended: 278 | 2026-10-02T16:52:35+00:00 | Vulnerability · Source |