VEX records
Browse vendor VEX statements available in this Vulnerability-Lookup instance and pivot to the related vulnerability.
283044 VEX records
API response| Vulnerability | Source | Title | Product status | Imported | Links |
|---|---|---|---|---|---|
| CVE-2017-9502 | suse_vex | SUSE CVE CVE-2017-9502 | known affected: 320 known not affected: 62 recommended: 362 | 2026-07-19T18:32:53+00:00 | Vulnerability · Source |
| CVE-2017-9524 | suse_vex | SUSE CVE CVE-2017-9524 | known affected: 394 known not affected: 126 recommended: 1707 | 2026-07-19T18:32:52+00:00 | Vulnerability · Source |
| CVE-2017-9747 | suse_vex | SUSE CVE CVE-2017-9747 | known affected: 394 known not affected: 333 recommended: 336 | 2026-07-19T18:32:50+00:00 | Vulnerability · Source |
| CVE-2017-9750 | suse_vex | SUSE CVE CVE-2017-9750 | known affected: 394 known not affected: 352 recommended: 336 | 2026-07-19T18:32:49+00:00 | Vulnerability · Source |
| CVE-2017-9814 | suse_vex | SUSE CVE CVE-2017-9814 | known affected: 494 known not affected: 55 recommended: 411 | 2026-07-19T18:32:48+00:00 | Vulnerability · Source |
| CVE-2017-9951 | suse_vex | SUSE CVE CVE-2017-9951 | known affected: 14 known not affected: 40 recommended: 113 | 2026-07-19T18:32:46+00:00 | Vulnerability · Source |
| CVE-2017-10196 | suse_vex | SUSE CVE CVE-2017-10196 | known not affected: 42 | 2026-07-19T18:32:45+00:00 | Vulnerability · Source |
| CVE-2017-10320 | suse_vex | SUSE CVE CVE-2017-10320 | known not affected: 218 recommended: 398 | 2026-07-19T18:32:44+00:00 | Vulnerability · Source |
| CVE-2017-10384 | suse_vex | SUSE CVE CVE-2017-10384 | known affected: 1 known not affected: 216 recommended: 426 | 2026-07-19T18:32:42+00:00 | Vulnerability · Source |
| CVE-2017-10788 | suse_vex | SUSE CVE CVE-2017-10788 | known affected: 1 known not affected: 24 recommended: 70 | 2026-07-19T18:32:41+00:00 | Vulnerability · Source |
| CVE-2017-10790 | suse_vex | SUSE CVE CVE-2017-10790 | known affected: 435 known not affected: 205 recommended: 413 | 2026-07-19T18:32:40+00:00 | Vulnerability · Source |
| CVE-2017-10988 | suse_vex | SUSE CVE CVE-2017-10988 | known affected: 13 known not affected: 101 recommended: 580 | 2026-07-19T18:32:39+00:00 | Vulnerability · Source |
| CVE-2017-11103 | suse_vex | SUSE CVE CVE-2017-11103 | known affected: 320 known not affected: 354 recommended: 3273 | 2026-07-19T18:32:37+00:00 | Vulnerability · Source |
| CVE-2017-11108 | suse_vex | SUSE CVE CVE-2017-11108 | known affected: 334 known not affected: 24 recommended: 148 | 2026-07-19T18:32:36+00:00 | Vulnerability · Source |
| CVE-2017-11185 | suse_vex | SUSE CVE CVE-2017-11185 | known affected: 59 known not affected: 51 recommended: 374 | 2026-07-19T18:32:34+00:00 | Vulnerability · Source |
| CVE-2017-11311 | suse_vex | SUSE CVE CVE-2017-11311 | known affected: 2 recommended: 286 | 2026-07-19T18:32:33+00:00 | Vulnerability · Source |
| CVE-2017-11334 | suse_vex | SUSE CVE CVE-2017-11334 | known affected: 437 known not affected: 1176 recommended: 1852 | 2026-07-19T18:32:31+00:00 | Vulnerability · Source |
| CVE-2017-11337 | suse_vex | SUSE CVE CVE-2017-11337 | known affected: 96 known not affected: 39 recommended: 157 | 2026-07-19T18:32:30+00:00 | Vulnerability · Source |
| CVE-2017-11368 | suse_vex | SUSE CVE CVE-2017-11368 | known affected: 320 known not affected: 108 recommended: 554 | 2026-07-19T18:32:29+00:00 | Vulnerability · Source |
| CVE-2017-11410 | suse_vex | SUSE CVE CVE-2017-11410 | known affected: 69 known not affected: 115 recommended: 541 | 2026-07-19T18:32:28+00:00 | Vulnerability · Source |
| CVE-2017-11411 | suse_vex | SUSE CVE CVE-2017-11411 | known affected: 69 known not affected: 115 recommended: 541 | 2026-07-19T18:32:26+00:00 | Vulnerability · Source |
| CVE-2017-11542 | suse_vex | SUSE CVE CVE-2017-11542 | known affected: 334 known not affected: 24 recommended: 148 | 2026-07-19T18:32:25+00:00 | Vulnerability · Source |
| CVE-2017-11592 | suse_vex | SUSE CVE CVE-2017-11592 | known affected: 28 known not affected: 89 recommended: 157 | 2026-07-19T18:32:24+00:00 | Vulnerability · Source |
| CVE-2017-11624 | suse_vex | SUSE CVE CVE-2017-11624 | known affected: 2 known not affected: 33 recommended: 312 | 2026-07-19T18:32:23+00:00 | Vulnerability · Source |
| CVE-2017-11625 | suse_vex | SUSE CVE CVE-2017-11625 | known affected: 2 known not affected: 33 recommended: 316 | 2026-07-19T18:32:21+00:00 | Vulnerability · Source |
| CVE-2017-12132 | suse_vex | SUSE CVE CVE-2017-12132 | known affected: 370 known not affected: 276 recommended: 1279 | 2026-07-19T18:32:20+00:00 | Vulnerability · Source |
| CVE-2017-12166 | suse_vex | SUSE CVE CVE-2017-12166 | known affected: 51 known not affected: 72 recommended: 236 | 2026-07-19T18:32:18+00:00 | Vulnerability · Source |
| CVE-2017-12377 | suse_vex | SUSE CVE CVE-2017-12377 | known affected: 1 known not affected: 78 recommended: 277 | 2026-07-19T18:32:17+00:00 | Vulnerability · Source |
| CVE-2017-12379 | suse_vex | SUSE CVE CVE-2017-12379 | known affected: 1 known not affected: 78 recommended: 277 | 2026-07-19T18:32:16+00:00 | Vulnerability · Source |
| CVE-2017-12452 | suse_vex | SUSE CVE CVE-2017-12452 | known affected: 394 known not affected: 21 recommended: 327 | 2026-07-19T18:32:14+00:00 | Vulnerability · Source |
| CVE-2017-12562 | suse_vex | SUSE CVE CVE-2017-12562 | known affected: 394 known not affected: 110 recommended: 121 | 2026-07-19T18:32:13+00:00 | Vulnerability · Source |
| CVE-2017-12627 | suse_vex | SUSE CVE CVE-2017-12627 | known affected: 23 recommended: 191 | 2026-07-19T18:32:12+00:00 | Vulnerability · Source |
| CVE-2017-12794 | suse_vex | SUSE CVE CVE-2017-12794 | known not affected: 3 recommended: 21 | 2026-07-19T18:32:11+00:00 | Vulnerability · Source |
| CVE-2017-12894 | suse_vex | SUSE CVE CVE-2017-12894 | known affected: 334 known not affected: 24 recommended: 148 | 2026-07-19T18:32:09+00:00 | Vulnerability · Source |
| CVE-2017-12897 | suse_vex | SUSE CVE CVE-2017-12897 | known affected: 334 known not affected: 24 recommended: 148 | 2026-07-19T18:32:08+00:00 | Vulnerability · Source |
| CVE-2017-12902 | suse_vex | SUSE CVE CVE-2017-12902 | known affected: 334 known not affected: 24 recommended: 148 | 2026-07-19T18:32:07+00:00 | Vulnerability · Source |
| CVE-2017-12990 | suse_vex | SUSE CVE CVE-2017-12990 | known affected: 334 known not affected: 24 recommended: 144 | 2026-07-19T18:32:05+00:00 | Vulnerability · Source |
| CVE-2017-12996 | suse_vex | SUSE CVE CVE-2017-12996 | known affected: 334 known not affected: 24 recommended: 148 | 2026-07-19T18:32:04+00:00 | Vulnerability · Source |
| CVE-2017-13008 | suse_vex | SUSE CVE CVE-2017-13008 | known affected: 334 known not affected: 24 recommended: 148 | 2026-07-19T18:32:03+00:00 | Vulnerability · Source |
| CVE-2017-13011 | suse_vex | SUSE CVE CVE-2017-13011 | known affected: 334 known not affected: 24 recommended: 148 | 2026-07-19T18:32:01+00:00 | Vulnerability · Source |
| CVE-2017-13012 | suse_vex | SUSE CVE CVE-2017-13012 | known affected: 334 known not affected: 24 recommended: 148 | 2026-07-19T18:32:00+00:00 | Vulnerability · Source |
| CVE-2017-13013 | suse_vex | SUSE CVE CVE-2017-13013 | known affected: 334 known not affected: 24 recommended: 148 | 2026-07-19T18:31:59+00:00 | Vulnerability · Source |
| CVE-2017-13022 | suse_vex | SUSE CVE CVE-2017-13022 | known affected: 334 known not affected: 24 recommended: 148 | 2026-07-19T18:31:58+00:00 | Vulnerability · Source |
| CVE-2017-13028 | suse_vex | SUSE CVE CVE-2017-13028 | known affected: 334 known not affected: 24 recommended: 148 | 2026-07-19T18:31:56+00:00 | Vulnerability · Source |
| CVE-2017-13036 | suse_vex | SUSE CVE CVE-2017-13036 | known affected: 334 known not affected: 24 recommended: 148 | 2026-07-19T18:31:55+00:00 | Vulnerability · Source |
| CVE-2017-13039 | suse_vex | SUSE CVE CVE-2017-13039 | known affected: 334 known not affected: 24 recommended: 144 | 2026-07-19T18:31:53+00:00 | Vulnerability · Source |
| CVE-2017-13045 | suse_vex | SUSE CVE CVE-2017-13045 | known affected: 334 known not affected: 24 recommended: 144 | 2026-07-19T18:31:52+00:00 | Vulnerability · Source |
| CVE-2017-13052 | suse_vex | SUSE CVE CVE-2017-13052 | known affected: 334 known not affected: 24 recommended: 144 | 2026-07-19T18:31:51+00:00 | Vulnerability · Source |
| CVE-2017-13082 | suse_vex | SUSE CVE CVE-2017-13082 | known affected: 6 known not affected: 344 recommended: 93 | 2026-07-19T18:31:50+00:00 | Vulnerability · Source |
| CVE-2017-13087 | suse_vex | SUSE CVE CVE-2017-13087 | known affected: 6 known not affected: 344 recommended: 113 | 2026-07-19T18:31:48+00:00 | Vulnerability · Source |