VEX records
Browse vendor VEX statements available in this Vulnerability-Lookup instance and pivot to the related vulnerability.
291935 VEX records
API response| Vulnerability | Source | Title | Product status | Imported | Links |
|---|---|---|---|---|---|
| CVE-2019-6446 | suse_vex | SUSE CVE CVE-2019-6446 | known affected: 411 known not affected: 27 recommended: 527 | 2026-07-25T18:07:02+00:00 | Vulnerability · Source |
| CVE-2019-6462 | suse_vex | SUSE CVE CVE-2019-6462 | known affected: 627 known not affected: 62 recommended: 87 | 2026-07-25T18:07:00+00:00 | Vulnerability · Source |
| CVE-2019-6477 | suse_vex | SUSE CVE CVE-2019-6477 | known affected: 414 known not affected: 40 recommended: 875 | 2026-07-25T18:06:55+00:00 | Vulnerability · Source |
| CVE-2019-7398 | suse_vex | SUSE CVE CVE-2019-7398 | known affected: 46 recommended: 842 | 2026-07-25T18:06:49+00:00 | Vulnerability · Source |
| CVE-2019-7573 | suse_vex | SUSE CVE CVE-2019-7573 | known affected: 71 recommended: 323 | 2026-07-25T18:06:47+00:00 | Vulnerability · Source |
| CVE-2019-7574 | suse_vex | SUSE CVE CVE-2019-7574 | known affected: 71 recommended: 323 | 2026-07-25T18:06:46+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-8324 | suse_vex | SUSE CVE CVE-2019-8324 | known affected: 320 known not affected: 2 recommended: 523 | 2026-07-25T18:06:37+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-8518 | suse_vex | SUSE CVE CVE-2019-8518 | known not affected: 159 recommended: 942 | 2026-07-25T18:06:30+00:00 | Vulnerability · Source |
| CVE-2019-8551 | suse_vex | SUSE CVE CVE-2019-8551 | known affected: 154 known not affected: 82 recommended: 1221 | 2026-07-25T18:06:28+00:00 | Vulnerability · Source |
| CVE-2019-8564 | suse_vex | SUSE CVE CVE-2019-8564 | known not affected: 103 recommended: 490 | 2026-07-25T18:06:23+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-8623 | suse_vex | SUSE CVE CVE-2019-8623 | known affected: 153 known not affected: 82 recommended: 298 | 2026-07-25T18:06:16+00:00 | Vulnerability · Source |
| CVE-2019-8666 | suse_vex | SUSE CVE CVE-2019-8666 | known affected: 107 known not affected: 82 recommended: 1136 | 2026-07-25T18:06:14+00:00 | Vulnerability · Source |
| CVE-2019-8672 | suse_vex | SUSE CVE CVE-2019-8672 | known affected: 107 known not affected: 82 recommended: 1124 | 2026-07-25T18:06:11+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-8764 | suse_vex | SUSE CVE CVE-2019-8764 | known not affected: 10 recommended: 1090 | 2026-07-25T18:05:59+00:00 | Vulnerability · Source |
| CVE-2019-8765 | suse_vex | SUSE CVE CVE-2019-8765 | known not affected: 10 recommended: 983 | 2026-07-25T18:05:57+00:00 | Vulnerability · Source |
| CVE-2019-8782 | suse_vex | SUSE CVE CVE-2019-8782 | known not affected: 10 recommended: 1321 | 2026-07-25T18:05:51+00:00 | Vulnerability · Source |
| CVE-2019-8783 | suse_vex | SUSE CVE CVE-2019-8783 | known not affected: 10 recommended: 1102 | 2026-07-25T18:05:49+00:00 | Vulnerability · Source |
| CVE-2019-8808 | suse_vex | SUSE CVE CVE-2019-8808 | known not affected: 10 recommended: 1321 | 2026-07-25T18:05:48+00:00 | Vulnerability · Source |
| CVE-2019-8815 | suse_vex | SUSE CVE CVE-2019-8815 | known not affected: 10 recommended: 1321 | 2026-07-25T18:05:46+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-8821 | suse_vex | SUSE CVE CVE-2019-8821 | known not affected: 10 recommended: 995 | 2026-07-25T18:05:43+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-8934 | suse_vex | SUSE CVE CVE-2019-8934 | known affected: 529 known not affected: 374 recommended: 1786 | 2026-07-25T18:05:36+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-9022 | suse_vex | SUSE CVE CVE-2019-9022 | known affected: 1610 known not affected: 1146 recommended: 2629 | 2026-07-25T18:05:28+00:00 | Vulnerability · Source |
| CVE-2019-9024 | suse_vex | SUSE CVE CVE-2019-9024 | known affected: 550 known not affected: 1601 recommended: 4011 | 2026-07-25T18:05:26+00:00 | Vulnerability · Source |
| CVE-2019-9075 | suse_vex | SUSE CVE CVE-2019-9075 | known affected: 395 recommended: 553 | 2026-07-25T18:05:24+00:00 | Vulnerability · Source |
| CVE-2019-9371 | suse_vex | SUSE CVE CVE-2019-9371 | known affected: 21 known not affected: 55 recommended: 165 | 2026-07-25T18:05:18+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-9497 | suse_vex | SUSE CVE CVE-2019-9497 | known affected: 8 known not affected: 10 recommended: 98 | 2026-07-25T18:05:07+00:00 | Vulnerability · Source |
| CVE-2019-9500 | suse_vex | SUSE CVE CVE-2019-9500 | known affected: 65 known not affected: 64 recommended: 613 | 2026-07-25T18:05:05+00:00 | Vulnerability · Source |
| CVE-2019-9513 | suse_vex | SUSE CVE CVE-2019-9513 | known affected: 181 known not affected: 415 recommended: 654 | 2026-07-25T18:05:02+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-9543 | suse_vex | SUSE CVE CVE-2019-9543 | known affected: 10 known not affected: 20 | 2026-07-25T18:04:59+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 |