VEX records
Browse vendor VEX statements available in this Vulnerability-Lookup instance and pivot to the related vulnerability.
292117 VEX records
API response| Vulnerability | Source | Title | Product status | Imported | Links |
|---|---|---|---|---|---|
| CVE-2025-1181 | suse_vex | SUSE CVE CVE-2025-1181 | known affected: 469 known not affected: 73 recommended: 521 | 2026-07-23T01:51:56+00:00 | Vulnerability · Source |
| CVE-2025-1414 | suse_vex | SUSE CVE CVE-2025-1414 | known not affected: 150 | 2026-07-23T01:51:55+00:00 | Vulnerability · Source |
| CVE-2025-1933 | suse_vex | SUSE CVE CVE-2025-1933 | known affected: 37 recommended: 170 | 2026-07-23T01:51:50+00:00 | Vulnerability · Source |
| CVE-2025-2174 | suse_vex | SUSE CVE CVE-2025-2174 | known affected: 8 recommended: 57 | 2026-07-23T01:51:47+00:00 | Vulnerability · Source |
| CVE-2025-2175 | suse_vex | SUSE CVE CVE-2025-2175 | known affected: 8 recommended: 57 | 2026-07-23T01:51:46+00:00 | Vulnerability · Source |
| CVE-2025-2296 | suse_vex | SUSE CVE CVE-2025-2296 | known affected: 130 known not affected: 49 recommended: 13 | 2026-07-23T01:51:42+00:00 | Vulnerability · Source |
| CVE-2025-2591 | suse_vex | SUSE CVE CVE-2025-2591 | known not affected: 998 recommended: 10 | 2026-07-23T01:51:41+00:00 | Vulnerability · Source |
| CVE-2025-2592 | suse_vex | SUSE CVE CVE-2025-2592 | known affected: 1030 recommended: 12 | 2026-07-23T01:51:39+00:00 | Vulnerability · Source |
| CVE-2025-3030 | suse_vex | SUSE CVE CVE-2025-3030 | known affected: 37 recommended: 133 | 2026-07-23T01:51:35+00:00 | Vulnerability · Source |
| CVE-2025-3198 | suse_vex | SUSE CVE CVE-2025-3198 | known affected: 468 known not affected: 1 recommended: 515 | 2026-07-23T01:51:33+00:00 | Vulnerability · Source |
| CVE-2025-3360 | suse_vex | SUSE CVE CVE-2025-3360 | known affected: 574 known not affected: 137 recommended: 283 | 2026-07-23T01:51:31+00:00 | Vulnerability · Source |
| CVE-2025-3522 | suse_vex | SUSE CVE CVE-2025-3522 | known affected: 8 known not affected: 108 recommended: 24 | 2026-07-23T01:51:30+00:00 | Vulnerability · Source |
| CVE-2025-3887 | suse_vex | SUSE CVE CVE-2025-3887 | known affected: 90 recommended: 924 | 2026-07-23T01:51:28+00:00 | Vulnerability · Source |
| CVE-2025-4478 | suse_vex | SUSE CVE CVE-2025-4478 | known not affected: 47 recommended: 106 | 2026-07-23T01:51:26+00:00 | Vulnerability · Source |
| CVE-2025-5917 | suse_vex | SUSE CVE CVE-2025-5917 | known affected: 460 known not affected: 49 recommended: 79 | 2026-07-23T01:51:11+00:00 | Vulnerability · Source |
| CVE-2025-6547 | suse_vex | SUSE CVE CVE-2025-6547 | known affected: 25 known not affected: 332 recommended: 167 | 2026-07-23T01:51:02+00:00 | Vulnerability · Source |
| CVE-2025-7039 | suse_vex | SUSE CVE CVE-2025-7039 | known affected: 768 known not affected: 1813 recommended: 338 | 2026-07-23T01:51:00+00:00 | Vulnerability · Source |
| CVE-2025-7545 | suse_vex | SUSE CVE CVE-2025-7545 | known affected: 457 recommended: 527 | 2026-07-23T01:50:58+00:00 | Vulnerability · Source |
| CVE-2025-8030 | suse_vex | SUSE CVE CVE-2025-8030 | known affected: 37 recommended: 354 | 2026-07-23T01:50:56+00:00 | Vulnerability · Source |
| CVE-2025-8031 | suse_vex | SUSE CVE CVE-2025-8031 | known affected: 37 recommended: 354 | 2026-07-23T01:50:55+00:00 | Vulnerability · Source |
| CVE-2025-8039 | suse_vex | SUSE CVE CVE-2025-8039 | known affected: 37 recommended: 335 | 2026-07-23T01:50:52+00:00 | Vulnerability · Source |
| CVE-2025-8176 | suse_vex | SUSE CVE CVE-2025-8176 | known affected: 443 known not affected: 7 recommended: 148 | 2026-07-23T01:50:50+00:00 | Vulnerability · Source |
| CVE-2025-8836 | suse_vex | SUSE CVE CVE-2025-8836 | known affected: 485 recommended: 52 | 2026-07-23T01:50:46+00:00 | Vulnerability · Source |
| CVE-2025-8961 | suse_vex | SUSE CVE CVE-2025-8961 | known affected: 515 known not affected: 8 recommended: 95 | 2026-07-23T01:50:44+00:00 | Vulnerability · Source |
| CVE-2025-9301 | suse_vex | SUSE CVE CVE-2025-9301 | known affected: 418 known not affected: 13 recommended: 28 | 2026-07-23T01:50:39+00:00 | Vulnerability · Source |
| CVE-2025-9390 | suse_vex | SUSE CVE CVE-2025-9390 | known affected: 35 known not affected: 226 | 2026-07-23T01:50:38+00:00 | Vulnerability · Source |
| CVE-2025-9640 | suse_vex | SUSE CVE CVE-2025-9640 | known affected: 937 recommended: 958 | 2026-07-23T01:50:36+00:00 | Vulnerability · Source |
| CVE-2025-9714 | suse_vex | SUSE CVE CVE-2025-9714 | known affected: 374 known not affected: 215 recommended: 57 | 2026-07-23T01:50:35+00:00 | Vulnerability · Source |
| CVE-2025-10527 | suse_vex | SUSE CVE CVE-2025-10527 | known affected: 37 recommended: 184 | 2026-07-23T01:50:29+00:00 | Vulnerability · Source |
| CVE-2025-10966 | suse_vex | SUSE CVE CVE-2025-10966 | known not affected: 187 recommended: 16 | 2026-07-23T01:50:26+00:00 | Vulnerability · Source |
| CVE-2025-11413 | suse_vex | SUSE CVE CVE-2025-11413 | known affected: 445 known not affected: 22 recommended: 521 | 2026-07-23T01:50:23+00:00 | Vulnerability · Source |
| CVE-2025-11626 | suse_vex | SUSE CVE CVE-2025-11626 | known affected: 151 known not affected: 41 recommended: 96 | 2026-07-23T01:50:21+00:00 | Vulnerability · Source |
| CVE-2025-11711 | suse_vex | SUSE CVE CVE-2025-11711 | known affected: 70 recommended: 182 | 2026-07-23T01:50:20+00:00 | Vulnerability · Source |
| CVE-2025-11896 | suse_vex | SUSE CVE CVE-2025-11896 | known affected: 220 recommended: 168 | 2026-07-23T01:50:16+00:00 | Vulnerability · Source |
| CVE-2025-11964 | suse_vex | SUSE CVE CVE-2025-11964 | known not affected: 94 | 2026-07-23T01:50:15+00:00 | Vulnerability · Source |
| CVE-2025-12781 | suse_vex | SUSE CVE CVE-2025-12781 | known affected: 394 known not affected: 112 recommended: 244 | 2026-07-23T01:50:12+00:00 | Vulnerability · Source |
| CVE-2025-12839 | suse_vex | SUSE CVE CVE-2025-12839 | known not affected: 146 recommended: 67 | 2026-07-23T01:50:09+00:00 | Vulnerability · Source |
| CVE-2025-12840 | suse_vex | SUSE CVE CVE-2025-12840 | known not affected: 146 recommended: 67 | 2026-07-23T01:50:08+00:00 | Vulnerability · Source |
| CVE-2025-13034 | suse_vex | SUSE CVE CVE-2025-13034 | known not affected: 202 | 2026-07-23T01:50:04+00:00 | Vulnerability · Source |
| CVE-2025-13193 | suse_vex | SUSE CVE CVE-2025-13193 | known affected: 1413 recommended: 558 | 2026-07-23T01:50:01+00:00 | Vulnerability · Source |
| CVE-2025-13502 | suse_vex | SUSE CVE CVE-2025-13502 | known affected: 132 recommended: 625 | 2026-07-23T01:49:57+00:00 | Vulnerability · Source |
| CVE-2025-13947 | suse_vex | SUSE CVE CVE-2025-13947 | known affected: 132 recommended: 607 | 2026-07-23T01:49:51+00:00 | Vulnerability · Source |
| CVE-2025-14017 | suse_vex | SUSE CVE CVE-2025-14017 | known affected: 482 recommended: 124 | 2026-07-23T01:49:50+00:00 | Vulnerability · Source |
| CVE-2025-14325 | suse_vex | SUSE CVE CVE-2025-14325 | known affected: 37 recommended: 180 | 2026-07-23T01:49:45+00:00 | Vulnerability · Source |
| CVE-2025-14876 | suse_vex | SUSE CVE CVE-2025-14876 | known affected: 835 known not affected: 646 recommended: 688 | 2026-07-23T01:49:40+00:00 | Vulnerability · Source |
| CVE-2025-15079 | suse_vex | SUSE CVE CVE-2025-15079 | known affected: 495 known not affected: 9 recommended: 114 | 2026-07-23T01:49:38+00:00 | Vulnerability · Source |
| CVE-2025-20128 | suse_vex | SUSE CVE CVE-2025-20128 | known not affected: 15 recommended: 237 | 2026-07-23T01:49:33+00:00 | Vulnerability · Source |
| CVE-2025-20623 | suse_vex | SUSE CVE CVE-2025-20623 | known affected: 10 recommended: 46 | 2026-07-23T01:49:31+00:00 | Vulnerability · Source |
| CVE-2025-21587 | suse_vex | SUSE CVE CVE-2025-21587 | known affected: 458 known not affected: 83 recommended: 818 | 2026-07-23T01:49:30+00:00 | Vulnerability · Source |
| CVE-2025-21631 | suse_vex | SUSE CVE CVE-2025-21631 | known affected: 410 known not affected: 306 recommended: 403 | 2026-07-23T01:49:28+00:00 | Vulnerability · Source |