VEX records
Browse vendor VEX statements available in this Vulnerability-Lookup instance and pivot to the related vulnerability.
282994 VEX records
API response| Vulnerability | Source | Title | Product status | Imported | Links |
|---|---|---|---|---|---|
| CVE-2015-8783 | suse_vex | SUSE CVE CVE-2015-8783 | known not affected: 256 recommended: 289 | 2026-07-19T18:40:09+00:00 | Vulnerability · Source |
| CVE-2015-8803 | suse_vex | SUSE CVE CVE-2015-8803 | recommended: 411 | 2026-07-19T18:40:07+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-2015-9261 | suse_vex | SUSE CVE CVE-2015-9261 | known affected: 1 known not affected: 5 recommended: 132 | 2026-07-19T18:40:04+00:00 | Vulnerability · Source |
| CVE-2016-0606 | suse_vex | SUSE CVE CVE-2016-0606 | known affected: 1 known not affected: 157 recommended: 654 | 2026-07-19T18:40:03+00:00 | Vulnerability · Source |
| CVE-2016-0609 | suse_vex | SUSE CVE CVE-2016-0609 | known not affected: 114 recommended: 664 | 2026-07-19T18:40:01+00:00 | Vulnerability · Source |
| CVE-2016-0649 | suse_vex | SUSE CVE CVE-2016-0649 | known not affected: 114 recommended: 632 | 2026-07-19T18:40:00+00:00 | Vulnerability · Source |
| CVE-2016-0705 | suse_vex | SUSE CVE CVE-2016-0705 | known affected: 321 known not affected: 297 recommended: 1289 | 2026-07-19T18:39:58+00:00 | Vulnerability · Source |
| CVE-2016-0797 | suse_vex | SUSE CVE CVE-2016-0797 | known affected: 321 known not affected: 211 recommended: 1039 | 2026-07-19T18:39:56+00:00 | Vulnerability · Source |
| CVE-2016-0800 | suse_vex | SUSE CVE CVE-2016-0800 | known affected: 321 known not affected: 267 recommended: 1041 | 2026-07-19T18:39:55+00:00 | Vulnerability · Source |
| CVE-2016-1234 | suse_vex | SUSE CVE CVE-2016-1234 | known affected: 321 known not affected: 97 recommended: 1294 | 2026-07-19T18:39:53+00:00 | Vulnerability · Source |
| CVE-2016-1283 | suse_vex | SUSE CVE CVE-2016-1283 | known affected: 320 known not affected: 172 recommended: 729 | 2026-07-19T18:39:52+00:00 | Vulnerability · Source |
| CVE-2016-1285 | suse_vex | SUSE CVE CVE-2016-1285 | known affected: 452 recommended: 966 | 2026-07-19T18:39:51+00:00 | Vulnerability · Source |
| CVE-2016-1286 | suse_vex | SUSE CVE CVE-2016-1286 | known affected: 452 recommended: 966 | 2026-07-19T18:39:49+00:00 | Vulnerability · Source |
| CVE-2016-1521 | suse_vex | SUSE CVE CVE-2016-1521 | known affected: 395 recommended: 243 | 2026-07-19T18:39:48+00:00 | Vulnerability · Source |
| CVE-2016-1834 | suse_vex | SUSE CVE CVE-2016-1834 | known affected: 1 known not affected: 83 recommended: 507 | 2026-07-19T18:39:46+00:00 | Vulnerability · Source |
| CVE-2016-1857 | suse_vex | SUSE CVE CVE-2016-1857 | known not affected: 130 recommended: 912 | 2026-07-19T18:39:45+00:00 | Vulnerability · Source |
| CVE-2016-1930 | suse_vex | SUSE CVE CVE-2016-1930 | known affected: 1 recommended: 602 | 2026-07-19T18:39:44+00:00 | Vulnerability · Source |
| CVE-2016-1946 | suse_vex | SUSE CVE CVE-2016-1946 | known affected: 21 recommended: 246 | 2026-07-19T18:39:42+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-1957 | suse_vex | SUSE CVE CVE-2016-1957 | known affected: 2 recommended: 604 | 2026-07-19T18:39:40+00:00 | Vulnerability · Source |
| CVE-2016-1966 | suse_vex | SUSE CVE CVE-2016-1966 | known affected: 2 recommended: 599 | 2026-07-19T18:39:38+00:00 | Vulnerability · Source |
| CVE-2016-1967 | suse_vex | SUSE CVE CVE-2016-1967 | known affected: 33 known not affected: 183 recommended: 250 | 2026-07-19T18:39:37+00:00 | Vulnerability · Source |
| CVE-2016-2037 | suse_vex | SUSE CVE CVE-2016-2037 | known affected: 345 recommended: 329 | 2026-07-19T18:39:36+00:00 | Vulnerability · Source |
| CVE-2016-2089 | suse_vex | SUSE CVE CVE-2016-2089 | known affected: 1 recommended: 196 | 2026-07-19T18:39:35+00:00 | Vulnerability · Source |
| CVE-2016-2109 | suse_vex | SUSE CVE CVE-2016-2109 | known affected: 350 known not affected: 275 recommended: 1042 | 2026-07-19T18:39:33+00:00 | Vulnerability · Source |
| CVE-2016-2118 | suse_vex | SUSE CVE CVE-2016-2118 | known affected: 321 known not affected: 46 recommended: 4181 | 2026-07-19T18:39:31+00:00 | Vulnerability · Source |
| CVE-2016-2125 | suse_vex | SUSE CVE CVE-2016-2125 | known affected: 366 known not affected: 1233 recommended: 4030 | 2026-07-19T18:39:29+00:00 | Vulnerability · Source |
| CVE-2016-2179 | suse_vex | SUSE CVE CVE-2016-2179 | known affected: 325 known not affected: 277 recommended: 1032 | 2026-07-19T18:39:27+00:00 | Vulnerability · Source |
| CVE-2016-2315 | suse_vex | SUSE CVE CVE-2016-2315 | known affected: 103 recommended: 976 | 2026-07-19T18:39:26+00:00 | Vulnerability · Source |
| CVE-2016-2464 | suse_vex | SUSE CVE CVE-2016-2464 | known not affected: 42 recommended: 146 | 2026-07-19T18:39:24+00:00 | Vulnerability · Source |
| CVE-2016-2523 | suse_vex | SUSE CVE CVE-2016-2523 | known affected: 3 recommended: 526 | 2026-07-19T18:39:23+00:00 | Vulnerability · Source |
| CVE-2016-2532 | suse_vex | SUSE CVE CVE-2016-2532 | known affected: 3 recommended: 526 | 2026-07-19T18:39:22+00:00 | Vulnerability · Source |
| CVE-2016-2570 | suse_vex | SUSE CVE CVE-2016-2570 | known affected: 3 known not affected: 30 recommended: 45 | 2026-07-19T18:39:21+00:00 | Vulnerability · Source |
| CVE-2016-2791 | suse_vex | SUSE CVE CVE-2016-2791 | known affected: 2 recommended: 600 | 2026-07-19T18:39:19+00:00 | Vulnerability · Source |
| CVE-2016-2795 | suse_vex | SUSE CVE CVE-2016-2795 | known affected: 2 recommended: 600 | 2026-07-19T18:39:18+00:00 | Vulnerability · Source |
| CVE-2016-2796 | suse_vex | SUSE CVE CVE-2016-2796 | known affected: 2 recommended: 604 | 2026-07-19T18:39:17+00:00 | Vulnerability · Source |
| CVE-2016-2797 | suse_vex | SUSE CVE CVE-2016-2797 | known affected: 2 recommended: 600 | 2026-07-19T18:39:15+00:00 | Vulnerability · Source |
| CVE-2016-2800 | suse_vex | SUSE CVE CVE-2016-2800 | known affected: 2 recommended: 604 | 2026-07-19T18:39:14+00:00 | Vulnerability · Source |
| CVE-2016-2801 | suse_vex | SUSE CVE CVE-2016-2801 | known affected: 2 recommended: 600 | 2026-07-19T18:39:13+00:00 | Vulnerability · Source |
| CVE-2016-2804 | suse_vex | SUSE CVE CVE-2016-2804 | known affected: 1 known not affected: 38 recommended: 250 | 2026-07-19T18:39:12+00:00 | Vulnerability · Source |
| CVE-2016-2806 | suse_vex | SUSE CVE CVE-2016-2806 | known affected: 1 known not affected: 38 recommended: 333 | 2026-07-19T18:39:10+00:00 | Vulnerability · Source |
| CVE-2016-2815 | suse_vex | SUSE CVE CVE-2016-2815 | known affected: 2 recommended: 661 | 2026-07-19T18:39:09+00:00 | Vulnerability · Source |
| CVE-2016-2816 | suse_vex | SUSE CVE CVE-2016-2816 | known affected: 1 known not affected: 38 recommended: 250 | 2026-07-19T18:39:08+00:00 | Vulnerability · Source |
| CVE-2016-2818 | suse_vex | SUSE CVE CVE-2016-2818 | known affected: 2 recommended: 659 | 2026-07-19T18:39:07+00:00 | Vulnerability · Source |
| CVE-2016-2821 | suse_vex | SUSE CVE CVE-2016-2821 | known affected: 2 recommended: 576 | 2026-07-19T18:39:05+00:00 | Vulnerability · Source |
| CVE-2016-2822 | suse_vex | SUSE CVE CVE-2016-2822 | known affected: 2 recommended: 576 | 2026-07-19T18:39:04+00:00 | Vulnerability · Source |
| CVE-2016-2824 | suse_vex | SUSE CVE CVE-2016-2824 | known affected: 2 recommended: 575 | 2026-07-19T18:39:03+00:00 | Vulnerability · Source |
| CVE-2016-2825 | suse_vex | SUSE CVE CVE-2016-2825 | known affected: 1 known not affected: 37 recommended: 250 | 2026-07-19T18:39:02+00:00 | Vulnerability · Source |
| CVE-2016-2828 | suse_vex | SUSE CVE CVE-2016-2828 | known affected: 2 recommended: 576 | 2026-07-19T18:39:00+00:00 | Vulnerability · Source |