VEX records
Browse vendor VEX statements available in this Vulnerability-Lookup instance and pivot to the related vulnerability.
293999 VEX records
API response| Vulnerability | Source | Title | Product status | Imported | Links |
|---|---|---|---|---|---|
| CVE-2016-0502 | suse_vex | SUSE CVE CVE-2016-0502 | known affected: 2 known not affected: 176 recommended: 70 | 2026-07-26T01:07:32+00:00 | Vulnerability · Source |
| CVE-2016-0504 | suse_vex | SUSE CVE CVE-2016-0504 | known affected: 1 known not affected: 176 recommended: 10 | 2026-07-26T01:07:29+00:00 | Vulnerability · Source |
| CVE-2016-0505 | suse_vex | SUSE CVE CVE-2016-0505 | known not affected: 121 recommended: 708 | 2026-07-26T01:07:27+00:00 | Vulnerability · Source |
| CVE-2016-0595 | suse_vex | SUSE CVE CVE-2016-0595 | known affected: 2 known not affected: 176 recommended: 10 | 2026-07-26T01:07:25+00:00 | Vulnerability · Source |
| CVE-2016-0643 | suse_vex | SUSE CVE CVE-2016-0643 | known not affected: 121 recommended: 293 | 2026-07-26T01:07:00+00:00 | Vulnerability · Source |
| CVE-2016-0644 | suse_vex | SUSE CVE CVE-2016-0644 | known not affected: 121 recommended: 666 | 2026-07-26T01:06:58+00:00 | Vulnerability · Source |
| CVE-2016-0648 | suse_vex | SUSE CVE CVE-2016-0648 | known not affected: 121 recommended: 293 | 2026-07-26T01:06:52+00:00 | Vulnerability · Source |
| CVE-2016-0653 | suse_vex | SUSE CVE CVE-2016-0653 | known not affected: 121 | 2026-07-26T01:06:45+00:00 | Vulnerability · Source |
| CVE-2016-0657 | suse_vex | SUSE CVE CVE-2016-0657 | known not affected: 121 | 2026-07-26T01:06:43+00:00 | Vulnerability · Source |
| CVE-2016-0663 | suse_vex | SUSE CVE CVE-2016-0663 | known not affected: 121 | 2026-07-26T01:06:40+00:00 | Vulnerability · Source |
| CVE-2016-0695 | suse_vex | SUSE CVE CVE-2016-0695 | known affected: 112 known not affected: 93 recommended: 364 | 2026-07-26T01:06:33+00:00 | Vulnerability · Source |
| CVE-2016-0729 | suse_vex | SUSE CVE CVE-2016-0729 | recommended: 192 | 2026-07-26T01:06:22+00:00 | Vulnerability · Source |
| CVE-2016-0736 | suse_vex | SUSE CVE CVE-2016-0736 | known affected: 86 known not affected: 38 recommended: 415 | 2026-07-26T01:06:20+00:00 | Vulnerability · Source |
| CVE-2016-0749 | suse_vex | SUSE CVE CVE-2016-0749 | known not affected: 139 recommended: 137 | 2026-07-26T01:06:17+00:00 | Vulnerability · Source |
| CVE-2016-0766 | suse_vex | SUSE CVE CVE-2016-0766 | known affected: 1 known not affected: 20 recommended: 252 | 2026-07-26T01:06:07+00:00 | Vulnerability · Source |
| CVE-2016-0773 | suse_vex | SUSE CVE CVE-2016-0773 | known affected: 1 known not affected: 19 recommended: 263 | 2026-07-26T01:05:58+00:00 | Vulnerability · Source |
| CVE-2016-0821 | suse_vex | SUSE CVE CVE-2016-0821 | known not affected: 582 | 2026-07-26T01:05:44+00:00 | Vulnerability · Source |
| CVE-2016-1237 | suse_vex | SUSE CVE CVE-2016-1237 | known affected: 3 known not affected: 637 recommended: 189 | 2026-07-26T01:05:40+00:00 | Vulnerability · Source |
| CVE-2016-1246 | suse_vex | SUSE CVE CVE-2016-1246 | known affected: 17 recommended: 78 | 2026-07-26T01:05:35+00:00 | Vulnerability · Source |
| CVE-2016-1372 | suse_vex | SUSE CVE CVE-2016-1372 | known not affected: 12 recommended: 16 | 2026-07-26T01:05:25+00:00 | Vulnerability · Source |
| CVE-2016-1526 | suse_vex | SUSE CVE CVE-2016-1526 | known affected: 1 recommended: 66 | 2026-07-26T01:05:20+00:00 | Vulnerability · Source |
| CVE-2016-1572 | suse_vex | SUSE CVE CVE-2016-1572 | known affected: 11 recommended: 232 | 2026-07-26T01:05:06+00:00 | Vulnerability · Source |
| CVE-2016-1949 | suse_vex | SUSE CVE CVE-2016-1949 | known affected: 1 known not affected: 43 recommended: 250 | 2026-07-26T01:04:37+00:00 | Vulnerability · Source |
| CVE-2016-1959 | suse_vex | SUSE CVE CVE-2016-1959 | known affected: 38 known not affected: 183 recommended: 250 | 2026-07-26T01:04:29+00:00 | Vulnerability · Source |
| CVE-2016-2114 | suse_vex | SUSE CVE CVE-2016-2114 | known not affected: 635 recommended: 53 | 2026-07-26T01:04:06+00:00 | Vulnerability · Source |
| CVE-2016-2270 | suse_vex | SUSE CVE CVE-2016-2270 | known affected: 320 known not affected: 12 recommended: 544 | 2026-07-26T01:03:36+00:00 | Vulnerability · Source |
| CVE-2016-2335 | suse_vex | SUSE CVE CVE-2016-2335 | recommended: 100 | 2026-07-26T01:03:30+00:00 | Vulnerability · Source |
| CVE-2016-2339 | suse_vex | SUSE CVE CVE-2016-2339 | known affected: 5 known not affected: 50 recommended: 140 | 2026-07-26T01:03:25+00:00 | Vulnerability · Source |
| CVE-2016-2524 | suse_vex | SUSE CVE CVE-2016-2524 | known affected: 3 recommended: 442 | 2026-07-26T01:03:18+00:00 | Vulnerability · Source |
| CVE-2016-2547 | suse_vex | SUSE CVE CVE-2016-2547 | known not affected: 201 recommended: 185 | 2026-07-26T01:03:12+00:00 | Vulnerability · Source |
| CVE-2016-2553 | suse_vex | SUSE CVE CVE-2016-2553 | known affected: 12 known not affected: 111 | 2026-07-26T01:03:08+00:00 | Vulnerability · Source |
| CVE-2016-2800 | suse_vex | SUSE CVE CVE-2016-2800 | known affected: 2 recommended: 648 | 2026-07-26T01:02:50+00:00 | Vulnerability · Source |
| CVE-2016-2819 | suse_vex | SUSE CVE CVE-2016-2819 | known affected: 2 recommended: 622 | 2026-07-26T01:02:38+00:00 | Vulnerability · Source |
| CVE-2016-2841 | suse_vex | SUSE CVE CVE-2016-2841 | known affected: 320 known not affected: 144 recommended: 621 | 2026-07-26T01:02:24+00:00 | Vulnerability · Source |
| CVE-2016-2857 | suse_vex | SUSE CVE CVE-2016-2857 | recommended: 110 | 2026-07-26T01:02:21+00:00 | Vulnerability · Source |
| CVE-2016-3065 | suse_vex | SUSE CVE CVE-2016-3065 | known not affected: 410 recommended: 94 | 2026-07-26T01:02:19+00:00 | Vulnerability · Source |
| CVE-2016-3075 | suse_vex | SUSE CVE CVE-2016-3075 | known affected: 321 known not affected: 121 recommended: 1361 | 2026-07-26T01:02:16+00:00 | Vulnerability · Source |
| CVE-2016-3159 | suse_vex | SUSE CVE CVE-2016-3159 | known affected: 1 recommended: 126 | 2026-07-26T01:02:06+00:00 | Vulnerability · Source |
| CVE-2016-3177 | suse_vex | SUSE CVE CVE-2016-3177 | known not affected: 56 | 2026-07-26T01:02:04+00:00 | Vulnerability · Source |
| CVE-2016-3183 | suse_vex | SUSE CVE CVE-2016-3183 | known not affected: 66 recommended: 20 | 2026-07-26T01:02:01+00:00 | Vulnerability · Source |
| CVE-2016-3190 | suse_vex | SUSE CVE CVE-2016-3190 | known not affected: 25 recommended: 48 | 2026-07-26T01:01:59+00:00 | Vulnerability · Source |
| CVE-2016-3461 | suse_vex | SUSE CVE CVE-2016-3461 | known not affected: 121 | 2026-07-26T01:01:54+00:00 | Vulnerability · Source |
| CVE-2016-3477 | suse_vex | SUSE CVE CVE-2016-3477 | known affected: 1 known not affected: 44 recommended: 671 | 2026-07-26T01:01:52+00:00 | Vulnerability · Source |
| CVE-2016-3500 | suse_vex | SUSE CVE CVE-2016-3500 | known not affected: 96 recommended: 351 | 2026-07-26T01:01:47+00:00 | Vulnerability · Source |
| CVE-2016-3550 | suse_vex | SUSE CVE CVE-2016-3550 | known not affected: 96 recommended: 351 | 2026-07-26T01:01:44+00:00 | Vulnerability · Source |
| CVE-2016-3619 | suse_vex | SUSE CVE CVE-2016-3619 | known not affected: 30 recommended: 22 | 2026-07-26T01:01:37+00:00 | Vulnerability · Source |
| CVE-2016-3623 | suse_vex | SUSE CVE CVE-2016-3623 | known affected: 463 recommended: 281 | 2026-07-26T01:01:36+00:00 | Vulnerability · Source |
| CVE-2016-3627 | suse_vex | SUSE CVE CVE-2016-3627 | known affected: 321 known not affected: 102 recommended: 586 | 2026-07-26T01:01:34+00:00 | Vulnerability · Source |
| CVE-2016-4302 | suse_vex | SUSE CVE CVE-2016-4302 | known affected: 30 known not affected: 17 recommended: 40 | 2026-07-26T01:01:05+00:00 | Vulnerability · Source |
| CVE-2016-4347 | suse_vex | SUSE CVE CVE-2016-4347 | known not affected: 161 | 2026-07-26T01:01:03+00:00 | Vulnerability · Source |