VEX records
Browse vendor VEX statements available in this Vulnerability-Lookup instance and pivot to the related vulnerability.
291935 VEX records
API response| Vulnerability | Source | Title | Product status | Imported | Links |
|---|---|---|---|---|---|
| CVE-2015-8959 | suse_vex | SUSE CVE CVE-2015-8959 | known affected: 95 known not affected: 2 recommended: 168 | 2026-07-26T01:08:08+00:00 | Vulnerability · Source |
| CVE-2015-8960 | suse_vex | SUSE CVE CVE-2015-8960 | known not affected: 85 | 2026-07-26T01:08:06+00:00 | Vulnerability · Source |
| CVE-2015-8961 | suse_vex | SUSE CVE CVE-2015-8961 | known not affected: 41 | 2026-07-26T01:08:04+00:00 | Vulnerability · Source |
| CVE-2015-8963 | suse_vex | SUSE CVE CVE-2015-8963 | known not affected: 569 recommended: 121 | 2026-07-26T01:08:01+00:00 | Vulnerability · Source |
| CVE-2015-8967 | suse_vex | SUSE CVE CVE-2015-8967 | known affected: 12 known not affected: 20 | 2026-07-26T01:07:59+00:00 | Vulnerability · Source |
| CVE-2015-8985 | suse_vex | SUSE CVE CVE-2015-8985 | known affected: 454 known not affected: 150 recommended: 655 | 2026-07-26T01:07:57+00:00 | Vulnerability · Source |
| CVE-2015-9019 | suse_vex | SUSE CVE CVE-2015-9019 | known affected: 452 known not affected: 78 recommended: 290 | 2026-07-26T01:07:54+00:00 | Vulnerability · Source |
| CVE-2015-9105 | suse_vex | SUSE CVE CVE-2015-9105 | known affected: 143 known not affected: 84 | 2026-07-26T01:07:52+00:00 | Vulnerability · Source |
| CVE-2015-9252 | suse_vex | SUSE CVE CVE-2015-9252 | known not affected: 157 | 2026-07-26T01:07:49+00:00 | Vulnerability · Source |
| CVE-2015-9382 | suse_vex | SUSE CVE CVE-2015-9382 | known affected: 1 known not affected: 240 recommended: 427 | 2026-07-26T01:07:44+00:00 | Vulnerability · Source |
| CVE-2015-9383 | suse_vex | SUSE CVE CVE-2015-9383 | known affected: 1 known not affected: 240 recommended: 3 | 2026-07-26T01:07:42+00:00 | Vulnerability · Source |
| CVE-2016-0264 | suse_vex | SUSE CVE CVE-2016-0264 | known affected: 1 known not affected: 65 recommended: 424 | 2026-07-26T01:07:39+00:00 | Vulnerability · Source |
| CVE-2016-0376 | suse_vex | SUSE CVE CVE-2016-0376 | known affected: 397 known not affected: 65 recommended: 424 | 2026-07-26T01:07:37+00:00 | Vulnerability · Source |
| CVE-2016-0448 | suse_vex | SUSE CVE CVE-2016-0448 | known affected: 37 known not affected: 93 recommended: 766 | 2026-07-26T01:07:34+00:00 | Vulnerability · Source |
| 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-0596 | suse_vex | SUSE CVE CVE-2016-0596 | known affected: 1 known not affected: 176 recommended: 698 | 2026-07-26T01:07:22+00:00 | Vulnerability · Source |
| CVE-2016-0600 | suse_vex | SUSE CVE CVE-2016-0600 | known not affected: 121 recommended: 698 | 2026-07-26T01:07:17+00:00 | Vulnerability · Source |
| CVE-2016-0639 | suse_vex | SUSE CVE CVE-2016-0639 | known not affected: 121 recommended: 10 | 2026-07-26T01:07:05+00:00 | Vulnerability · Source |
| CVE-2016-0640 | suse_vex | SUSE CVE CVE-2016-0640 | known not affected: 121 recommended: 666 | 2026-07-26T01:07:02+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-0647 | suse_vex | SUSE CVE CVE-2016-0647 | known not affected: 121 recommended: 293 | 2026-07-26T01:06:55+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-0652 | suse_vex | SUSE CVE CVE-2016-0652 | known not affected: 121 | 2026-07-26T01:06:47+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-0687 | suse_vex | SUSE CVE CVE-2016-0687 | known affected: 112 known not affected: 93 recommended: 788 | 2026-07-26T01:06:35+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-0703 | suse_vex | SUSE CVE CVE-2016-0703 | recommended: 184 | 2026-07-26T01:06:30+00:00 | Vulnerability · Source |
| CVE-2016-0706 | suse_vex | SUSE CVE CVE-2016-0706 | known affected: 394 known not affected: 4 recommended: 252 | 2026-07-26T01:06:25+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-0755 | suse_vex | SUSE CVE CVE-2016-0755 | known affected: 337 known not affected: 21 recommended: 474 | 2026-07-26T01:06:14+00:00 | Vulnerability · Source |
| CVE-2016-0758 | suse_vex | SUSE CVE CVE-2016-0758 | known affected: 5 known not affected: 443 recommended: 438 | 2026-07-26T01:06:12+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-0771 | suse_vex | SUSE CVE CVE-2016-0771 | known affected: 320 known not affected: 749 recommended: 3467 | 2026-07-26T01:06:04+00:00 | Vulnerability · Source |
| CVE-2016-0772 | suse_vex | SUSE CVE CVE-2016-0772 | known affected: 320 known not affected: 443 recommended: 1456 | 2026-07-26T01:06:01+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-0795 | suse_vex | SUSE CVE CVE-2016-0795 | recommended: 5100 | 2026-07-26T01:05:52+00:00 | Vulnerability · Source |
| CVE-2016-0800 | suse_vex | SUSE CVE CVE-2016-0800 | known affected: 321 known not affected: 292 recommended: 1078 | 2026-07-26T01:05:47+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-0823 | suse_vex | SUSE CVE CVE-2016-0823 | known not affected: 403 recommended: 193 | 2026-07-26T01:05:42+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-1245 | suse_vex | SUSE CVE CVE-2016-1245 | known affected: 3 known not affected: 125 recommended: 349 | 2026-07-26T01:05:37+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 |