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-4517 | suse_vex | SUSE CVE CVE-2025-4517 | known affected: 435 known not affected: 165 recommended: 976 | 2026-10-16T01:09:37+00:00 | Vulnerability · Source |
| CVE-2025-4563 | suse_vex | SUSE CVE CVE-2025-4563 | known affected: 0 known not affected: 478 recommended: 5 | 2026-10-16T01:09:35+00:00 | Vulnerability · Source |
| CVE-2025-4573 | suse_vex | SUSE CVE CVE-2025-4573 | recommended: 5 | 2026-10-16T01:09:33+00:00 | Vulnerability · Source |
| CVE-2025-4575 | suse_vex | SUSE CVE CVE-2025-4575 | known affected: 0 known not affected: 854 recommended: 38 | 2026-10-16T01:09:31+00:00 | Vulnerability · Source |
| CVE-2025-4598 | suse_vex | SUSE CVE CVE-2025-4598 | known affected: 672 known not affected: 419 recommended: 571 | 2026-10-16T01:09:29+00:00 | Vulnerability · Source |
| CVE-2025-4674 | suse_vex | SUSE CVE CVE-2025-4674 | known affected: 0 known not affected: 64 recommended: 471 | 2026-10-16T01:09:26+00:00 | Vulnerability · Source |
| CVE-2025-4748 | suse_vex | SUSE CVE CVE-2025-4748 | known affected: 53 recommended: 116 | 2026-10-16T01:09:24+00:00 | Vulnerability · Source |
| CVE-2025-4877 | suse_vex | SUSE CVE CVE-2025-4877 | known affected: 418 recommended: 202 | 2026-10-16T01:09:21+00:00 | Vulnerability · Source |
| CVE-2025-4878 | suse_vex | SUSE CVE CVE-2025-4878 | known affected: 418 recommended: 202 | 2026-10-16T01:09:19+00:00 | Vulnerability · Source |
| CVE-2025-4918 | suse_vex | SUSE CVE CVE-2025-4918 | known affected: 65 recommended: 159 | 2026-10-16T01:09:16+00:00 | Vulnerability · Source |
| CVE-2025-4920 | suse_vex | SUSE CVE CVE-2025-4920 | known affected: 65 recommended: 13 | 2026-10-16T01:09:14+00:00 | Vulnerability · Source |
| CVE-2025-4921 | suse_vex | SUSE CVE CVE-2025-4921 | known affected: 65 recommended: 13 | 2026-10-16T01:09:12+00:00 | Vulnerability · Source |
| CVE-2025-4945 | suse_vex | SUSE CVE CVE-2025-4945 | known affected: 329 recommended: 139 | 2026-10-16T01:09:10+00:00 | Vulnerability · Source |
| CVE-2025-4948 | suse_vex | SUSE CVE CVE-2025-4948 | known affected: 41 recommended: 257 | 2026-10-16T01:09:08+00:00 | Vulnerability · Source |
| CVE-2025-4953 | suse_vex | SUSE CVE CVE-2025-4953 | known affected: 0 known not affected: 130 recommended: 37 | 2026-10-16T01:09:07+00:00 | Vulnerability · Source |
| CVE-2025-4969 | suse_vex | SUSE CVE CVE-2025-4969 | known affected: 109 recommended: 246 | 2026-10-16T01:09:05+00:00 | Vulnerability · Source |
| CVE-2025-5024 | suse_vex | SUSE CVE CVE-2025-5024 | known affected: 10 recommended: 28 | 2026-10-16T01:09:04+00:00 | Vulnerability · Source |
| CVE-2025-5025 | suse_vex | SUSE CVE CVE-2025-5025 | known affected: 394 known not affected: 183 recommended: 73 | 2026-10-16T01:09:02+00:00 | Vulnerability · Source |
| CVE-2025-5030 | suse_vex | SUSE CVE CVE-2025-5030 | recommended: 5 | 2026-10-16T01:09:00+00:00 | Vulnerability · Source |
| CVE-2025-5222 | suse_vex | SUSE CVE CVE-2025-5222 | known affected: 526 known not affected: 364 recommended: 223 | 2026-10-16T01:08:58+00:00 | Vulnerability · Source |
| CVE-2025-5244 | suse_vex | SUSE CVE CVE-2025-5244 | known affected: 483 recommended: 498 | 2026-10-16T01:08:56+00:00 | Vulnerability · Source |
| CVE-2025-5245 | suse_vex | SUSE CVE CVE-2025-5245 | known affected: 528 recommended: 495 | 2026-10-16T01:08:54+00:00 | Vulnerability · Source |
| CVE-2025-5265 | suse_vex | SUSE CVE CVE-2025-5265 | known affected: 73 recommended: 183 | 2026-10-16T01:08:52+00:00 | Vulnerability · Source |
| CVE-2025-5267 | suse_vex | SUSE CVE CVE-2025-5267 | known affected: 73 recommended: 191 | 2026-10-16T01:08:50+00:00 | Vulnerability · Source |
| CVE-2025-5268 | suse_vex | SUSE CVE CVE-2025-5268 | known affected: 73 recommended: 191 | 2026-10-16T01:08:48+00:00 | Vulnerability · Source |
| CVE-2025-5269 | suse_vex | SUSE CVE CVE-2025-5269 | known affected: 73 recommended: 186 | 2026-10-16T01:08:46+00:00 | Vulnerability · Source |
| CVE-2025-5278 | suse_vex | SUSE CVE CVE-2025-5278 | known affected: 390 recommended: 180 | 2026-10-16T01:08:43+00:00 | Vulnerability · Source |
| CVE-2025-5399 | suse_vex | SUSE CVE CVE-2025-5399 | known affected: 394 known not affected: 183 recommended: 88 | 2026-10-16T01:08:41+00:00 | Vulnerability · Source |
| CVE-2025-5449 | suse_vex | SUSE CVE CVE-2025-5449 | known affected: 0 known not affected: 267 recommended: 16 | 2026-10-16T01:08:39+00:00 | Vulnerability · Source |
| CVE-2025-5689 | suse_vex | SUSE CVE CVE-2025-5689 | recommended: 5 | 2026-10-16T01:08:37+00:00 | Vulnerability · Source |
| CVE-2025-5745 | suse_vex | SUSE CVE CVE-2025-5745 | known affected: 0 known not affected: 696 recommended: 64 | 2026-10-16T01:08:35+00:00 | Vulnerability · Source |
| CVE-2025-5889 | suse_vex | SUSE CVE CVE-2025-5889 | known affected: 647 known not affected: 6 recommended: 203 | 2026-10-16T01:08:32+00:00 | Vulnerability · Source |
| CVE-2025-5994 | suse_vex | SUSE CVE CVE-2025-5994 | known affected: 0 known not affected: 221 recommended: 40 | 2026-10-16T01:08:29+00:00 | Vulnerability · Source |
| CVE-2025-6018 | suse_vex | SUSE CVE CVE-2025-6018 | known affected: 465 known not affected: 18 recommended: 610 | 2026-10-16T01:08:27+00:00 | Vulnerability · Source |
| CVE-2025-6019 | suse_vex | SUSE CVE CVE-2025-6019 | known affected: 36 recommended: 591 | 2026-10-16T01:08:25+00:00 | Vulnerability · Source |
| CVE-2025-6021 | suse_vex | SUSE CVE CVE-2025-6021 | known affected: 486 known not affected: 456 recommended: 286 | 2026-10-16T01:08:22+00:00 | Vulnerability · Source |
| CVE-2025-6023 | suse_vex | SUSE CVE CVE-2025-6023 | recommended: 71 | 2026-10-16T01:08:20+00:00 | Vulnerability · Source |
| CVE-2025-6052 | suse_vex | SUSE CVE CVE-2025-6052 | known affected: 394 known not affected: 655 recommended: 218 | 2026-10-16T01:08:18+00:00 | Vulnerability · Source |
| CVE-2025-6170 | suse_vex | SUSE CVE CVE-2025-6170 | known affected: 487 known not affected: 65 recommended: 286 | 2026-10-16T01:08:16+00:00 | Vulnerability · Source |
| CVE-2025-6199 | suse_vex | SUSE CVE CVE-2025-6199 | known affected: 464 known not affected: 169 recommended: 301 | 2026-10-16T01:08:14+00:00 | Vulnerability · Source |
| CVE-2025-6226 | suse_vex | SUSE CVE CVE-2025-6226 | recommended: 5 | 2026-10-16T01:08:11+00:00 | Vulnerability · Source |
| CVE-2025-6227 | suse_vex | SUSE CVE CVE-2025-6227 | recommended: 5 | 2026-10-16T01:08:09+00:00 | Vulnerability · Source |
| CVE-2025-6297 | suse_vex | SUSE CVE CVE-2025-6297 | known affected: 76 recommended: 57 | 2026-10-16T01:08:07+00:00 | Vulnerability · Source |
| CVE-2025-6395 | suse_vex | SUSE CVE CVE-2025-6395 | known affected: 471 known not affected: 79 recommended: 314 | 2026-10-16T01:08:05+00:00 | Vulnerability · Source |
| CVE-2025-6424 | suse_vex | SUSE CVE CVE-2025-6424 | known affected: 73 recommended: 363 | 2026-10-16T01:08:04+00:00 | Vulnerability · Source |
| CVE-2025-6425 | suse_vex | SUSE CVE CVE-2025-6425 | known affected: 73 recommended: 363 | 2026-10-16T01:08:01+00:00 | Vulnerability · Source |
| CVE-2025-6427 | suse_vex | SUSE CVE CVE-2025-6427 | known affected: 73 recommended: 340 | 2026-10-16T01:07:59+00:00 | Vulnerability · Source |
| CVE-2025-6430 | suse_vex | SUSE CVE CVE-2025-6430 | known affected: 73 recommended: 363 | 2026-10-16T01:07:57+00:00 | Vulnerability · Source |
| CVE-2025-6433 | suse_vex | SUSE CVE CVE-2025-6433 | known affected: 73 recommended: 340 | 2026-10-16T01:07:54+00:00 | Vulnerability · Source |
| CVE-2025-6434 | suse_vex | SUSE CVE CVE-2025-6434 | known affected: 73 recommended: 340 | 2026-10-16T01:07:52+00:00 | Vulnerability · Source |