VEX records
Browse vendor VEX statements available in this Vulnerability-Lookup instance and pivot to the related vulnerability.
291911 VEX records
API response| Vulnerability | Source | Title | Product status | Imported | Links |
|---|---|---|---|---|---|
| CVE-2015-0261 | suse_vex | SUSE CVE CVE-2015-0261 | known affected: 320 recommended: 192 | 2026-08-02T16:57:11+00:00 | Vulnerability · Source |
| CVE-2015-0480 | suse_vex | SUSE CVE CVE-2015-0480 | known affected: 40 known not affected: 141 recommended: 515 | 2026-08-02T16:57:09+00:00 | Vulnerability · Source |
| CVE-2015-0973 | suse_vex | SUSE CVE CVE-2015-0973 | known affected: 394 recommended: 201 | 2026-08-02T16:57:07+00:00 | Vulnerability · Source |
| CVE-2015-1798 | suse_vex | SUSE CVE CVE-2015-1798 | known not affected: 3 recommended: 97 | 2026-08-02T16:57:03+00:00 | Vulnerability · Source |
| CVE-2015-2621 | suse_vex | SUSE CVE CVE-2015-2621 | known affected: 103 known not affected: 192 recommended: 770 | 2026-08-02T16:57:01+00:00 | Vulnerability · Source |
| CVE-2015-2709 | suse_vex | SUSE CVE CVE-2015-2709 | known affected: 1 recommended: 329 | 2026-08-02T16:56:59+00:00 | Vulnerability · Source |
| CVE-2015-2724 | suse_vex | SUSE CVE CVE-2015-2724 | known affected: 23 known not affected: 144 recommended: 618 | 2026-08-02T16:56:57+00:00 | Vulnerability · Source |
| CVE-2015-2725 | suse_vex | SUSE CVE CVE-2015-2725 | known affected: 23 known not affected: 144 recommended: 614 | 2026-08-02T16:56:56+00:00 | Vulnerability · Source |
| CVE-2015-4805 | suse_vex | SUSE CVE CVE-2015-4805 | known affected: 95 known not affected: 289 recommended: 771 | 2026-08-02T16:56:48+00:00 | Vulnerability · Source |
| CVE-2015-4910 | suse_vex | SUSE CVE CVE-2015-4910 | known affected: 13 known not affected: 117 recommended: 70 | 2026-08-02T16:56:46+00:00 | Vulnerability · Source |
| CVE-2015-5600 | suse_vex | SUSE CVE CVE-2015-5600 | known affected: 2 recommended: 98 | 2026-08-02T16:56:41+00:00 | Vulnerability · Source |
| CVE-2015-7979 | suse_vex | SUSE CVE CVE-2015-7979 | known affected: 31 recommended: 132 | 2026-08-02T16:56:36+00:00 | Vulnerability · Source |
| CVE-2015-8078 | suse_vex | SUSE CVE CVE-2015-8078 | known affected: 1 recommended: 40 | 2026-08-02T16:56:34+00:00 | Vulnerability · Source |
| CVE-2015-8313 | suse_vex | SUSE CVE CVE-2015-8313 | known not affected: 29 recommended: 55 | 2026-08-02T16:56:29+00:00 | Vulnerability · Source |
| CVE-2015-8927 | suse_vex | SUSE CVE CVE-2015-8927 | known not affected: 231 | 2026-08-02T16:56:25+00:00 | Vulnerability · Source |
| CVE-2016-0494 | suse_vex | SUSE CVE CVE-2016-0494 | known affected: 37 known not affected: 93 recommended: 766 | 2026-08-02T16:56:22+00:00 | Vulnerability · Source |
| CVE-2016-0662 | suse_vex | SUSE CVE CVE-2016-0662 | known not affected: 121 | 2026-08-02T16:56:19+00:00 | Vulnerability · Source |
| CVE-2016-1907 | suse_vex | SUSE CVE CVE-2016-1907 | known not affected: 320 | 2026-08-02T16:56:12+00:00 | Vulnerability · Source |
| CVE-2016-2197 | suse_vex | SUSE CVE CVE-2016-2197 | known not affected: 49 recommended: 51 | 2026-08-02T16:56:08+00:00 | Vulnerability · Source |
| CVE-2016-2342 | suse_vex | SUSE CVE CVE-2016-2342 | known not affected: 125 recommended: 319 | 2026-08-02T16:56:05+00:00 | Vulnerability · Source |
| CVE-2016-3624 | suse_vex | SUSE CVE CVE-2016-3624 | known not affected: 53 | 2026-08-02T16:56:02+00:00 | Vulnerability · Source |
| CVE-2016-4480 | suse_vex | SUSE CVE CVE-2016-4480 | known affected: 1 known not affected: 246 recommended: 77 | 2026-08-02T16:55:56+00:00 | Vulnerability · Source |
| CVE-2016-4557 | suse_vex | SUSE CVE CVE-2016-4557 | known affected: 24 known not affected: 149 recommended: 189 | 2026-08-02T16:55:53+00:00 | Vulnerability · Source |
| CVE-2016-4804 | suse_vex | SUSE CVE CVE-2016-4804 | known affected: 17 known not affected: 34 recommended: 20 | 2026-08-02T16:55:51+00:00 | Vulnerability · Source |
| CVE-2016-5240 | suse_vex | SUSE CVE CVE-2016-5240 | known not affected: 109 recommended: 20 | 2026-08-02T16:55:45+00:00 | Vulnerability · Source |
| CVE-2016-5265 | suse_vex | SUSE CVE CVE-2016-5265 | known affected: 5 recommended: 438 | 2026-08-02T16:55:43+00:00 | Vulnerability · Source |
| CVE-2016-5292 | suse_vex | SUSE CVE CVE-2016-5292 | known affected: 1 known not affected: 24 recommended: 321 | 2026-08-02T16:55:40+00:00 | Vulnerability · Source |
| CVE-2016-5549 | suse_vex | SUSE CVE CVE-2016-5549 | known affected: 124 known not affected: 166 recommended: 561 | 2026-08-02T16:55:35+00:00 | Vulnerability · Source |
| CVE-2016-6307 | suse_vex | SUSE CVE CVE-2016-6307 | known not affected: 102 | 2026-08-02T16:55:29+00:00 | Vulnerability · Source |
| CVE-2016-6786 | suse_vex | SUSE CVE CVE-2016-6786 | known not affected: 529 | 2026-08-02T16:55:27+00:00 | Vulnerability · Source |
| CVE-2016-6888 | suse_vex | SUSE CVE CVE-2016-6888 | known affected: 1 known not affected: 178 recommended: 1831 | 2026-08-02T16:55:25+00:00 | Vulnerability · Source |
| CVE-2016-7908 | suse_vex | SUSE CVE CVE-2016-7908 | known affected: 349 known not affected: 169 recommended: 2390 | 2026-08-02T16:55:21+00:00 | Vulnerability · Source |
| CVE-2016-7909 | suse_vex | SUSE CVE CVE-2016-7909 | known affected: 347 known not affected: 157 recommended: 2390 | 2026-08-02T16:55:18+00:00 | Vulnerability · Source |
| CVE-2016-8668 | suse_vex | SUSE CVE CVE-2016-8668 | known affected: 420 known not affected: 136 recommended: 1754 | 2026-08-02T16:55:15+00:00 | Vulnerability · Source |
| CVE-2016-8735 | suse_vex | SUSE CVE CVE-2016-8735 | known affected: 46 recommended: 192 | 2026-08-02T16:55:12+00:00 | Vulnerability · Source |
| CVE-2016-9103 | suse_vex | SUSE CVE CVE-2016-9103 | known affected: 395 known not affected: 192 recommended: 1834 | 2026-08-02T16:55:10+00:00 | Vulnerability · Source |
| CVE-2016-9312 | suse_vex | SUSE CVE CVE-2016-9312 | known affected: 4 known not affected: 16 | 2026-08-02T16:55:07+00:00 | Vulnerability · Source |
| CVE-2016-9423 | suse_vex | SUSE CVE CVE-2016-9423 | known not affected: 35 recommended: 4 | 2026-08-02T16:55:04+00:00 | Vulnerability · Source |
| CVE-2016-9574 | suse_vex | SUSE CVE CVE-2016-9574 | known affected: 1 recommended: 512 | 2026-08-02T16:55:01+00:00 | Vulnerability · Source |
| CVE-2016-9793 | suse_vex | SUSE CVE CVE-2016-9793 | known affected: 12 known not affected: 73 recommended: 404 | 2026-08-02T16:54:59+00:00 | Vulnerability · Source |
| CVE-2016-10025 | suse_vex | SUSE CVE CVE-2016-10025 | known affected: 332 known not affected: 104 recommended: 430 | 2026-08-02T16:54:56+00:00 | Vulnerability · Source |
| CVE-2016-10088 | suse_vex | SUSE CVE CVE-2016-10088 | known not affected: 379 recommended: 331 | 2026-08-02T16:54:53+00:00 | Vulnerability · Source |
| CVE-2016-10154 | suse_vex | SUSE CVE CVE-2016-10154 | known not affected: 34 | 2026-08-02T16:54:50+00:00 | Vulnerability · Source |
| CVE-2016-10195 | suse_vex | SUSE CVE CVE-2016-10195 | known affected: 30 recommended: 39 | 2026-08-02T16:54:48+00:00 | Vulnerability · Source |
| CVE-2016-10708 | suse_vex | SUSE CVE CVE-2016-10708 | known affected: 19 recommended: 107 | 2026-08-02T16:54:44+00:00 | Vulnerability · Source |
| CVE-2016-10764 | suse_vex | SUSE CVE CVE-2016-10764 | known not affected: 229 | 2026-08-02T16:54:42+00:00 | Vulnerability · Source |
| CVE-2017-5391 | suse_vex | SUSE CVE CVE-2017-5391 | known affected: 1 known not affected: 38 recommended: 249 | 2026-08-02T16:54:33+00:00 | Vulnerability · Source |
| CVE-2017-5402 | suse_vex | SUSE CVE CVE-2017-5402 | known affected: 1 recommended: 416 | 2026-08-02T16:54:31+00:00 | Vulnerability · Source |
| CVE-2017-6214 | suse_vex | SUSE CVE CVE-2017-6214 | known not affected: 364 recommended: 346 | 2026-08-02T16:54:21+00:00 | Vulnerability · Source |
| CVE-2017-6313 | suse_vex | SUSE CVE CVE-2017-6313 | known affected: 394 known not affected: 136 recommended: 672 | 2026-08-02T16:54:19+00:00 | Vulnerability · Source |