VEX records
Browse vendor VEX statements available in this Vulnerability-Lookup instance and pivot to the related vulnerability.
285064 VEX records
API response| Vulnerability | Source | Title | Product status | Imported | Links |
|---|---|---|---|---|---|
| CVE-2015-4836 | suse_vex | SUSE CVE CVE-2015-4836 | known affected: 13 known not affected: 117 recommended: 711 | 2026-07-26T17:01:56+00:00 | Vulnerability · Source |
| CVE-2015-4893 | suse_vex | SUSE CVE CVE-2015-4893 | known affected: 489 known not affected: 289 recommended: 771 | 2026-07-26T17:01:54+00:00 | Vulnerability · Source |
| CVE-2015-5225 | suse_vex | SUSE CVE CVE-2015-5225 | known affected: 394 known not affected: 219 recommended: 1776 | 2026-07-26T17:01:52+00:00 | Vulnerability · Source |
| CVE-2015-5307 | suse_vex | SUSE CVE CVE-2015-5307 | known affected: 323 known not affected: 476 recommended: 894 | 2026-07-26T17:01:50+00:00 | Vulnerability · Source |
| CVE-2015-5809 | suse_vex | SUSE CVE CVE-2015-5809 | known not affected: 18 recommended: 238 | 2026-07-26T17:01:48+00:00 | Vulnerability · Source |
| CVE-2015-6525 | suse_vex | SUSE CVE CVE-2015-6525 | known not affected: 172 | 2026-07-26T17:01:46+00:00 | Vulnerability · Source |
| CVE-2015-7215 | suse_vex | SUSE CVE CVE-2015-7215 | known affected: 2 recommended: 255 | 2026-07-26T17:01:44+00:00 | Vulnerability · Source |
| CVE-2015-7835 | suse_vex | SUSE CVE CVE-2015-7835 | known affected: 321 known not affected: 12 recommended: 567 | 2026-07-26T17:01:42+00:00 | Vulnerability · Source |
| CVE-2015-7990 | suse_vex | SUSE CVE CVE-2015-7990 | known affected: 26 known not affected: 384 recommended: 335 | 2026-07-26T17:01:40+00:00 | Vulnerability · Source |
| CVE-2015-8721 | suse_vex | SUSE CVE CVE-2015-8721 | known affected: 86 recommended: 549 | 2026-07-26T17:01:38+00:00 | Vulnerability · Source |
| CVE-2015-8730 | suse_vex | SUSE CVE CVE-2015-8730 | known affected: 86 recommended: 549 | 2026-07-26T17:01:36+00:00 | Vulnerability · Source |
| CVE-2015-8731 | suse_vex | SUSE CVE CVE-2015-8731 | known affected: 86 recommended: 549 | 2026-07-26T17:01:35+00:00 | Vulnerability · Source |
| CVE-2015-8743 | suse_vex | SUSE CVE CVE-2015-8743 | known affected: 323 known not affected: 174 recommended: 2341 | 2026-07-26T17:01:32+00:00 | Vulnerability · Source |
| CVE-2015-8805 | suse_vex | SUSE CVE CVE-2015-8805 | known affected: 320 recommended: 505 | 2026-07-26T17:01:31+00:00 | Vulnerability · Source |
| CVE-2015-8870 | suse_vex | SUSE CVE CVE-2015-8870 | known not affected: 28 recommended: 26 | 2026-07-26T17:01:29+00:00 | Vulnerability · Source |
| CVE-2015-8920 | suse_vex | SUSE CVE CVE-2015-8920 | known affected: 31 recommended: 55 | 2026-07-26T17:01:27+00:00 | Vulnerability · Source |
| CVE-2016-0686 | suse_vex | SUSE CVE CVE-2016-0686 | known affected: 506 known not affected: 93 recommended: 788 | 2026-07-26T17:01:25+00:00 | Vulnerability · Source |
| CVE-2016-0728 | suse_vex | SUSE CVE CVE-2016-0728 | known affected: 30 known not affected: 235 recommended: 361 | 2026-07-26T17:01:23+00:00 | Vulnerability · Source |
| CVE-2016-1248 | suse_vex | SUSE CVE CVE-2016-1248 | known affected: 404 recommended: 129 | 2026-07-26T17:01:21+00:00 | Vulnerability · Source |
| CVE-2016-1908 | suse_vex | SUSE CVE CVE-2016-1908 | known affected: 2 recommended: 107 | 2026-07-26T17:01:19+00:00 | Vulnerability · Source |
| CVE-2016-1930 | suse_vex | SUSE CVE CVE-2016-1930 | known affected: 1 recommended: 644 | 2026-07-26T17:01:17+00:00 | Vulnerability · Source |
| CVE-2016-1942 | suse_vex | SUSE CVE CVE-2016-1942 | known affected: 21 recommended: 250 | 2026-07-26T17:01:16+00:00 | Vulnerability · Source |
| CVE-2016-1960 | suse_vex | SUSE CVE CVE-2016-1960 | known affected: 2 recommended: 648 | 2026-07-26T17:01:14+00:00 | Vulnerability · Source |
| CVE-2016-1962 | suse_vex | SUSE CVE CVE-2016-1962 | known affected: 2 recommended: 642 | 2026-07-26T17:01:12+00:00 | Vulnerability · Source |
| CVE-2016-2807 | suse_vex | SUSE CVE CVE-2016-2807 | known affected: 2 recommended: 500 | 2026-07-26T17:01:09+00:00 | Vulnerability · Source |
| CVE-2016-3426 | suse_vex | SUSE CVE CVE-2016-3426 | known affected: 112 known not affected: 93 recommended: 692 | 2026-07-26T17:01:07+00:00 | Vulnerability · Source |
| CVE-2016-4052 | suse_vex | SUSE CVE CVE-2016-4052 | known affected: 394 known not affected: 55 recommended: 49 | 2026-07-26T17:01:05+00:00 | Vulnerability · Source |
| CVE-2016-4470 | suse_vex | SUSE CVE CVE-2016-4470 | known affected: 50 known not affected: 493 recommended: 548 | 2026-07-26T17:01:02+00:00 | Vulnerability · Source |
| CVE-2016-4797 | suse_vex | SUSE CVE CVE-2016-4797 | known not affected: 143 recommended: 20 | 2026-07-26T17:01:00+00:00 | Vulnerability · Source |
| CVE-2016-4956 | suse_vex | SUSE CVE CVE-2016-4956 | known affected: 31 recommended: 109 | 2026-07-26T17:00:59+00:00 | Vulnerability · Source |
| CVE-2016-5104 | suse_vex | SUSE CVE CVE-2016-5104 | known not affected: 88 recommended: 383 | 2026-07-26T17:00:57+00:00 | Vulnerability · Source |
| CVE-2016-5276 | suse_vex | SUSE CVE CVE-2016-5276 | known affected: 5 recommended: 332 | 2026-07-26T17:00:55+00:00 | Vulnerability · Source |
| CVE-2016-5299 | suse_vex | SUSE CVE CVE-2016-5299 | known affected: 1 known not affected: 38 recommended: 250 | 2026-07-26T17:00:54+00:00 | Vulnerability · Source |
| CVE-2016-5652 | suse_vex | SUSE CVE CVE-2016-5652 | known affected: 394 recommended: 302 | 2026-07-26T17:00:51+00:00 | Vulnerability · Source |
| CVE-2016-5728 | suse_vex | SUSE CVE CVE-2016-5728 | known not affected: 22 | 2026-07-26T17:00:50+00:00 | Vulnerability · Source |
| CVE-2016-6128 | suse_vex | SUSE CVE CVE-2016-6128 | known affected: 1476 known not affected: 1295 recommended: 1329 | 2026-07-26T17:00:48+00:00 | Vulnerability · Source |
| CVE-2016-6509 | suse_vex | SUSE CVE CVE-2016-6509 | known affected: 75 recommended: 533 | 2026-07-26T17:00:46+00:00 | Vulnerability · Source |
| CVE-2016-7154 | suse_vex | SUSE CVE CVE-2016-7154 | known affected: 1 known not affected: 27 recommended: 34 | 2026-07-26T17:00:43+00:00 | Vulnerability · Source |
| CVE-2016-7180 | suse_vex | SUSE CVE CVE-2016-7180 | known affected: 1 recommended: 586 | 2026-07-26T17:00:42+00:00 | Vulnerability · Source |
| CVE-2016-7445 | suse_vex | SUSE CVE CVE-2016-7445 | recommended: 137 | 2026-07-26T17:00:40+00:00 | Vulnerability · Source |
| CVE-2016-7534 | suse_vex | SUSE CVE CVE-2016-7534 | known affected: 94 known not affected: 39 recommended: 132 | 2026-07-26T17:00:38+00:00 | Vulnerability · Source |
| CVE-2016-7932 | suse_vex | SUSE CVE CVE-2016-7932 | known affected: 320 recommended: 182 | 2026-07-26T17:00:36+00:00 | Vulnerability · Source |
| CVE-2016-7937 | suse_vex | SUSE CVE CVE-2016-7937 | known affected: 320 recommended: 186 | 2026-07-26T17:00:35+00:00 | Vulnerability · Source |
| CVE-2016-7945 | suse_vex | SUSE CVE CVE-2016-7945 | known affected: 36 recommended: 270 | 2026-07-26T17:00:33+00:00 | Vulnerability · Source |
| CVE-2016-7993 | suse_vex | SUSE CVE CVE-2016-7993 | known affected: 320 recommended: 186 | 2026-07-26T17:00:32+00:00 | Vulnerability · Source |
| CVE-2016-7997 | suse_vex | SUSE CVE CVE-2016-7997 | known affected: 97 recommended: 190 | 2026-07-26T17:00:30+00:00 | Vulnerability · Source |
| CVE-2016-8617 | suse_vex | SUSE CVE CVE-2016-8617 | known affected: 340 known not affected: 21 recommended: 449 | 2026-07-26T17:00:28+00:00 | Vulnerability · Source |
| CVE-2016-8635 | suse_vex | SUSE CVE CVE-2016-8635 | known affected: 1 recommended: 519 | 2026-07-26T17:00:27+00:00 | Vulnerability · Source |
| CVE-2016-8885 | suse_vex | SUSE CVE CVE-2016-8885 | known affected: 1 recommended: 204 | 2026-07-26T17:00:25+00:00 | Vulnerability · Source |
| CVE-2016-9440 | suse_vex | SUSE CVE CVE-2016-9440 | known affected: 1 recommended: 87 | 2026-07-26T17:00:22+00:00 | Vulnerability · Source |