VEX records
Browse vendor VEX statements available in this Vulnerability-Lookup instance and pivot to the related vulnerability.
291864 VEX records
API response| Vulnerability | Source | Title | Product status | Imported | Links |
|---|---|---|---|---|---|
| CVE-2025-62168 | suse_vex | SUSE CVE CVE-2025-62168 | known affected: 10 recommended: 40 | 2026-08-12T16:48:49+00:00 | Vulnerability · Source |
| CVE-2025-62231 | suse_vex | SUSE CVE CVE-2025-62231 | known affected: 421 recommended: 187 | 2026-08-12T16:48:46+00:00 | Vulnerability · Source |
| CVE-2025-62348 | suse_vex | SUSE CVE CVE-2025-62348 | known affected: 454 known not affected: 30 recommended: 484 | 2026-08-12T16:48:44+00:00 | Vulnerability · Source |
| CVE-2025-62594 | suse_vex | SUSE CVE CVE-2025-62594 | known affected: 81 known not affected: 153 recommended: 229 | 2026-08-12T16:48:41+00:00 | Vulnerability · Source |
| CVE-2025-66004 | suse_vex | SUSE CVE CVE-2025-66004 | known affected: 11 recommended: 9 | 2026-08-12T16:48:36+00:00 | Vulnerability · Source |
| CVE-2025-66293 | suse_vex | SUSE CVE CVE-2025-66293 | known affected: 406 known not affected: 149 recommended: 350 | 2026-08-12T16:48:33+00:00 | Vulnerability · Source |
| CVE-2025-66614 | suse_vex | SUSE CVE CVE-2025-66614 | known affected: 79 recommended: 456 | 2026-08-12T16:48:28+00:00 | Vulnerability · Source |
| CVE-2025-66864 | suse_vex | SUSE CVE CVE-2025-66864 | known affected: 1 known not affected: 213 | 2026-08-12T16:48:24+00:00 | Vulnerability · Source |
| CVE-2025-68114 | suse_vex | SUSE CVE CVE-2025-68114 | known affected: 37 recommended: 24 | 2026-08-12T16:48:19+00:00 | Vulnerability · Source |
| CVE-2025-68173 | suse_vex | SUSE CVE CVE-2025-68173 | first fixed: 2 known affected: 395 known not affected: 38 recommended: 172 | 2026-08-12T16:48:15+00:00 | Vulnerability · Source |
| CVE-2025-68177 | suse_vex | SUSE CVE CVE-2025-68177 | known not affected: 453 | 2026-08-12T16:48:13+00:00 | Vulnerability · Source |
| CVE-2025-68196 | suse_vex | SUSE CVE CVE-2025-68196 | known not affected: 432 | 2026-08-12T16:48:05+00:00 | Vulnerability · Source |
| CVE-2025-68213 | suse_vex | SUSE CVE CVE-2025-68213 | first fixed: 2 known affected: 394 known not affected: 415 recommended: 172 | 2026-08-12T16:47:59+00:00 | Vulnerability · Source |
| CVE-2025-68214 | suse_vex | SUSE CVE CVE-2025-68214 | known affected: 398 known not affected: 52 recommended: 83 | 2026-08-12T16:47:58+00:00 | Vulnerability · Source |
| CVE-2025-68219 | suse_vex | SUSE CVE CVE-2025-68219 | known affected: 351 known not affected: 99 | 2026-08-12T16:47:54+00:00 | Vulnerability · Source |
| CVE-2025-68225 | suse_vex | SUSE CVE CVE-2025-68225 | known not affected: 418 | 2026-08-12T16:47:52+00:00 | Vulnerability · Source |
| CVE-2025-68242 | suse_vex | SUSE CVE CVE-2025-68242 | first fixed: 2 known affected: 394 known not affected: 415 recommended: 172 | 2026-08-12T16:47:45+00:00 | Vulnerability · Source |
| CVE-2025-68247 | suse_vex | SUSE CVE CVE-2025-68247 | known not affected: 418 | 2026-08-12T16:47:42+00:00 | Vulnerability · Source |
| CVE-2025-68253 | suse_vex | SUSE CVE CVE-2025-68253 | known not affected: 418 | 2026-08-12T16:47:38+00:00 | Vulnerability · Source |
| CVE-2025-68281 | suse_vex | SUSE CVE CVE-2025-68281 | known not affected: 432 recommended: 27 | 2026-08-12T16:47:34+00:00 | Vulnerability · Source |
| CVE-2025-68305 | suse_vex | SUSE CVE CVE-2025-68305 | first fixed: 2 known affected: 394 known not affected: 289 recommended: 522 | 2026-08-12T16:47:23+00:00 | Vulnerability · Source |
| CVE-2025-68309 | suse_vex | SUSE CVE CVE-2025-68309 | known not affected: 418 | 2026-08-12T16:47:19+00:00 | Vulnerability · Source |
| CVE-2025-68311 | suse_vex | SUSE CVE CVE-2025-68311 | first fixed: 2 known affected: 394 known not affected: 436 recommended: 172 | 2026-08-12T16:47:17+00:00 | Vulnerability · Source |
| CVE-2025-68316 | suse_vex | SUSE CVE CVE-2025-68316 | known not affected: 418 | 2026-08-12T16:47:14+00:00 | Vulnerability · Source |
| CVE-2025-68318 | suse_vex | SUSE CVE CVE-2025-68318 | known not affected: 448 | 2026-08-12T16:47:12+00:00 | Vulnerability · Source |
| CVE-2025-68357 | suse_vex | SUSE CVE CVE-2025-68357 | known not affected: 453 recommended: 6 | 2026-08-12T16:47:03+00:00 | Vulnerability · Source |
| CVE-2025-68358 | suse_vex | SUSE CVE CVE-2025-68358 | known affected: 449 known not affected: 6 recommended: 6 | 2026-08-12T16:47:01+00:00 | Vulnerability · Source |
| CVE-2025-68366 | suse_vex | SUSE CVE CVE-2025-68366 | first fixed: 2 known affected: 709 known not affected: 22 recommended: 439 | 2026-08-12T16:46:59+00:00 | Vulnerability · Source |
| CVE-2025-68471 | suse_vex | SUSE CVE CVE-2025-68471 | known affected: 711 recommended: 368 | 2026-08-12T16:46:53+00:00 | Vulnerability · Source |
| CVE-2025-68615 | suse_vex | SUSE CVE CVE-2025-68615 | known affected: 492 known not affected: 10 recommended: 234 | 2026-08-12T16:46:50+00:00 | Vulnerability · Source |
| CVE-2025-68729 | suse_vex | SUSE CVE CVE-2025-68729 | known not affected: 453 recommended: 6 | 2026-08-12T16:46:47+00:00 | Vulnerability · Source |
| CVE-2025-68754 | suse_vex | SUSE CVE CVE-2025-68754 | known not affected: 353 recommended: 6 | 2026-08-12T16:46:42+00:00 | Vulnerability · Source |
| CVE-2025-68784 | suse_vex | SUSE CVE CVE-2025-68784 | first fixed: 2 known affected: 5 known not affected: 331 recommended: 172 | 2026-08-12T16:46:36+00:00 | Vulnerability · Source |
| CVE-2025-68790 | suse_vex | SUSE CVE CVE-2025-68790 | known not affected: 336 recommended: 27 | 2026-08-12T16:46:33+00:00 | Vulnerability · Source |
| CVE-2025-68807 | suse_vex | SUSE CVE CVE-2025-68807 | known not affected: 336 recommended: 27 | 2026-08-12T16:46:29+00:00 | Vulnerability · Source |
| CVE-2025-68823 | suse_vex | SUSE CVE CVE-2025-68823 | known not affected: 222 | 2026-08-12T16:46:25+00:00 | Vulnerability · Source |
| CVE-2025-68950 | suse_vex | SUSE CVE CVE-2025-68950 | known affected: 196 known not affected: 117 recommended: 164 | 2026-08-12T16:46:23+00:00 | Vulnerability · Source |
| CVE-2025-69230 | suse_vex | SUSE CVE CVE-2025-69230 | known not affected: 66 recommended: 4 | 2026-08-12T16:46:20+00:00 | Vulnerability · Source |
| CVE-2025-70067 | suse_vex | SUSE CVE CVE-2025-70067 | known affected: 736 recommended: 2 | 2026-08-12T16:46:13+00:00 | Vulnerability · Source |
| CVE-2025-70069 | suse_vex | SUSE CVE CVE-2025-70069 | known affected: 736 | 2026-08-12T16:46:12+00:00 | Vulnerability · Source |
| CVE-2025-71096 | suse_vex | SUSE CVE CVE-2025-71096 | first fixed: 2 known affected: 544 known not affected: 40 recommended: 344 | 2026-08-12T16:46:05+00:00 | Vulnerability · Source |
| CVE-2025-71121 | suse_vex | SUSE CVE CVE-2025-71121 | known not affected: 340 | 2026-08-12T16:46:00+00:00 | Vulnerability · Source |
| CVE-2025-71129 | suse_vex | SUSE CVE CVE-2025-71129 | known not affected: 342 | 2026-08-12T16:45:58+00:00 | Vulnerability · Source |
| CVE-2025-71142 | suse_vex | SUSE CVE CVE-2025-71142 | first fixed: 2 known affected: 399 known not affected: 259 recommended: 283 | 2026-08-12T16:45:54+00:00 | Vulnerability · Source |
| CVE-2025-71176 | suse_vex | SUSE CVE CVE-2025-71176 | known affected: 44 recommended: 13 | 2026-08-12T16:45:50+00:00 | Vulnerability · Source |
| CVE-2025-71193 | suse_vex | SUSE CVE CVE-2025-71193 | first fixed: 2 known affected: 124 known not affected: 138 recommended: 172 | 2026-08-12T16:45:47+00:00 | Vulnerability · Source |
| CVE-2025-71265 | suse_vex | SUSE CVE CVE-2025-71265 | known not affected: 332 | 2026-08-12T16:45:39+00:00 | Vulnerability · Source |
| CVE-2025-71266 | suse_vex | SUSE CVE CVE-2025-71266 | known not affected: 332 | 2026-08-12T16:45:38+00:00 | Vulnerability · Source |
| CVE-2025-71288 | suse_vex | SUSE CVE CVE-2025-71288 | first fixed: 68 known affected: 97 known not affected: 198 recommended: 76 | 2026-08-12T16:45:30+00:00 | Vulnerability · Source |
| CVE-2025-71302 | suse_vex | SUSE CVE CVE-2025-71302 | first fixed: 2 known affected: 411 known not affected: 223 recommended: 270 | 2026-08-12T16:45:25+00:00 | Vulnerability · Source |