VEX records
Browse vendor VEX statements available in this Vulnerability-Lookup instance and pivot to the related vulnerability.
294458 VEX records
API response| Vulnerability | Source | Title | Product status | Imported | Links |
|---|---|---|---|---|---|
| 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-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-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-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 |
| CVE-2017-5526 | suse_vex | SUSE CVE CVE-2017-5526 | known affected: 420 known not affected: 231 recommended: 2011 | 2026-08-27T01:34:46+00:00 | Vulnerability · Source |
| CVE-2017-5648 | suse_vex | SUSE CVE CVE-2017-5648 | known affected: 440 known not affected: 141 recommended: 242 | 2026-08-27T01:34:41+00:00 | Vulnerability · Source |
| CVE-2017-5667 | suse_vex | SUSE CVE CVE-2017-5667 | known affected: 420 known not affected: 190 recommended: 1871 | 2026-08-27T01:34:39+00:00 | Vulnerability · Source |
| CVE-2017-5669 | suse_vex | SUSE CVE CVE-2017-5669 | known affected: 2 known not affected: 378 recommended: 233 | 2026-08-27T01:34:37+00:00 | Vulnerability · Source |
| CVE-2017-5735 | suse_vex | SUSE CVE CVE-2017-5735 | known affected: 29 recommended: 237 | 2026-08-27T01:34:32+00:00 | Vulnerability · Source |
| CVE-2017-5837 | suse_vex | SUSE CVE CVE-2017-5837 | known affected: 299 recommended: 1219 | 2026-08-27T01:34:29+00:00 | Vulnerability · Source |
| CVE-2017-5856 | suse_vex | SUSE CVE CVE-2017-5856 | known affected: 422 known not affected: 145 recommended: 1939 | 2026-08-27T01:34:25+00:00 | Vulnerability · Source |
| CVE-2017-5885 | suse_vex | SUSE CVE CVE-2017-5885 | known not affected: 408 recommended: 534 | 2026-08-27T01:34:23+00:00 | Vulnerability · Source |
| CVE-2017-5931 | suse_vex | SUSE CVE CVE-2017-5931 | known not affected: 283 recommended: 1681 | 2026-08-27T01:34:19+00:00 | Vulnerability · Source |
| CVE-2017-6469 | suse_vex | SUSE CVE CVE-2017-6469 | known affected: 73 recommended: 450 | 2026-08-27T01:34:06+00:00 | Vulnerability · Source |
| CVE-2017-6474 | suse_vex | SUSE CVE CVE-2017-6474 | known affected: 73 recommended: 450 | 2026-08-27T01:34:03+00:00 | Vulnerability · Source |
| CVE-2017-7049 | suse_vex | SUSE CVE CVE-2017-7049 | known affected: 12 known not affected: 329 recommended: 945 | 2026-08-27T01:33:47+00:00 | Vulnerability · Source |
| CVE-2017-7090 | suse_vex | SUSE CVE CVE-2017-7090 | known not affected: 87 recommended: 945 | 2026-08-27T01:33:40+00:00 | Vulnerability · Source |
| CVE-2017-7476 | suse_vex | SUSE CVE CVE-2017-7476 | known affected: 320 known not affected: 444 recommended: 618 | 2026-08-27T01:33:17+00:00 | Vulnerability · Source |
| CVE-2017-7485 | suse_vex | SUSE CVE CVE-2017-7485 | recommended: 142 | 2026-08-27T01:33:15+00:00 | Vulnerability · Source |
| CVE-2017-7487 | suse_vex | SUSE CVE CVE-2017-7487 | known affected: 14 known not affected: 422 recommended: 432 | 2026-08-27T01:33:13+00:00 | Vulnerability · Source |
| CVE-2017-7506 | suse_vex | SUSE CVE CVE-2017-7506 | known affected: 5 recommended: 42 | 2026-08-27T01:33:10+00:00 | Vulnerability · Source |
| CVE-2017-7520 | suse_vex | SUSE CVE CVE-2017-7520 | known affected: 31 known not affected: 60 recommended: 39 | 2026-08-27T01:33:08+00:00 | Vulnerability · Source |
| CVE-2017-7533 | suse_vex | SUSE CVE CVE-2017-7533 | known affected: 125 known not affected: 333 recommended: 468 | 2026-08-27T01:33:05+00:00 | Vulnerability · Source |