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-3458 | suse_vex | SUSE CVE CVE-2016-3458 | recommended: 319 | 2026-07-28T00:11:53+00:00 | Vulnerability · Source |
| CVE-2016-3689 | suse_vex | SUSE CVE CVE-2016-3689 | known affected: 24 known not affected: 93 recommended: 294 | 2026-07-28T00:11:51+00:00 | Vulnerability · Source |
| CVE-2016-4001 | suse_vex | SUSE CVE CVE-2016-4001 | known affected: 3 known not affected: 472 recommended: 197 | 2026-07-28T00:11:46+00:00 | Vulnerability · Source |
| CVE-2016-4356 | suse_vex | SUSE CVE CVE-2016-4356 | known not affected: 11 | 2026-07-28T00:11:43+00:00 | Vulnerability · Source |
| CVE-2016-4415 | suse_vex | SUSE CVE CVE-2016-4415 | known not affected: 64 | 2026-07-28T00:11:42+00:00 | Vulnerability · Source |
| CVE-2016-4490 | suse_vex | SUSE CVE CVE-2016-4490 | known not affected: 986 | 2026-07-28T00:11:40+00:00 | Vulnerability · Source |
| CVE-2016-4562 | suse_vex | SUSE CVE CVE-2016-4562 | known not affected: 480 recommended: 194 | 2026-07-28T00:11:39+00:00 | Vulnerability · Source |
| CVE-2016-4568 | suse_vex | SUSE CVE CVE-2016-4568 | known not affected: 417 | 2026-07-28T00:11:37+00:00 | Vulnerability · Source |
| CVE-2016-4574 | suse_vex | SUSE CVE CVE-2016-4574 | known affected: 321 recommended: 269 | 2026-07-28T00:11:35+00:00 | Vulnerability · Source |
| CVE-2016-4858 | suse_vex | SUSE CVE CVE-2016-4858 | known not affected: 359 | 2026-07-28T00:11:32+00:00 | Vulnerability · Source |
| CVE-2016-4964 | suse_vex | SUSE CVE CVE-2016-4964 | known affected: 394 known not affected: 202 recommended: 1662 | 2026-07-28T00:11:30+00:00 | Vulnerability · Source |
| CVE-2016-4975 | suse_vex | SUSE CVE CVE-2016-4975 | known affected: 63 known not affected: 63 recommended: 107 | 2026-07-28T00:11:29+00:00 | Vulnerability · Source |
| CVE-2016-5239 | suse_vex | SUSE CVE CVE-2016-5239 | known not affected: 109 recommended: 6 | 2026-07-28T00:11:25+00:00 | Vulnerability · Source |
| CVE-2016-5279 | suse_vex | SUSE CVE CVE-2016-5279 | known affected: 3 recommended: 250 | 2026-07-28T00:11:22+00:00 | Vulnerability · Source |
| CVE-2016-5280 | suse_vex | SUSE CVE CVE-2016-5280 | known affected: 3 recommended: 320 | 2026-07-28T00:11:20+00:00 | Vulnerability · Source |
| CVE-2016-5288 | suse_vex | SUSE CVE CVE-2016-5288 | known affected: 1 known not affected: 48 recommended: 250 | 2026-07-28T00:11:19+00:00 | Vulnerability · Source |
| CVE-2016-5319 | suse_vex | SUSE CVE CVE-2016-5319 | recommended: 58 | 2026-07-28T00:11:17+00:00 | Vulnerability · Source |
| CVE-2016-5322 | suse_vex | SUSE CVE CVE-2016-5322 | known not affected: 43 | 2026-07-28T00:11:16+00:00 | Vulnerability · Source |
| CVE-2016-5359 | suse_vex | SUSE CVE CVE-2016-5359 | known not affected: 103 recommended: 77 | 2026-07-28T00:11:13+00:00 | Vulnerability · Source |
| CVE-2016-5548 | suse_vex | SUSE CVE CVE-2016-5548 | known affected: 482 known not affected: 139 recommended: 540 | 2026-07-28T00:11:11+00:00 | Vulnerability · Source |
| CVE-2016-5568 | suse_vex | SUSE CVE CVE-2016-5568 | known affected: 374 known not affected: 160 recommended: 714 | 2026-07-28T00:11:09+00:00 | Vulnerability · Source |
| CVE-2016-5689 | suse_vex | SUSE CVE CVE-2016-5689 | known affected: 76 recommended: 194 | 2026-07-28T00:11:07+00:00 | Vulnerability · Source |
| CVE-2016-6136 | suse_vex | SUSE CVE CVE-2016-6136 | known affected: 3 known not affected: 436 recommended: 12 | 2026-07-28T00:11:04+00:00 | Vulnerability · Source |
| CVE-2016-6187 | suse_vex | SUSE CVE CVE-2016-6187 | known not affected: 107 recommended: 106 | 2026-07-28T00:11:02+00:00 | Vulnerability · Source |
| CVE-2016-6308 | suse_vex | SUSE CVE CVE-2016-6308 | known not affected: 86 | 2026-07-28T00:11:00+00:00 | Vulnerability · Source |
| CVE-2016-6349 | suse_vex | SUSE CVE CVE-2016-6349 | known not affected: 72 | 2026-07-28T00:10:59+00:00 | Vulnerability · Source |
| CVE-2016-6503 | suse_vex | SUSE CVE CVE-2016-6503 | known not affected: 76 | 2026-07-28T00:10:57+00:00 | Vulnerability · Source |
| CVE-2016-7053 | suse_vex | SUSE CVE CVE-2016-7053 | known not affected: 46 | 2026-07-28T00:10:56+00:00 | Vulnerability · Source |
| CVE-2016-7421 | suse_vex | SUSE CVE CVE-2016-7421 | known affected: 394 known not affected: 125 recommended: 1716 | 2026-07-28T00:10:52+00:00 | Vulnerability · Source |
| CVE-2016-7513 | suse_vex | SUSE CVE CVE-2016-7513 | known affected: 75 known not affected: 49 recommended: 126 | 2026-07-28T00:10:48+00:00 | Vulnerability · Source |
| CVE-2016-7524 | suse_vex | SUSE CVE CVE-2016-7524 | known affected: 76 recommended: 176 | 2026-07-28T00:10:47+00:00 | Vulnerability · Source |
| CVE-2016-7567 | suse_vex | SUSE CVE CVE-2016-7567 | known affected: 401 known not affected: 19 recommended: 282 | 2026-07-28T00:10:45+00:00 | Vulnerability · Source |
| CVE-2016-7578 | suse_vex | SUSE CVE CVE-2016-7578 | known affected: 57 known not affected: 18 | 2026-07-28T00:10:43+00:00 | Vulnerability · Source |
| CVE-2016-7598 | suse_vex | SUSE CVE CVE-2016-7598 | known not affected: 87 recommended: 924 | 2026-07-28T00:10:42+00:00 | Vulnerability · Source |
| CVE-2016-7610 | suse_vex | SUSE CVE CVE-2016-7610 | known not affected: 69 recommended: 894 | 2026-07-28T00:10:40+00:00 | Vulnerability · Source |
| CVE-2016-7984 | suse_vex | SUSE CVE CVE-2016-7984 | known affected: 320 recommended: 180 | 2026-07-28T00:10:35+00:00 | Vulnerability · Source |
| CVE-2016-8577 | suse_vex | SUSE CVE CVE-2016-8577 | known affected: 408 known not affected: 121 recommended: 1769 | 2026-07-28T00:10:32+00:00 | Vulnerability · Source |
| CVE-2016-8618 | suse_vex | SUSE CVE CVE-2016-8618 | known affected: 317 known not affected: 15 recommended: 430 | 2026-07-28T00:10:30+00:00 | Vulnerability · Source |
| CVE-2016-8636 | suse_vex | SUSE CVE CVE-2016-8636 | known affected: 6 known not affected: 175 recommended: 88 | 2026-07-28T00:10:28+00:00 | Vulnerability · Source |
| CVE-2016-8654 | suse_vex | SUSE CVE CVE-2016-8654 | known affected: 31 known not affected: 123 recommended: 194 | 2026-07-28T00:10:27+00:00 | Vulnerability · Source |
| CVE-2016-8883 | suse_vex | SUSE CVE CVE-2016-8883 | known affected: 1 recommended: 194 | 2026-07-28T00:10:22+00:00 | Vulnerability · Source |
| CVE-2016-9076 | suse_vex | SUSE CVE CVE-2016-9076 | known affected: 1 known not affected: 50 recommended: 308 | 2026-07-28T00:10:20+00:00 | Vulnerability · Source |
| CVE-2016-9104 | suse_vex | SUSE CVE CVE-2016-9104 | known affected: 388 known not affected: 111 recommended: 1729 | 2026-07-28T00:10:19+00:00 | Vulnerability · Source |
| CVE-2016-9115 | suse_vex | SUSE CVE CVE-2016-9115 | recommended: 17 | 2026-07-28T00:10:17+00:00 | Vulnerability · Source |
| CVE-2016-9117 | suse_vex | SUSE CVE CVE-2016-9117 | recommended: 17 | 2026-07-28T00:10:16+00:00 | Vulnerability · Source |
| CVE-2016-9180 | suse_vex | SUSE CVE CVE-2016-9180 | known affected: 401 recommended: 79 | 2026-07-28T00:10:14+00:00 | Vulnerability · Source |
| CVE-2016-9392 | suse_vex | SUSE CVE CVE-2016-9392 | known affected: 31 recommended: 188 | 2026-07-28T00:10:09+00:00 | Vulnerability · Source |
| CVE-2016-9532 | suse_vex | SUSE CVE CVE-2016-9532 | known not affected: 133 | 2026-07-28T00:10:06+00:00 | Vulnerability · Source |
| CVE-2016-9556 | suse_vex | SUSE CVE CVE-2016-9556 | known affected: 1 recommended: 210 | 2026-07-28T00:10:03+00:00 | Vulnerability · Source |
| CVE-2016-9559 | suse_vex | SUSE CVE CVE-2016-9559 | known affected: 1 recommended: 210 | 2026-07-28T00:10:00+00:00 | Vulnerability · Source |