VEX records
Browse vendor VEX statements available in this Vulnerability-Lookup instance and pivot to the related vulnerability.
294144 VEX records
API response| Vulnerability | Source | Title | Product status | Imported | Links |
|---|---|---|---|---|---|
| CVE-2018-1000035 | suse_vex | SUSE CVE CVE-2018-1000035 | known affected: 397 known not affected: 30 recommended: 92 | 2026-07-25T18:09:57+00:00 | Vulnerability · Source |
| CVE-2018-1000041 | suse_vex | SUSE CVE CVE-2018-1000041 | recommended: 72 | 2026-07-25T18:09:56+00:00 | Vulnerability · Source |
| CVE-2018-1000116 | suse_vex | SUSE CVE CVE-2018-1000116 | known affected: 2 known not affected: 52 | 2026-07-25T18:09:47+00:00 | Vulnerability · Source |
| CVE-2018-1000802 | suse_vex | SUSE CVE CVE-2018-1000802 | known affected: 438 known not affected: 2 recommended: 1387 | 2026-07-25T18:09:38+00:00 | Vulnerability · Source |
| CVE-2018-1000858 | suse_vex | SUSE CVE CVE-2018-1000858 | known affected: 331 known not affected: 40 recommended: 204 | 2026-07-25T18:09:34+00:00 | Vulnerability · Source |
| CVE-2019-0190 | suse_vex | SUSE CVE CVE-2019-0190 | known not affected: 138 | 2026-07-25T18:09:27+00:00 | Vulnerability · Source |
| CVE-2019-0215 | suse_vex | SUSE CVE CVE-2019-0215 | known not affected: 150 recommended: 11 | 2026-07-25T18:09:23+00:00 | Vulnerability · Source |
| CVE-2019-2011 | suse_vex | SUSE CVE CVE-2019-2011 | known not affected: 109 | 2026-07-25T18:09:04+00:00 | Vulnerability · Source |
| CVE-2019-2054 | suse_vex | SUSE CVE CVE-2019-2054 | known not affected: 413 | 2026-07-25T18:09:02+00:00 | Vulnerability · Source |
| CVE-2019-2214 | suse_vex | SUSE CVE CVE-2019-2214 | known not affected: 208 | 2026-07-25T18:08:59+00:00 | Vulnerability · Source |
| CVE-2019-2426 | suse_vex | SUSE CVE CVE-2019-2426 | known affected: 480 known not affected: 9 recommended: 814 | 2026-07-25T18:08:58+00:00 | Vulnerability · Source |
| CVE-2019-2481 | suse_vex | SUSE CVE CVE-2019-2481 | known affected: 70 known not affected: 185 recommended: 10 | 2026-07-25T18:08:56+00:00 | Vulnerability · Source |
| CVE-2019-2513 | suse_vex | SUSE CVE CVE-2019-2513 | known affected: 70 known not affected: 185 | 2026-07-25T18:08:54+00:00 | Vulnerability · Source |
| CVE-2019-2528 | suse_vex | SUSE CVE CVE-2019-2528 | known affected: 70 known not affected: 185 recommended: 10 | 2026-07-25T18:08:51+00:00 | Vulnerability · Source |
| CVE-2019-2533 | suse_vex | SUSE CVE CVE-2019-2533 | known affected: 70 known not affected: 185 recommended: 10 | 2026-07-25T18:08:50+00:00 | Vulnerability · Source |
| CVE-2019-2911 | suse_vex | SUSE CVE CVE-2019-2911 | known affected: 13 known not affected: 121 recommended: 10 | 2026-07-25T18:08:24+00:00 | Vulnerability · Source |
| CVE-2019-2920 | suse_vex | SUSE CVE CVE-2019-2920 | known affected: 13 known not affected: 121 | 2026-07-25T18:08:23+00:00 | Vulnerability · Source |
| CVE-2019-2948 | suse_vex | SUSE CVE CVE-2019-2948 | known affected: 13 known not affected: 121 recommended: 10 | 2026-07-25T18:08:19+00:00 | Vulnerability · Source |
| CVE-2019-2969 | suse_vex | SUSE CVE CVE-2019-2969 | known affected: 13 known not affected: 121 recommended: 10 | 2026-07-25T18:08:13+00:00 | Vulnerability · Source |
| CVE-2019-2991 | suse_vex | SUSE CVE CVE-2019-2991 | known affected: 13 known not affected: 121 recommended: 10 | 2026-07-25T18:08:10+00:00 | Vulnerability · Source |
| CVE-2019-2992 | suse_vex | SUSE CVE CVE-2019-2992 | known affected: 525 recommended: 1129 | 2026-07-25T18:08:08+00:00 | Vulnerability · Source |
| CVE-2019-2996 | suse_vex | SUSE CVE CVE-2019-2996 | known affected: 131 recommended: 295 | 2026-07-25T18:08:07+00:00 | Vulnerability · Source |
| CVE-2019-3693 | suse_vex | SUSE CVE CVE-2019-3693 | recommended: 31 | 2026-07-25T18:07:59+00:00 | Vulnerability · Source |
| CVE-2019-3896 | suse_vex | SUSE CVE CVE-2019-3896 | known not affected: 272 recommended: 49 | 2026-07-25T18:07:42+00:00 | Vulnerability · Source |
| CVE-2019-5018 | suse_vex | SUSE CVE CVE-2019-5018 | known not affected: 356 recommended: 5 | 2026-07-25T18:07:41+00:00 | Vulnerability · Source |
| CVE-2019-5418 | suse_vex | SUSE CVE CVE-2019-5418 | known affected: 405 recommended: 208 | 2026-07-25T18:07:36+00:00 | Vulnerability · Source |
| CVE-2019-6237 | suse_vex | SUSE CVE CVE-2019-6237 | known affected: 153 known not affected: 82 recommended: 298 | 2026-07-25T18:07:03+00:00 | Vulnerability · Source |
| CVE-2019-7635 | suse_vex | SUSE CVE CVE-2019-7635 | known affected: 71 recommended: 343 | 2026-07-25T18:06:43+00:00 | Vulnerability · Source |
| CVE-2019-7665 | suse_vex | SUSE CVE CVE-2019-7665 | known affected: 522 recommended: 1124 | 2026-07-25T18:06:42+00:00 | Vulnerability · Source |
| CVE-2019-8322 | suse_vex | SUSE CVE CVE-2019-8322 | known affected: 320 known not affected: 2 recommended: 523 | 2026-07-25T18:06:40+00:00 | Vulnerability · Source |
| CVE-2019-8323 | suse_vex | SUSE CVE CVE-2019-8323 | known affected: 320 known not affected: 2 recommended: 523 | 2026-07-25T18:06:39+00:00 | Vulnerability · Source |
| CVE-2019-8413 | suse_vex | SUSE CVE CVE-2019-8413 | known not affected: 144 | 2026-07-25T18:06:36+00:00 | Vulnerability · Source |
| CVE-2019-8571 | suse_vex | SUSE CVE CVE-2019-8571 | known affected: 153 known not affected: 82 recommended: 298 | 2026-07-25T18:06:21+00:00 | Vulnerability · Source |
| CVE-2019-8608 | suse_vex | SUSE CVE CVE-2019-8608 | known affected: 153 known not affected: 82 recommended: 298 | 2026-07-25T18:06:20+00:00 | Vulnerability · Source |
| CVE-2019-8686 | suse_vex | SUSE CVE CVE-2019-8686 | known affected: 107 known not affected: 82 recommended: 1136 | 2026-07-25T18:06:05+00:00 | Vulnerability · Source |
| CVE-2019-8820 | suse_vex | SUSE CVE CVE-2019-8820 | known not affected: 10 recommended: 1090 | 2026-07-25T18:05:45+00:00 | Vulnerability · Source |
| CVE-2019-8905 | suse_vex | SUSE CVE CVE-2019-8905 | known affected: 378 known not affected: 1432 recommended: 572 | 2026-07-25T18:05:40+00:00 | Vulnerability · Source |
| CVE-2019-9003 | suse_vex | SUSE CVE CVE-2019-9003 | known affected: 60 known not affected: 281 recommended: 572 | 2026-07-25T18:05:35+00:00 | Vulnerability · Source |
| CVE-2019-9445 | suse_vex | SUSE CVE CVE-2019-9445 | known not affected: 215 | 2026-07-25T18:05:16+00:00 | Vulnerability · Source |
| CVE-2019-9447 | suse_vex | SUSE CVE CVE-2019-9447 | known not affected: 215 | 2026-07-25T18:05:14+00:00 | Vulnerability · Source |
| CVE-2019-9449 | suse_vex | SUSE CVE CVE-2019-9449 | known not affected: 215 | 2026-07-25T18:05:13+00:00 | Vulnerability · Source |
| CVE-2019-9450 | suse_vex | SUSE CVE CVE-2019-9450 | known not affected: 215 | 2026-07-25T18:05:12+00:00 | Vulnerability · Source |
| CVE-2019-9453 | suse_vex | SUSE CVE CVE-2019-9453 | known not affected: 192 | 2026-07-25T18:05:10+00:00 | Vulnerability · Source |
| CVE-2019-9454 | suse_vex | SUSE CVE CVE-2019-9454 | known not affected: 199 recommended: 13 | 2026-07-25T18:05:09+00:00 | Vulnerability · Source |
| CVE-2019-9496 | suse_vex | SUSE CVE CVE-2019-9496 | known not affected: 27 recommended: 4 | 2026-07-25T18:05:08+00:00 | Vulnerability · Source |
| CVE-2019-9517 | suse_vex | SUSE CVE CVE-2019-9517 | known affected: 627 known not affected: 325 recommended: 775 | 2026-07-25T18:05:00+00:00 | Vulnerability · Source |
| CVE-2019-9578 | suse_vex | SUSE CVE CVE-2019-9578 | recommended: 197 | 2026-07-25T18:04:58+00:00 | Vulnerability · Source |
| CVE-2019-9619 | suse_vex | SUSE CVE CVE-2019-9619 | known affected: 22 known not affected: 229 | 2026-07-25T18:04:55+00:00 | Vulnerability · Source |
| CVE-2019-9706 | suse_vex | SUSE CVE CVE-2019-9706 | known not affected: 49 | 2026-07-25T18:04:51+00:00 | Vulnerability · Source |
| CVE-2019-9813 | suse_vex | SUSE CVE CVE-2019-9813 | known affected: 21 recommended: 420 | 2026-07-25T18:04:41+00:00 | Vulnerability · Source |