VEX records
Browse vendor VEX statements available in this Vulnerability-Lookup instance and pivot to the related vulnerability.
291911 VEX records
API response| Vulnerability | Source | Title | Product status | Imported | Links |
|---|---|---|---|---|---|
| CVE-2017-13221 | suse_vex | SUSE CVE CVE-2017-13221 | known not affected: 48 | 2026-08-01T23:36:10+00:00 | Vulnerability · Source |
| CVE-2017-14160 | suse_vex | SUSE CVE CVE-2017-14160 | known affected: 516 known not affected: 120 recommended: 367 | 2026-08-01T23:36:06+00:00 | Vulnerability · Source |
| CVE-2017-14341 | suse_vex | SUSE CVE CVE-2017-14341 | known affected: 94 recommended: 186 | 2026-08-01T23:36:04+00:00 | Vulnerability · Source |
| CVE-2017-14342 | suse_vex | SUSE CVE CVE-2017-14342 | known affected: 94 recommended: 186 | 2026-08-01T23:36:03+00:00 | Vulnerability · Source |
| CVE-2017-14861 | suse_vex | SUSE CVE CVE-2017-14861 | known affected: 4 known not affected: 53 | 2026-08-01T23:36:01+00:00 | Vulnerability · Source |
| CVE-2017-14954 | suse_vex | SUSE CVE CVE-2017-14954 | known not affected: 28 | 2026-08-01T23:36:00+00:00 | Vulnerability · Source |
| CVE-2017-15085 | suse_vex | SUSE CVE CVE-2017-15085 | known affected: 534 known not affected: 263 | 2026-08-01T23:35:59+00:00 | Vulnerability · Source |
| CVE-2017-15086 | suse_vex | SUSE CVE CVE-2017-15086 | known affected: 533 known not affected: 355 | 2026-08-01T23:35:57+00:00 | Vulnerability · Source |
| CVE-2017-15306 | suse_vex | SUSE CVE CVE-2017-15306 | known not affected: 14 | 2026-08-01T23:35:55+00:00 | Vulnerability · Source |
| CVE-2017-15631 | suse_vex | SUSE CVE CVE-2017-15631 | known not affected: 15 recommended: 62 | 2026-08-01T23:35:54+00:00 | Vulnerability · Source |
| CVE-2017-15868 | suse_vex | SUSE CVE CVE-2017-15868 | known affected: 16 known not affected: 374 recommended: 260 | 2026-08-01T23:35:52+00:00 | Vulnerability · Source |
| CVE-2017-15930 | suse_vex | SUSE CVE CVE-2017-15930 | known affected: 94 recommended: 186 | 2026-08-01T23:35:51+00:00 | Vulnerability · Source |
| CVE-2017-16650 | suse_vex | SUSE CVE CVE-2017-16650 | known affected: 21 known not affected: 304 recommended: 373 | 2026-08-01T23:35:47+00:00 | Vulnerability · Source |
| CVE-2017-17558 | suse_vex | SUSE CVE CVE-2017-17558 | known affected: 23 known not affected: 569 recommended: 514 | 2026-08-01T23:35:44+00:00 | Vulnerability · Source |
| CVE-2017-17669 | suse_vex | SUSE CVE CVE-2017-17669 | known not affected: 22 recommended: 23 | 2026-08-01T23:35:43+00:00 | Vulnerability · Source |
| CVE-2017-18184 | suse_vex | SUSE CVE CVE-2017-18184 | known not affected: 157 | 2026-08-01T23:35:42+00:00 | Vulnerability · Source |
| CVE-2017-18233 | suse_vex | SUSE CVE CVE-2017-18233 | known affected: 4 known not affected: 17 recommended: 26 | 2026-08-01T23:35:40+00:00 | Vulnerability · Source |
| CVE-2017-18870 | suse_vex | SUSE CVE CVE-2017-18870 | No product status | 2026-08-01T23:35:39+00:00 | Vulnerability · Source |
| CVE-2017-18871 | suse_vex | SUSE CVE CVE-2017-18871 | No product status | 2026-08-01T23:35:38+00:00 | Vulnerability · Source |
| CVE-2017-18872 | suse_vex | SUSE CVE CVE-2017-18872 | recommended: 1 | 2026-08-01T23:35:37+00:00 | Vulnerability · Source |
| CVE-2017-18883 | suse_vex | SUSE CVE CVE-2017-18883 | No product status | 2026-08-01T23:35:35+00:00 | Vulnerability · Source |
| CVE-2017-18884 | suse_vex | SUSE CVE CVE-2017-18884 | No product status | 2026-08-01T23:35:34+00:00 | Vulnerability · Source |
| CVE-2017-18885 | suse_vex | SUSE CVE CVE-2017-18885 | No product status | 2026-08-01T23:35:33+00:00 | Vulnerability · Source |
| CVE-2017-18886 | suse_vex | SUSE CVE CVE-2017-18886 | No product status | 2026-08-01T23:35:32+00:00 | Vulnerability · Source |
| CVE-2017-18888 | suse_vex | SUSE CVE CVE-2017-18888 | No product status | 2026-08-01T23:35:31+00:00 | Vulnerability · Source |
| CVE-2017-18894 | suse_vex | SUSE CVE CVE-2017-18894 | No product status | 2026-08-01T23:35:28+00:00 | Vulnerability · Source |
| CVE-2017-18900 | suse_vex | SUSE CVE CVE-2017-18900 | No product status | 2026-08-01T23:35:26+00:00 | Vulnerability · Source |
| CVE-2018-2582 | suse_vex | SUSE CVE CVE-2018-2582 | known affected: 73 known not affected: 279 recommended: 669 | 2026-08-01T23:35:18+00:00 | Vulnerability · Source |
| CVE-2018-2641 | suse_vex | SUSE CVE CVE-2018-2641 | known affected: 73 known not affected: 263 recommended: 730 | 2026-08-01T23:35:15+00:00 | Vulnerability · Source |
| CVE-2018-3064 | suse_vex | SUSE CVE CVE-2018-3064 | known affected: 65 known not affected: 59 recommended: 590 | 2026-08-01T23:35:14+00:00 | Vulnerability · Source |
| CVE-2018-3180 | suse_vex | SUSE CVE CVE-2018-3180 | known affected: 411 known not affected: 55 recommended: 1133 | 2026-08-01T23:35:12+00:00 | Vulnerability · Source |
| CVE-2018-4127 | suse_vex | SUSE CVE CVE-2018-4127 | known affected: 116 known not affected: 169 recommended: 915 | 2026-08-01T23:35:07+00:00 | Vulnerability · Source |
| CVE-2018-4213 | suse_vex | SUSE CVE CVE-2018-4213 | known affected: 108 known not affected: 82 recommended: 959 | 2026-08-01T23:35:05+00:00 | Vulnerability · Source |
| CVE-2018-4265 | suse_vex | SUSE CVE CVE-2018-4265 | known affected: 108 known not affected: 82 recommended: 957 | 2026-08-01T23:35:03+00:00 | Vulnerability · Source |
| CVE-2018-4311 | suse_vex | SUSE CVE CVE-2018-4311 | known affected: 108 known not affected: 82 | 2026-08-01T23:35:02+00:00 | Vulnerability · Source |
| CVE-2018-5097 | suse_vex | SUSE CVE CVE-2018-5097 | known affected: 2 recommended: 408 | 2026-08-01T23:34:59+00:00 | Vulnerability · Source |
| CVE-2018-5130 | suse_vex | SUSE CVE CVE-2018-5130 | known affected: 2 recommended: 311 | 2026-08-01T23:34:58+00:00 | Vulnerability · Source |
| CVE-2018-5144 | suse_vex | SUSE CVE CVE-2018-5144 | known affected: 2 recommended: 384 | 2026-08-01T23:34:57+00:00 | Vulnerability · Source |
| CVE-2018-5163 | suse_vex | SUSE CVE CVE-2018-5163 | known affected: 26 recommended: 83 | 2026-08-01T23:34:56+00:00 | Vulnerability · Source |
| CVE-2018-5167 | suse_vex | SUSE CVE CVE-2018-5167 | known affected: 26 recommended: 83 | 2026-08-01T23:34:55+00:00 | Vulnerability · Source |
| CVE-2018-7544 | suse_vex | SUSE CVE CVE-2018-7544 | known affected: 43 known not affected: 42 recommended: 165 | 2026-08-01T23:34:51+00:00 | Vulnerability · Source |
| CVE-2018-7549 | suse_vex | SUSE CVE CVE-2018-7549 | known affected: 17 known not affected: 45 recommended: 16 | 2026-08-01T23:34:50+00:00 | Vulnerability · Source |
| CVE-2018-7730 | suse_vex | SUSE CVE CVE-2018-7730 | known affected: 5 known not affected: 60 recommended: 154 | 2026-08-01T23:34:49+00:00 | Vulnerability · Source |
| CVE-2018-8897 | suse_vex | SUSE CVE CVE-2018-8897 | known affected: 338 known not affected: 342 recommended: 930 | 2026-08-01T23:34:45+00:00 | Vulnerability · Source |
| CVE-2018-10903 | suse_vex | SUSE CVE CVE-2018-10903 | known affected: 382 recommended: 310 | 2026-08-01T23:34:43+00:00 | Vulnerability · Source |
| CVE-2018-10910 | suse_vex | SUSE CVE CVE-2018-10910 | known not affected: 123 recommended: 11 | 2026-08-01T23:34:42+00:00 | Vulnerability · Source |
| CVE-2018-11489 | suse_vex | SUSE CVE CVE-2018-11489 | known affected: 2 known not affected: 103 | 2026-08-01T23:34:40+00:00 | Vulnerability · Source |
| CVE-2018-12193 | suse_vex | SUSE CVE CVE-2018-12193 | known not affected: 111 | 2026-08-01T23:34:37+00:00 | Vulnerability · Source |
| CVE-2018-12207 | suse_vex | SUSE CVE CVE-2018-12207 | known affected: 633 known not affected: 238 recommended: 2940 | 2026-08-01T23:34:36+00:00 | Vulnerability · Source |
| CVE-2018-12364 | suse_vex | SUSE CVE CVE-2018-12364 | known affected: 21 recommended: 451 | 2026-08-01T23:34:35+00:00 | Vulnerability · Source |