VEX records
Browse vendor VEX statements available in this Vulnerability-Lookup instance and pivot to the related vulnerability.
292225 VEX records
API response| Vulnerability | Source | Title | Product status | Imported | Links |
|---|---|---|---|---|---|
| CVE-2016-4483 | suse_vex | SUSE CVE CVE-2016-4483 | known affected: 1 known not affected: 83 recommended: 503 | 2026-07-17T14:23:32+00:00 | Vulnerability · Source |
| CVE-2016-4493 | suse_vex | SUSE CVE CVE-2016-4493 | known affected: 2 known not affected: 416 | 2026-07-17T14:23:30+00:00 | Vulnerability · Source |
| CVE-2016-5386 | suse_vex | SUSE CVE CVE-2016-5386 | known not affected: 147 recommended: 59 | 2026-07-17T14:23:08+00:00 | Vulnerability · Source |
| CVE-2016-6489 | suse_vex | SUSE CVE CVE-2016-6489 | known affected: 320 recommended: 457 | 2026-07-17T14:22:54+00:00 | Vulnerability · Source |
| CVE-2016-7466 | suse_vex | SUSE CVE CVE-2016-7466 | known affected: 407 known not affected: 125 recommended: 1740 | 2026-07-17T14:22:37+00:00 | Vulnerability · Source |
| CVE-2016-9376 | suse_vex | SUSE CVE CVE-2016-9376 | known affected: 1 recommended: 562 | 2026-07-17T14:22:06+00:00 | Vulnerability · Source |
| CVE-2016-9629 | suse_vex | SUSE CVE CVE-2016-9629 | known affected: 1 recommended: 83 | 2026-07-17T14:21:48+00:00 | Vulnerability · Source |
| CVE-2016-10044 | suse_vex | SUSE CVE CVE-2016-10044 | known not affected: 469 recommended: 99 | 2026-07-17T14:21:33+00:00 | Vulnerability · Source |
| CVE-2016-10267 | suse_vex | SUSE CVE CVE-2016-10267 | known affected: 434 known not affected: 80 recommended: 286 | 2026-07-17T14:21:25+00:00 | Vulnerability · Source |
| CVE-2016-10270 | suse_vex | SUSE CVE CVE-2016-10270 | known affected: 434 known not affected: 80 recommended: 286 | 2026-07-17T14:21:24+00:00 | Vulnerability · Source |
| CVE-2016-1000339 | suse_vex | SUSE CVE CVE-2016-1000339 | known not affected: 18 recommended: 134 | 2026-07-17T14:21:21+00:00 | Vulnerability · Source |
| CVE-2017-2836 | suse_vex | SUSE CVE CVE-2017-2836 | recommended: 222 | 2026-07-17T14:21:08+00:00 | Vulnerability · Source |
| CVE-2017-5398 | suse_vex | SUSE CVE CVE-2017-5398 | known affected: 1 recommended: 408 | 2026-07-17T14:20:53+00:00 | Vulnerability · Source |
| CVE-2017-5468 | suse_vex | SUSE CVE CVE-2017-5468 | known not affected: 42 recommended: 12 | 2026-07-17T14:20:39+00:00 | Vulnerability · Source |
| CVE-2017-5471 | suse_vex | SUSE CVE CVE-2017-5471 | known affected: 2 known not affected: 42 | 2026-07-17T14:20:37+00:00 | Vulnerability · Source |
| CVE-2017-5483 | suse_vex | SUSE CVE CVE-2017-5483 | known affected: 320 recommended: 180 | 2026-07-17T14:20:35+00:00 | Vulnerability · Source |
| CVE-2017-7529 | suse_vex | SUSE CVE CVE-2017-7529 | known not affected: 5 recommended: 91 | 2026-07-17T14:19:47+00:00 | Vulnerability · Source |
| CVE-2017-7760 | suse_vex | SUSE CVE CVE-2017-7760 | known affected: 2 known not affected: 42 recommended: 237 | 2026-07-17T14:19:31+00:00 | Vulnerability · Source |
| CVE-2017-7761 | suse_vex | SUSE CVE CVE-2017-7761 | known affected: 2 known not affected: 42 recommended: 369 | 2026-07-17T14:19:30+00:00 | Vulnerability · Source |
| CVE-2017-7793 | suse_vex | SUSE CVE CVE-2017-7793 | known not affected: 42 recommended: 614 | 2026-07-17T14:19:23+00:00 | Vulnerability · Source |
| CVE-2017-9232 | suse_vex | SUSE CVE CVE-2017-9232 | recommended: 3 | 2026-07-17T14:18:55+00:00 | Vulnerability · Source |
| CVE-2017-10197 | suse_vex | SUSE CVE CVE-2017-10197 | known not affected: 42 | 2026-07-17T14:18:40+00:00 | Vulnerability · Source |
| CVE-2017-11550 | suse_vex | SUSE CVE CVE-2017-11550 | known affected: 6 known not affected: 18 recommended: 89 | 2026-07-17T14:18:28+00:00 | Vulnerability · Source |
| CVE-2017-11551 | suse_vex | SUSE CVE CVE-2017-11551 | known affected: 6 known not affected: 18 recommended: 86 | 2026-07-17T14:18:26+00:00 | Vulnerability · Source |
| CVE-2017-12620 | suse_vex | SUSE CVE CVE-2017-12620 | recommended: 4 | 2026-07-17T14:18:20+00:00 | Vulnerability · Source |
| CVE-2017-14039 | suse_vex | SUSE CVE CVE-2017-14039 | known not affected: 65 recommended: 202 | 2026-07-17T14:17:46+00:00 | Vulnerability · Source |
| CVE-2017-14491 | suse_vex | SUSE CVE CVE-2017-14491 | known affected: 20 known not affected: 5 recommended: 98 | 2026-07-17T14:17:41+00:00 | Vulnerability · Source |
| CVE-2017-14494 | suse_vex | SUSE CVE CVE-2017-14494 | known affected: 20 known not affected: 6 recommended: 97 | 2026-07-17T14:17:39+00:00 | Vulnerability · Source |
| CVE-2017-15134 | suse_vex | SUSE CVE CVE-2017-15134 | recommended: 154 | 2026-07-17T14:17:28+00:00 | Vulnerability · Source |
| CVE-2017-16539 | suse_vex | SUSE CVE CVE-2017-16539 | known affected: 320 known not affected: 147 recommended: 324 | 2026-07-17T14:17:16+00:00 | Vulnerability · Source |
| CVE-2017-16837 | suse_vex | SUSE CVE CVE-2017-16837 | known not affected: 25 recommended: 66 | 2026-07-17T14:17:15+00:00 | Vulnerability · Source |
| CVE-2017-16876 | suse_vex | SUSE CVE CVE-2017-16876 | recommended: 16 | 2026-07-17T14:17:14+00:00 | Vulnerability · Source |
| CVE-2017-17458 | suse_vex | SUSE CVE CVE-2017-17458 | known not affected: 24 recommended: 54 | 2026-07-17T14:17:09+00:00 | Vulnerability · Source |
| CVE-2018-3620 | suse_vex | SUSE CVE CVE-2018-3620 | known affected: 53 known not affected: 93 recommended: 762 | 2026-07-17T14:16:37+00:00 | Vulnerability · Source |
| CVE-2018-4163 | suse_vex | SUSE CVE CVE-2018-4163 | known affected: 92 known not affected: 169 recommended: 904 | 2026-07-17T14:16:25+00:00 | Vulnerability · Source |
| CVE-2018-4392 | suse_vex | SUSE CVE CVE-2018-4392 | known affected: 84 recommended: 944 | 2026-07-17T14:16:12+00:00 | Vulnerability · Source |
| CVE-2018-4464 | suse_vex | SUSE CVE CVE-2018-4464 | known affected: 84 recommended: 965 | 2026-07-17T14:16:09+00:00 | Vulnerability · Source |
| CVE-2018-5099 | suse_vex | SUSE CVE CVE-2018-5099 | known affected: 2 recommended: 402 | 2026-07-17T14:16:06+00:00 | Vulnerability · Source |
| CVE-2018-5145 | suse_vex | SUSE CVE CVE-2018-5145 | known affected: 2 recommended: 378 | 2026-07-17T14:16:02+00:00 | Vulnerability · Source |
| CVE-2018-5160 | suse_vex | SUSE CVE CVE-2018-5160 | known affected: 24 recommended: 74 | 2026-07-17T14:15:53+00:00 | Vulnerability · Source |
| CVE-2018-5181 | suse_vex | SUSE CVE CVE-2018-5181 | known affected: 24 recommended: 74 | 2026-07-17T14:15:49+00:00 | Vulnerability · Source |
| CVE-2018-5187 | suse_vex | SUSE CVE CVE-2018-5187 | known affected: 21 recommended: 105 | 2026-07-17T14:15:47+00:00 | Vulnerability · Source |
| CVE-2018-8036 | suse_vex | SUSE CVE CVE-2018-8036 | known affected: 6 known not affected: 9 recommended: 75 | 2026-07-17T14:15:16+00:00 | Vulnerability · Source |
| CVE-2018-8788 | suse_vex | SUSE CVE CVE-2018-8788 | recommended: 219 | 2026-07-17T14:15:13+00:00 | Vulnerability · Source |
| CVE-2018-9135 | suse_vex | SUSE CVE CVE-2018-9135 | known affected: 80 known not affected: 185 recommended: 662 | 2026-07-17T14:15:11+00:00 | Vulnerability · Source |
| CVE-2018-10529 | suse_vex | SUSE CVE CVE-2018-10529 | known not affected: 72 recommended: 76 | 2026-07-17T14:15:02+00:00 | Vulnerability · Source |
| CVE-2018-10839 | suse_vex | SUSE CVE CVE-2018-10839 | known affected: 529 known not affected: 1210 recommended: 1918 | 2026-07-17T14:15:00+00:00 | Vulnerability · Source |
| CVE-2018-10935 | suse_vex | SUSE CVE CVE-2018-10935 | recommended: 154 | 2026-07-17T14:14:55+00:00 | Vulnerability · Source |
| CVE-2018-11307 | suse_vex | SUSE CVE CVE-2018-11307 | recommended: 47 | 2026-07-17T14:14:53+00:00 | Vulnerability · Source |
| CVE-2018-12361 | suse_vex | SUSE CVE CVE-2018-12361 | known affected: 21 recommended: 105 | 2026-07-17T14:14:41+00:00 | Vulnerability · Source |