VEX records
Browse vendor VEX statements available in this Vulnerability-Lookup instance and pivot to the related vulnerability.
294144 VEX records
API response| Vulnerability | Source | Title | Product status | Imported | Links |
|---|---|---|---|---|---|
| CVE-2016-7777 | suse_vex | SUSE CVE CVE-2016-7777 | known affected: 334 known not affected: 6 recommended: 556 | 2026-08-27T01:39:53+00:00 | Vulnerability · Source |
| CVE-2016-7914 | suse_vex | SUSE CVE CVE-2016-7914 | known not affected: 139 recommended: 121 | 2026-08-27T01:39:45+00:00 | Vulnerability · Source |
| CVE-2016-8399 | suse_vex | SUSE CVE CVE-2016-8399 | known not affected: 29 recommended: 315 | 2026-08-27T01:39:20+00:00 | Vulnerability · Source |
| CVE-2016-8619 | suse_vex | SUSE CVE CVE-2016-8619 | known affected: 340 known not affected: 21 recommended: 455 | 2026-08-27T01:39:15+00:00 | Vulnerability · Source |
| CVE-2016-8637 | suse_vex | SUSE CVE CVE-2016-8637 | known affected: 321 known not affected: 22 recommended: 326 | 2026-08-27T01:39:08+00:00 | Vulnerability · Source |
| CVE-2016-8668 | suse_vex | SUSE CVE CVE-2016-8668 | known affected: 420 known not affected: 136 recommended: 1794 | 2026-08-27T01:38:59+00:00 | Vulnerability · Source |
| CVE-2016-8858 | suse_vex | SUSE CVE CVE-2016-8858 | known affected: 339 recommended: 519 | 2026-08-27T01:38:48+00:00 | Vulnerability · Source |
| CVE-2016-9071 | suse_vex | SUSE CVE CVE-2016-9071 | known affected: 1 known not affected: 60 recommended: 325 | 2026-08-27T01:38:41+00:00 | Vulnerability · Source |
| CVE-2016-9103 | suse_vex | SUSE CVE CVE-2016-9103 | known affected: 395 known not affected: 192 recommended: 1874 | 2026-08-27T01:38:31+00:00 | Vulnerability · Source |
| CVE-2016-9374 | suse_vex | SUSE CVE CVE-2016-9374 | known affected: 1 recommended: 592 | 2026-08-27T01:38:17+00:00 | Vulnerability · Source |
| CVE-2016-9388 | suse_vex | SUSE CVE CVE-2016-9388 | known affected: 37 recommended: 196 | 2026-08-27T01:38:11+00:00 | Vulnerability · Source |
| CVE-2016-9390 | suse_vex | SUSE CVE CVE-2016-9390 | known affected: 37 recommended: 196 | 2026-08-27T01:38:07+00:00 | Vulnerability · Source |
| CVE-2016-9427 | suse_vex | SUSE CVE CVE-2016-9427 | recommended: 37 | 2026-08-27T01:38:02+00:00 | Vulnerability · Source |
| CVE-2016-9584 | suse_vex | SUSE CVE CVE-2016-9584 | recommended: 251 | 2026-08-27T01:37:54+00:00 | Vulnerability · Source |
| CVE-2016-9601 | suse_vex | SUSE CVE CVE-2016-9601 | known affected: 37 recommended: 99 | 2026-08-27T01:37:49+00:00 | Vulnerability · Source |
| CVE-2016-9776 | suse_vex | SUSE CVE CVE-2016-9776 | known affected: 1 known not affected: 136 recommended: 1944 | 2026-08-27T01:37:42+00:00 | Vulnerability · Source |
| CVE-2016-9794 | suse_vex | SUSE CVE CVE-2016-9794 | known affected: 14 known not affected: 486 recommended: 456 | 2026-08-27T01:37:41+00:00 | Vulnerability · Source |
| CVE-2016-9812 | suse_vex | SUSE CVE CVE-2016-9812 | known affected: 120 recommended: 253 | 2026-08-27T01:37:34+00:00 | Vulnerability · Source |
| CVE-2016-9898 | suse_vex | SUSE CVE CVE-2016-9898 | known affected: 1 recommended: 422 | 2026-08-27T01:37:29+00:00 | Vulnerability · Source |
| CVE-2016-9901 | suse_vex | SUSE CVE CVE-2016-9901 | known affected: 1 recommended: 339 | 2026-08-27T01:37:27+00:00 | Vulnerability · Source |
| CVE-2016-9902 | suse_vex | SUSE CVE CVE-2016-9902 | known affected: 1 recommended: 339 | 2026-08-27T01:37:25+00:00 | Vulnerability · Source |
| CVE-2016-9912 | suse_vex | SUSE CVE CVE-2016-9912 | known not affected: 179 recommended: 1747 | 2026-08-27T01:37:17+00:00 | Vulnerability · Source |
| CVE-2016-9913 | suse_vex | SUSE CVE CVE-2016-9913 | known not affected: 251 recommended: 1747 | 2026-08-27T01:37:15+00:00 | Vulnerability · Source |
| CVE-2016-10002 | suse_vex | SUSE CVE CVE-2016-10002 | known affected: 394 known not affected: 30 recommended: 64 | 2026-08-27T01:37:07+00:00 | Vulnerability · Source |
| CVE-2016-10269 | suse_vex | SUSE CVE CVE-2016-10269 | known affected: 442 known not affected: 80 recommended: 301 | 2026-08-27T01:36:44+00:00 | Vulnerability · Source |
| CVE-2016-10271 | suse_vex | SUSE CVE CVE-2016-10271 | known affected: 441 known not affected: 99 recommended: 279 | 2026-08-27T01:36:42+00:00 | Vulnerability · Source |
| CVE-2016-10371 | suse_vex | SUSE CVE CVE-2016-10371 | known affected: 438 known not affected: 99 recommended: 267 | 2026-08-27T01:36:40+00:00 | Vulnerability · Source |
| CVE-2016-10708 | suse_vex | SUSE CVE CVE-2016-10708 | known affected: 19 recommended: 107 | 2026-08-27T01:36:38+00:00 | Vulnerability · Source |
| CVE-2016-1000339 | suse_vex | SUSE CVE CVE-2016-1000339 | known not affected: 18 recommended: 142 | 2026-08-27T01:36:32+00:00 | Vulnerability · Source |
| CVE-2016-1000343 | suse_vex | SUSE CVE CVE-2016-1000343 | known not affected: 18 recommended: 142 | 2026-08-27T01:36:30+00:00 | Vulnerability · Source |
| CVE-2017-0641 | suse_vex | SUSE CVE CVE-2017-0641 | known not affected: 159 recommended: 148 | 2026-08-27T01:36:28+00:00 | Vulnerability · Source |
| CVE-2017-2363 | suse_vex | SUSE CVE CVE-2017-2363 | known not affected: 248 recommended: 945 | 2026-08-27T01:36:25+00:00 | Vulnerability · Source |
| CVE-2017-2583 | suse_vex | SUSE CVE CVE-2017-2583 | known affected: 12 known not affected: 290 recommended: 234 | 2026-08-27T01:36:20+00:00 | Vulnerability · Source |
| CVE-2017-2836 | suse_vex | SUSE CVE CVE-2017-2836 | recommended: 235 | 2026-08-27T01:36:11+00:00 | Vulnerability · Source |
| CVE-2017-2838 | suse_vex | SUSE CVE CVE-2017-2838 | recommended: 235 | 2026-08-27T01:36:10+00:00 | Vulnerability · Source |
| CVE-2017-2885 | suse_vex | SUSE CVE CVE-2017-2885 | known not affected: 71 recommended: 466 | 2026-08-27T01:36:08+00:00 | Vulnerability · Source |
| CVE-2017-3302 | suse_vex | SUSE CVE CVE-2017-3302 | known affected: 35 known not affected: 104 recommended: 664 | 2026-08-27T01:36:00+00:00 | Vulnerability · Source |
| CVE-2017-3318 | suse_vex | SUSE CVE CVE-2017-3318 | known not affected: 93 recommended: 684 | 2026-08-27T01:35:58+00:00 | Vulnerability · Source |
| CVE-2017-3586 | suse_vex | SUSE CVE CVE-2017-3586 | recommended: 18 | 2026-08-27T01:35:54+00:00 | Vulnerability · Source |
| CVE-2017-3644 | suse_vex | SUSE CVE CVE-2017-3644 | known affected: 1 known not affected: 64 | 2026-08-27T01:35:52+00:00 | Vulnerability · Source |
| CVE-2017-3731 | suse_vex | SUSE CVE CVE-2017-3731 | known affected: 386 known not affected: 329 recommended: 1050 | 2026-08-27T01:35:49+00:00 | Vulnerability · Source |
| CVE-2017-5339 | suse_vex | SUSE CVE CVE-2017-5339 | recommended: 155 | 2026-08-27T01:35:32+00:00 | Vulnerability · Source |
| CVE-2017-5380 | suse_vex | SUSE CVE CVE-2017-5380 | known affected: 1 recommended: 420 | 2026-08-27T01:35:30+00:00 | Vulnerability · Source |
| CVE-2017-5383 | suse_vex | SUSE CVE CVE-2017-5383 | known affected: 1 recommended: 420 | 2026-08-27T01:35:27+00:00 | Vulnerability · Source |
| CVE-2017-5384 | suse_vex | SUSE CVE CVE-2017-5384 | known affected: 1 known not affected: 38 recommended: 253 | 2026-08-27T01:35:26+00:00 | Vulnerability · Source |
| CVE-2017-5393 | suse_vex | SUSE CVE CVE-2017-5393 | known affected: 1 known not affected: 38 recommended: 253 | 2026-08-27T01:35:19+00:00 | Vulnerability · Source |
| CVE-2017-5408 | suse_vex | SUSE CVE CVE-2017-5408 | known affected: 1 recommended: 420 | 2026-08-27T01:35:10+00:00 | Vulnerability · Source |
| CVE-2017-5410 | suse_vex | SUSE CVE CVE-2017-5410 | known affected: 1 recommended: 420 | 2026-08-27T01:35:09+00:00 | Vulnerability · Source |
| CVE-2017-5421 | suse_vex | SUSE CVE CVE-2017-5421 | known affected: 1 recommended: 337 | 2026-08-27T01:35:05+00:00 | Vulnerability · Source |
| CVE-2017-5455 | suse_vex | SUSE CVE CVE-2017-5455 | known affected: 2 known not affected: 42 recommended: 393 | 2026-08-27T01:34:55+00:00 | Vulnerability · Source |