VEX records
Browse vendor VEX statements available in this Vulnerability-Lookup instance and pivot to the related vulnerability.
104719 VEX records
API response| Vulnerability | Source | Title | Product status | Imported | Links |
|---|---|---|---|---|---|
| CVE-2025-47907 | suse_vex | SUSE CVE CVE-2025-47907 | known affected: 36 known not affected: 69 recommended: 510 | 2026-10-15T16:23:14+00:00 | Vulnerability · Source |
| CVE-2025-47908 | suse_vex | SUSE CVE CVE-2025-47908 | known not affected: 156 recommended: 52 | 2026-10-15T16:23:12+00:00 | Vulnerability · Source |
| CVE-2025-47912 | suse_vex | SUSE CVE CVE-2025-47912 | known affected: 30 known not affected: 69 recommended: 294 | 2026-10-15T16:23:09+00:00 | Vulnerability · Source |
| CVE-2025-47913 | suse_vex | SUSE CVE CVE-2025-47913 | known affected: 709 recommended: 492 | 2026-10-15T16:23:07+00:00 | Vulnerability · Source |
| CVE-2025-47943 | suse_vex | SUSE CVE CVE-2025-47943 | recommended: 4 | 2026-10-15T16:23:06+00:00 | Vulnerability · Source |
| CVE-2025-47947 | suse_vex | SUSE CVE CVE-2025-47947 | known affected: 21 recommended: 38 | 2026-10-15T16:23:04+00:00 | Vulnerability · Source |
| CVE-2025-47952 | suse_vex | SUSE CVE CVE-2025-47952 | recommended: 6 | 2026-10-15T16:23:02+00:00 | Vulnerability · Source |
| CVE-2025-48038 | suse_vex | SUSE CVE CVE-2025-48038 | known affected: 63 recommended: 100 | 2026-10-15T16:23:00+00:00 | Vulnerability · Source |
| CVE-2025-48039 | suse_vex | SUSE CVE CVE-2025-48039 | known affected: 63 recommended: 100 | 2026-10-15T16:22:58+00:00 | Vulnerability · Source |
| CVE-2025-48056 | suse_vex | SUSE CVE CVE-2025-48056 | recommended: 4 | 2026-10-15T16:22:57+00:00 | Vulnerability · Source |
| CVE-2025-48069 | suse_vex | SUSE CVE CVE-2025-48069 | recommended: 4 | 2026-10-15T16:22:55+00:00 | Vulnerability · Source |
| CVE-2025-48071 | suse_vex | SUSE CVE CVE-2025-48071 | known not affected: 186 recommended: 30 | 2026-10-15T16:22:54+00:00 | Vulnerability · Source |
| CVE-2025-48072 | suse_vex | SUSE CVE CVE-2025-48072 | known not affected: 186 recommended: 30 | 2026-10-15T16:22:52+00:00 | Vulnerability · Source |
| CVE-2025-48374 | suse_vex | SUSE CVE CVE-2025-48374 | recommended: 4 | 2026-10-15T16:22:51+00:00 | Vulnerability · Source |
| CVE-2025-48379 | suse_vex | SUSE CVE CVE-2025-48379 | known not affected: 65 recommended: 12 | 2026-10-15T16:22:50+00:00 | Vulnerability · Source |
| CVE-2025-48385 | suse_vex | SUSE CVE CVE-2025-48385 | known not affected: 261 recommended: 397 | 2026-10-15T16:22:48+00:00 | Vulnerability · Source |
| CVE-2025-48495 | suse_vex | SUSE CVE CVE-2025-48495 | recommended: 4 | 2026-10-15T16:22:47+00:00 | Vulnerability · Source |
| CVE-2025-48708 | suse_vex | SUSE CVE CVE-2025-48708 | known affected: 139 known not affected: 1 recommended: 53 | 2026-10-15T16:22:45+00:00 | Vulnerability · Source |
| CVE-2025-48710 | suse_vex | SUSE CVE CVE-2025-48710 | recommended: 4 | 2026-10-15T16:22:44+00:00 | Vulnerability · Source |
| CVE-2025-48731 | suse_vex | SUSE CVE CVE-2025-48731 | recommended: 1 | 2026-10-15T16:22:42+00:00 | Vulnerability · Source |
| CVE-2025-48734 | suse_vex | SUSE CVE CVE-2025-48734 | known affected: 406 recommended: 551 | 2026-10-15T16:22:40+00:00 | Vulnerability · Source |
| CVE-2025-48865 | suse_vex | SUSE CVE CVE-2025-48865 | recommended: 4 | 2026-10-15T16:22:39+00:00 | Vulnerability · Source |
| CVE-2025-48964 | suse_vex | SUSE CVE CVE-2025-48964 | known affected: 421 recommended: 90 | 2026-10-15T16:22:38+00:00 | Vulnerability · Source |
| CVE-2025-49133 | suse_vex | SUSE CVE CVE-2025-49133 | known affected: 82 recommended: 147 | 2026-10-15T16:22:36+00:00 | Vulnerability · Source |
| CVE-2025-49146 | suse_vex | SUSE CVE CVE-2025-49146 | known not affected: 46 recommended: 8 | 2026-10-15T16:22:34+00:00 | Vulnerability · Source |
| CVE-2025-49175 | suse_vex | SUSE CVE CVE-2025-49175 | known affected: 447 recommended: 195 | 2026-10-15T16:22:33+00:00 | Vulnerability · Source |
| CVE-2025-49176 | suse_vex | SUSE CVE CVE-2025-49176 | known affected: 447 recommended: 195 | 2026-10-15T16:22:31+00:00 | Vulnerability · Source |
| CVE-2025-49177 | suse_vex | SUSE CVE CVE-2025-49177 | known affected: 394 known not affected: 114 recommended: 87 | 2026-10-15T16:22:29+00:00 | Vulnerability · Source |
| CVE-2025-49178 | suse_vex | SUSE CVE CVE-2025-49178 | known affected: 446 known not affected: 1 recommended: 178 | 2026-10-15T16:22:28+00:00 | Vulnerability · Source |
| CVE-2025-49179 | suse_vex | SUSE CVE CVE-2025-49179 | known affected: 447 recommended: 195 | 2026-10-15T16:22:26+00:00 | Vulnerability · Source |
| CVE-2025-49630 | suse_vex | SUSE CVE CVE-2025-49630 | known affected: 484 known not affected: 49 recommended: 251 | 2026-10-15T16:22:24+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-15T16:22:22+00:00 | Vulnerability · Source |
| CVE-2025-49812 | suse_vex | SUSE CVE CVE-2025-49812 | known affected: 534 recommended: 309 | 2026-10-15T16:22:21+00:00 | Vulnerability · Source |
| CVE-2025-49825 | suse_vex | SUSE CVE CVE-2025-49825 | recommended: 17 | 2026-10-15T16:22:19+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-15T16:22:18+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-15T16:22:16+00:00 | Vulnerability · Source |
| CVE-2025-50101 | suse_vex | SUSE CVE CVE-2025-50101 | recommended: 34 | 2026-10-15T16:22:14+00:00 | Vulnerability · Source |
| CVE-2025-50106 | suse_vex | SUSE CVE CVE-2025-50106 | known affected: 626 recommended: 910 | 2026-10-15T16:22:13+00:00 | Vulnerability · Source |
| CVE-2025-50181 | suse_vex | SUSE CVE CVE-2025-50181 | known affected: 480 recommended: 103 | 2026-10-15T16:22:11+00:00 | Vulnerability · Source |
| CVE-2025-50182 | suse_vex | SUSE CVE CVE-2025-50182 | known not affected: 179 recommended: 6 | 2026-10-15T16:22:09+00:00 | Vulnerability · Source |
| CVE-2025-52473 | suse_vex | SUSE CVE CVE-2025-52473 | known affected: 16 recommended: 34 | 2026-10-15T16:22:07+00:00 | Vulnerability · Source |
| CVE-2025-52477 | suse_vex | SUSE CVE CVE-2025-52477 | recommended: 4 | 2026-10-15T16:22:06+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-15T16:22:04+00:00 | Vulnerability · Source |
| CVE-2025-52996 | suse_vex | SUSE CVE CVE-2025-52996 | recommended: 4 | 2026-10-15T16:22:03+00:00 | Vulnerability · Source |
| CVE-2025-53015 | suse_vex | SUSE CVE CVE-2025-53015 | known not affected: 355 recommended: 164 | 2026-10-15T16:22:01+00:00 | Vulnerability · Source |
| CVE-2025-53019 | suse_vex | SUSE CVE CVE-2025-53019 | known affected: 322 known not affected: 24 recommended: 195 | 2026-10-15T16:22:00+00:00 | Vulnerability · Source |
| CVE-2025-53066 | suse_vex | SUSE CVE CVE-2025-53066 | known affected: 394 known not affected: 208 recommended: 954 | 2026-10-15T16:21:58+00:00 | Vulnerability · Source |
| CVE-2026-90272 | redhat_vex | kernel: perf: arm_pmuv3: Zero initialize hw_id branch stack field | known affected: 77 known not affected: 200 | 2026-10-15T16:10:06+00:00 | Vulnerability · Source |
| CVE-2026-89640 | redhat_vex | kernel: cifs: fix loff_t underflow in cifs_remap_file_range() when len == 0 | known affected: 235 known not affected: 42 | 2026-10-15T16:10:02+00:00 | Vulnerability · Source |
| CVE-2026-89635 | redhat_vex | kernel: ksmbd: only rebind the reopened file's own oplock on durable reconnect | known not affected: 277 | 2026-10-15T16:09:57+00:00 | Vulnerability · Source |