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-9391 | suse_vex | SUSE CVE CVE-2016-9391 | known affected: 37 recommended: 194 | 2026-07-29T00:06:42+00:00 | Vulnerability · Source |
| CVE-2016-9453 | suse_vex | SUSE CVE CVE-2016-9453 | known affected: 394 known not affected: 88 recommended: 298 | 2026-07-29T00:06:39+00:00 | Vulnerability · Source |
| CVE-2016-9536 | suse_vex | SUSE CVE CVE-2016-9536 | known not affected: 28 recommended: 26 | 2026-07-29T00:06:38+00:00 | Vulnerability · Source |
| CVE-2016-9576 | suse_vex | SUSE CVE CVE-2016-9576 | known not affected: 379 recommended: 582 | 2026-07-29T00:06:36+00:00 | Vulnerability · Source |
| CVE-2016-9625 | suse_vex | SUSE CVE CVE-2016-9625 | known affected: 1 recommended: 87 | 2026-07-29T00:06:35+00:00 | Vulnerability · Source |
| CVE-2016-9636 | suse_vex | SUSE CVE CVE-2016-9636 | known affected: 32 recommended: 86 | 2026-07-29T00:06:33+00:00 | Vulnerability · Source |
| CVE-2016-9794 | suse_vex | SUSE CVE CVE-2016-9794 | known affected: 14 known not affected: 486 recommended: 456 | 2026-07-29T00:06:32+00:00 | Vulnerability · Source |
| CVE-2016-9893 | suse_vex | SUSE CVE CVE-2016-9893 | known affected: 1 recommended: 419 | 2026-07-29T00:06:29+00:00 | Vulnerability · Source |
| CVE-2016-9902 | suse_vex | SUSE CVE CVE-2016-9902 | known affected: 1 recommended: 335 | 2026-07-29T00:06:27+00:00 | Vulnerability · Source |
| CVE-2016-9907 | suse_vex | SUSE CVE CVE-2016-9907 | known affected: 395 known not affected: 167 recommended: 1899 | 2026-07-29T00:06:25+00:00 | Vulnerability · Source |
| CVE-2016-9912 | suse_vex | SUSE CVE CVE-2016-9912 | known not affected: 179 recommended: 1707 | 2026-07-29T00:06:22+00:00 | Vulnerability · Source |
| CVE-2016-9922 | suse_vex | SUSE CVE CVE-2016-9922 | known affected: 1 known not affected: 228 recommended: 2252 | 2026-07-29T00:06:21+00:00 | Vulnerability · Source |
| CVE-2016-9952 | suse_vex | SUSE CVE CVE-2016-9952 | known not affected: 63 | 2026-07-29T00:06:19+00:00 | Vulnerability · Source |
| CVE-2016-10029 | suse_vex | SUSE CVE CVE-2016-10029 | known not affected: 1021 recommended: 66 | 2026-07-29T00:06:16+00:00 | Vulnerability · Source |
| CVE-2016-10046 | suse_vex | SUSE CVE CVE-2016-10046 | known affected: 1 recommended: 204 | 2026-07-29T00:06:15+00:00 | Vulnerability · Source |
| CVE-2016-10050 | suse_vex | SUSE CVE CVE-2016-10050 | recommended: 218 | 2026-07-29T00:06:13+00:00 | Vulnerability · Source |
| CVE-2016-10058 | suse_vex | SUSE CVE CVE-2016-10058 | known affected: 10 known not affected: 113 | 2026-07-29T00:06:12+00:00 | Vulnerability · Source |
| CVE-2016-10164 | suse_vex | SUSE CVE CVE-2016-10164 | recommended: 261 | 2026-07-29T00:06:10+00:00 | Vulnerability · Source |
| CVE-2016-10208 | suse_vex | SUSE CVE CVE-2016-10208 | known affected: 14 known not affected: 392 recommended: 122 | 2026-07-29T00:06:08+00:00 | Vulnerability · Source |
| CVE-2016-10318 | suse_vex | SUSE CVE CVE-2016-10318 | known not affected: 34 | 2026-07-29T00:06:06+00:00 | Vulnerability · Source |
| CVE-2016-10350 | suse_vex | SUSE CVE CVE-2016-10350 | known affected: 24 known not affected: 16 recommended: 25 | 2026-07-29T00:06:05+00:00 | Vulnerability · Source |
| CVE-2017-2538 | suse_vex | SUSE CVE CVE-2017-2538 | known affected: 116 known not affected: 87 recommended: 939 | 2026-07-29T00:05:59+00:00 | Vulnerability · Source |
| CVE-2017-3144 | suse_vex | SUSE CVE CVE-2017-3144 | known affected: 344 known not affected: 95 recommended: 407 | 2026-07-29T00:05:55+00:00 | Vulnerability · Source |
| CVE-2017-3638 | suse_vex | SUSE CVE CVE-2017-3638 | known affected: 1 known not affected: 64 | 2026-07-29T00:05:52+00:00 | Vulnerability · Source |
| CVE-2017-3649 | suse_vex | SUSE CVE CVE-2017-3649 | known affected: 1 known not affected: 64 | 2026-07-29T00:05:50+00:00 | Vulnerability · Source |
| CVE-2017-3730 | suse_vex | SUSE CVE CVE-2017-3730 | known not affected: 103 | 2026-07-29T00:05:49+00:00 | Vulnerability · Source |
| CVE-2017-5336 | suse_vex | SUSE CVE CVE-2017-5336 | known affected: 8 known not affected: 4 recommended: 176 | 2026-07-29T00:05:43+00:00 | Vulnerability · Source |
| CVE-2017-5374 | suse_vex | SUSE CVE CVE-2017-5374 | known affected: 1 known not affected: 38 recommended: 249 | 2026-07-29T00:05:42+00:00 | Vulnerability · Source |
| CVE-2017-5448 | suse_vex | SUSE CVE CVE-2017-5448 | known not affected: 42 recommended: 685 | 2026-07-29T00:05:40+00:00 | Vulnerability · Source |
| CVE-2017-5500 | suse_vex | SUSE CVE CVE-2017-5500 | known affected: 46 known not affected: 16 | 2026-07-29T00:05:36+00:00 | Vulnerability · Source |
| CVE-2017-5501 | suse_vex | SUSE CVE CVE-2017-5501 | known affected: 46 known not affected: 16 | 2026-07-29T00:05:34+00:00 | Vulnerability · Source |
| CVE-2017-5507 | suse_vex | SUSE CVE CVE-2017-5507 | known affected: 1 known not affected: 14 recommended: 204 | 2026-07-29T00:05:33+00:00 | Vulnerability · Source |
| CVE-2017-5650 | suse_vex | SUSE CVE CVE-2017-5650 | known not affected: 54 | 2026-07-29T00:05:32+00:00 | Vulnerability · Source |
| CVE-2017-5856 | suse_vex | SUSE CVE CVE-2017-5856 | known affected: 422 known not affected: 145 recommended: 1899 | 2026-07-29T00:05:30+00:00 | Vulnerability · Source |
| CVE-2017-5932 | suse_vex | SUSE CVE CVE-2017-5932 | known not affected: 461 | 2026-07-29T00:05:28+00:00 | Vulnerability · Source |
| CVE-2017-5967 | suse_vex | SUSE CVE CVE-2017-5967 | known not affected: 351 | 2026-07-29T00:05:27+00:00 | Vulnerability · Source |
| CVE-2017-5987 | suse_vex | SUSE CVE CVE-2017-5987 | known affected: 26 known not affected: 146 recommended: 1760 | 2026-07-29T00:05:25+00:00 | Vulnerability · Source |
| CVE-2017-6355 | suse_vex | SUSE CVE CVE-2017-6355 | recommended: 29 | 2026-07-29T00:05:22+00:00 | Vulnerability · Source |
| CVE-2017-6451 | suse_vex | SUSE CVE CVE-2017-6451 | known affected: 31 recommended: 98 | 2026-07-29T00:05:21+00:00 | Vulnerability · Source |
| CVE-2017-6460 | suse_vex | SUSE CVE CVE-2017-6460 | known affected: 31 recommended: 98 | 2026-07-29T00:05:19+00:00 | Vulnerability · Source |
| CVE-2017-6470 | suse_vex | SUSE CVE CVE-2017-6470 | known affected: 73 recommended: 444 | 2026-07-29T00:05:18+00:00 | Vulnerability · Source |
| CVE-2017-6472 | suse_vex | SUSE CVE CVE-2017-6472 | known affected: 73 recommended: 444 | 2026-07-29T00:05:16+00:00 | Vulnerability · Source |
| CVE-2017-6499 | suse_vex | SUSE CVE CVE-2017-6499 | known affected: 10 known not affected: 113 | 2026-07-29T00:05:15+00:00 | Vulnerability · Source |
| CVE-2017-6832 | suse_vex | SUSE CVE CVE-2017-6832 | known affected: 45 recommended: 202 | 2026-07-29T00:05:13+00:00 | Vulnerability · Source |
| CVE-2017-6836 | suse_vex | SUSE CVE CVE-2017-6836 | known affected: 45 recommended: 196 | 2026-07-29T00:05:12+00:00 | Vulnerability · Source |
| CVE-2017-6891 | suse_vex | SUSE CVE CVE-2017-6891 | known not affected: 321 recommended: 89 | 2026-07-29T00:05:10+00:00 | Vulnerability · Source |
| CVE-2017-7048 | suse_vex | SUSE CVE CVE-2017-7048 | known affected: 12 known not affected: 329 recommended: 927 | 2026-07-29T00:05:09+00:00 | Vulnerability · Source |
| CVE-2017-7109 | suse_vex | SUSE CVE CVE-2017-7109 | known not affected: 87 recommended: 927 | 2026-07-29T00:05:05+00:00 | Vulnerability · Source |
| CVE-2017-7186 | suse_vex | SUSE CVE CVE-2017-7186 | known affected: 328 known not affected: 590 recommended: 1069 | 2026-07-29T00:05:04+00:00 | Vulnerability · Source |
| CVE-2017-7286 | suse_vex | SUSE CVE CVE-2017-7286 | known not affected: 64 | 2026-07-29T00:05:02+00:00 | Vulnerability · Source |