VEX records
Browse vendor VEX statements available in this Vulnerability-Lookup instance and pivot to the related vulnerability.
291734 VEX records
API response| Vulnerability | Source | Title | Product status | Imported | Links |
|---|---|---|---|---|---|
| CVE-2022-50650 | redhat_vex | kernel: bpf: Fix reference state management for synchronous callbacks | known affected: 156 known not affected: 118 | 2026-08-05T03:20:46+00:00 | Vulnerability · Source |
| CVE-2023-41056 | redhat_vex | redis: Heap Buffer Overflow may lead to potential remote code execution | fixed: 18 known affected: 2 known not affected: 12 | 2026-08-05T03:20:43+00:00 | Vulnerability · Source |
| CVE-2022-23773 | redhat_vex | golang: cmd/go: misinterpretation of branch names can lead to incorrect access control | fixed: 855 known affected: 148 known not affected: 1049 | 2026-08-05T02:57:13+00:00 | Vulnerability · Source |
| CVE-2020-28362 | redhat_vex | golang: math/big: panic during recursive division of very large numbers | fixed: 807 known affected: 216 known not affected: 1585 | 2026-08-05T02:33:09+00:00 | Vulnerability · Source |
| CVE-2020-27813 | redhat_vex | golang-github-gorilla-websocket: integer overflow leads to denial of service | fixed: 19 known affected: 31 known not affected: 533 | 2026-08-05T02:32:59+00:00 | Vulnerability · Source |
| CVE-2005-3623 | suse_vex | SUSE CVE CVE-2005-3623 | known not affected: 372 | 2026-08-05T01:35:27+00:00 | Vulnerability · Source |
| CVE-2006-1017 | suse_vex | SUSE CVE CVE-2006-1017 | known affected: 2110 recommended: 201 | 2026-08-05T01:35:25+00:00 | Vulnerability · Source |
| CVE-2006-6106 | suse_vex | SUSE CVE CVE-2006-6106 | known not affected: 409 | 2026-08-05T01:35:23+00:00 | Vulnerability · Source |
| CVE-2007-0956 | suse_vex | SUSE CVE CVE-2007-0956 | recommended: 75 | 2026-08-05T01:35:21+00:00 | Vulnerability · Source |
| CVE-2007-2446 | suse_vex | SUSE CVE CVE-2007-2446 | recommended: 297 | 2026-08-05T01:35:19+00:00 | Vulnerability · Source |
| CVE-2008-1669 | suse_vex | SUSE CVE CVE-2008-1669 | known not affected: 116 recommended: 76 | 2026-08-05T01:35:14+00:00 | Vulnerability · Source |
| CVE-2008-1675 | suse_vex | SUSE CVE CVE-2008-1675 | known affected: 30 known not affected: 43 recommended: 76 | 2026-08-05T01:35:13+00:00 | Vulnerability · Source |
| CVE-2008-1948 | suse_vex | SUSE CVE CVE-2008-1948 | recommended: 55 | 2026-08-05T01:35:11+00:00 | Vulnerability · Source |
| CVE-2008-3142 | suse_vex | SUSE CVE CVE-2008-3142 | known not affected: 129 recommended: 403 | 2026-08-05T01:35:09+00:00 | Vulnerability · Source |
| CVE-2008-3833 | suse_vex | SUSE CVE CVE-2008-3833 | known not affected: 372 | 2026-08-05T01:35:07+00:00 | Vulnerability · Source |
| CVE-2008-4064 | suse_vex | SUSE CVE CVE-2008-4064 | known affected: 1 recommended: 28 | 2026-08-05T01:35:05+00:00 | Vulnerability · Source |
| CVE-2008-4936 | suse_vex | SUSE CVE CVE-2008-4936 | known not affected: 42 recommended: 17 | 2026-08-05T01:35:03+00:00 | Vulnerability · Source |
| CVE-2008-5300 | suse_vex | SUSE CVE CVE-2008-5300 | known affected: 30 known not affected: 43 recommended: 76 | 2026-08-05T01:35:02+00:00 | Vulnerability · Source |
| CVE-2009-0023 | suse_vex | SUSE CVE CVE-2009-0023 | recommended: 366 | 2026-08-05T01:35:00+00:00 | Vulnerability · Source |
| CVE-2009-0036 | suse_vex | SUSE CVE CVE-2009-0036 | known not affected: 213 | 2026-08-05T01:34:58+00:00 | Vulnerability · Source |
| CVE-2009-0316 | suse_vex | SUSE CVE CVE-2009-0316 | known affected: 320 recommended: 480 | 2026-08-05T01:34:56+00:00 | Vulnerability · Source |
| CVE-2009-0771 | suse_vex | SUSE CVE CVE-2009-0771 | known affected: 1 recommended: 234 | 2026-08-05T01:34:53+00:00 | Vulnerability · Source |
| CVE-2009-1298 | suse_vex | SUSE CVE CVE-2009-1298 | known not affected: 409 | 2026-08-05T01:34:51+00:00 | Vulnerability · Source |
| CVE-2009-2406 | suse_vex | SUSE CVE CVE-2009-2406 | known not affected: 495 recommended: 42 | 2026-08-05T01:34:47+00:00 | Vulnerability · Source |
| CVE-2009-3700 | suse_vex | SUSE CVE CVE-2009-3700 | recommended: 36 | 2026-08-05T01:34:44+00:00 | Vulnerability · Source |
| CVE-2009-3894 | suse_vex | SUSE CVE CVE-2009-3894 | known not affected: 12 recommended: 67 | 2026-08-05T01:34:41+00:00 | Vulnerability · Source |
| CVE-2010-0411 | suse_vex | SUSE CVE CVE-2010-0411 | recommended: 133 | 2026-08-05T01:34:35+00:00 | Vulnerability · Source |
| CVE-2010-0926 | suse_vex | SUSE CVE CVE-2010-0926 | known affected: 6 recommended: 1718 | 2026-08-05T01:34:33+00:00 | Vulnerability · Source |
| CVE-2010-1323 | suse_vex | SUSE CVE CVE-2010-1323 | recommended: 276 | 2026-08-05T01:34:31+00:00 | Vulnerability · Source |
| CVE-2010-2226 | suse_vex | SUSE CVE CVE-2010-2226 | known not affected: 495 recommended: 11 | 2026-08-05T01:34:29+00:00 | Vulnerability · Source |
| CVE-2010-3081 | suse_vex | SUSE CVE CVE-2010-3081 | known not affected: 489 recommended: 419 | 2026-08-05T01:34:24+00:00 | Vulnerability · Source |
| CVE-2010-3301 | suse_vex | SUSE CVE CVE-2010-3301 | known not affected: 393 recommended: 419 | 2026-08-05T01:34:19+00:00 | Vulnerability · Source |
| CVE-2010-3875 | suse_vex | SUSE CVE CVE-2010-3875 | known not affected: 458 recommended: 89 | 2026-08-05T01:34:17+00:00 | Vulnerability · Source |
| CVE-2010-4242 | suse_vex | SUSE CVE CVE-2010-4242 | known not affected: 409 recommended: 17 | 2026-08-05T01:34:14+00:00 | Vulnerability · Source |
| CVE-2010-4249 | suse_vex | SUSE CVE CVE-2010-4249 | known not affected: 495 | 2026-08-05T01:34:13+00:00 | Vulnerability · Source |
| CVE-2010-4538 | suse_vex | SUSE CVE CVE-2010-4538 | recommended: 149 | 2026-08-05T01:34:11+00:00 | Vulnerability · Source |
| CVE-2010-4655 | suse_vex | SUSE CVE CVE-2010-4655 | recommended: 17 | 2026-08-05T01:34:09+00:00 | Vulnerability · Source |
| CVE-2010-4777 | suse_vex | SUSE CVE CVE-2010-4777 | recommended: 176 | 2026-08-05T01:34:06+00:00 | Vulnerability · Source |
| CVE-2011-0191 | suse_vex | SUSE CVE CVE-2011-0191 | recommended: 54 | 2026-08-05T01:34:02+00:00 | Vulnerability · Source |
| CVE-2011-0463 | suse_vex | SUSE CVE CVE-2011-0463 | known not affected: 495 | 2026-08-05T01:34:00+00:00 | Vulnerability · Source |
| CVE-2011-0524 | suse_vex | SUSE CVE CVE-2011-0524 | recommended: 155 | 2026-08-05T01:33:58+00:00 | Vulnerability · Source |
| CVE-2011-0905 | suse_vex | SUSE CVE CVE-2011-0905 | recommended: 70 | 2026-08-05T01:33:56+00:00 | Vulnerability · Source |
| CVE-2011-1143 | suse_vex | SUSE CVE CVE-2011-1143 | recommended: 149 | 2026-08-05T01:33:54+00:00 | Vulnerability · Source |
| CVE-2011-1146 | suse_vex | SUSE CVE CVE-2011-1146 | known affected: 1 recommended: 807 | 2026-08-05T01:33:52+00:00 | Vulnerability · Source |
| CVE-2011-1155 | suse_vex | SUSE CVE CVE-2011-1155 | known affected: 320 recommended: 139 | 2026-08-05T01:33:49+00:00 | Vulnerability · Source |
| CVE-2011-1476 | suse_vex | SUSE CVE CVE-2011-1476 | known affected: 3 known not affected: 218 recommended: 31 | 2026-08-05T01:33:48+00:00 | Vulnerability · Source |
| CVE-2011-1490 | suse_vex | SUSE CVE CVE-2011-1490 | known affected: 22 known not affected: 264 | 2026-08-05T01:33:47+00:00 | Vulnerability · Source |
| CVE-2011-1493 | suse_vex | SUSE CVE CVE-2011-1493 | known not affected: 387 | 2026-08-05T01:33:46+00:00 | Vulnerability · Source |
| CVE-2011-1526 | suse_vex | SUSE CVE CVE-2011-1526 | known not affected: 62 recommended: 71 | 2026-08-05T01:33:44+00:00 | Vulnerability · Source |
| CVE-2011-1529 | suse_vex | SUSE CVE CVE-2011-1529 | recommended: 220 | 2026-08-05T01:33:41+00:00 | Vulnerability · Source |