VEX records
Browse vendor VEX statements available in this Vulnerability-Lookup instance and pivot to the related vulnerability.
285064 VEX records
API response| Vulnerability | Source | Title | Product status | Imported | Links |
|---|---|---|---|---|---|
| CVE-2015-8784 | suse_vex | SUSE CVE CVE-2015-8784 | known not affected: 308 recommended: 4 | 2026-07-26T01:08:46+00:00 | Vulnerability · Source |
| CVE-2015-8803 | suse_vex | SUSE CVE CVE-2015-8803 | recommended: 431 | 2026-07-26T01:08:43+00:00 | Vulnerability · Source |
| CVE-2015-8817 | suse_vex | SUSE CVE CVE-2015-8817 | known affected: 1 known not affected: 4 recommended: 188 | 2026-07-26T01:08:41+00:00 | Vulnerability · Source |
| CVE-2015-8830 | suse_vex | SUSE CVE CVE-2015-8830 | known not affected: 485 recommended: 13 | 2026-07-26T01:08:38+00:00 | Vulnerability · Source |
| CVE-2015-8853 | suse_vex | SUSE CVE CVE-2015-8853 | known affected: 59 recommended: 115 | 2026-07-26T01:08:36+00:00 | Vulnerability · Source |
| CVE-2015-8875 | suse_vex | SUSE CVE CVE-2015-8875 | known not affected: 61 | 2026-07-26T01:08:33+00:00 | Vulnerability · Source |
| CVE-2015-8876 | suse_vex | SUSE CVE CVE-2015-8876 | known affected: 1168 known not affected: 168 recommended: 581 | 2026-07-26T01:08:31+00:00 | Vulnerability · Source |
| CVE-2015-8896 | suse_vex | SUSE CVE CVE-2015-8896 | known affected: 97 recommended: 222 | 2026-07-26T01:08:28+00:00 | Vulnerability · Source |
| CVE-2015-8897 | suse_vex | SUSE CVE CVE-2015-8897 | known affected: 97 recommended: 208 | 2026-07-26T01:08:26+00:00 | Vulnerability · Source |
| CVE-2015-8900 | suse_vex | SUSE CVE CVE-2015-8900 | known affected: 96 known not affected: 347 recommended: 166 | 2026-07-26T01:08:24+00:00 | Vulnerability · Source |
| CVE-2015-8917 | suse_vex | SUSE CVE CVE-2015-8917 | recommended: 189 | 2026-07-26T01:08:21+00:00 | Vulnerability · Source |
| CVE-2015-8932 | suse_vex | SUSE CVE CVE-2015-8932 | known affected: 30 known not affected: 17 recommended: 40 | 2026-07-26T01:08:19+00:00 | Vulnerability · Source |
| CVE-2015-8933 | suse_vex | SUSE CVE CVE-2015-8933 | known affected: 12 known not affected: 126 recommended: 221 | 2026-07-26T01:08:17+00:00 | Vulnerability · Source |
| CVE-2015-8952 | suse_vex | SUSE CVE CVE-2015-8952 | known not affected: 235 | 2026-07-26T01:08:14+00:00 | Vulnerability · Source |
| CVE-2015-8953 | suse_vex | SUSE CVE CVE-2015-8953 | known not affected: 401 | 2026-07-26T01:08:12+00:00 | Vulnerability · Source |
| CVE-2015-8956 | suse_vex | SUSE CVE CVE-2015-8956 | known not affected: 114 recommended: 326 | 2026-07-26T01:08:10+00:00 | Vulnerability · Source |
| 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-9261 | suse_vex | SUSE CVE CVE-2015-9261 | known affected: 1 known not affected: 5 recommended: 136 | 2026-07-26T01:07:47+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-0597 | suse_vex | SUSE CVE CVE-2016-0597 | known affected: 1 known not affected: 176 recommended: 698 | 2026-07-26T01:07:20+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-0606 | suse_vex | SUSE CVE CVE-2016-0606 | known affected: 1 known not affected: 176 recommended: 698 | 2026-07-26T01:07:15+00:00 | Vulnerability · Source |
| CVE-2016-0609 | suse_vex | SUSE CVE CVE-2016-0609 | known not affected: 121 recommended: 708 | 2026-07-26T01:07:09+00:00 | Vulnerability · Source |
| CVE-2016-0610 | suse_vex | SUSE CVE CVE-2016-0610 | known not affected: 169 recommended: 383 | 2026-07-26T01:07:07+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-0650 | suse_vex | SUSE CVE CVE-2016-0650 | known not affected: 121 recommended: 666 | 2026-07-26T01:06:50+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 |