VEX records
Browse vendor VEX statements available in this Vulnerability-Lookup instance and pivot to the related vulnerability.
292108 VEX records
API response| Vulnerability | Source | Title | Product status | Imported | Links |
|---|---|---|---|---|---|
| CVE-2025-43343 | suse_vex | SUSE CVE CVE-2025-43343 | known affected: 132 recommended: 608 | 2026-07-25T00:30:26+00:00 | Vulnerability · Source |
| CVE-2025-43368 | suse_vex | SUSE CVE CVE-2025-43368 | known affected: 132 recommended: 608 | 2026-07-25T00:30:24+00:00 | Vulnerability · Source |
| CVE-2025-43419 | suse_vex | SUSE CVE CVE-2025-43419 | known affected: 124 recommended: 632 | 2026-07-25T00:30:21+00:00 | Vulnerability · Source |
| CVE-2025-43425 | suse_vex | SUSE CVE CVE-2025-43425 | known affected: 124 recommended: 632 | 2026-07-25T00:30:19+00:00 | Vulnerability · Source |
| CVE-2025-43457 | suse_vex | SUSE CVE CVE-2025-43457 | known affected: 88 recommended: 528 | 2026-07-25T00:30:16+00:00 | Vulnerability · Source |
| CVE-2025-43718 | suse_vex | SUSE CVE CVE-2025-43718 | known affected: 16 known not affected: 74 recommended: 193 | 2026-07-25T00:30:14+00:00 | Vulnerability · Source |
| CVE-2025-43919 | suse_vex | SUSE CVE CVE-2025-43919 | known not affected: 10 | 2026-07-25T00:30:10+00:00 | Vulnerability · Source |
| CVE-2025-43920 | suse_vex | SUSE CVE CVE-2025-43920 | known not affected: 10 | 2026-07-25T00:30:09+00:00 | Vulnerability · Source |
| CVE-2025-43965 | suse_vex | SUSE CVE CVE-2025-43965 | known affected: 207 known not affected: 16 recommended: 172 | 2026-07-25T00:30:07+00:00 | Vulnerability · Source |
| CVE-2025-46397 | suse_vex | SUSE CVE CVE-2025-46397 | known affected: 7 recommended: 17 | 2026-07-25T00:30:04+00:00 | Vulnerability · Source |
| CVE-2025-46420 | suse_vex | SUSE CVE CVE-2025-46420 | known affected: 55 recommended: 244 | 2026-07-25T00:30:02+00:00 | Vulnerability · Source |
| CVE-2025-46802 | suse_vex | SUSE CVE CVE-2025-46802 | known affected: 424 recommended: 21 | 2026-07-25T00:29:59+00:00 | Vulnerability · Source |
| CVE-2025-48038 | suse_vex | SUSE CVE CVE-2025-48038 | known affected: 57 recommended: 104 | 2026-07-25T00:29:53+00:00 | Vulnerability · Source |
| CVE-2025-48039 | suse_vex | SUSE CVE CVE-2025-48039 | known affected: 57 recommended: 104 | 2026-07-25T00:29:51+00:00 | Vulnerability · Source |
| CVE-2025-48040 | suse_vex | SUSE CVE CVE-2025-48040 | known affected: 57 recommended: 84 | 2026-07-25T00:29:49+00:00 | Vulnerability · Source |
| CVE-2025-48041 | suse_vex | SUSE CVE CVE-2025-48041 | known affected: 10 recommended: 124 | 2026-07-25T00:29:46+00:00 | Vulnerability · Source |
| CVE-2025-48386 | suse_vex | SUSE CVE CVE-2025-48386 | known not affected: 434 recommended: 44 | 2026-07-25T00:29:43+00:00 | Vulnerability · Source |
| CVE-2025-48708 | suse_vex | SUSE CVE CVE-2025-48708 | known affected: 96 known not affected: 1 recommended: 59 | 2026-07-25T00:29:41+00:00 | Vulnerability · Source |
| CVE-2025-48976 | suse_vex | SUSE CVE CVE-2025-48976 | known affected: 406 recommended: 51 | 2026-07-25T00:29:39+00:00 | Vulnerability · Source |
| CVE-2025-50181 | suse_vex | SUSE CVE CVE-2025-50181 | known affected: 442 recommended: 104 | 2026-07-25T00:29:33+00:00 | Vulnerability · Source |
| CVE-2025-50422 | suse_vex | SUSE CVE CVE-2025-50422 | known affected: 601 recommended: 120 | 2026-07-25T00:29:32+00:00 | Vulnerability · Source |
| CVE-2025-52886 | suse_vex | SUSE CVE CVE-2025-52886 | known affected: 94 recommended: 288 | 2026-07-25T00:29:27+00:00 | Vulnerability · Source |
| CVE-2025-53015 | suse_vex | SUSE CVE CVE-2025-53015 | known not affected: 235 recommended: 178 | 2026-07-25T00:29:22+00:00 | Vulnerability · Source |
| CVE-2025-55158 | suse_vex | SUSE CVE CVE-2025-55158 | known affected: 498 known not affected: 1 recommended: 136 | 2026-07-25T00:29:07+00:00 | Vulnerability · Source |
| CVE-2025-55298 | suse_vex | SUSE CVE CVE-2025-55298 | known affected: 75 known not affected: 24 recommended: 366 | 2026-07-25T00:29:00+00:00 | Vulnerability · Source |
| CVE-2025-57812 | suse_vex | SUSE CVE CVE-2025-57812 | known affected: 69 recommended: 36 | 2026-07-25T00:28:55+00:00 | Vulnerability · Source |
| CVE-2025-59028 | suse_vex | SUSE CVE CVE-2025-59028 | known not affected: 263 recommended: 37 | 2026-07-25T00:28:50+00:00 | Vulnerability · Source |
| CVE-2025-59799 | suse_vex | SUSE CVE CVE-2025-59799 | known affected: 24 known not affected: 67 recommended: 59 | 2026-07-25T00:28:46+00:00 | Vulnerability · Source |
| CVE-2025-60018 | suse_vex | SUSE CVE CVE-2025-60018 | known not affected: 94 | 2026-07-25T00:28:44+00:00 | Vulnerability · Source |
| CVE-2025-61105 | suse_vex | SUSE CVE CVE-2025-61105 | known affected: 233 known not affected: 238 recommended: 112 | 2026-07-25T00:28:41+00:00 | Vulnerability · Source |
| CVE-2025-61145 | suse_vex | SUSE CVE CVE-2025-61145 | known affected: 34 known not affected: 119 | 2026-07-25T00:28:39+00:00 | Vulnerability · Source |
| CVE-2025-61664 | suse_vex | SUSE CVE CVE-2025-61664 | known affected: 596 recommended: 302 | 2026-07-25T00:28:36+00:00 | Vulnerability · Source |
| CVE-2025-62689 | suse_vex | SUSE CVE CVE-2025-62689 | known not affected: 90 recommended: 33 | 2026-07-25T00:28:33+00:00 | Vulnerability · Source |
| CVE-2025-66215 | suse_vex | SUSE CVE CVE-2025-66215 | known affected: 404 recommended: 38 | 2026-07-25T00:28:23+00:00 | Vulnerability · Source |
| CVE-2025-66286 | suse_vex | SUSE CVE CVE-2025-66286 | known affected: 122 | 2026-07-25T00:28:21+00:00 | Vulnerability · Source |
| CVE-2025-66628 | suse_vex | SUSE CVE CVE-2025-66628 | known affected: 141 known not affected: 24 recommended: 327 | 2026-07-25T00:28:12+00:00 | Vulnerability · Source |
| CVE-2025-68168 | suse_vex | SUSE CVE CVE-2025-68168 | known affected: 394 known not affected: 343 recommended: 230 | 2026-07-25T00:28:07+00:00 | Vulnerability · Source |
| CVE-2025-68169 | suse_vex | SUSE CVE CVE-2025-68169 | known not affected: 418 | 2026-07-25T00:28:05+00:00 | Vulnerability · Source |
| CVE-2025-68170 | suse_vex | SUSE CVE CVE-2025-68170 | first fixed: 2 known affected: 394 known not affected: 358 recommended: 283 | 2026-07-25T00:28:03+00:00 | Vulnerability · Source |
| CVE-2025-68172 | suse_vex | SUSE CVE CVE-2025-68172 | first fixed: 2 known affected: 394 known not affected: 321 recommended: 402 | 2026-07-25T00:28:00+00:00 | Vulnerability · Source |
| CVE-2025-68174 | suse_vex | SUSE CVE CVE-2025-68174 | first fixed: 2 known affected: 602 known not affected: 154 recommended: 307 | 2026-07-25T00:27:57+00:00 | Vulnerability · Source |
| CVE-2025-68176 | suse_vex | SUSE CVE CVE-2025-68176 | first fixed: 2 known affected: 506 known not affected: 209 recommended: 402 | 2026-07-25T00:27:55+00:00 | Vulnerability · Source |
| CVE-2025-68178 | suse_vex | SUSE CVE CVE-2025-68178 | first fixed: 2 known affected: 490 known not affected: 270 recommended: 307 | 2026-07-25T00:27:53+00:00 | Vulnerability · Source |
| CVE-2025-68188 | suse_vex | SUSE CVE CVE-2025-68188 | first fixed: 2 known affected: 657 known not affected: 69 recommended: 330 | 2026-07-25T00:27:47+00:00 | Vulnerability · Source |
| CVE-2025-68189 | suse_vex | SUSE CVE CVE-2025-68189 | known not affected: 418 | 2026-07-25T00:27:45+00:00 | Vulnerability · Source |
| CVE-2025-68190 | suse_vex | SUSE CVE CVE-2025-68190 | first fixed: 2 known affected: 394 known not affected: 330 recommended: 330 | 2026-07-25T00:27:42+00:00 | Vulnerability · Source |
| CVE-2025-68195 | suse_vex | SUSE CVE CVE-2025-68195 | first fixed: 2 known affected: 394 known not affected: 321 recommended: 402 | 2026-07-25T00:27:38+00:00 | Vulnerability · Source |
| CVE-2025-68197 | suse_vex | SUSE CVE CVE-2025-68197 | first fixed: 2 known affected: 394 known not affected: 374 recommended: 283 | 2026-07-25T00:27:36+00:00 | Vulnerability · Source |
| CVE-2025-68200 | suse_vex | SUSE CVE CVE-2025-68200 | first fixed: 2 known affected: 547 known not affected: 209 recommended: 307 | 2026-07-25T00:27:34+00:00 | Vulnerability · Source |
| CVE-2025-68201 | suse_vex | SUSE CVE CVE-2025-68201 | first fixed: 2 known affected: 506 known not affected: 250 recommended: 307 | 2026-07-25T00:27:32+00:00 | Vulnerability · Source |