VEX records
Browse vendor VEX statements available in this Vulnerability-Lookup instance and pivot to the related vulnerability.
283003 VEX records
API response| Vulnerability | Source | Title | Product status | Imported | Links |
|---|---|---|---|---|---|
| CVE-2016-9894 | suse_vex | SUSE CVE CVE-2016-9894 | known affected: 1 recommended: 250 | 2026-07-19T18:36:07+00:00 | Vulnerability · Source |
| CVE-2016-9897 | suse_vex | SUSE CVE CVE-2016-9897 | known affected: 1 recommended: 410 | 2026-07-19T18:36:06+00:00 | Vulnerability · Source |
| CVE-2016-9898 | suse_vex | SUSE CVE CVE-2016-9898 | known affected: 1 recommended: 410 | 2026-07-19T18:36:05+00:00 | Vulnerability · Source |
| CVE-2016-9907 | suse_vex | SUSE CVE CVE-2016-9907 | known affected: 395 known not affected: 146 recommended: 1827 | 2026-07-19T18:36:03+00:00 | Vulnerability · Source |
| CVE-2016-9908 | suse_vex | SUSE CVE CVE-2016-9908 | known not affected: 150 recommended: 1656 | 2026-07-19T18:36:02+00:00 | Vulnerability · Source |
| CVE-2016-9912 | suse_vex | SUSE CVE CVE-2016-9912 | known not affected: 150 recommended: 1656 | 2026-07-19T18:36:00+00:00 | Vulnerability · Source |
| CVE-2016-9913 | suse_vex | SUSE CVE CVE-2016-9913 | known not affected: 209 recommended: 1656 | 2026-07-19T18:35:59+00:00 | Vulnerability · Source |
| CVE-2016-9922 | suse_vex | SUSE CVE CVE-2016-9922 | known affected: 1 known not affected: 201 recommended: 2162 | 2026-07-19T18:35:57+00:00 | Vulnerability · Source |
| CVE-2016-9957 | suse_vex | SUSE CVE CVE-2016-9957 | recommended: 152 | 2026-07-19T18:35:56+00:00 | Vulnerability · Source |
| CVE-2016-9958 | suse_vex | SUSE CVE CVE-2016-9958 | recommended: 149 | 2026-07-19T18:35:54+00:00 | Vulnerability · Source |
| CVE-2016-9959 | suse_vex | SUSE CVE CVE-2016-9959 | recommended: 152 | 2026-07-19T18:35:53+00:00 | Vulnerability · Source |
| CVE-2016-10009 | suse_vex | SUSE CVE CVE-2016-10009 | known affected: 334 recommended: 504 | 2026-07-19T18:35:52+00:00 | Vulnerability · Source |
| CVE-2016-10012 | suse_vex | SUSE CVE CVE-2016-10012 | known affected: 334 recommended: 488 | 2026-07-19T18:35:51+00:00 | Vulnerability · Source |
| CVE-2016-10028 | suse_vex | SUSE CVE CVE-2016-10028 | known affected: 394 known not affected: 189 recommended: 1703 | 2026-07-19T18:35:49+00:00 | Vulnerability · Source |
| CVE-2016-10075 | suse_vex | SUSE CVE CVE-2016-10075 | recommended: 18 | 2026-07-19T18:35:48+00:00 | Vulnerability · Source |
| CVE-2016-10155 | suse_vex | SUSE CVE CVE-2016-10155 | known affected: 408 known not affected: 122 recommended: 1871 | 2026-07-19T18:35:46+00:00 | Vulnerability · Source |
| CVE-2016-10198 | suse_vex | SUSE CVE CVE-2016-10198 | recommended: 458 | 2026-07-19T18:35:45+00:00 | Vulnerability · Source |
| CVE-2016-10217 | suse_vex | SUSE CVE CVE-2016-10217 | known not affected: 32 recommended: 198 | 2026-07-19T18:35:43+00:00 | Vulnerability · Source |
| CVE-2016-10218 | suse_vex | SUSE CVE CVE-2016-10218 | known affected: 36 known not affected: 56 recommended: 198 | 2026-07-19T18:35:42+00:00 | Vulnerability · Source |
| CVE-2016-10219 | suse_vex | SUSE CVE CVE-2016-10219 | known affected: 1 known not affected: 5 recommended: 260 | 2026-07-19T18:35:41+00:00 | Vulnerability · Source |
| CVE-2016-10220 | suse_vex | SUSE CVE CVE-2016-10220 | known affected: 30 known not affected: 32 recommended: 232 | 2026-07-19T18:35:40+00:00 | Vulnerability · Source |
| CVE-2016-10371 | suse_vex | SUSE CVE CVE-2016-10371 | known affected: 430 known not affected: 99 recommended: 255 | 2026-07-19T18:35:37+00:00 | Vulnerability · Source |
| CVE-2016-10505 | suse_vex | SUSE CVE CVE-2016-10505 | known not affected: 106 recommended: 184 | 2026-07-19T18:35:36+00:00 | Vulnerability · Source |
| CVE-2016-10739 | suse_vex | SUSE CVE CVE-2016-10739 | known affected: 378 known not affected: 143 recommended: 1358 | 2026-07-19T18:35:35+00:00 | Vulnerability · Source |
| CVE-2016-1000343 | suse_vex | SUSE CVE CVE-2016-1000343 | known not affected: 18 recommended: 134 | 2026-07-19T18:35:33+00:00 | Vulnerability · Source |
| CVE-2016-1000344 | suse_vex | SUSE CVE CVE-2016-1000344 | known not affected: 18 recommended: 134 | 2026-07-19T18:35:32+00:00 | Vulnerability · Source |
| CVE-2016-1000346 | suse_vex | SUSE CVE CVE-2016-1000346 | known not affected: 18 recommended: 134 | 2026-07-19T18:35:31+00:00 | Vulnerability · Source |
| CVE-2017-0381 | suse_vex | SUSE CVE CVE-2017-0381 | recommended: 178 | 2026-07-19T18:35:30+00:00 | Vulnerability · Source |
| CVE-2017-2366 | suse_vex | SUSE CVE CVE-2017-2366 | known not affected: 248 recommended: 912 | 2026-07-19T18:35:28+00:00 | Vulnerability · Source |
| CVE-2017-2373 | suse_vex | SUSE CVE CVE-2017-2373 | known not affected: 248 recommended: 924 | 2026-07-19T18:35:27+00:00 | Vulnerability · Source |
| CVE-2017-2510 | suse_vex | SUSE CVE CVE-2017-2510 | known affected: 81 known not affected: 169 recommended: 924 | 2026-07-19T18:35:26+00:00 | Vulnerability · Source |
| CVE-2017-2616 | suse_vex | SUSE CVE CVE-2017-2616 | known affected: 320 known not affected: 85 recommended: 1623 | 2026-07-19T18:35:24+00:00 | Vulnerability · Source |
| CVE-2017-2626 | suse_vex | SUSE CVE CVE-2017-2626 | known affected: 424 known not affected: 14 recommended: 407 | 2026-07-19T18:35:23+00:00 | Vulnerability · Source |
| CVE-2017-2635 | suse_vex | SUSE CVE CVE-2017-2635 | known affected: 394 known not affected: 347 recommended: 1805 | 2026-07-19T18:35:21+00:00 | Vulnerability · Source |
| CVE-2017-2835 | suse_vex | SUSE CVE CVE-2017-2835 | recommended: 222 | 2026-07-19T18:35:20+00:00 | Vulnerability · Source |
| CVE-2017-2837 | suse_vex | SUSE CVE CVE-2017-2837 | recommended: 222 | 2026-07-19T18:35:19+00:00 | Vulnerability · Source |
| CVE-2017-2885 | suse_vex | SUSE CVE CVE-2017-2885 | known not affected: 71 recommended: 450 | 2026-07-19T18:35:18+00:00 | Vulnerability · Source |
| CVE-2017-3141 | suse_vex | SUSE CVE CVE-2017-3141 | known affected: 334 known not affected: 683 recommended: 719 | 2026-07-19T18:35:16+00:00 | Vulnerability · Source |
| CVE-2017-3145 | suse_vex | SUSE CVE CVE-2017-3145 | known affected: 320 known not affected: 373 recommended: 912 | 2026-07-19T18:35:15+00:00 | Vulnerability · Source |
| CVE-2017-3636 | suse_vex | SUSE CVE CVE-2017-3636 | known affected: 29 known not affected: 97 recommended: 587 | 2026-07-19T18:35:13+00:00 | Vulnerability · Source |
| CVE-2017-3641 | suse_vex | SUSE CVE CVE-2017-3641 | known affected: 29 known not affected: 97 recommended: 577 | 2026-07-19T18:35:12+00:00 | Vulnerability · Source |
| CVE-2017-3653 | suse_vex | SUSE CVE CVE-2017-3653 | known affected: 29 known not affected: 97 recommended: 577 | 2026-07-19T18:35:10+00:00 | Vulnerability · Source |
| CVE-2017-5031 | suse_vex | SUSE CVE CVE-2017-5031 | known not affected: 87 recommended: 243 | 2026-07-19T18:35:09+00:00 | Vulnerability · Source |
| CVE-2017-5338 | suse_vex | SUSE CVE CVE-2017-5338 | recommended: 153 | 2026-07-19T18:35:08+00:00 | Vulnerability · Source |
| CVE-2017-5341 | suse_vex | SUSE CVE CVE-2017-5341 | known affected: 320 recommended: 176 | 2026-07-19T18:35:07+00:00 | Vulnerability · Source |
| CVE-2017-5342 | suse_vex | SUSE CVE CVE-2017-5342 | known affected: 320 recommended: 176 | 2026-07-19T18:35:05+00:00 | Vulnerability · Source |
| CVE-2017-5376 | suse_vex | SUSE CVE CVE-2017-5376 | known affected: 1 recommended: 408 | 2026-07-19T18:35:04+00:00 | Vulnerability · Source |
| CVE-2017-5379 | suse_vex | SUSE CVE CVE-2017-5379 | known affected: 1 known not affected: 34 recommended: 249 | 2026-07-19T18:35:03+00:00 | Vulnerability · Source |
| CVE-2017-5383 | suse_vex | SUSE CVE CVE-2017-5383 | known affected: 1 recommended: 408 | 2026-07-19T18:35:02+00:00 | Vulnerability · Source |
| CVE-2017-5384 | suse_vex | SUSE CVE CVE-2017-5384 | known affected: 1 known not affected: 34 recommended: 249 | 2026-07-19T18:35:00+00:00 | Vulnerability · Source |