VEX records
Browse vendor VEX statements available in this Vulnerability-Lookup instance and pivot to the related vulnerability.
292225 VEX records
API response| Vulnerability | Source | Title | Product status | Imported | Links |
|---|---|---|---|---|---|
| CVE-2025-47283 | suse_vex | SUSE CVE CVE-2025-47283 | recommended: 3 | 2026-07-16T18:13:40+00:00 | Vulnerability · Source |
| CVE-2025-47711 | suse_vex | SUSE CVE CVE-2025-47711 | known not affected: 3 recommended: 128 | 2026-07-16T18:13:37+00:00 | Vulnerability · Source |
| CVE-2025-47933 | suse_vex | SUSE CVE CVE-2025-47933 | recommended: 3 | 2026-07-16T18:13:30+00:00 | Vulnerability · Source |
| CVE-2025-48371 | suse_vex | SUSE CVE CVE-2025-48371 | recommended: 3 | 2026-07-16T18:13:27+00:00 | Vulnerability · Source |
| CVE-2025-48494 | suse_vex | SUSE CVE CVE-2025-48494 | recommended: 3 | 2026-07-16T18:13:25+00:00 | Vulnerability · Source |
| CVE-2025-48710 | suse_vex | SUSE CVE CVE-2025-48710 | recommended: 3 | 2026-07-16T18:13:23+00:00 | Vulnerability · Source |
| CVE-2025-49112 | suse_vex | SUSE CVE CVE-2025-49112 | recommended: 36 | 2026-07-16T18:13:19+00:00 | Vulnerability · Source |
| CVE-2025-49133 | suse_vex | SUSE CVE CVE-2025-49133 | known affected: 83 recommended: 143 | 2026-07-16T18:13:18+00:00 | Vulnerability · Source |
| CVE-2025-49825 | suse_vex | SUSE CVE CVE-2025-49825 | recommended: 16 | 2026-07-16T18:13:15+00:00 | Vulnerability · Source |
| CVE-2025-50420 | suse_vex | SUSE CVE CVE-2025-50420 | known affected: 162 known not affected: 11 recommended: 219 | 2026-07-16T18:13:13+00:00 | Vulnerability · Source |
| CVE-2025-52901 | suse_vex | SUSE CVE CVE-2025-52901 | recommended: 3 | 2026-07-16T18:13:08+00:00 | Vulnerability · Source |
| CVE-2025-54389 | suse_vex | SUSE CVE CVE-2025-54389 | known affected: 4 known not affected: 54 recommended: 7 | 2026-07-16T18:12:54+00:00 | Vulnerability · Source |
| CVE-2025-54997 | suse_vex | SUSE CVE CVE-2025-54997 | recommended: 3 | 2026-07-16T18:12:47+00:00 | Vulnerability · Source |
| CVE-2025-55001 | suse_vex | SUSE CVE CVE-2025-55001 | recommended: 3 | 2026-07-16T18:12:45+00:00 | Vulnerability · Source |
| CVE-2025-55199 | suse_vex | SUSE CVE CVE-2025-55199 | known not affected: 78 recommended: 49 | 2026-07-16T18:12:40+00:00 | Vulnerability · Source |
| CVE-2025-58364 | suse_vex | SUSE CVE CVE-2025-58364 | known affected: 451 known not affected: 1 recommended: 424 | 2026-07-16T18:12:30+00:00 | Vulnerability · Source |
| CVE-2025-59432 | suse_vex | SUSE CVE CVE-2025-59432 | known affected: 426 recommended: 137 | 2026-07-16T18:12:28+00:00 | Vulnerability · Source |
| CVE-2025-61099 | suse_vex | SUSE CVE CVE-2025-61099 | known affected: 233 known not affected: 237 recommended: 122 | 2026-07-16T18:12:22+00:00 | Vulnerability · Source |
| CVE-2025-61107 | suse_vex | SUSE CVE CVE-2025-61107 | known affected: 233 recommended: 112 | 2026-07-16T18:12:20+00:00 | Vulnerability · Source |
| CVE-2025-61748 | suse_vex | SUSE CVE CVE-2025-61748 | known affected: 394 known not affected: 438 recommended: 337 | 2026-07-16T18:12:11+00:00 | Vulnerability · Source |
| CVE-2025-61912 | suse_vex | SUSE CVE CVE-2025-61912 | known affected: 18 recommended: 17 | 2026-07-16T18:12:09+00:00 | Vulnerability · Source |
| CVE-2025-62518 | suse_vex | SUSE CVE CVE-2025-62518 | recommended: 13 | 2026-07-16T18:12:03+00:00 | Vulnerability · Source |
| CVE-2025-62727 | suse_vex | SUSE CVE CVE-2025-62727 | known not affected: 2 recommended: 10 | 2026-07-16T18:12:02+00:00 | Vulnerability · Source |
| CVE-2025-64076 | suse_vex | SUSE CVE CVE-2025-64076 | recommended: 4 | 2026-07-16T18:12:01+00:00 | Vulnerability · Source |
| CVE-2025-64182 | suse_vex | SUSE CVE CVE-2025-64182 | known not affected: 142 recommended: 30 | 2026-07-16T18:12:00+00:00 | Vulnerability · Source |
| CVE-2025-66034 | suse_vex | SUSE CVE CVE-2025-66034 | known affected: 2 recommended: 9 | 2026-07-16T18:11:54+00:00 | Vulnerability · Source |
| CVE-2025-66453 | suse_vex | SUSE CVE CVE-2025-66453 | known affected: 19 recommended: 41 | 2026-07-16T18:11:53+00:00 | Vulnerability · Source |
| CVE-2025-67221 | suse_vex | SUSE CVE CVE-2025-67221 | recommended: 7 | 2026-07-16T18:11:49+00:00 | Vulnerability · Source |
| CVE-2025-67268 | suse_vex | SUSE CVE CVE-2025-67268 | recommended: 13 | 2026-07-16T18:11:48+00:00 | Vulnerability · Source |
| CVE-2025-68131 | suse_vex | SUSE CVE CVE-2025-68131 | known affected: 5 recommended: 8 | 2026-07-16T18:11:45+00:00 | Vulnerability · Source |
| CVE-2025-68146 | suse_vex | SUSE CVE CVE-2025-68146 | known affected: 39 recommended: 23 | 2026-07-16T18:11:44+00:00 | Vulnerability · Source |
| CVE-2025-69224 | suse_vex | SUSE CVE CVE-2025-69224 | known affected: 394 recommended: 53 | 2026-07-16T18:10:15+00:00 | Vulnerability · Source |
| CVE-2025-69227 | suse_vex | SUSE CVE CVE-2025-69227 | known affected: 394 recommended: 53 | 2026-07-16T18:10:14+00:00 | Vulnerability · Source |
| CVE-2025-69229 | suse_vex | SUSE CVE CVE-2025-69229 | known affected: 394 recommended: 53 | 2026-07-16T18:10:13+00:00 | Vulnerability · Source |
| CVE-2026-2243 | suse_vex | SUSE CVE CVE-2026-2243 | known affected: 976 recommended: 678 | 2026-07-16T18:09:09+00:00 | Vulnerability · Source |
| CVE-2026-7814 | suse_vex | SUSE CVE CVE-2026-7814 | known not affected: 75 | 2026-07-16T18:08:30+00:00 | Vulnerability · Source |
| CVE-2026-7815 | suse_vex | SUSE CVE CVE-2026-7815 | known not affected: 75 | 2026-07-16T18:08:29+00:00 | Vulnerability · Source |
| CVE-2026-9501 | suse_vex | SUSE CVE CVE-2026-9501 | recommended: 6 | 2026-07-16T18:08:23+00:00 | Vulnerability · Source |
| CVE-2026-15747 | suse_vex | SUSE CVE CVE-2026-15747 | known affected: 1 recommended: 1 | 2026-07-16T18:08:04+00:00 | Vulnerability · Source |
| CVE-2026-23479 | suse_vex | SUSE CVE CVE-2026-23479 | known not affected: 20 recommended: 43 | 2026-07-16T18:06:28+00:00 | Vulnerability · Source |
| CVE-2026-25243 | suse_vex | SUSE CVE CVE-2026-25243 | known affected: 4 recommended: 64 | 2026-07-16T18:06:25+00:00 | Vulnerability · Source |
| CVE-2026-27651 | suse_vex | SUSE CVE CVE-2026-27651 | known affected: 406 recommended: 75 | 2026-07-16T18:06:09+00:00 | Vulnerability · Source |
| CVE-2026-28847 | suse_vex | SUSE CVE CVE-2026-28847 | known affected: 70 recommended: 487 | 2026-07-16T18:06:04+00:00 | Vulnerability · Source |
| CVE-2026-33815 | suse_vex | SUSE CVE CVE-2026-33815 | known not affected: 5 recommended: 39 | 2026-07-16T18:04:09+00:00 | Vulnerability · Source |
| CVE-2026-34956 | suse_vex | SUSE CVE CVE-2026-34956 | known affected: 335 known not affected: 1 recommended: 179 | 2026-07-16T18:04:01+00:00 | Vulnerability · Source |
| CVE-2026-38752 | suse_vex | SUSE CVE CVE-2026-38752 | known affected: 50 | 2026-07-16T18:03:51+00:00 | Vulnerability · Source |
| CVE-2026-38753 | suse_vex | SUSE CVE CVE-2026-38753 | known affected: 50 | 2026-07-16T18:03:50+00:00 | Vulnerability · Source |
| CVE-2026-38755 | suse_vex | SUSE CVE CVE-2026-38755 | known affected: 50 | 2026-07-16T18:03:49+00:00 | Vulnerability · Source |
| CVE-2026-41888 | suse_vex | SUSE CVE CVE-2026-41888 | known affected: 37 recommended: 83 | 2026-07-16T18:03:18+00:00 | Vulnerability · Source |
| CVE-2026-44216 | suse_vex | SUSE CVE CVE-2026-44216 | recommended: 17 | 2026-07-16T18:00:30+00:00 | Vulnerability · Source |