VEX records
Browse vendor VEX statements available in this Vulnerability-Lookup instance and pivot to the related vulnerability.
306223 VEX records
API response| Vulnerability | Source | Title | Product status | Imported | Links |
|---|---|---|---|---|---|
| CVE-2025-1215 | suse_vex | SUSE CVE CVE-2025-1215 | known affected: 540 known not affected: 4 recommended: 158 | 2026-10-10T16:49:21+00:00 | Vulnerability · Source |
| CVE-2025-1218 | suse_vex | SUSE CVE CVE-2025-1218 | known affected: 2257 recommended: 307 | 2026-10-10T16:49:19+00:00 | Vulnerability · Source |
| CVE-2025-1377 | suse_vex | SUSE CVE CVE-2025-1377 | known affected: 173 known not affected: 373 recommended: 282 | 2026-10-10T16:49:16+00:00 | Vulnerability · Source |
| CVE-2025-1472 | suse_vex | SUSE CVE CVE-2025-1472 | recommended: 4 | 2026-10-10T16:49:13+00:00 | Vulnerability · Source |
| CVE-2025-1594 | suse_vex | SUSE CVE CVE-2025-1594 | known affected: 705 recommended: 199 | 2026-10-10T16:49:10+00:00 | Vulnerability · Source |
| CVE-2025-1736 | suse_vex | SUSE CVE CVE-2025-1736 | known not affected: 648 recommended: 1953 | 2026-10-10T16:49:07+00:00 | Vulnerability · Source |
| CVE-2025-1816 | suse_vex | SUSE CVE CVE-2025-1816 | known not affected: 673 recommended: 52 | 2026-10-10T16:49:04+00:00 | Vulnerability · Source |
| CVE-2025-1941 | suse_vex | SUSE CVE CVE-2025-1941 | recommended: 9 | 2026-10-10T16:49:01+00:00 | Vulnerability · Source |
| CVE-2025-2176 | suse_vex | SUSE CVE CVE-2025-2176 | known affected: 16 recommended: 64 | 2026-10-10T16:48:57+00:00 | Vulnerability · Source |
| CVE-2025-2177 | suse_vex | SUSE CVE CVE-2025-2177 | known affected: 16 recommended: 64 | 2026-10-10T16:48:54+00:00 | Vulnerability · Source |
| CVE-2025-2312 | suse_vex | SUSE CVE CVE-2025-2312 | known affected: 342 known not affected: 499 recommended: 460 | 2026-10-10T16:48:52+00:00 | Vulnerability · Source |
| CVE-2025-2588 | suse_vex | SUSE CVE CVE-2025-2588 | known affected: 500 recommended: 175 | 2026-10-10T16:48:48+00:00 | Vulnerability · Source |
| CVE-2025-3028 | suse_vex | SUSE CVE CVE-2025-3028 | known affected: 73 recommended: 151 | 2026-10-10T16:48:44+00:00 | Vulnerability · Source |
| CVE-2025-3608 | suse_vex | SUSE CVE CVE-2025-3608 | known affected: 32 known not affected: 165 recommended: 9 | 2026-10-10T16:48:39+00:00 | Vulnerability · Source |
| CVE-2025-3879 | suse_vex | SUSE CVE CVE-2025-3879 | known not affected: 94 recommended: 4 | 2026-10-10T16:48:36+00:00 | Vulnerability · Source |
| CVE-2025-3891 | suse_vex | SUSE CVE CVE-2025-3891 | known affected: 12 recommended: 31 | 2026-10-10T16:48:32+00:00 | Vulnerability · Source |
| CVE-2025-4123 | suse_vex | SUSE CVE CVE-2025-4123 | known not affected: 2 recommended: 13 | 2026-10-10T16:48:29+00:00 | Vulnerability · Source |
| CVE-2025-4330 | suse_vex | SUSE CVE CVE-2025-4330 | known affected: 394 known not affected: 256 recommended: 930 | 2026-10-10T16:48:25+00:00 | Vulnerability · Source |
| CVE-2025-4478 | suse_vex | SUSE CVE CVE-2025-4478 | known not affected: 75 recommended: 117 | 2026-10-10T16:48:22+00:00 | Vulnerability · Source |
| CVE-2025-4517 | suse_vex | SUSE CVE CVE-2025-4517 | known affected: 435 known not affected: 165 recommended: 962 | 2026-10-10T16:48:19+00:00 | Vulnerability · Source |
| CVE-2025-4802 | suse_vex | SUSE CVE CVE-2025-4802 | known affected: 339 known not affected: 332 recommended: 1138 | 2026-10-10T16:48:15+00:00 | Vulnerability · Source |
| CVE-2025-4878 | suse_vex | SUSE CVE CVE-2025-4878 | known affected: 418 recommended: 199 | 2026-10-10T16:48:12+00:00 | Vulnerability · Source |
| CVE-2025-4918 | suse_vex | SUSE CVE CVE-2025-4918 | known affected: 65 recommended: 155 | 2026-10-10T16:48:09+00:00 | Vulnerability · Source |
| CVE-2025-4945 | suse_vex | SUSE CVE CVE-2025-4945 | known affected: 329 recommended: 134 | 2026-10-10T16:48:07+00:00 | Vulnerability · Source |
| CVE-2025-4948 | suse_vex | SUSE CVE CVE-2025-4948 | known affected: 41 recommended: 252 | 2026-10-10T16:48:05+00:00 | Vulnerability · Source |
| CVE-2025-5264 | suse_vex | SUSE CVE CVE-2025-5264 | known affected: 73 recommended: 185 | 2026-10-10T16:48:00+00:00 | Vulnerability · Source |
| CVE-2025-5270 | suse_vex | SUSE CVE CVE-2025-5270 | known affected: 73 recommended: 9 | 2026-10-10T16:47:58+00:00 | Vulnerability · Source |
| CVE-2025-5399 | suse_vex | SUSE CVE CVE-2025-5399 | known affected: 394 known not affected: 183 recommended: 81 | 2026-10-10T16:47:56+00:00 | Vulnerability · Source |
| CVE-2025-5455 | suse_vex | SUSE CVE CVE-2025-5455 | known affected: 2438 known not affected: 118 recommended: 817 | 2026-10-10T16:47:53+00:00 | Vulnerability · Source |
| CVE-2025-5601 | suse_vex | SUSE CVE CVE-2025-5601 | known affected: 304 recommended: 221 | 2026-10-10T16:47:51+00:00 | Vulnerability · Source |
| CVE-2025-5914 | suse_vex | SUSE CVE CVE-2025-5914 | known affected: 489 known not affected: 64 recommended: 94 | 2026-10-10T16:47:49+00:00 | Vulnerability · Source |
| CVE-2025-5918 | suse_vex | SUSE CVE CVE-2025-5918 | known affected: 503 known not affected: 63 recommended: 70 | 2026-10-10T16:47:47+00:00 | Vulnerability · Source |
| CVE-2025-6000 | suse_vex | SUSE CVE CVE-2025-6000 | recommended: 12 | 2026-10-10T16:47:45+00:00 | Vulnerability · Source |
| CVE-2025-6019 | suse_vex | SUSE CVE CVE-2025-6019 | known affected: 36 recommended: 552 | 2026-10-10T16:47:42+00:00 | Vulnerability · Source |
| CVE-2025-6021 | suse_vex | SUSE CVE CVE-2025-6021 | known affected: 486 known not affected: 455 recommended: 281 | 2026-10-10T16:47:41+00:00 | Vulnerability · Source |
| CVE-2025-6037 | suse_vex | SUSE CVE CVE-2025-6037 | recommended: 4 | 2026-10-10T16:47:39+00:00 | Vulnerability · Source |
| CVE-2025-6075 | suse_vex | SUSE CVE CVE-2025-6075 | known affected: 634 recommended: 893 | 2026-10-10T16:47:37+00:00 | Vulnerability · Source |
| CVE-2025-6176 | suse_vex | SUSE CVE CVE-2025-6176 | known not affected: 65 recommended: 22 | 2026-10-10T16:47:34+00:00 | Vulnerability · Source |
| CVE-2025-6436 | suse_vex | SUSE CVE CVE-2025-6436 | known affected: 73 recommended: 336 | 2026-10-10T16:47:31+00:00 | Vulnerability · Source |
| CVE-2025-6558 | suse_vex | SUSE CVE CVE-2025-6558 | known affected: 220 recommended: 575 | 2026-10-10T16:47:29+00:00 | Vulnerability · Source |
| CVE-2025-8041 | suse_vex | SUSE CVE CVE-2025-8041 | recommended: 9 | 2026-10-10T16:47:25+00:00 | Vulnerability · Source |
| CVE-2025-8067 | suse_vex | SUSE CVE CVE-2025-8067 | known affected: 493 recommended: 255 | 2026-10-10T16:47:23+00:00 | Vulnerability · Source |
| CVE-2025-8077 | suse_vex | SUSE CVE CVE-2025-8077 | recommended: 1 | 2026-10-10T16:47:21+00:00 | Vulnerability · Source |
| CVE-2025-8194 | suse_vex | SUSE CVE CVE-2025-8194 | known affected: 713 recommended: 901 | 2026-10-10T16:47:19+00:00 | Vulnerability · Source |
| CVE-2025-8341 | suse_vex | SUSE CVE CVE-2025-8341 | recommended: 4 | 2026-10-10T16:47:17+00:00 | Vulnerability · Source |
| CVE-2025-8671 | suse_vex | SUSE CVE CVE-2025-8671 | known not affected: 2 recommended: 28 | 2026-10-10T16:47:15+00:00 | Vulnerability · Source |
| CVE-2025-9086 | suse_vex | SUSE CVE CVE-2025-9086 | known affected: 382 known not affected: 59 recommended: 242 | 2026-10-10T16:47:12+00:00 | Vulnerability · Source |
| CVE-2025-9180 | suse_vex | SUSE CVE CVE-2025-9180 | known affected: 73 recommended: 185 | 2026-10-10T16:47:09+00:00 | Vulnerability · Source |
| CVE-2025-9182 | suse_vex | SUSE CVE CVE-2025-9182 | known affected: 73 recommended: 171 | 2026-10-10T16:47:07+00:00 | Vulnerability · Source |
| CVE-2025-9230 | suse_vex | SUSE CVE CVE-2025-9230 | known affected: 556 known not affected: 117 recommended: 556 | 2026-10-10T16:47:04+00:00 | Vulnerability · Source |