VEX records
Browse vendor VEX statements available in this Vulnerability-Lookup instance and pivot to the related vulnerability.
289533 VEX records
API response| Vulnerability | Source | Title | Product status | Imported | Links |
|---|---|---|---|---|---|
| CVE-2019-0196 | suse_vex | SUSE CVE CVE-2019-0196 | known affected: 111 known not affected: 65 recommended: 212 | 2026-08-06T02:12:12+00:00 | Vulnerability · Source |
| CVE-2019-1563 | suse_vex | SUSE CVE CVE-2019-1563 | known affected: 404 known not affected: 271 recommended: 984 | 2026-08-06T02:12:10+00:00 | Vulnerability · Source |
| CVE-2019-3892 | suse_vex | SUSE CVE CVE-2019-3892 | known not affected: 78 | 2026-08-06T02:12:07+00:00 | Vulnerability · Source |
| CVE-2019-6502 | suse_vex | SUSE CVE CVE-2019-6502 | known affected: 17 known not affected: 9 recommended: 64 | 2026-08-06T02:12:04+00:00 | Vulnerability · Source |
| CVE-2019-8763 | suse_vex | SUSE CVE CVE-2019-8763 | known not affected: 10 recommended: 983 | 2026-08-06T02:12:01+00:00 | Vulnerability · Source |
| CVE-2019-11026 | suse_vex | SUSE CVE CVE-2019-11026 | known affected: 10 known not affected: 223 | 2026-08-06T02:11:53+00:00 | Vulnerability · Source |
| CVE-2019-11360 | suse_vex | SUSE CVE CVE-2019-11360 | known not affected: 248 | 2026-08-06T02:11:51+00:00 | Vulnerability · Source |
| CVE-2019-11728 | suse_vex | SUSE CVE CVE-2019-11728 | known affected: 21 recommended: 613 | 2026-08-06T02:11:49+00:00 | Vulnerability · Source |
| CVE-2019-12290 | suse_vex | SUSE CVE CVE-2019-12290 | known affected: 320 recommended: 310 | 2026-08-06T02:11:47+00:00 | Vulnerability · Source |
| CVE-2019-14540 | suse_vex | SUSE CVE CVE-2019-14540 | known not affected: 25 recommended: 93 | 2026-08-06T02:11:44+00:00 | Vulnerability · Source |
| CVE-2019-16115 | suse_vex | SUSE CVE CVE-2019-16115 | known affected: 114 known not affected: 246 recommended: 93 | 2026-08-06T02:11:38+00:00 | Vulnerability · Source |
| CVE-2019-18224 | suse_vex | SUSE CVE CVE-2019-18224 | known affected: 320 recommended: 313 | 2026-08-06T02:11:35+00:00 | Vulnerability · Source |
| CVE-2019-19232 | suse_vex | SUSE CVE CVE-2019-19232 | known affected: 12 known not affected: 24 recommended: 1 | 2026-08-06T02:11:31+00:00 | Vulnerability · Source |
| CVE-2019-19244 | suse_vex | SUSE CVE CVE-2019-19244 | known affected: 299 known not affected: 268 recommended: 435 | 2026-08-06T02:11:30+00:00 | Vulnerability · Source |
| CVE-2019-19581 | suse_vex | SUSE CVE CVE-2019-19581 | known affected: 92 known not affected: 147 recommended: 235 | 2026-08-06T02:11:27+00:00 | Vulnerability · Source |
| CVE-2019-25162 | suse_vex | SUSE CVE CVE-2019-25162 | known affected: 339 known not affected: 66 recommended: 747 | 2026-08-06T02:11:24+00:00 | Vulnerability · Source |
| CVE-2020-6829 | suse_vex | SUSE CVE CVE-2020-6829 | known affected: 311 known not affected: 232 recommended: 1607 | 2026-08-06T02:11:17+00:00 | Vulnerability · Source |
| CVE-2020-8032 | suse_vex | SUSE CVE CVE-2020-8032 | known affected: 320 known not affected: 567 recommended: 772 | 2026-08-06T02:11:15+00:00 | Vulnerability · Source |
| CVE-2020-9327 | suse_vex | SUSE CVE CVE-2020-9327 | known affected: 364 known not affected: 268 recommended: 440 | 2026-08-06T02:11:12+00:00 | Vulnerability · Source |
| CVE-2020-10029 | suse_vex | SUSE CVE CVE-2020-10029 | known affected: 380 known not affected: 66 recommended: 1443 | 2026-08-06T02:11:10+00:00 | Vulnerability · Source |
| CVE-2020-10543 | suse_vex | SUSE CVE CVE-2020-10543 | known affected: 321 known not affected: 95 recommended: 527 | 2026-08-06T02:11:09+00:00 | Vulnerability · Source |
| CVE-2020-12400 | suse_vex | SUSE CVE CVE-2020-12400 | known not affected: 232 recommended: 1508 | 2026-08-06T02:11:05+00:00 | Vulnerability · Source |
| CVE-2020-12723 | suse_vex | SUSE CVE CVE-2020-12723 | known affected: 321 known not affected: 95 recommended: 527 | 2026-08-06T02:11:03+00:00 | Vulnerability · Source |
| CVE-2020-12888 | suse_vex | SUSE CVE CVE-2020-12888 | known affected: 416 known not affected: 23 recommended: 1408 | 2026-08-06T02:11:01+00:00 | Vulnerability · Source |
| CVE-2020-15676 | suse_vex | SUSE CVE CVE-2020-15676 | known affected: 3 known not affected: 155 recommended: 561 | 2026-08-06T02:10:56+00:00 | Vulnerability · Source |
| CVE-2020-15678 | suse_vex | SUSE CVE CVE-2020-15678 | known affected: 3 known not affected: 155 recommended: 561 | 2026-08-06T02:10:55+00:00 | Vulnerability · Source |
| CVE-2020-15999 | suse_vex | SUSE CVE CVE-2020-15999 | known affected: 282 known not affected: 87 recommended: 1072 | 2026-08-06T02:10:53+00:00 | Vulnerability · Source |
| CVE-2020-16121 | suse_vex | SUSE CVE CVE-2020-16121 | known affected: 36 known not affected: 4 recommended: 489 | 2026-08-06T02:10:52+00:00 | Vulnerability · Source |
| CVE-2020-24332 | suse_vex | SUSE CVE CVE-2020-24332 | known affected: 7 known not affected: 24 recommended: 90 | 2026-08-06T02:10:49+00:00 | Vulnerability · Source |
| CVE-2020-25592 | suse_vex | SUSE CVE CVE-2020-25592 | known affected: 394 known not affected: 421 recommended: 1148 | 2026-08-06T02:10:46+00:00 | Vulnerability · Source |
| CVE-2020-25657 | suse_vex | SUSE CVE CVE-2020-25657 | known affected: 397 recommended: 194 | 2026-08-06T02:10:44+00:00 | Vulnerability · Source |
| CVE-2020-26142 | suse_vex | SUSE CVE CVE-2020-26142 | known affected: 22 known not affected: 165 | 2026-08-06T02:10:42+00:00 | Vulnerability · Source |
| CVE-2020-26259 | suse_vex | SUSE CVE CVE-2020-26259 | known affected: 394 recommended: 186 | 2026-08-06T02:10:41+00:00 | Vulnerability · Source |
| CVE-2020-28477 | suse_vex | SUSE CVE CVE-2020-28477 | known affected: 394 recommended: 189 | 2026-08-06T02:10:38+00:00 | Vulnerability · Source |
| CVE-2020-35448 | suse_vex | SUSE CVE CVE-2020-35448 | known affected: 398 recommended: 542 | 2026-08-06T02:10:35+00:00 | Vulnerability · Source |
| CVE-2020-35496 | suse_vex | SUSE CVE CVE-2020-35496 | known affected: 395 known not affected: 2 recommended: 540 | 2026-08-06T02:10:34+00:00 | Vulnerability · Source |
| CVE-2021-3447 | suse_vex | SUSE CVE CVE-2021-3447 | recommended: 138 | 2026-08-06T02:10:26+00:00 | Vulnerability · Source |
| CVE-2021-3620 | suse_vex | SUSE CVE CVE-2021-3620 | known not affected: 2 recommended: 138 | 2026-08-06T02:10:23+00:00 | Vulnerability · Source |
| CVE-2021-3653 | suse_vex | SUSE CVE CVE-2021-3653 | known affected: 427 known not affected: 61 recommended: 1834 | 2026-08-06T02:10:20+00:00 | Vulnerability · Source |
| CVE-2021-3826 | suse_vex | SUSE CVE CVE-2021-3826 | known affected: 395 known not affected: 1 recommended: 466 | 2026-08-06T02:10:17+00:00 | Vulnerability · Source |
| CVE-2021-21344 | suse_vex | SUSE CVE CVE-2021-21344 | known affected: 394 recommended: 69 | 2026-08-06T02:10:08+00:00 | Vulnerability · Source |
| CVE-2021-21349 | suse_vex | SUSE CVE CVE-2021-21349 | known affected: 394 recommended: 67 | 2026-08-06T02:10:07+00:00 | Vulnerability · Source |
| CVE-2021-21350 | suse_vex | SUSE CVE CVE-2021-21350 | known affected: 394 recommended: 69 | 2026-08-06T02:10:06+00:00 | Vulnerability · Source |
| CVE-2021-27962 | suse_vex | SUSE CVE CVE-2021-27962 | known not affected: 12 recommended: 242 | 2026-08-06T02:10:02+00:00 | Vulnerability · Source |
| CVE-2021-28041 | suse_vex | SUSE CVE CVE-2021-28041 | known affected: 338 known not affected: 166 recommended: 348 | 2026-08-06T02:10:00+00:00 | Vulnerability · Source |
| CVE-2021-28831 | suse_vex | SUSE CVE CVE-2021-28831 | known affected: 5 recommended: 162 | 2026-08-06T02:09:59+00:00 | Vulnerability · Source |
| CVE-2021-29622 | suse_vex | SUSE CVE CVE-2021-29622 | recommended: 242 | 2026-08-06T02:09:56+00:00 | Vulnerability · Source |
| CVE-2021-30858 | suse_vex | SUSE CVE CVE-2021-30858 | known affected: 38 known not affected: 10 recommended: 1047 | 2026-08-06T02:09:53+00:00 | Vulnerability · Source |
| CVE-2021-35517 | suse_vex | SUSE CVE CVE-2021-35517 | recommended: 55 | 2026-08-06T02:09:47+00:00 | Vulnerability · Source |
| CVE-2021-37137 | suse_vex | SUSE CVE CVE-2021-37137 | known affected: 394 known not affected: 32 recommended: 16 | 2026-08-06T02:09:45+00:00 | Vulnerability · Source |