VEX records
Browse vendor VEX statements available in this Vulnerability-Lookup instance and pivot to the related vulnerability.
294017 VEX records
API response| Vulnerability | Source | Title | Product status | Imported | Links |
|---|---|---|---|---|---|
| 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-9587 | suse_vex | SUSE CVE CVE-2019-9587 | known not affected: 381 | 2026-07-25T18:04:56+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 |
| CVE-2019-9904 | suse_vex | SUSE CVE CVE-2019-9904 | known not affected: 57 | 2026-07-25T18:04:32+00:00 | Vulnerability · Source |
| CVE-2019-10125 | suse_vex | SUSE CVE CVE-2019-10125 | known not affected: 495 | 2026-07-25T18:04:19+00:00 | Vulnerability · Source |
| CVE-2019-10140 | suse_vex | SUSE CVE CVE-2019-10140 | known not affected: 222 | 2026-07-25T18:04:14+00:00 | Vulnerability · Source |
| CVE-2019-10142 | suse_vex | SUSE CVE CVE-2019-10142 | known not affected: 534 | 2026-07-25T18:04:13+00:00 | Vulnerability · Source |
| CVE-2019-10166 | suse_vex | SUSE CVE CVE-2019-10166 | known affected: 735 known not affected: 563 recommended: 1985 | 2026-07-25T18:04:08+00:00 | Vulnerability · Source |
| CVE-2019-11005 | suse_vex | SUSE CVE CVE-2019-11005 | known affected: 20 known not affected: 374 recommended: 16 | 2026-07-25T18:03:48+00:00 | Vulnerability · Source |
| CVE-2019-11006 | suse_vex | SUSE CVE CVE-2019-11006 | known affected: 20 known not affected: 421 recommended: 16 | 2026-07-25T18:03:47+00:00 | Vulnerability · Source |
| CVE-2019-11042 | suse_vex | SUSE CVE CVE-2019-11042 | known affected: 500 known not affected: 1101 recommended: 4197 | 2026-07-25T18:03:42+00:00 | Vulnerability · Source |
| CVE-2019-11059 | suse_vex | SUSE CVE CVE-2019-11059 | known affected: 19 recommended: 46 | 2026-07-25T18:03:40+00:00 | Vulnerability · Source |
| CVE-2019-11098 | suse_vex | SUSE CVE CVE-2019-11098 | known affected: 10 known not affected: 31 recommended: 61 | 2026-07-25T18:03:35+00:00 | Vulnerability · Source |
| CVE-2019-11473 | suse_vex | SUSE CVE CVE-2019-11473 | known affected: 20 known not affected: 375 recommended: 16 | 2026-07-25T18:03:27+00:00 | Vulnerability · Source |
| CVE-2019-11690 | suse_vex | SUSE CVE CVE-2019-11690 | known affected: 19 recommended: 46 | 2026-07-25T18:03:15+00:00 | Vulnerability · Source |
| CVE-2019-11727 | suse_vex | SUSE CVE CVE-2019-11727 | known affected: 48 known not affected: 376 recommended: 654 | 2026-07-25T18:03:02+00:00 | Vulnerability · Source |
| CVE-2019-11741 | suse_vex | SUSE CVE CVE-2019-11741 | known not affected: 87 recommended: 9 | 2026-07-25T18:02:57+00:00 | Vulnerability · Source |
| CVE-2019-11754 | suse_vex | SUSE CVE CVE-2019-11754 | known not affected: 87 recommended: 9 | 2026-07-25T18:02:48+00:00 | Vulnerability · Source |
| CVE-2019-11760 | suse_vex | SUSE CVE CVE-2019-11760 | known not affected: 160 recommended: 587 | 2026-07-25T18:02:47+00:00 | Vulnerability · Source |
| CVE-2019-12312 | suse_vex | SUSE CVE CVE-2019-12312 | known not affected: 142 recommended: 1 | 2026-07-25T18:02:34+00:00 | Vulnerability · Source |
| CVE-2019-12378 | suse_vex | SUSE CVE CVE-2019-12378 | known not affected: 278 | 2026-07-25T18:02:32+00:00 | Vulnerability · Source |
| CVE-2019-12379 | suse_vex | SUSE CVE CVE-2019-12379 | known not affected: 184 | 2026-07-25T18:02:31+00:00 | Vulnerability · Source |
| CVE-2019-12978 | suse_vex | SUSE CVE CVE-2019-12978 | known affected: 142 known not affected: 117 recommended: 708 | 2026-07-25T18:02:02+00:00 | Vulnerability · Source |
| CVE-2019-13050 | suse_vex | SUSE CVE CVE-2019-13050 | known affected: 361 recommended: 229 | 2026-07-25T18:02:00+00:00 | Vulnerability · Source |
| CVE-2019-13104 | suse_vex | SUSE CVE CVE-2019-13104 | known affected: 8 known not affected: 4 recommended: 40 | 2026-07-25T18:01:59+00:00 | Vulnerability · Source |