VEX records
Browse vendor VEX statements available in this Vulnerability-Lookup instance and pivot to the related vulnerability.
283120 VEX records
API response| Vulnerability | Source | Title | Product status | Imported | Links |
|---|---|---|---|---|---|
| CVE-2016-5297 | suse_vex | SUSE CVE CVE-2016-5297 | known affected: 2 recommended: 617 | 2026-07-19T18:38:10+00:00 | Vulnerability · Source |
| CVE-2016-5299 | suse_vex | SUSE CVE CVE-2016-5299 | known affected: 1 known not affected: 34 recommended: 250 | 2026-07-19T18:38:09+00:00 | Vulnerability · Source |
| CVE-2016-5300 | suse_vex | SUSE CVE CVE-2016-5300 | known affected: 320 known not affected: 24 recommended: 433 | 2026-07-19T18:38:08+00:00 | Vulnerability · Source |
| CVE-2016-5337 | suse_vex | SUSE CVE CVE-2016-5337 | known affected: 396 known not affected: 138 recommended: 1783 | 2026-07-19T18:38:06+00:00 | Vulnerability · Source |
| CVE-2016-5338 | suse_vex | SUSE CVE CVE-2016-5338 | known affected: 323 known not affected: 420 recommended: 2251 | 2026-07-19T18:38:05+00:00 | Vulnerability · Source |
| CVE-2016-5355 | suse_vex | SUSE CVE CVE-2016-5355 | known not affected: 115 recommended: 519 | 2026-07-19T18:38:03+00:00 | Vulnerability · Source |
| CVE-2016-5358 | suse_vex | SUSE CVE CVE-2016-5358 | known not affected: 115 recommended: 519 | 2026-07-19T18:38:02+00:00 | Vulnerability · Source |
| CVE-2016-5410 | suse_vex | SUSE CVE CVE-2016-5410 | known affected: 394 recommended: 390 | 2026-07-19T18:38:01+00:00 | Vulnerability · Source |
| CVE-2016-5416 | suse_vex | SUSE CVE CVE-2016-5416 | recommended: 146 | 2026-07-19T18:38:00+00:00 | Vulnerability · Source |
| CVE-2016-5417 | suse_vex | SUSE CVE CVE-2016-5417 | known affected: 320 known not affected: 521 recommended: 1013 | 2026-07-19T18:37:58+00:00 | Vulnerability · Source |
| CVE-2016-5440 | suse_vex | SUSE CVE CVE-2016-5440 | known affected: 1 known not affected: 37 recommended: 643 | 2026-07-19T18:37:57+00:00 | Vulnerability · Source |
| CVE-2016-5735 | suse_vex | SUSE CVE CVE-2016-5735 | known affected: 320 known not affected: 18 recommended: 330 | 2026-07-19T18:37:55+00:00 | Vulnerability · Source |
| CVE-2016-5759 | suse_vex | SUSE CVE CVE-2016-5759 | known affected: 320 known not affected: 16 recommended: 157 | 2026-07-19T18:37:54+00:00 | Vulnerability · Source |
| CVE-2016-5766 | suse_vex | SUSE CVE CVE-2016-5766 | known affected: 944 known not affected: 970 recommended: 1554 | 2026-07-19T18:37:52+00:00 | Vulnerability · Source |
| CVE-2016-5875 | suse_vex | SUSE CVE CVE-2016-5875 | known affected: 446 recommended: 286 | 2026-07-19T18:37:51+00:00 | Vulnerability · Source |
| CVE-2016-6131 | suse_vex | SUSE CVE CVE-2016-6131 | known affected: 184 known not affected: 302 recommended: 54 | 2026-07-19T18:37:50+00:00 | Vulnerability · Source |
| CVE-2016-6207 | suse_vex | SUSE CVE CVE-2016-6207 | known affected: 1519 known not affected: 382 recommended: 1325 | 2026-07-19T18:37:48+00:00 | Vulnerability · Source |
| CVE-2016-6210 | suse_vex | SUSE CVE CVE-2016-6210 | known affected: 322 known not affected: 41 recommended: 497 | 2026-07-19T18:37:47+00:00 | Vulnerability · Source |
| CVE-2016-6223 | suse_vex | SUSE CVE CVE-2016-6223 | known affected: 449 recommended: 257 | 2026-07-19T18:37:46+00:00 | Vulnerability · Source |
| CVE-2016-6304 | suse_vex | SUSE CVE CVE-2016-6304 | known affected: 325 known not affected: 333 recommended: 1229 | 2026-07-19T18:37:44+00:00 | Vulnerability · Source |
| CVE-2016-6306 | suse_vex | SUSE CVE CVE-2016-6306 | known affected: 325 known not affected: 331 recommended: 1223 | 2026-07-19T18:37:43+00:00 | Vulnerability · Source |
| CVE-2016-6313 | suse_vex | SUSE CVE CVE-2016-6313 | known affected: 321 known not affected: 10 recommended: 466 | 2026-07-19T18:37:41+00:00 | Vulnerability · Source |
| CVE-2016-6321 | suse_vex | SUSE CVE CVE-2016-6321 | known affected: 322 known not affected: 55 recommended: 305 | 2026-07-19T18:37:40+00:00 | Vulnerability · Source |
| CVE-2016-6328 | suse_vex | SUSE CVE CVE-2016-6328 | known affected: 24 known not affected: 14 recommended: 211 | 2026-07-19T18:37:39+00:00 | Vulnerability · Source |
| CVE-2016-6354 | suse_vex | SUSE CVE CVE-2016-6354 | known affected: 3 known not affected: 39 recommended: 935 | 2026-07-19T18:37:37+00:00 | Vulnerability · Source |
| CVE-2016-6509 | suse_vex | SUSE CVE CVE-2016-6509 | known affected: 63 recommended: 519 | 2026-07-19T18:37:36+00:00 | Vulnerability · Source |
| CVE-2016-6581 | suse_vex | SUSE CVE CVE-2016-6581 | known not affected: 16 recommended: 32 | 2026-07-19T18:37:35+00:00 | Vulnerability · Source |
| CVE-2016-6662 | suse_vex | SUSE CVE CVE-2016-6662 | known affected: 1 known not affected: 209 recommended: 633 | 2026-07-19T18:37:34+00:00 | Vulnerability · Source |
| CVE-2016-6833 | suse_vex | SUSE CVE CVE-2016-6833 | known affected: 1 known not affected: 150 recommended: 1759 | 2026-07-19T18:37:32+00:00 | Vulnerability · Source |
| CVE-2016-6836 | suse_vex | SUSE CVE CVE-2016-6836 | known affected: 395 known not affected: 150 recommended: 1806 | 2026-07-19T18:37:30+00:00 | Vulnerability · Source |
| CVE-2016-7055 | suse_vex | SUSE CVE CVE-2016-7055 | known affected: 320 known not affected: 337 recommended: 958 | 2026-07-19T18:37:29+00:00 | Vulnerability · Source |
| CVE-2016-7056 | suse_vex | SUSE CVE CVE-2016-7056 | known affected: 325 known not affected: 283 recommended: 947 | 2026-07-19T18:37:27+00:00 | Vulnerability · Source |
| CVE-2016-7076 | suse_vex | SUSE CVE CVE-2016-7076 | known affected: 322 known not affected: 83 recommended: 315 | 2026-07-19T18:37:26+00:00 | Vulnerability · Source |
| CVE-2016-7155 | suse_vex | SUSE CVE CVE-2016-7155 | known not affected: 138 recommended: 1703 | 2026-07-19T18:37:24+00:00 | Vulnerability · Source |
| CVE-2016-7157 | suse_vex | SUSE CVE CVE-2016-7157 | known affected: 394 known not affected: 161 recommended: 1687 | 2026-07-19T18:37:23+00:00 | Vulnerability · Source |
| CVE-2016-7167 | suse_vex | SUSE CVE CVE-2016-7167 | known affected: 334 known not affected: 50 recommended: 440 | 2026-07-19T18:37:21+00:00 | Vulnerability · Source |
| CVE-2016-7177 | suse_vex | SUSE CVE CVE-2016-7177 | known affected: 1 recommended: 562 | 2026-07-19T18:37:20+00:00 | Vulnerability · Source |
| CVE-2016-7422 | suse_vex | SUSE CVE CVE-2016-7422 | known affected: 407 known not affected: 149 recommended: 1703 | 2026-07-19T18:37:18+00:00 | Vulnerability · Source |
| CVE-2016-7592 | suse_vex | SUSE CVE CVE-2016-7592 | known not affected: 87 recommended: 912 | 2026-07-19T18:37:17+00:00 | Vulnerability · Source |
| CVE-2016-7598 | suse_vex | SUSE CVE CVE-2016-7598 | known not affected: 87 recommended: 924 | 2026-07-19T18:37:15+00:00 | Vulnerability · Source |
| CVE-2016-7632 | suse_vex | SUSE CVE CVE-2016-7632 | known not affected: 87 recommended: 912 | 2026-07-19T18:37:14+00:00 | Vulnerability · Source |
| CVE-2016-7929 | suse_vex | SUSE CVE CVE-2016-7929 | known affected: 320 recommended: 176 | 2026-07-19T18:37:13+00:00 | Vulnerability · Source |
| CVE-2016-7930 | suse_vex | SUSE CVE CVE-2016-7930 | known affected: 320 recommended: 176 | 2026-07-19T18:37:11+00:00 | Vulnerability · Source |
| CVE-2016-7931 | suse_vex | SUSE CVE CVE-2016-7931 | known affected: 320 recommended: 180 | 2026-07-19T18:37:10+00:00 | Vulnerability · Source |
| CVE-2016-7933 | suse_vex | SUSE CVE CVE-2016-7933 | known affected: 320 recommended: 176 | 2026-07-19T18:37:09+00:00 | Vulnerability · Source |
| CVE-2016-7935 | suse_vex | SUSE CVE CVE-2016-7935 | known affected: 320 recommended: 180 | 2026-07-19T18:37:07+00:00 | Vulnerability · Source |
| CVE-2016-7939 | suse_vex | SUSE CVE CVE-2016-7939 | known affected: 320 recommended: 180 | 2026-07-19T18:37:06+00:00 | Vulnerability · Source |
| CVE-2016-7948 | suse_vex | SUSE CVE CVE-2016-7948 | known not affected: 51 recommended: 423 | 2026-07-19T18:37:05+00:00 | Vulnerability · Source |
| CVE-2016-7970 | suse_vex | SUSE CVE CVE-2016-7970 | recommended: 137 | 2026-07-19T18:37:04+00:00 | Vulnerability · Source |
| CVE-2016-7975 | suse_vex | SUSE CVE CVE-2016-7975 | known affected: 320 recommended: 180 | 2026-07-19T18:37:02+00:00 | Vulnerability · Source |