VEX records
Browse vendor VEX statements available in this Vulnerability-Lookup instance and pivot to the related vulnerability.
283038 VEX records
API response| Vulnerability | Source | Title | Product status | Imported | Links |
|---|---|---|---|---|---|
| CVE-2018-15857 | suse_vex | SUSE CVE CVE-2018-15857 | known affected: 557 known not affected: 65 recommended: 383 | 2026-07-19T18:27:42+00:00 | Vulnerability · Source |
| CVE-2018-15859 | suse_vex | SUSE CVE CVE-2018-15859 | known affected: 557 known not affected: 65 recommended: 420 | 2026-07-19T18:27:40+00:00 | Vulnerability · Source |
| CVE-2018-15861 | suse_vex | SUSE CVE CVE-2018-15861 | known affected: 557 known not affected: 65 recommended: 431 | 2026-07-19T18:27:39+00:00 | Vulnerability · Source |
| CVE-2018-15909 | suse_vex | SUSE CVE CVE-2018-15909 | known affected: 1 known not affected: 8 recommended: 364 | 2026-07-19T18:27:38+00:00 | Vulnerability · Source |
| CVE-2018-16056 | suse_vex | SUSE CVE CVE-2018-16056 | known affected: 101 recommended: 1004 | 2026-07-19T18:27:36+00:00 | Vulnerability · Source |
| CVE-2018-16152 | suse_vex | SUSE CVE CVE-2018-16152 | known affected: 26 known not affected: 135 recommended: 420 | 2026-07-19T18:27:35+00:00 | Vulnerability · Source |
| CVE-2018-16300 | suse_vex | SUSE CVE CVE-2018-16300 | known affected: 329 recommended: 143 | 2026-07-19T18:27:34+00:00 | Vulnerability · Source |
| CVE-2018-16323 | suse_vex | SUSE CVE CVE-2018-16323 | known affected: 1 recommended: 715 | 2026-07-19T18:27:33+00:00 | Vulnerability · Source |
| CVE-2018-16419 | suse_vex | SUSE CVE CVE-2018-16419 | known affected: 14 known not affected: 19 recommended: 104 | 2026-07-19T18:27:31+00:00 | Vulnerability · Source |
| CVE-2018-16420 | suse_vex | SUSE CVE CVE-2018-16420 | known affected: 13 known not affected: 37 recommended: 80 | 2026-07-19T18:27:30+00:00 | Vulnerability · Source |
| CVE-2018-16428 | suse_vex | SUSE CVE CVE-2018-16428 | known affected: 321 known not affected: 428 recommended: 1161 | 2026-07-19T18:27:29+00:00 | Vulnerability · Source |
| CVE-2018-16451 | suse_vex | SUSE CVE CVE-2018-16451 | known affected: 332 recommended: 143 | 2026-07-19T18:27:28+00:00 | Vulnerability · Source |
| CVE-2018-16452 | suse_vex | SUSE CVE CVE-2018-16452 | known affected: 332 recommended: 143 | 2026-07-19T18:27:26+00:00 | Vulnerability · Source |
| CVE-2018-16511 | suse_vex | SUSE CVE CVE-2018-16511 | known affected: 16 recommended: 418 | 2026-07-19T18:27:25+00:00 | Vulnerability · Source |
| CVE-2018-16540 | suse_vex | SUSE CVE CVE-2018-16540 | known affected: 16 recommended: 418 | 2026-07-19T18:27:24+00:00 | Vulnerability · Source |
| CVE-2018-16543 | suse_vex | SUSE CVE CVE-2018-16543 | known affected: 18 recommended: 359 | 2026-07-19T18:27:23+00:00 | Vulnerability · Source |
| CVE-2018-16642 | suse_vex | SUSE CVE CVE-2018-16642 | known affected: 81 recommended: 732 | 2026-07-19T18:27:21+00:00 | Vulnerability · Source |
| CVE-2018-16852 | suse_vex | SUSE CVE CVE-2018-16852 | known affected: 320 known not affected: 1438 recommended: 2761 | 2026-07-19T18:27:19+00:00 | Vulnerability · Source |
| CVE-2018-16857 | suse_vex | SUSE CVE CVE-2018-16857 | known affected: 320 known not affected: 1438 recommended: 2761 | 2026-07-19T18:27:17+00:00 | Vulnerability · Source |
| CVE-2018-16865 | suse_vex | SUSE CVE CVE-2018-16865 | known affected: 419 recommended: 1273 | 2026-07-19T18:27:16+00:00 | Vulnerability · Source |
| CVE-2018-16984 | suse_vex | SUSE CVE CVE-2018-16984 | recommended: 17 | 2026-07-19T18:27:15+00:00 | Vulnerability · Source |
| CVE-2018-17000 | suse_vex | SUSE CVE CVE-2018-17000 | known affected: 394 known not affected: 20 recommended: 251 | 2026-07-19T18:27:13+00:00 | Vulnerability · Source |
| CVE-2018-17097 | suse_vex | SUSE CVE CVE-2018-17097 | known affected: 16 recommended: 187 | 2026-07-19T18:27:12+00:00 | Vulnerability · Source |
| CVE-2018-17101 | suse_vex | SUSE CVE CVE-2018-17101 | known affected: 451 recommended: 288 | 2026-07-19T18:27:11+00:00 | Vulnerability · Source |
| CVE-2018-17229 | suse_vex | SUSE CVE CVE-2018-17229 | known affected: 13 known not affected: 97 recommended: 157 | 2026-07-19T18:27:09+00:00 | Vulnerability · Source |
| CVE-2018-17795 | suse_vex | SUSE CVE CVE-2018-17795 | known affected: 457 recommended: 284 | 2026-07-19T18:27:08+00:00 | Vulnerability · Source |
| CVE-2018-17961 | suse_vex | SUSE CVE CVE-2018-17961 | known affected: 1 known not affected: 87 recommended: 394 | 2026-07-19T18:27:06+00:00 | Vulnerability · Source |
| CVE-2018-18310 | suse_vex | SUSE CVE CVE-2018-18310 | known affected: 494 recommended: 1112 | 2026-07-19T18:27:05+00:00 | Vulnerability · Source |
| CVE-2018-18311 | suse_vex | SUSE CVE CVE-2018-18311 | known affected: 320 known not affected: 95 recommended: 494 | 2026-07-19T18:27:03+00:00 | Vulnerability · Source |
| CVE-2018-18440 | suse_vex | SUSE CVE CVE-2018-18440 | known not affected: 24 recommended: 150 | 2026-07-19T18:27:02+00:00 | Vulnerability · Source |
| CVE-2018-18493 | suse_vex | SUSE CVE CVE-2018-18493 | known affected: 20 known not affected: 168 recommended: 1185 | 2026-07-19T18:27:00+00:00 | Vulnerability · Source |
| CVE-2018-18501 | suse_vex | SUSE CVE CVE-2018-18501 | known not affected: 154 recommended: 1138 | 2026-07-19T18:26:59+00:00 | Vulnerability · Source |
| CVE-2018-18521 | suse_vex | SUSE CVE CVE-2018-18521 | known affected: 494 recommended: 1097 | 2026-07-19T18:26:58+00:00 | Vulnerability · Source |
| CVE-2018-18557 | suse_vex | SUSE CVE CVE-2018-18557 | known affected: 451 known not affected: 21 recommended: 270 | 2026-07-19T18:26:56+00:00 | Vulnerability · Source |
| CVE-2018-18607 | suse_vex | SUSE CVE CVE-2018-18607 | known affected: 437 recommended: 481 | 2026-07-19T18:26:55+00:00 | Vulnerability · Source |
| CVE-2018-19045 | suse_vex | SUSE CVE CVE-2018-19045 | known affected: 2 recommended: 13 | 2026-07-19T18:26:54+00:00 | Vulnerability · Source |
| CVE-2018-19046 | suse_vex | SUSE CVE CVE-2018-19046 | known affected: 2 recommended: 13 | 2026-07-19T18:26:53+00:00 | Vulnerability · Source |
| CVE-2018-19198 | suse_vex | SUSE CVE CVE-2018-19198 | recommended: 62 | 2026-07-19T18:26:52+00:00 | Vulnerability · Source |
| CVE-2018-19199 | suse_vex | SUSE CVE CVE-2018-19199 | recommended: 62 | 2026-07-19T18:26:51+00:00 | Vulnerability · Source |
| CVE-2018-19519 | suse_vex | SUSE CVE CVE-2018-19519 | known affected: 326 known not affected: 6 recommended: 146 | 2026-07-19T18:26:49+00:00 | Vulnerability · Source |
| CVE-2018-19541 | suse_vex | SUSE CVE CVE-2018-19541 | known affected: 36 recommended: 174 | 2026-07-19T18:26:48+00:00 | Vulnerability · Source |
| CVE-2018-19567 | suse_vex | SUSE CVE CVE-2018-19567 | known not affected: 85 recommended: 24 | 2026-07-19T18:26:47+00:00 | Vulnerability · Source |
| CVE-2018-19626 | suse_vex | SUSE CVE CVE-2018-19626 | known affected: 94 known not affected: 37 recommended: 910 | 2026-07-19T18:26:45+00:00 | Vulnerability · Source |
| CVE-2018-19644 | suse_vex | SUSE CVE CVE-2018-19644 | recommended: 167 | 2026-07-19T18:26:44+00:00 | Vulnerability · Source |
| CVE-2018-19655 | suse_vex | SUSE CVE CVE-2018-19655 | known not affected: 85 recommended: 29 | 2026-07-19T18:26:43+00:00 | Vulnerability · Source |
| CVE-2018-19664 | suse_vex | SUSE CVE CVE-2018-19664 | known not affected: 172 recommended: 167 | 2026-07-19T18:26:42+00:00 | Vulnerability · Source |
| CVE-2018-19788 | suse_vex | SUSE CVE CVE-2018-19788 | known affected: 415 known not affected: 52 recommended: 391 | 2026-07-19T18:26:40+00:00 | Vulnerability · Source |
| CVE-2018-19935 | suse_vex | SUSE CVE CVE-2018-19935 | known affected: 1080 known not affected: 1493 recommended: 2503 | 2026-07-19T18:26:38+00:00 | Vulnerability · Source |
| CVE-2018-20019 | suse_vex | SUSE CVE CVE-2018-20019 | known affected: 33 recommended: 123 | 2026-07-19T18:26:37+00:00 | Vulnerability · Source |
| CVE-2018-20020 | suse_vex | SUSE CVE CVE-2018-20020 | known affected: 33 recommended: 123 | 2026-07-19T18:26:36+00:00 | Vulnerability · Source |