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-2016-5241 | suse_vex | SUSE CVE CVE-2016-5241 | known affected: 3 known not affected: 46 recommended: 14 | 2026-08-01T23:38:36+00:00 | Vulnerability · Source |
| CVE-2016-5403 | suse_vex | SUSE CVE CVE-2016-5403 | known affected: 396 known not affected: 163 recommended: 1906 | 2026-08-01T23:38:33+00:00 | Vulnerability · Source |
| CVE-2016-5824 | suse_vex | SUSE CVE CVE-2016-5824 | known affected: 1 recommended: 335 | 2026-08-01T23:38:30+00:00 | Vulnerability · Source |
| CVE-2016-6198 | suse_vex | SUSE CVE CVE-2016-6198 | known affected: 3 known not affected: 488 recommended: 12 | 2026-08-01T23:38:28+00:00 | Vulnerability · Source |
| CVE-2016-6223 | suse_vex | SUSE CVE CVE-2016-6223 | known affected: 457 recommended: 263 | 2026-08-01T23:38:27+00:00 | Vulnerability · Source |
| CVE-2016-6328 | suse_vex | SUSE CVE CVE-2016-6328 | known affected: 27 known not affected: 14 recommended: 223 | 2026-08-01T23:38:24+00:00 | Vulnerability · Source |
| CVE-2016-7166 | suse_vex | SUSE CVE CVE-2016-7166 | known affected: 30 known not affected: 108 recommended: 4 | 2026-08-01T23:38:19+00:00 | Vulnerability · Source |
| CVE-2016-7175 | suse_vex | SUSE CVE CVE-2016-7175 | known affected: 1 recommended: 586 | 2026-08-01T23:38:18+00:00 | Vulnerability · Source |
| CVE-2016-7520 | suse_vex | SUSE CVE CVE-2016-7520 | known affected: 94 known not affected: 51 recommended: 132 | 2026-08-01T23:38:15+00:00 | Vulnerability · Source |
| CVE-2016-7568 | suse_vex | SUSE CVE CVE-2016-7568 | known affected: 550 known not affected: 139 recommended: 1130 | 2026-08-01T23:38:14+00:00 | Vulnerability · Source |
| CVE-2016-7586 | suse_vex | SUSE CVE CVE-2016-7586 | known not affected: 87 recommended: 927 | 2026-08-01T23:38:12+00:00 | Vulnerability · Source |
| CVE-2016-7599 | suse_vex | SUSE CVE CVE-2016-7599 | known not affected: 87 recommended: 927 | 2026-08-01T23:38:11+00:00 | Vulnerability · Source |
| CVE-2016-7915 | suse_vex | SUSE CVE CVE-2016-7915 | known not affected: 234 recommended: 203 | 2026-08-01T23:38:09+00:00 | Vulnerability · Source |
| CVE-2016-7944 | suse_vex | SUSE CVE CVE-2016-7944 | known affected: 36 recommended: 270 | 2026-08-01T23:38:07+00:00 | Vulnerability · Source |
| CVE-2016-7948 | suse_vex | SUSE CVE CVE-2016-7948 | known not affected: 62 recommended: 463 | 2026-08-01T23:38:05+00:00 | Vulnerability · Source |
| CVE-2016-8678 | suse_vex | SUSE CVE CVE-2016-8678 | known not affected: 119 | 2026-08-01T23:38:02+00:00 | Vulnerability · Source |
| CVE-2016-9112 | suse_vex | SUSE CVE CVE-2016-9112 | recommended: 20 | 2026-08-01T23:37:58+00:00 | Vulnerability · Source |
| CVE-2016-9380 | suse_vex | SUSE CVE CVE-2016-9380 | known affected: 14 known not affected: 6 recommended: 474 | 2026-08-01T23:37:56+00:00 | Vulnerability · Source |
| CVE-2016-9386 | suse_vex | SUSE CVE CVE-2016-9386 | known affected: 334 known not affected: 6 recommended: 556 | 2026-08-01T23:37:55+00:00 | Vulnerability · Source |
| CVE-2016-9401 | suse_vex | SUSE CVE CVE-2016-9401 | known affected: 320 recommended: 686 | 2026-08-01T23:37:54+00:00 | Vulnerability · Source |
| CVE-2016-9430 | suse_vex | SUSE CVE CVE-2016-9430 | known not affected: 15 | 2026-08-01T23:37:53+00:00 | Vulnerability · Source |
| CVE-2016-9778 | suse_vex | SUSE CVE CVE-2016-9778 | known affected: 320 known not affected: 261 recommended: 719 | 2026-08-01T23:37:51+00:00 | Vulnerability · Source |
| CVE-2016-9800 | suse_vex | SUSE CVE CVE-2016-9800 | known not affected: 46 recommended: 310 | 2026-08-01T23:37:49+00:00 | Vulnerability · Source |
| CVE-2016-10054 | suse_vex | SUSE CVE CVE-2016-10054 | known affected: 10 known not affected: 113 | 2026-08-01T23:37:47+00:00 | Vulnerability · Source |
| CVE-2016-10199 | suse_vex | SUSE CVE CVE-2016-10199 | recommended: 456 | 2026-08-01T23:37:45+00:00 | Vulnerability · Source |
| CVE-2016-10255 | suse_vex | SUSE CVE CVE-2016-10255 | known affected: 136 recommended: 172 | 2026-08-01T23:37:42+00:00 | Vulnerability · Source |
| CVE-2016-11066 | suse_vex | SUSE CVE CVE-2016-11066 | recommended: 1 | 2026-08-01T23:37:40+00:00 | Vulnerability · Source |
| CVE-2017-0861 | suse_vex | SUSE CVE CVE-2017-0861 | known affected: 71 known not affected: 277 recommended: 319 | 2026-08-01T23:37:34+00:00 | Vulnerability · Source |
| CVE-2017-0898 | suse_vex | SUSE CVE CVE-2017-0898 | known affected: 1 known not affected: 77 recommended: 98 | 2026-08-01T23:37:33+00:00 | Vulnerability · Source |
| CVE-2017-0903 | suse_vex | SUSE CVE CVE-2017-0903 | known affected: 3 known not affected: 7 recommended: 98 | 2026-08-01T23:37:32+00:00 | Vulnerability · Source |
| CVE-2017-2633 | suse_vex | SUSE CVE CVE-2017-2633 | known affected: 2 known not affected: 1409 recommended: 1730 | 2026-08-01T23:37:30+00:00 | Vulnerability · Source |
| CVE-2017-3260 | suse_vex | SUSE CVE CVE-2017-3260 | known affected: 15 known not affected: 150 recommended: 331 | 2026-08-01T23:37:28+00:00 | Vulnerability · Source |
| CVE-2017-5386 | suse_vex | SUSE CVE CVE-2017-5386 | known affected: 1 recommended: 331 | 2026-08-01T23:37:26+00:00 | Vulnerability · Source |
| CVE-2017-5397 | suse_vex | SUSE CVE CVE-2017-5397 | known affected: 24 known not affected: 15 | 2026-08-01T23:37:25+00:00 | Vulnerability · Source |
| CVE-2017-5420 | suse_vex | SUSE CVE CVE-2017-5420 | known affected: 1 recommended: 249 | 2026-08-01T23:37:24+00:00 | Vulnerability · Source |
| CVE-2017-5597 | suse_vex | SUSE CVE CVE-2017-5597 | known affected: 1 recommended: 588 | 2026-08-01T23:37:23+00:00 | Vulnerability · Source |
| CVE-2017-6196 | suse_vex | SUSE CVE CVE-2017-6196 | known affected: 6 known not affected: 54 | 2026-08-01T23:37:18+00:00 | Vulnerability · Source |
| CVE-2017-6264 | suse_vex | SUSE CVE CVE-2017-6264 | known not affected: 298 | 2026-08-01T23:37:17+00:00 | Vulnerability · Source |
| CVE-2017-6469 | suse_vex | SUSE CVE CVE-2017-6469 | known affected: 73 recommended: 444 | 2026-08-01T23:37:15+00:00 | Vulnerability · Source |
| CVE-2017-6827 | suse_vex | SUSE CVE CVE-2017-6827 | known affected: 45 recommended: 196 | 2026-08-01T23:37:14+00:00 | Vulnerability · Source |
| CVE-2017-6951 | suse_vex | SUSE CVE CVE-2017-6951 | known affected: 2 known not affected: 108 recommended: 272 | 2026-08-01T23:37:13+00:00 | Vulnerability · Source |
| CVE-2017-7142 | suse_vex | SUSE CVE CVE-2017-7142 | known not affected: 87 recommended: 927 | 2026-08-01T23:37:11+00:00 | Vulnerability · Source |
| CVE-2017-7308 | suse_vex | SUSE CVE CVE-2017-7308 | known not affected: 377 recommended: 494 | 2026-08-01T23:37:07+00:00 | Vulnerability · Source |
| CVE-2017-7377 | suse_vex | SUSE CVE CVE-2017-7377 | known affected: 26 known not affected: 43 recommended: 119 | 2026-08-01T23:37:06+00:00 | Vulnerability · Source |
| CVE-2017-7487 | suse_vex | SUSE CVE CVE-2017-7487 | known affected: 14 known not affected: 422 recommended: 432 | 2026-08-01T23:37:03+00:00 | Vulnerability · Source |
| CVE-2017-7614 | suse_vex | SUSE CVE CVE-2017-7614 | known affected: 1 known not affected: 134 recommended: 54 | 2026-08-01T23:37:01+00:00 | Vulnerability · Source |
| CVE-2017-7668 | suse_vex | SUSE CVE CVE-2017-7668 | known not affected: 43 recommended: 64 | 2026-08-01T23:37:00+00:00 | Vulnerability · Source |
| CVE-2017-7822 | suse_vex | SUSE CVE CVE-2017-7822 | known not affected: 42 recommended: 12 | 2026-08-01T23:36:57+00:00 | Vulnerability · Source |
| CVE-2017-7836 | suse_vex | SUSE CVE CVE-2017-7836 | known affected: 1 known not affected: 42 recommended: 12 | 2026-08-01T23:36:56+00:00 | Vulnerability · Source |
| CVE-2017-7857 | suse_vex | SUSE CVE CVE-2017-7857 | known affected: 6 known not affected: 52 | 2026-08-01T23:36:55+00:00 | Vulnerability · Source |