VEX records
Browse vendor VEX statements available in this Vulnerability-Lookup instance and pivot to the related vulnerability.
306217 VEX records
API response| Vulnerability | Source | Title | Product status | Imported | Links |
|---|---|---|---|---|---|
| CVE-2025-47183 | suse_vex | SUSE CVE CVE-2025-47183 | known affected: 82 recommended: 49 | 2026-10-10T01:48:46+00:00 | Vulnerability · Source |
| CVE-2025-47273 | suse_vex | SUSE CVE CVE-2025-47273 | known affected: 391 known not affected: 9 recommended: 401 | 2026-10-10T01:48:44+00:00 | Vulnerability · Source |
| CVE-2025-47281 | suse_vex | SUSE CVE CVE-2025-47281 | recommended: 4 | 2026-10-10T01:48:42+00:00 | Vulnerability · Source |
| CVE-2025-47283 | suse_vex | SUSE CVE CVE-2025-47283 | recommended: 4 | 2026-10-10T01:48:40+00:00 | Vulnerability · Source |
| CVE-2025-47712 | suse_vex | SUSE CVE CVE-2025-47712 | known not affected: 3 recommended: 120 | 2026-10-10T01:48:38+00:00 | Vulnerability · Source |
| CVE-2025-47806 | suse_vex | SUSE CVE CVE-2025-47806 | known affected: 1013 known not affected: 28 recommended: 535 | 2026-10-10T01:48:35+00:00 | Vulnerability · Source |
| CVE-2025-47807 | suse_vex | SUSE CVE CVE-2025-47807 | known affected: 1013 known not affected: 28 recommended: 535 | 2026-10-10T01:48:33+00:00 | Vulnerability · Source |
| CVE-2025-47913 | suse_vex | SUSE CVE CVE-2025-47913 | known affected: 709 recommended: 492 | 2026-10-10T01:48:29+00:00 | Vulnerability · Source |
| CVE-2025-47914 | suse_vex | SUSE CVE CVE-2025-47914 | known affected: 848 known not affected: 4 recommended: 324 | 2026-10-10T01:48:27+00:00 | Vulnerability · Source |
| CVE-2025-48060 | suse_vex | SUSE CVE CVE-2025-48060 | known affected: 435 recommended: 123 | 2026-10-10T01:48:25+00:00 | Vulnerability · Source |
| CVE-2025-48074 | suse_vex | SUSE CVE CVE-2025-48074 | known not affected: 186 recommended: 30 | 2026-10-10T01:48:23+00:00 | Vulnerability · Source |
| CVE-2025-48371 | suse_vex | SUSE CVE CVE-2025-48371 | recommended: 4 | 2026-10-10T01:48:21+00:00 | Vulnerability · Source |
| CVE-2025-48379 | suse_vex | SUSE CVE CVE-2025-48379 | known not affected: 65 recommended: 12 | 2026-10-10T01:48:19+00:00 | Vulnerability · Source |
| CVE-2025-48384 | suse_vex | SUSE CVE CVE-2025-48384 | known affected: 214 recommended: 462 | 2026-10-10T01:48:17+00:00 | Vulnerability · Source |
| CVE-2025-48622 | suse_vex | SUSE CVE CVE-2025-48622 | known affected: 214 | 2026-10-10T01:48:14+00:00 | Vulnerability · Source |
| CVE-2025-48734 | suse_vex | SUSE CVE CVE-2025-48734 | known affected: 406 recommended: 551 | 2026-10-10T01:48:11+00:00 | Vulnerability · Source |
| CVE-2025-48798 | suse_vex | SUSE CVE CVE-2025-48798 | recommended: 82 | 2026-10-10T01:48:08+00:00 | Vulnerability · Source |
| CVE-2025-48865 | suse_vex | SUSE CVE CVE-2025-48865 | recommended: 4 | 2026-10-10T01:48:06+00:00 | Vulnerability · Source |
| CVE-2025-48866 | suse_vex | SUSE CVE CVE-2025-48866 | known affected: 21 recommended: 36 | 2026-10-10T01:48:05+00:00 | Vulnerability · Source |
| CVE-2025-48938 | suse_vex | SUSE CVE CVE-2025-48938 | recommended: 4 | 2026-10-10T01:48:03+00:00 | Vulnerability · Source |
| CVE-2025-48948 | suse_vex | SUSE CVE CVE-2025-48948 | recommended: 4 | 2026-10-10T01:48:01+00:00 | Vulnerability · Source |
| CVE-2025-48976 | suse_vex | SUSE CVE CVE-2025-48976 | known affected: 416 recommended: 57 | 2026-10-10T01:47:59+00:00 | Vulnerability · Source |
| CVE-2025-48989 | suse_vex | SUSE CVE CVE-2025-48989 | known affected: 521 known not affected: 38 recommended: 466 | 2026-10-10T01:47:57+00:00 | Vulnerability · Source |
| CVE-2025-49010 | suse_vex | SUSE CVE CVE-2025-49010 | known affected: 414 recommended: 37 | 2026-10-10T01:47:54+00:00 | Vulnerability · Source |
| CVE-2025-49014 | suse_vex | SUSE CVE CVE-2025-49014 | known not affected: 125 recommended: 6 | 2026-10-10T01:47:52+00:00 | Vulnerability · Source |
| CVE-2025-49112 | suse_vex | SUSE CVE CVE-2025-49112 | recommended: 33 | 2026-10-10T01:47:49+00:00 | Vulnerability · Source |
| CVE-2025-49179 | suse_vex | SUSE CVE CVE-2025-49179 | known affected: 447 recommended: 195 | 2026-10-10T01:47:46+00:00 | Vulnerability · Source |
| CVE-2025-49180 | suse_vex | SUSE CVE CVE-2025-49180 | known affected: 446 known not affected: 1 recommended: 195 | 2026-10-10T01:47:44+00:00 | Vulnerability · Source |
| CVE-2025-49794 | suse_vex | SUSE CVE CVE-2025-49794 | known affected: 487 known not affected: 67 recommended: 281 | 2026-10-10T01:47:41+00:00 | Vulnerability · Source |
| CVE-2025-49796 | suse_vex | SUSE CVE CVE-2025-49796 | known affected: 487 known not affected: 67 recommended: 281 | 2026-10-10T01:47:38+00:00 | Vulnerability · Source |
| CVE-2025-49812 | suse_vex | SUSE CVE CVE-2025-49812 | known affected: 534 recommended: 309 | 2026-10-10T01:47:36+00:00 | Vulnerability · Source |
| CVE-2025-49844 | suse_vex | SUSE CVE CVE-2025-49844 | known affected: 4 known not affected: 7 recommended: 80 | 2026-10-10T01:47:34+00:00 | Vulnerability · Source |
| CVE-2025-50059 | suse_vex | SUSE CVE CVE-2025-50059 | known affected: 466 known not affected: 274 recommended: 766 | 2026-10-10T01:47:31+00:00 | Vulnerability · Source |
| CVE-2025-50083 | suse_vex | SUSE CVE CVE-2025-50083 | recommended: 48 | 2026-10-10T01:47:28+00:00 | Vulnerability · Source |
| CVE-2025-50087 | suse_vex | SUSE CVE CVE-2025-50087 | recommended: 48 | 2026-10-10T01:47:26+00:00 | Vulnerability · Source |
| CVE-2025-50104 | suse_vex | SUSE CVE CVE-2025-50104 | recommended: 48 | 2026-10-10T01:47:23+00:00 | Vulnerability · Source |
| CVE-2025-50106 | suse_vex | SUSE CVE CVE-2025-50106 | known affected: 626 recommended: 910 | 2026-10-10T01:47:21+00:00 | Vulnerability · Source |
| CVE-2025-50422 | suse_vex | SUSE CVE CVE-2025-50422 | known affected: 677 recommended: 110 | 2026-10-10T01:47:18+00:00 | Vulnerability · Source |
| CVE-2025-50946 | suse_vex | SUSE CVE CVE-2025-50946 | recommended: 1 | 2026-10-10T01:47:16+00:00 | Vulnerability · Source |
| CVE-2025-52194 | suse_vex | SUSE CVE CVE-2025-52194 | known affected: 112 recommended: 56 | 2026-10-10T01:47:11+00:00 | Vulnerability · Source |
| CVE-2025-52434 | suse_vex | SUSE CVE CVE-2025-52434 | known affected: 521 known not affected: 246 recommended: 244 | 2026-10-10T01:47:08+00:00 | Vulnerability · Source |
| CVE-2025-52565 | suse_vex | SUSE CVE CVE-2025-52565 | known affected: 397 known not affected: 1291 recommended: 226 | 2026-10-10T01:47:05+00:00 | Vulnerability · Source |
| CVE-2025-52885 | suse_vex | SUSE CVE CVE-2025-52885 | known affected: 32 known not affected: 132 recommended: 213 | 2026-10-10T01:47:03+00:00 | Vulnerability · Source |
| CVE-2025-52889 | suse_vex | SUSE CVE CVE-2025-52889 | recommended: 9 | 2026-10-10T01:47:00+00:00 | Vulnerability · Source |
| CVE-2025-52890 | suse_vex | SUSE CVE CVE-2025-52890 | recommended: 9 | 2026-10-10T01:46:57+00:00 | Vulnerability · Source |
| CVE-2025-52891 | suse_vex | SUSE CVE CVE-2025-52891 | known not affected: 58 recommended: 4 | 2026-10-10T01:46:54+00:00 | Vulnerability · Source |
| CVE-2025-52900 | suse_vex | SUSE CVE CVE-2025-52900 | recommended: 4 | 2026-10-10T01:46:52+00:00 | Vulnerability · Source |
| CVE-2025-52904 | suse_vex | SUSE CVE CVE-2025-52904 | recommended: 4 | 2026-10-10T01:46:49+00:00 | Vulnerability · Source |
| CVE-2025-52996 | suse_vex | SUSE CVE CVE-2025-52996 | recommended: 4 | 2026-10-10T01:46:47+00:00 | Vulnerability · Source |
| CVE-2025-52999 | suse_vex | SUSE CVE CVE-2025-52999 | known not affected: 43 recommended: 46 | 2026-10-10T01:46:45+00:00 | Vulnerability · Source |