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-2783 | suse_vex | SUSE CVE CVE-2025-2783 | recommended: 43 | 2026-10-16T13:06:03+00:00 | Vulnerability · Source |
| CVE-2025-3228 | suse_vex | SUSE CVE CVE-2025-3228 | recommended: 5 | 2026-10-16T13:06:01+00:00 | Vulnerability · Source |
| CVE-2025-3230 | suse_vex | SUSE CVE CVE-2025-3230 | recommended: 5 | 2026-10-16T13:05:59+00:00 | Vulnerability · Source |
| CVE-2025-3454 | suse_vex | SUSE CVE CVE-2025-3454 | known affected: 1 recommended: 27 | 2026-10-16T13:05:58+00:00 | Vulnerability · Source |
| CVE-2025-4947 | suse_vex | SUSE CVE CVE-2025-4947 | known affected: 394 known not affected: 183 recommended: 73 | 2026-10-16T13:05:55+00:00 | Vulnerability · Source |
| CVE-2025-5187 | suse_vex | SUSE CVE CVE-2025-5187 | known affected: 0 known not affected: 441 recommended: 3 | 2026-10-16T13:05:53+00:00 | Vulnerability · Source |
| CVE-2025-5601 | suse_vex | SUSE CVE CVE-2025-5601 | known affected: 304 recommended: 227 | 2026-10-16T13:05:51+00:00 | Vulnerability · Source |
| CVE-2025-5981 | suse_vex | SUSE CVE CVE-2025-5981 | recommended: 5 | 2026-10-16T13:05:49+00:00 | Vulnerability · Source |
| CVE-2025-5987 | suse_vex | SUSE CVE CVE-2025-5987 | known affected: 394 known not affected: 261 recommended: 29 | 2026-10-16T13:05:47+00:00 | Vulnerability · Source |
| CVE-2025-6011 | suse_vex | SUSE CVE CVE-2025-6011 | recommended: 13 | 2026-10-16T13:05:46+00:00 | Vulnerability · Source |
| CVE-2025-6013 | suse_vex | SUSE CVE CVE-2025-6013 | recommended: 13 | 2026-10-16T13:05:44+00:00 | Vulnerability · Source |
| CVE-2025-6020 | suse_vex | SUSE CVE CVE-2025-6020 | known affected: 503 recommended: 223 | 2026-10-16T13:05:42+00:00 | Vulnerability · Source |
| CVE-2025-6032 | suse_vex | SUSE CVE CVE-2025-6032 | known affected: 394 known not affected: 17 recommended: 164 | 2026-10-16T13:05:41+00:00 | Vulnerability · Source |
| CVE-2025-6037 | suse_vex | SUSE CVE CVE-2025-6037 | recommended: 5 | 2026-10-16T13:05:39+00:00 | Vulnerability · Source |
| CVE-2025-6203 | suse_vex | SUSE CVE CVE-2025-6203 | recommended: 11 | 2026-10-16T13:05:37+00:00 | Vulnerability · Source |
| CVE-2025-6233 | suse_vex | SUSE CVE CVE-2025-6233 | recommended: 5 | 2026-10-16T13:05:35+00:00 | Vulnerability · Source |
| CVE-2025-6264 | suse_vex | SUSE CVE CVE-2025-6264 | known affected: 0 known not affected: 3 recommended: 5 | 2026-10-16T13:05:33+00:00 | Vulnerability · Source |
| CVE-2025-6431 | suse_vex | SUSE CVE CVE-2025-6431 | known affected: 73 recommended: 303 | 2026-10-16T13:05:30+00:00 | Vulnerability · Source |
| CVE-2025-6472 | suse_vex | SUSE CVE CVE-2025-6472 | No product status | 2026-10-16T13:05:29+00:00 | Vulnerability · Source |
| CVE-2025-7519 | suse_vex | SUSE CVE CVE-2025-7519 | known affected: 478 recommended: 201 | 2026-10-16T13:05:26+00:00 | Vulnerability · Source |
| CVE-2025-8038 | suse_vex | SUSE CVE CVE-2025-8038 | known affected: 73 recommended: 336 | 2026-10-16T13:05:23+00:00 | Vulnerability · Source |
| CVE-2025-8039 | suse_vex | SUSE CVE CVE-2025-8039 | known affected: 73 recommended: 336 | 2026-10-16T13:05:20+00:00 | Vulnerability · Source |
| CVE-2025-8040 | suse_vex | SUSE CVE CVE-2025-8040 | known affected: 73 recommended: 336 | 2026-10-16T13:05:19+00:00 | Vulnerability · Source |
| CVE-2025-8110 | suse_vex | SUSE CVE CVE-2025-8110 | recommended: 2 | 2026-10-16T13:05:17+00:00 | Vulnerability · Source |
| CVE-2025-8176 | suse_vex | SUSE CVE CVE-2025-8176 | known affected: 479 known not affected: 7 recommended: 154 | 2026-10-16T13:05:16+00:00 | Vulnerability · Source |
| CVE-2025-8283 | suse_vex | SUSE CVE CVE-2025-8283 | known affected: 0 known not affected: 31 | 2026-10-16T13:05:15+00:00 | Vulnerability · Source |
| CVE-2025-8341 | suse_vex | SUSE CVE CVE-2025-8341 | recommended: 5 | 2026-10-16T13:05:13+00:00 | Vulnerability · Source |
| CVE-2025-8715 | suse_vex | SUSE CVE CVE-2025-8715 | known affected: 615 known not affected: 524 recommended: 1402 | 2026-10-16T13:05:09+00:00 | Vulnerability · Source |
| CVE-2025-8835 | suse_vex | SUSE CVE CVE-2025-8835 | known affected: 532 recommended: 52 | 2026-10-16T13:05:08+00:00 | Vulnerability · Source |
| CVE-2025-9084 | suse_vex | SUSE CVE CVE-2025-9084 | recommended: 3 | 2026-10-16T13:05:06+00:00 | Vulnerability · Source |
| CVE-2025-9086 | suse_vex | SUSE CVE CVE-2025-9086 | known affected: 382 known not affected: 59 recommended: 249 | 2026-10-16T13:05:05+00:00 | Vulnerability · Source |
| CVE-2025-9231 | suse_vex | SUSE CVE CVE-2025-9231 | known affected: 0 known not affected: 824 recommended: 101 | 2026-10-16T13:05:02+00:00 | Vulnerability · Source |
| CVE-2025-9566 | suse_vex | SUSE CVE CVE-2025-9566 | known affected: 394 recommended: 169 | 2026-10-16T13:04:59+00:00 | Vulnerability · Source |
| CVE-2025-9951 | suse_vex | SUSE CVE CVE-2025-9951 | known affected: 705 recommended: 217 | 2026-10-16T13:04:57+00:00 | Vulnerability · Source |
| CVE-2025-10256 | suse_vex | SUSE CVE CVE-2025-10256 | known affected: 618 recommended: 289 | 2026-10-16T13:04:56+00:00 | Vulnerability · Source |
| CVE-2025-10543 | suse_vex | SUSE CVE CVE-2025-10543 | recommended: 2 | 2026-10-16T13:04:52+00:00 | Vulnerability · Source |
| CVE-2025-11230 | suse_vex | SUSE CVE CVE-2025-11230 | known affected: 0 known not affected: 3 recommended: 20 | 2026-10-16T13:04:50+00:00 | Vulnerability · Source |
| CVE-2025-11411 | suse_vex | SUSE CVE CVE-2025-11411 | known affected: 148 recommended: 89 | 2026-10-16T13:04:49+00:00 | Vulnerability · Source |
| CVE-2025-11713 | suse_vex | SUSE CVE CVE-2025-11713 | known affected: 73 recommended: 176 | 2026-10-16T13:04:45+00:00 | Vulnerability · Source |
| CVE-2025-11715 | suse_vex | SUSE CVE CVE-2025-11715 | known affected: 73 recommended: 184 | 2026-10-16T13:04:43+00:00 | Vulnerability · Source |
| CVE-2025-12818 | suse_vex | SUSE CVE CVE-2025-12818 | known affected: 553 known not affected: 684 recommended: 1925 | 2026-10-16T13:04:39+00:00 | Vulnerability · Source |
| CVE-2025-12863 | suse_vex | SUSE CVE CVE-2025-12863 | No product status | 2026-10-16T13:04:38+00:00 | Vulnerability · Source |
| CVE-2025-13012 | suse_vex | SUSE CVE CVE-2025-13012 | known affected: 28 recommended: 186 | 2026-10-16T13:04:36+00:00 | Vulnerability · Source |
| CVE-2025-13014 | suse_vex | SUSE CVE CVE-2025-13014 | known affected: 28 recommended: 186 | 2026-10-16T13:04:35+00:00 | Vulnerability · Source |
| CVE-2025-13016 | suse_vex | SUSE CVE CVE-2025-13016 | known affected: 28 recommended: 186 | 2026-10-16T13:04:34+00:00 | Vulnerability · Source |
| CVE-2025-13034 | suse_vex | SUSE CVE CVE-2025-13034 | known affected: 0 known not affected: 251 | 2026-10-16T13:04:32+00:00 | Vulnerability · Source |
| CVE-2025-14177 | suse_vex | SUSE CVE CVE-2025-14177 | known affected: 188 known not affected: 2193 recommended: 617 | 2026-10-16T13:04:29+00:00 | Vulnerability · Source |
| CVE-2025-14322 | suse_vex | SUSE CVE CVE-2025-14322 | known affected: 73 recommended: 186 | 2026-10-16T13:04:26+00:00 | Vulnerability · Source |
| CVE-2025-14327 | suse_vex | SUSE CVE CVE-2025-14327 | known affected: 73 recommended: 147 | 2026-10-16T13:04:25+00:00 | Vulnerability · Source |
| CVE-2025-14813 | suse_vex | SUSE CVE CVE-2025-14813 | known affected: 40 recommended: 108 | 2026-10-16T13:04:23+00:00 | Vulnerability · Source |