VEX records
Browse vendor VEX statements available in this Vulnerability-Lookup instance and pivot to the related vulnerability.
306231 VEX records
API response| Vulnerability | Source | Title | Product status | Imported | Links |
|---|---|---|---|---|---|
| CVE-2025-10528 | suse_vex | SUSE CVE CVE-2025-10528 | known affected: 73 recommended: 182 | 2026-10-10T16:47:00+00:00 | Vulnerability · Source |
| CVE-2025-10532 | suse_vex | SUSE CVE CVE-2025-10532 | known affected: 73 recommended: 182 | 2026-10-10T16:46:58+00:00 | Vulnerability · Source |
| CVE-2025-10534 | suse_vex | SUSE CVE CVE-2025-10534 | known affected: 73 recommended: 9 | 2026-10-10T16:46:56+00:00 | Vulnerability · Source |
| CVE-2025-10536 | suse_vex | SUSE CVE CVE-2025-10536 | known affected: 73 recommended: 182 | 2026-10-10T16:46:54+00:00 | Vulnerability · Source |
| CVE-2025-10922 | suse_vex | SUSE CVE CVE-2025-10922 | recommended: 96 | 2026-10-10T16:46:51+00:00 | Vulnerability · Source |
| CVE-2025-10954 | suse_vex | SUSE CVE CVE-2025-10954 | recommended: 1 | 2026-10-10T16:46:50+00:00 | Vulnerability · Source |
| CVE-2025-11561 | suse_vex | SUSE CVE CVE-2025-11561 | known affected: 412 recommended: 1024 | 2026-10-10T16:46:45+00:00 | Vulnerability · Source |
| CVE-2025-11621 | suse_vex | SUSE CVE CVE-2025-11621 | recommended: 1 | 2026-10-10T16:46:42+00:00 | Vulnerability · Source |
| CVE-2025-11714 | suse_vex | SUSE CVE CVE-2025-11714 | known affected: 73 recommended: 180 | 2026-10-10T16:46:39+00:00 | Vulnerability · Source |
| CVE-2025-12044 | suse_vex | SUSE CVE CVE-2025-12044 | recommended: 1 | 2026-10-10T16:46:37+00:00 | Vulnerability · Source |
| CVE-2025-12380 | suse_vex | SUSE CVE CVE-2025-12380 | known not affected: 193 recommended: 9 | 2026-10-10T16:46:35+00:00 | Vulnerability · Source |
| CVE-2025-12495 | suse_vex | SUSE CVE CVE-2025-12495 | known not affected: 190 recommended: 67 | 2026-10-10T16:46:32+00:00 | Vulnerability · Source |
| CVE-2025-12748 | suse_vex | SUSE CVE CVE-2025-12748 | known affected: 1238 recommended: 556 | 2026-10-10T16:46:29+00:00 | Vulnerability · Source |
| CVE-2025-13016 | suse_vex | SUSE CVE CVE-2025-13016 | known affected: 28 recommended: 182 | 2026-10-10T16:46:25+00:00 | Vulnerability · Source |
| CVE-2025-13019 | suse_vex | SUSE CVE CVE-2025-13019 | known affected: 28 recommended: 182 | 2026-10-10T16:46:22+00:00 | Vulnerability · Source |
| CVE-2025-13462 | suse_vex | SUSE CVE CVE-2025-13462 | known affected: 430 known not affected: 116 recommended: 825 | 2026-10-10T16:46:18+00:00 | Vulnerability · Source |
| CVE-2025-13499 | suse_vex | SUSE CVE CVE-2025-13499 | known affected: 234 known not affected: 85 recommended: 193 | 2026-10-10T16:46:16+00:00 | Vulnerability · Source |
| CVE-2025-13836 | suse_vex | SUSE CVE CVE-2025-13836 | known affected: 793 recommended: 1141 | 2026-10-10T16:46:14+00:00 | Vulnerability · Source |
| CVE-2025-14174 | suse_vex | SUSE CVE CVE-2025-14174 | known affected: 222 recommended: 590 | 2026-10-10T16:46:12+00:00 | Vulnerability · Source |
| CVE-2025-14329 | suse_vex | SUSE CVE CVE-2025-14329 | known affected: 73 recommended: 182 | 2026-10-10T16:46:09+00:00 | Vulnerability · Source |
| CVE-2025-15467 | suse_vex | SUSE CVE CVE-2025-15467 | known affected: 396 known not affected: 600 recommended: 154 | 2026-10-10T16:46:02+00:00 | Vulnerability · Source |
| CVE-2025-20053 | suse_vex | SUSE CVE CVE-2025-20053 | known affected: 24 recommended: 42 | 2026-10-10T16:45:59+00:00 | Vulnerability · Source |
| CVE-2025-20086 | suse_vex | SUSE CVE CVE-2025-20086 | recommended: 4 | 2026-10-10T16:45:56+00:00 | Vulnerability · Source |
| CVE-2025-20260 | suse_vex | SUSE CVE CVE-2025-20260 | known affected: 78 recommended: 242 | 2026-10-10T16:45:53+00:00 | Vulnerability · Source |
| CVE-2025-21088 | suse_vex | SUSE CVE CVE-2025-21088 | recommended: 4 | 2026-10-10T16:45:50+00:00 | Vulnerability · Source |
| CVE-2025-21500 | suse_vex | SUSE CVE CVE-2025-21500 | recommended: 25 | 2026-10-10T16:45:49+00:00 | Vulnerability · Source |
| CVE-2025-21632 | suse_vex | SUSE CVE CVE-2025-21632 | known affected: 410 known not affected: 428 recommended: 358 | 2026-10-10T16:45:45+00:00 | Vulnerability · Source |
| CVE-2025-21633 | suse_vex | SUSE CVE CVE-2025-21633 | known not affected: 463 recommended: 253 | 2026-10-10T16:45:43+00:00 | Vulnerability · Source |
| CVE-2025-21640 | suse_vex | SUSE CVE CVE-2025-21640 | known affected: 761 known not affected: 38 recommended: 398 | 2026-10-10T16:45:40+00:00 | Vulnerability · Source |
| CVE-2025-21646 | suse_vex | SUSE CVE CVE-2025-21646 | known affected: 524 known not affected: 384 recommended: 366 | 2026-10-10T16:45:38+00:00 | Vulnerability · Source |
| CVE-2025-21647 | suse_vex | SUSE CVE CVE-2025-21647 | known affected: 384 known not affected: 359 recommended: 572 | 2026-10-10T16:45:36+00:00 | Vulnerability · Source |
| CVE-2025-21651 | suse_vex | SUSE CVE CVE-2025-21651 | known affected: 609 known not affected: 229 recommended: 358 | 2026-10-10T16:45:34+00:00 | Vulnerability · Source |
| CVE-2025-21669 | suse_vex | SUSE CVE CVE-2025-21669 | known affected: 540 known not affected: 298 recommended: 444 | 2026-10-10T16:45:31+00:00 | Vulnerability · Source |
| CVE-2025-21672 | suse_vex | SUSE CVE CVE-2025-21672 | known not affected: 570 recommended: 41 | 2026-10-10T16:45:27+00:00 | Vulnerability · Source |
| CVE-2025-21675 | suse_vex | SUSE CVE CVE-2025-21675 | known affected: 540 known not affected: 298 recommended: 358 | 2026-10-10T16:45:25+00:00 | Vulnerability · Source |
| CVE-2025-21678 | suse_vex | SUSE CVE CVE-2025-21678 | known affected: 718 known not affected: 68 recommended: 384 | 2026-10-10T16:45:22+00:00 | Vulnerability · Source |
| CVE-2025-21683 | suse_vex | SUSE CVE CVE-2025-21683 | known affected: 583 known not affected: 223 recommended: 407 | 2026-10-10T16:45:20+00:00 | Vulnerability · Source |
| CVE-2025-21684 | suse_vex | SUSE CVE CVE-2025-21684 | known affected: 522 known not affected: 282 recommended: 358 | 2026-10-10T16:45:18+00:00 | Vulnerability · Source |
| CVE-2025-21687 | suse_vex | SUSE CVE CVE-2025-21687 | known affected: 410 known not affected: 428 recommended: 358 | 2026-10-10T16:45:16+00:00 | Vulnerability · Source |
| CVE-2025-21694 | suse_vex | SUSE CVE CVE-2025-21694 | known affected: 13 known not affected: 549 recommended: 86 | 2026-10-10T16:45:14+00:00 | Vulnerability · Source |
| CVE-2025-21702 | suse_vex | SUSE CVE CVE-2025-21702 | known affected: 612 recommended: 916 | 2026-10-10T16:45:11+00:00 | Vulnerability · Source |
| CVE-2025-21708 | suse_vex | SUSE CVE CVE-2025-21708 | known affected: 736 known not affected: 28 recommended: 397 | 2026-10-10T16:45:09+00:00 | Vulnerability · Source |
| CVE-2025-21713 | suse_vex | SUSE CVE CVE-2025-21713 | known affected: 394 known not affected: 469 recommended: 171 | 2026-10-10T16:45:07+00:00 | Vulnerability · Source |
| CVE-2025-21718 | suse_vex | SUSE CVE CVE-2025-21718 | known affected: 334 known not affected: 248 recommended: 189 | 2026-10-10T16:45:05+00:00 | Vulnerability · Source |
| CVE-2025-21724 | suse_vex | SUSE CVE CVE-2025-21724 | known affected: 394 known not affected: 428 recommended: 358 | 2026-10-10T16:45:03+00:00 | Vulnerability · Source |
| CVE-2025-21733 | suse_vex | SUSE CVE CVE-2025-21733 | known affected: 479 known not affected: 359 recommended: 357 | 2026-10-10T16:44:59+00:00 | Vulnerability · Source |
| CVE-2025-21734 | suse_vex | SUSE CVE CVE-2025-21734 | known affected: 591 known not affected: 213 recommended: 357 | 2026-10-10T16:44:56+00:00 | Vulnerability · Source |
| CVE-2025-21741 | suse_vex | SUSE CVE CVE-2025-21741 | known affected: 461 known not affected: 343 recommended: 399 | 2026-10-10T16:44:53+00:00 | Vulnerability · Source |
| CVE-2025-21749 | suse_vex | SUSE CVE CVE-2025-21749 | known affected: 743 known not affected: 131 recommended: 357 | 2026-10-10T16:44:50+00:00 | Vulnerability · Source |
| CVE-2025-21751 | suse_vex | SUSE CVE CVE-2025-21751 | known not affected: 469 recommended: 125 | 2026-10-10T16:44:48+00:00 | Vulnerability · Source |