VEX records
Browse vendor VEX statements available in this Vulnerability-Lookup instance and pivot to the related vulnerability.
287378 VEX records
API response| Vulnerability | Source | Title | Product status | Imported | Links |
|---|---|---|---|---|---|
| CVE-2025-21680 | suse_vex | SUSE CVE CVE-2025-21680 | known affected: 410 known not affected: 308 recommended: 437 | 2026-07-31T01:20:53+00:00 | Vulnerability · Source |
| CVE-2025-21693 | suse_vex | SUSE CVE CVE-2025-21693 | known affected: 369 known not affected: 190 recommended: 687 | 2026-07-31T01:20:49+00:00 | Vulnerability · Source |
| CVE-2025-21717 | suse_vex | SUSE CVE CVE-2025-21717 | known not affected: 354 recommended: 145 | 2026-07-31T01:20:41+00:00 | Vulnerability · Source |
| CVE-2025-21726 | suse_vex | SUSE CVE CVE-2025-21726 | known affected: 370 known not affected: 166 recommended: 746 | 2026-07-31T01:20:35+00:00 | Vulnerability · Source |
| CVE-2025-21727 | suse_vex | SUSE CVE CVE-2025-21727 | known affected: 500 known not affected: 180 recommended: 468 | 2026-07-31T01:20:32+00:00 | Vulnerability · Source |
| CVE-2025-21738 | suse_vex | SUSE CVE CVE-2025-21738 | known affected: 477 known not affected: 40 recommended: 739 | 2026-07-31T01:20:27+00:00 | Vulnerability · Source |
| CVE-2025-21748 | suse_vex | SUSE CVE CVE-2025-21748 | known not affected: 461 | 2026-07-31T01:20:24+00:00 | Vulnerability · Source |
| CVE-2025-21751 | suse_vex | SUSE CVE CVE-2025-21751 | known not affected: 352 recommended: 112 | 2026-07-31T01:20:22+00:00 | Vulnerability · Source |
| CVE-2025-21752 | suse_vex | SUSE CVE CVE-2025-21752 | known not affected: 459 | 2026-07-31T01:20:19+00:00 | Vulnerability · Source |
| CVE-2025-21761 | suse_vex | SUSE CVE CVE-2025-21761 | known affected: 575 known not affected: 107 recommended: 437 | 2026-07-31T01:20:14+00:00 | Vulnerability · Source |
| CVE-2025-21765 | suse_vex | SUSE CVE CVE-2025-21765 | known affected: 551 recommended: 678 | 2026-07-31T01:20:10+00:00 | Vulnerability · Source |
| CVE-2025-21778 | suse_vex | SUSE CVE CVE-2025-21778 | known affected: 59 known not affected: 295 recommended: 53 | 2026-07-31T01:20:07+00:00 | Vulnerability · Source |
| CVE-2025-21782 | suse_vex | SUSE CVE CVE-2025-21782 | known affected: 634 known not affected: 93 recommended: 368 | 2026-07-31T01:20:03+00:00 | Vulnerability · Source |
| CVE-2025-21785 | suse_vex | SUSE CVE CVE-2025-21785 | known affected: 400 known not affected: 8 recommended: 793 | 2026-07-31T01:20:01+00:00 | Vulnerability · Source |
| CVE-2025-21786 | suse_vex | SUSE CVE CVE-2025-21786 | known affected: 57 known not affected: 295 recommended: 136 | 2026-07-31T01:19:58+00:00 | Vulnerability · Source |
| CVE-2025-21789 | suse_vex | SUSE CVE CVE-2025-21789 | known not affected: 468 | 2026-07-31T01:19:55+00:00 | Vulnerability · Source |
| CVE-2025-21791 | suse_vex | SUSE CVE CVE-2025-21791 | known affected: 450 known not affected: 54 recommended: 849 | 2026-07-31T01:19:52+00:00 | Vulnerability · Source |
| CVE-2025-21795 | suse_vex | SUSE CVE CVE-2025-21795 | known affected: 453 known not affected: 249 recommended: 446 | 2026-07-31T01:19:49+00:00 | Vulnerability · Source |
| CVE-2025-21796 | suse_vex | SUSE CVE CVE-2025-21796 | known affected: 654 recommended: 518 | 2026-07-31T01:19:46+00:00 | Vulnerability · Source |
| CVE-2025-21801 | suse_vex | SUSE CVE CVE-2025-21801 | known affected: 153 known not affected: 231 recommended: 53 | 2026-07-31T01:19:43+00:00 | Vulnerability · Source |
| CVE-2025-21805 | suse_vex | SUSE CVE CVE-2025-21805 | known affected: 394 known not affected: 352 recommended: 164 | 2026-07-31T01:19:40+00:00 | Vulnerability · Source |
| CVE-2025-21811 | suse_vex | SUSE CVE CVE-2025-21811 | known not affected: 463 | 2026-07-31T01:19:37+00:00 | Vulnerability · Source |
| CVE-2025-21826 | suse_vex | SUSE CVE CVE-2025-21826 | known not affected: 390 recommended: 136 | 2026-07-31T01:19:34+00:00 | Vulnerability · Source |
| CVE-2025-21827 | suse_vex | SUSE CVE CVE-2025-21827 | known not affected: 352 recommended: 112 | 2026-07-31T01:19:32+00:00 | Vulnerability · Source |
| CVE-2025-21828 | suse_vex | SUSE CVE CVE-2025-21828 | known affected: 394 known not affected: 286 recommended: 445 | 2026-07-31T01:19:31+00:00 | Vulnerability · Source |
| CVE-2025-21842 | suse_vex | SUSE CVE CVE-2025-21842 | known affected: 451 known not affected: 295 recommended: 164 | 2026-07-31T01:19:27+00:00 | Vulnerability · Source |
| CVE-2025-21844 | suse_vex | SUSE CVE CVE-2025-21844 | known affected: 573 known not affected: 103 recommended: 478 | 2026-07-31T01:19:25+00:00 | Vulnerability · Source |
| CVE-2025-21851 | suse_vex | SUSE CVE CVE-2025-21851 | known affected: 57 known not affected: 327 recommended: 136 | 2026-07-31T01:19:23+00:00 | Vulnerability · Source |
| CVE-2025-21855 | suse_vex | SUSE CVE CVE-2025-21855 | known affected: 244 known not affected: 6 recommended: 518 | 2026-07-31T01:19:21+00:00 | Vulnerability · Source |
| CVE-2025-21864 | suse_vex | SUSE CVE CVE-2025-21864 | known affected: 467 known not affected: 209 recommended: 478 | 2026-07-31T01:19:19+00:00 | Vulnerability · Source |
| CVE-2025-21896 | suse_vex | SUSE CVE CVE-2025-21896 | known not affected: 640 | 2026-07-31T01:19:12+00:00 | Vulnerability · Source |
| CVE-2025-21939 | suse_vex | SUSE CVE CVE-2025-21939 | known affected: 394 known not affected: 344 recommended: 164 | 2026-07-31T01:19:03+00:00 | Vulnerability · Source |
| CVE-2025-21944 | suse_vex | SUSE CVE CVE-2025-21944 | known not affected: 455 | 2026-07-31T01:19:00+00:00 | Vulnerability · Source |
| CVE-2025-21945 | suse_vex | SUSE CVE CVE-2025-21945 | known not affected: 451 | 2026-07-31T01:18:58+00:00 | Vulnerability · Source |
| CVE-2025-21946 | suse_vex | SUSE CVE CVE-2025-21946 | known not affected: 451 | 2026-07-31T01:18:56+00:00 | Vulnerability · Source |
| CVE-2025-21947 | suse_vex | SUSE CVE CVE-2025-21947 | known not affected: 453 | 2026-07-31T01:18:53+00:00 | Vulnerability · Source |
| CVE-2025-21949 | suse_vex | SUSE CVE CVE-2025-21949 | known not affected: 455 | 2026-07-31T01:18:50+00:00 | Vulnerability · Source |
| CVE-2025-21954 | suse_vex | SUSE CVE CVE-2025-21954 | known not affected: 348 recommended: 95 | 2026-07-31T01:18:48+00:00 | Vulnerability · Source |
| CVE-2025-21955 | suse_vex | SUSE CVE CVE-2025-21955 | known not affected: 455 | 2026-07-31T01:18:45+00:00 | Vulnerability · Source |
| CVE-2025-21957 | suse_vex | SUSE CVE CVE-2025-21957 | known affected: 678 known not affected: 63 recommended: 382 | 2026-07-31T01:18:43+00:00 | Vulnerability · Source |
| CVE-2025-21958 | suse_vex | SUSE CVE CVE-2025-21958 | known not affected: 348 recommended: 53 | 2026-07-31T01:18:40+00:00 | Vulnerability · Source |
| CVE-2025-21967 | suse_vex | SUSE CVE CVE-2025-21967 | known not affected: 455 | 2026-07-31T01:18:36+00:00 | Vulnerability · Source |
| CVE-2025-21984 | suse_vex | SUSE CVE CVE-2025-21984 | known not affected: 380 recommended: 53 | 2026-07-31T01:18:29+00:00 | Vulnerability · Source |
| CVE-2025-21994 | suse_vex | SUSE CVE CVE-2025-21994 | known not affected: 455 | 2026-07-31T01:18:26+00:00 | Vulnerability · Source |
| CVE-2025-22011 | suse_vex | SUSE CVE CVE-2025-22011 | known not affected: 455 recommended: 2 | 2026-07-31T01:18:21+00:00 | Vulnerability · Source |
| CVE-2025-22019 | suse_vex | SUSE CVE CVE-2025-22019 | known not affected: 455 | 2026-07-31T01:18:17+00:00 | Vulnerability · Source |
| CVE-2025-22025 | suse_vex | SUSE CVE CVE-2025-22025 | known affected: 394 known not affected: 262 recommended: 497 | 2026-07-31T01:18:12+00:00 | Vulnerability · Source |
| CVE-2025-22038 | suse_vex | SUSE CVE CVE-2025-22038 | known not affected: 453 | 2026-07-31T01:18:08+00:00 | Vulnerability · Source |
| CVE-2025-22042 | suse_vex | SUSE CVE CVE-2025-22042 | known not affected: 451 | 2026-07-31T01:18:04+00:00 | Vulnerability · Source |
| CVE-2025-22043 | suse_vex | SUSE CVE CVE-2025-22043 | known not affected: 451 | 2026-07-31T01:18:02+00:00 | Vulnerability · Source |