VEX records
Browse vendor VEX statements available in this Vulnerability-Lookup instance and pivot to the related vulnerability.
294119 VEX records
API response| Vulnerability | Source | Title | Product status | Imported | Links |
|---|---|---|---|---|---|
| CVE-2014-4607 | redhat_vex | lzo: lzo1x_decompress_safe() integer overflow | fixed: 132 known affected: 31 known not affected: 1 under investigation: 20 | 2026-07-20T05:16:05+00:00 | Vulnerability · Source |
| CVE-2026-50012 | redhat_vex | squid: memory corruption in cache_digest reply handling | known affected: 22 | 2026-07-20T03:33:17+00:00 | Vulnerability · Source |
| CVE-2026-62389 | microsoft_vex | ws < 8.21.1 Default maxFragments Allows Memory Exhaustion DoS | known affected: 1 | 2026-07-20T01:40:45+00:00 | Vulnerability · Source |
| CVE-2005-2475 | suse_vex | SUSE CVE CVE-2005-2475 | recommended: 10 | 2026-07-19T18:50:59+00:00 | Vulnerability · Source |
| CVE-2005-3193 | suse_vex | SUSE CVE CVE-2005-3193 | known not affected: 40 recommended: 28 | 2026-07-19T18:50:58+00:00 | Vulnerability · Source |
| CVE-2006-0225 | suse_vex | SUSE CVE CVE-2006-0225 | recommended: 43 | 2026-07-19T18:50:56+00:00 | Vulnerability · Source |
| CVE-2006-1614 | suse_vex | SUSE CVE CVE-2006-1614 | recommended: 19 | 2026-07-19T18:50:54+00:00 | Vulnerability · Source |
| CVE-2006-1940 | suse_vex | SUSE CVE CVE-2006-1940 | recommended: 12 | 2026-07-19T18:50:53+00:00 | Vulnerability · Source |
| CVE-2006-5468 | suse_vex | SUSE CVE CVE-2006-5468 | recommended: 29 | 2026-07-19T18:50:47+00:00 | Vulnerability · Source |
| CVE-2006-5680 | suse_vex | SUSE CVE CVE-2006-5680 | recommended: 20 | 2026-07-19T18:50:46+00:00 | Vulnerability · Source |
| CVE-2007-3738 | suse_vex | SUSE CVE CVE-2007-3738 | known affected: 1 recommended: 32 | 2026-07-19T18:50:31+00:00 | Vulnerability · Source |
| CVE-2007-4986 | suse_vex | SUSE CVE CVE-2007-4986 | recommended: 72 | 2026-07-19T18:50:27+00:00 | Vulnerability · Source |
| CVE-2008-1672 | suse_vex | SUSE CVE CVE-2008-1672 | known not affected: 597 recommended: 64 | 2026-07-19T18:50:14+00:00 | Vulnerability · Source |
| CVE-2008-1945 | suse_vex | SUSE CVE CVE-2008-1945 | recommended: 413 | 2026-07-19T18:50:12+00:00 | Vulnerability · Source |
| CVE-2010-0181 | suse_vex | SUSE CVE CVE-2010-0181 | known affected: 3 recommended: 215 | 2026-07-19T18:49:23+00:00 | Vulnerability · Source |
| CVE-2010-1196 | suse_vex | SUSE CVE CVE-2010-1196 | known affected: 2 recommended: 250 | 2026-07-19T18:49:16+00:00 | Vulnerability · Source |
| CVE-2010-3613 | suse_vex | SUSE CVE CVE-2010-3613 | recommended: 374 | 2026-07-19T18:48:38+00:00 | Vulnerability · Source |
| CVE-2011-4566 | suse_vex | SUSE CVE CVE-2011-4566 | known affected: 1080 known not affected: 1671 recommended: 527 | 2026-07-19T18:48:01+00:00 | Vulnerability · Source |
| CVE-2012-3418 | suse_vex | SUSE CVE CVE-2012-3418 | recommended: 880 | 2026-07-19T18:47:15+00:00 | Vulnerability · Source |
| CVE-2013-1776 | suse_vex | SUSE CVE CVE-2013-1776 | known not affected: 106 recommended: 90 | 2026-07-19T18:45:57+00:00 | Vulnerability · Source |
| CVE-2013-5610 | suse_vex | SUSE CVE CVE-2013-5610 | known affected: 3 known not affected: 14 recommended: 189 | 2026-07-19T18:45:01+00:00 | Vulnerability · Source |
| CVE-2014-0250 | suse_vex | SUSE CVE CVE-2014-0250 | known not affected: 15 recommended: 236 | 2026-07-19T18:44:31+00:00 | Vulnerability · Source |
| CVE-2014-1502 | suse_vex | SUSE CVE CVE-2014-1502 | known affected: 1 recommended: 81 | 2026-07-19T18:44:19+00:00 | Vulnerability · Source |
| CVE-2014-1561 | suse_vex | SUSE CVE CVE-2014-1561 | known not affected: 120 recommended: 41 | 2026-07-19T18:44:14+00:00 | Vulnerability · Source |
| CVE-2014-3423 | suse_vex | SUSE CVE CVE-2014-3423 | known affected: 3 known not affected: 99 recommended: 473 | 2026-07-19T18:43:53+00:00 | Vulnerability · Source |
| CVE-2014-6429 | suse_vex | SUSE CVE CVE-2014-6429 | recommended: 75 | 2026-07-19T18:43:17+00:00 | Vulnerability · Source |
| CVE-2014-8112 | suse_vex | SUSE CVE CVE-2014-8112 | known not affected: 13 recommended: 147 | 2026-07-19T18:43:09+00:00 | Vulnerability · Source |
| CVE-2015-3629 | suse_vex | SUSE CVE CVE-2015-3629 | known affected: 320 known not affected: 147 recommended: 291 | 2026-07-19T18:41:38+00:00 | Vulnerability · Source |
| CVE-2015-5145 | suse_vex | SUSE CVE CVE-2015-5145 | known not affected: 5 recommended: 20 | 2026-07-19T18:41:01+00:00 | Vulnerability · Source |
| CVE-2015-7830 | suse_vex | SUSE CVE CVE-2015-7830 | known affected: 69 recommended: 534 | 2026-07-19T18:40:22+00:00 | Vulnerability · Source |
| CVE-2015-8804 | suse_vex | SUSE CVE CVE-2015-8804 | known affected: 320 recommended: 485 | 2026-07-19T18:40:06+00:00 | Vulnerability · Source |
| CVE-2016-1950 | suse_vex | SUSE CVE CVE-2016-1950 | known affected: 353 known not affected: 183 recommended: 1733 | 2026-07-19T18:39:41+00:00 | Vulnerability · Source |
| CVE-2016-3615 | suse_vex | SUSE CVE CVE-2016-3615 | known affected: 1 known not affected: 37 recommended: 633 | 2026-07-19T18:38:54+00:00 | Vulnerability · Source |
| CVE-2016-3630 | suse_vex | SUSE CVE CVE-2016-3630 | known not affected: 24 recommended: 61 | 2026-07-19T18:38:50+00:00 | Vulnerability · Source |
| CVE-2016-6313 | suse_vex | SUSE CVE CVE-2016-6313 | known affected: 321 known not affected: 10 recommended: 466 | 2026-07-19T18:37:41+00:00 | Vulnerability · Source |
| CVE-2016-10219 | suse_vex | SUSE CVE CVE-2016-10219 | known affected: 1 known not affected: 5 recommended: 260 | 2026-07-19T18:35:41+00:00 | Vulnerability · Source |
| CVE-2017-5458 | suse_vex | SUSE CVE CVE-2017-5458 | known not affected: 42 recommended: 12 | 2026-07-19T18:34:46+00:00 | Vulnerability · Source |
| CVE-2017-5843 | suse_vex | SUSE CVE CVE-2017-5843 | known affected: 13 known not affected: 41 recommended: 588 | 2026-07-19T18:34:30+00:00 | Vulnerability · Source |
| CVE-2017-6437 | suse_vex | SUSE CVE CVE-2017-6437 | recommended: 335 | 2026-07-19T18:34:13+00:00 | Vulnerability · Source |
| CVE-2017-7770 | suse_vex | SUSE CVE CVE-2017-7770 | known affected: 2 known not affected: 42 | 2026-07-19T18:33:27+00:00 | Vulnerability · Source |
| CVE-2017-10196 | suse_vex | SUSE CVE CVE-2017-10196 | known not affected: 42 | 2026-07-19T18:32:45+00:00 | Vulnerability · Source |
| CVE-2017-11185 | suse_vex | SUSE CVE CVE-2017-11185 | known affected: 59 known not affected: 51 recommended: 374 | 2026-07-19T18:32:34+00:00 | Vulnerability · Source |
| CVE-2017-12794 | suse_vex | SUSE CVE CVE-2017-12794 | known not affected: 3 recommended: 21 | 2026-07-19T18:32:11+00:00 | Vulnerability · Source |
| CVE-2017-17521 | suse_vex | SUSE CVE CVE-2017-17521 | known not affected: 33 recommended: 20 | 2026-07-19T18:30:56+00:00 | Vulnerability · Source |
| CVE-2018-0886 | suse_vex | SUSE CVE CVE-2018-0886 | recommended: 221 | 2026-07-19T18:30:35+00:00 | Vulnerability · Source |
| CVE-2018-4096 | suse_vex | SUSE CVE CVE-2018-4096 | known affected: 135 known not affected: 87 recommended: 893 | 2026-07-19T18:30:17+00:00 | Vulnerability · Source |
| CVE-2018-4266 | suse_vex | SUSE CVE CVE-2018-4266 | known affected: 84 known not affected: 82 recommended: 942 | 2026-07-19T18:30:03+00:00 | Vulnerability · Source |
| CVE-2018-5815 | suse_vex | SUSE CVE CVE-2018-5815 | known not affected: 18 recommended: 98 | 2026-07-19T18:29:26+00:00 | Vulnerability · Source |
| CVE-2018-7536 | suse_vex | SUSE CVE CVE-2018-7536 | recommended: 23 | 2026-07-19T18:29:04+00:00 | Vulnerability · Source |
| CVE-2018-7537 | suse_vex | SUSE CVE CVE-2018-7537 | recommended: 23 | 2026-07-19T18:29:03+00:00 | Vulnerability · Source |