VEX records
Browse vendor VEX statements available in this Vulnerability-Lookup instance and pivot to the related vulnerability.
287962 VEX records
API response| Vulnerability | Source | Title | Product status | Imported | Links |
|---|---|---|---|---|---|
| CVE-2016-5630 | suse_vex | SUSE CVE CVE-2016-5630 | known affected: 1 known not affected: 93 recommended: 10 | 2026-07-31T01:48:35+00:00 | Vulnerability · Source |
| CVE-2016-5691 | suse_vex | SUSE CVE CVE-2016-5691 | known affected: 95 recommended: 202 | 2026-07-31T01:48:33+00:00 | Vulnerability · Source |
| CVE-2016-5825 | suse_vex | SUSE CVE CVE-2016-5825 | known affected: 1 known not affected: 41 recommended: 14 | 2026-07-31T01:48:30+00:00 | Vulnerability · Source |
| CVE-2016-6261 | suse_vex | SUSE CVE CVE-2016-6261 | known affected: 321 recommended: 808 | 2026-07-31T01:48:27+00:00 | Vulnerability · Source |
| CVE-2016-6323 | suse_vex | SUSE CVE CVE-2016-6323 | known affected: 320 known not affected: 84 recommended: 1007 | 2026-07-31T01:48:24+00:00 | Vulnerability · Source |
| CVE-2016-6352 | suse_vex | SUSE CVE CVE-2016-6352 | known affected: 397 known not affected: 204 recommended: 658 | 2026-07-31T01:48:22+00:00 | Vulnerability · Source |
| CVE-2016-6506 | suse_vex | SUSE CVE CVE-2016-6506 | known affected: 75 recommended: 91 | 2026-07-31T01:48:21+00:00 | Vulnerability · Source |
| CVE-2016-6507 | suse_vex | SUSE CVE CVE-2016-6507 | known affected: 75 recommended: 91 | 2026-07-31T01:48:19+00:00 | Vulnerability · Source |
| CVE-2016-6513 | suse_vex | SUSE CVE CVE-2016-6513 | known not affected: 71 recommended: 442 | 2026-07-31T01:48:17+00:00 | Vulnerability · Source |
| CVE-2016-6836 | suse_vex | SUSE CVE CVE-2016-6836 | known affected: 395 known not affected: 178 recommended: 1878 | 2026-07-31T01:48:14+00:00 | Vulnerability · Source |
| CVE-2016-7094 | suse_vex | SUSE CVE CVE-2016-7094 | known affected: 322 known not affected: 18 recommended: 549 | 2026-07-31T01:48:12+00:00 | Vulnerability · Source |
| CVE-2016-7176 | suse_vex | SUSE CVE CVE-2016-7176 | known affected: 1 recommended: 586 | 2026-07-31T01:48:10+00:00 | Vulnerability · Source |
| CVE-2016-7177 | suse_vex | SUSE CVE CVE-2016-7177 | known affected: 1 recommended: 586 | 2026-07-31T01:48:09+00:00 | Vulnerability · Source |
| CVE-2016-7179 | suse_vex | SUSE CVE CVE-2016-7179 | known affected: 1 recommended: 586 | 2026-07-31T01:48:07+00:00 | Vulnerability · Source |
| CVE-2016-7448 | suse_vex | SUSE CVE CVE-2016-7448 | known affected: 3 known not affected: 103 recommended: 14 | 2026-07-31T01:48:05+00:00 | Vulnerability · Source |
| CVE-2016-7530 | suse_vex | SUSE CVE CVE-2016-7530 | known affected: 1 recommended: 206 | 2026-07-31T01:48:04+00:00 | Vulnerability · Source |
| CVE-2016-7535 | suse_vex | SUSE CVE CVE-2016-7535 | known affected: 95 known not affected: 2 recommended: 168 | 2026-07-31T01:48:02+00:00 | Vulnerability · Source |
| CVE-2016-7545 | suse_vex | SUSE CVE CVE-2016-7545 | known affected: 394 known not affected: 17 recommended: 373 | 2026-07-31T01:48:00+00:00 | Vulnerability · Source |
| CVE-2016-7589 | suse_vex | SUSE CVE CVE-2016-7589 | known not affected: 87 recommended: 939 | 2026-07-31T01:47:58+00:00 | Vulnerability · Source |
| CVE-2016-7592 | suse_vex | SUSE CVE CVE-2016-7592 | known not affected: 87 recommended: 927 | 2026-07-31T01:47:57+00:00 | Vulnerability · Source |
| CVE-2016-7796 | suse_vex | SUSE CVE CVE-2016-7796 | known not affected: 196 recommended: 90 | 2026-07-31T01:47:55+00:00 | Vulnerability · Source |
| CVE-2016-7917 | suse_vex | SUSE CVE CVE-2016-7917 | known affected: 12 known not affected: 107 recommended: 89 | 2026-07-31T01:47:53+00:00 | Vulnerability · Source |
| CVE-2016-7952 | suse_vex | SUSE CVE CVE-2016-7952 | known affected: 36 recommended: 270 | 2026-07-31T01:47:51+00:00 | Vulnerability · Source |
| CVE-2016-7957 | suse_vex | SUSE CVE CVE-2016-7957 | known not affected: 92 | 2026-07-31T01:47:50+00:00 | Vulnerability · Source |
| CVE-2016-7974 | suse_vex | SUSE CVE CVE-2016-7974 | known affected: 320 recommended: 186 | 2026-07-31T01:47:48+00:00 | Vulnerability · Source |
| CVE-2016-8399 | suse_vex | SUSE CVE CVE-2016-8399 | known not affected: 29 recommended: 315 | 2026-07-31T01:47:46+00:00 | Vulnerability · Source |
| CVE-2016-8624 | suse_vex | SUSE CVE CVE-2016-8624 | known affected: 340 known not affected: 21 recommended: 449 | 2026-07-31T01:47:44+00:00 | Vulnerability · Source |
| CVE-2016-8655 | suse_vex | SUSE CVE CVE-2016-8655 | known not affected: 510 recommended: 365 | 2026-07-31T01:47:42+00:00 | Vulnerability · Source |
| CVE-2016-8705 | suse_vex | SUSE CVE CVE-2016-8705 | known not affected: 14 recommended: 111 | 2026-07-31T01:47:41+00:00 | Vulnerability · Source |
| CVE-2016-8743 | suse_vex | SUSE CVE CVE-2016-8743 | known affected: 87 known not affected: 24 recommended: 516 | 2026-07-31T01:47:39+00:00 | Vulnerability · Source |
| CVE-2016-8747 | suse_vex | SUSE CVE CVE-2016-8747 | known not affected: 54 | 2026-07-31T01:47:38+00:00 | Vulnerability · Source |
| CVE-2016-8866 | suse_vex | SUSE CVE CVE-2016-8866 | known affected: 1 recommended: 218 | 2026-07-31T01:47:36+00:00 | Vulnerability · Source |
| CVE-2016-9061 | suse_vex | SUSE CVE CVE-2016-9061 | known affected: 1 known not affected: 38 recommended: 250 | 2026-07-31T01:47:34+00:00 | Vulnerability · Source |
| CVE-2016-9147 | suse_vex | SUSE CVE CVE-2016-9147 | known affected: 63 known not affected: 118 recommended: 893 | 2026-07-31T01:47:32+00:00 | Vulnerability · Source |
| CVE-2016-9311 | suse_vex | SUSE CVE CVE-2016-9311 | known affected: 30 recommended: 114 | 2026-07-31T01:47:31+00:00 | Vulnerability · Source |
| CVE-2016-9382 | suse_vex | SUSE CVE CVE-2016-9382 | known affected: 334 known not affected: 6 recommended: 556 | 2026-07-31T01:47:29+00:00 | Vulnerability · Source |
| CVE-2016-9388 | suse_vex | SUSE CVE CVE-2016-9388 | known affected: 37 recommended: 194 | 2026-07-31T01:47:28+00:00 | Vulnerability · Source |
| CVE-2016-9429 | suse_vex | SUSE CVE CVE-2016-9429 | known not affected: 15 | 2026-07-31T01:47:26+00:00 | Vulnerability · Source |
| CVE-2016-9446 | suse_vex | SUSE CVE CVE-2016-9446 | known affected: 185 recommended: 593 | 2026-07-31T01:47:25+00:00 | Vulnerability · Source |
| CVE-2016-9539 | suse_vex | SUSE CVE CVE-2016-9539 | known not affected: 149 | 2026-07-31T01:47:23+00:00 | Vulnerability · Source |
| CVE-2016-9602 | suse_vex | SUSE CVE CVE-2016-9602 | known affected: 394 known not affected: 136 recommended: 1812 | 2026-07-31T01:47:21+00:00 | Vulnerability · Source |
| CVE-2016-9807 | suse_vex | SUSE CVE CVE-2016-9807 | known affected: 32 recommended: 86 | 2026-07-31T01:47:19+00:00 | Vulnerability · Source |
| CVE-2016-9841 | suse_vex | SUSE CVE CVE-2016-9841 | known affected: 201 known not affected: 278 recommended: 856 | 2026-07-31T01:47:17+00:00 | Vulnerability · Source |
| CVE-2016-9898 | suse_vex | SUSE CVE CVE-2016-9898 | known affected: 1 recommended: 418 | 2026-07-31T01:47:15+00:00 | Vulnerability · Source |
| CVE-2016-9960 | suse_vex | SUSE CVE CVE-2016-9960 | recommended: 153 | 2026-07-31T01:47:13+00:00 | Vulnerability · Source |
| CVE-2016-9969 | suse_vex | SUSE CVE CVE-2016-9969 | known affected: 100 known not affected: 359 recommended: 10 | 2026-07-31T01:47:11+00:00 | Vulnerability · Source |
| CVE-2016-10011 | suse_vex | SUSE CVE CVE-2016-10011 | known affected: 337 recommended: 518 | 2026-07-31T01:47:09+00:00 | Vulnerability · Source |
| CVE-2016-10059 | suse_vex | SUSE CVE CVE-2016-10059 | known affected: 1 recommended: 218 | 2026-07-31T01:47:08+00:00 | Vulnerability · Source |
| CVE-2016-10070 | suse_vex | SUSE CVE CVE-2016-10070 | known affected: 1 recommended: 218 | 2026-07-31T01:47:06+00:00 | Vulnerability · Source |
| CVE-2016-10197 | suse_vex | SUSE CVE CVE-2016-10197 | known affected: 30 recommended: 39 | 2026-07-31T01:47:04+00:00 | Vulnerability · Source |