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-2017-3317 | suse_vex | SUSE CVE CVE-2017-3317 | known not affected: 93 recommended: 667 | 2026-07-26T00:47:35+00:00 | Vulnerability · Source |
| CVE-2017-3318 | suse_vex | SUSE CVE CVE-2017-3318 | known not affected: 93 recommended: 677 | 2026-07-26T00:47:33+00:00 | Vulnerability · Source |
| CVE-2017-3319 | suse_vex | SUSE CVE CVE-2017-3319 | known not affected: 93 | 2026-07-26T00:47:32+00:00 | Vulnerability · Source |
| CVE-2017-3320 | suse_vex | SUSE CVE CVE-2017-3320 | known not affected: 93 | 2026-07-26T00:47:30+00:00 | Vulnerability · Source |
| CVE-2017-3450 | suse_vex | SUSE CVE CVE-2017-3450 | known affected: 35 known not affected: 66 | 2026-07-26T00:47:29+00:00 | Vulnerability · Source |
| CVE-2017-3452 | suse_vex | SUSE CVE CVE-2017-3452 | known affected: 35 known not affected: 66 | 2026-07-26T00:47:28+00:00 | Vulnerability · Source |
| CVE-2017-3453 | suse_vex | SUSE CVE CVE-2017-3453 | known affected: 35 known not affected: 104 recommended: 639 | 2026-07-26T00:47:26+00:00 | Vulnerability · Source |
| CVE-2017-3456 | suse_vex | SUSE CVE CVE-2017-3456 | known affected: 35 known not affected: 104 recommended: 649 | 2026-07-26T00:47:25+00:00 | Vulnerability · Source |
| CVE-2017-3461 | suse_vex | SUSE CVE CVE-2017-3461 | known affected: 35 known not affected: 104 recommended: 28 | 2026-07-26T00:47:24+00:00 | Vulnerability · Source |
| CVE-2017-3463 | suse_vex | SUSE CVE CVE-2017-3463 | known affected: 35 known not affected: 104 recommended: 28 | 2026-07-26T00:47:22+00:00 | Vulnerability · Source |
| CVE-2017-3509 | suse_vex | SUSE CVE CVE-2017-3509 | known affected: 395 known not affected: 109 recommended: 732 | 2026-07-26T00:47:21+00:00 | Vulnerability · Source |
| CVE-2017-3512 | suse_vex | SUSE CVE CVE-2017-3512 | known affected: 1 known not affected: 109 recommended: 552 | 2026-07-26T00:47:19+00:00 | Vulnerability · Source |
| CVE-2017-3600 | suse_vex | SUSE CVE CVE-2017-3600 | known affected: 35 known not affected: 104 recommended: 36 | 2026-07-26T00:47:18+00:00 | Vulnerability · Source |
| CVE-2017-3633 | suse_vex | SUSE CVE CVE-2017-3633 | known affected: 1 known not affected: 64 | 2026-07-26T00:47:15+00:00 | Vulnerability · Source |
| CVE-2017-3637 | suse_vex | SUSE CVE CVE-2017-3637 | known affected: 1 known not affected: 64 | 2026-07-26T00:47:14+00:00 | Vulnerability · Source |
| CVE-2017-3640 | suse_vex | SUSE CVE CVE-2017-3640 | known affected: 1 known not affected: 64 | 2026-07-26T00:47:12+00:00 | Vulnerability · Source |
| CVE-2017-3641 | suse_vex | SUSE CVE CVE-2017-3641 | known affected: 35 known not affected: 104 recommended: 609 | 2026-07-26T00:47:11+00:00 | Vulnerability · Source |
| CVE-2017-3647 | suse_vex | SUSE CVE CVE-2017-3647 | known affected: 1 known not affected: 64 | 2026-07-26T00:47:09+00:00 | Vulnerability · Source |
| CVE-2017-3648 | suse_vex | SUSE CVE CVE-2017-3648 | known affected: 1 known not affected: 44 recommended: 28 | 2026-07-26T00:47:08+00:00 | Vulnerability · Source |
| CVE-2017-3731 | suse_vex | SUSE CVE CVE-2017-3731 | known affected: 386 known not affected: 329 recommended: 1047 | 2026-07-26T00:47:05+00:00 | Vulnerability · Source |
| CVE-2017-3735 | suse_vex | SUSE CVE CVE-2017-3735 | known affected: 360 known not affected: 478 recommended: 1014 | 2026-07-26T00:46:51+00:00 | Vulnerability · Source |
| CVE-2017-3738 | suse_vex | SUSE CVE CVE-2017-3738 | known affected: 320 known not affected: 398 recommended: 972 | 2026-07-26T00:46:49+00:00 | Vulnerability · Source |
| CVE-2017-5130 | suse_vex | SUSE CVE CVE-2017-5130 | recommended: 116 | 2026-07-26T00:46:46+00:00 | Vulnerability · Source |
| CVE-2017-5334 | suse_vex | SUSE CVE CVE-2017-5334 | known not affected: 82 recommended: 5 | 2026-07-26T00:46:42+00:00 | Vulnerability · Source |
| CVE-2017-5335 | suse_vex | SUSE CVE CVE-2017-5335 | known affected: 8 known not affected: 4 recommended: 176 | 2026-07-26T00:46:41+00:00 | Vulnerability · Source |
| CVE-2017-5341 | suse_vex | SUSE CVE CVE-2017-5341 | known affected: 320 recommended: 182 | 2026-07-26T00:46:40+00:00 | Vulnerability · Source |
| CVE-2017-5378 | suse_vex | SUSE CVE CVE-2017-5378 | known affected: 1 recommended: 416 | 2026-07-26T00:46:38+00:00 | Vulnerability · Source |
| CVE-2017-5380 | suse_vex | SUSE CVE CVE-2017-5380 | known affected: 1 recommended: 416 | 2026-07-26T00:46:37+00:00 | Vulnerability · Source |
| CVE-2017-5383 | suse_vex | SUSE CVE CVE-2017-5383 | known affected: 1 recommended: 416 | 2026-07-26T00:46:33+00:00 | Vulnerability · Source |
| CVE-2017-5387 | suse_vex | SUSE CVE CVE-2017-5387 | known affected: 1 known not affected: 38 recommended: 249 | 2026-07-26T00:46:30+00:00 | Vulnerability · Source |
| CVE-2017-5390 | suse_vex | SUSE CVE CVE-2017-5390 | known affected: 1 recommended: 416 | 2026-07-26T00:46:27+00:00 | Vulnerability · Source |
| CVE-2017-5393 | suse_vex | SUSE CVE CVE-2017-5393 | known affected: 1 known not affected: 38 recommended: 249 | 2026-07-26T00:46:26+00:00 | Vulnerability · Source |
| CVE-2017-5396 | suse_vex | SUSE CVE CVE-2017-5396 | known affected: 1 recommended: 416 | 2026-07-26T00:46:24+00:00 | Vulnerability · Source |
| CVE-2017-5400 | suse_vex | SUSE CVE CVE-2017-5400 | known affected: 1 recommended: 416 | 2026-07-26T00:46:23+00:00 | Vulnerability · Source |
| CVE-2017-5403 | suse_vex | SUSE CVE CVE-2017-5403 | known affected: 1 recommended: 333 | 2026-07-26T00:46:21+00:00 | Vulnerability · Source |
| CVE-2017-5407 | suse_vex | SUSE CVE CVE-2017-5407 | known affected: 1 recommended: 416 | 2026-07-26T00:46:16+00:00 | Vulnerability · Source |
| CVE-2017-5408 | suse_vex | SUSE CVE CVE-2017-5408 | known affected: 1 recommended: 416 | 2026-07-26T00:46:14+00:00 | Vulnerability · Source |
| CVE-2017-5418 | suse_vex | SUSE CVE CVE-2017-5418 | known affected: 1 recommended: 333 | 2026-07-26T00:46:11+00:00 | Vulnerability · Source |
| CVE-2017-5425 | suse_vex | SUSE CVE CVE-2017-5425 | known affected: 1 | 2026-07-26T00:46:09+00:00 | Vulnerability · Source |
| CVE-2017-5426 | suse_vex | SUSE CVE CVE-2017-5426 | known affected: 1 recommended: 333 | 2026-07-26T00:46:08+00:00 | Vulnerability · Source |
| CVE-2017-5445 | suse_vex | SUSE CVE CVE-2017-5445 | known not affected: 42 recommended: 770 | 2026-07-26T00:45:53+00:00 | Vulnerability · Source |
| CVE-2017-5449 | suse_vex | SUSE CVE CVE-2017-5449 | known affected: 2 known not affected: 42 recommended: 474 | 2026-07-26T00:45:50+00:00 | Vulnerability · Source |
| CVE-2017-5455 | suse_vex | SUSE CVE CVE-2017-5455 | known affected: 2 known not affected: 42 recommended: 389 | 2026-07-26T00:45:49+00:00 | Vulnerability · Source |
| CVE-2017-5459 | suse_vex | SUSE CVE CVE-2017-5459 | known not affected: 42 recommended: 770 | 2026-07-26T00:45:47+00:00 | Vulnerability · Source |
| CVE-2017-5469 | suse_vex | SUSE CVE CVE-2017-5469 | known not affected: 42 recommended: 770 | 2026-07-26T00:45:43+00:00 | Vulnerability · Source |
| CVE-2017-5506 | suse_vex | SUSE CVE CVE-2017-5506 | known affected: 1 known not affected: 14 recommended: 204 | 2026-07-26T00:45:36+00:00 | Vulnerability · Source |
| CVE-2017-5508 | suse_vex | SUSE CVE CVE-2017-5508 | known affected: 1 known not affected: 14 recommended: 204 | 2026-07-26T00:45:35+00:00 | Vulnerability · Source |
| CVE-2017-5509 | suse_vex | SUSE CVE CVE-2017-5509 | known not affected: 113 | 2026-07-26T00:45:34+00:00 | Vulnerability · Source |
| CVE-2017-5510 | suse_vex | SUSE CVE CVE-2017-5510 | known not affected: 49 recommended: 168 | 2026-07-26T00:45:33+00:00 | Vulnerability · Source |
| CVE-2017-5511 | suse_vex | SUSE CVE CVE-2017-5511 | known affected: 1 recommended: 218 | 2026-07-26T00:45:31+00:00 | Vulnerability · Source |