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-68203 | suse_vex | SUSE CVE CVE-2025-68203 | known not affected: 453 | 2026-07-25T00:27:29+00:00 | Vulnerability · Source |
| CVE-2025-68205 | suse_vex | SUSE CVE CVE-2025-68205 | known not affected: 418 recommended: 27 | 2026-07-25T00:27:25+00:00 | Vulnerability · Source |
| CVE-2025-68206 | suse_vex | SUSE CVE CVE-2025-68206 | first fixed: 2 known affected: 704 known not affected: 22 recommended: 330 | 2026-07-25T00:27:23+00:00 | Vulnerability · Source |
| CVE-2025-68208 | suse_vex | SUSE CVE CVE-2025-68208 | first fixed: 2 known affected: 547 known not affected: 209 recommended: 307 | 2026-07-25T00:27:20+00:00 | Vulnerability · Source |
| CVE-2025-68212 | suse_vex | SUSE CVE CVE-2025-68212 | known not affected: 418 | 2026-07-25T00:27:17+00:00 | Vulnerability · Source |
| CVE-2025-68217 | suse_vex | SUSE CVE CVE-2025-68217 | first fixed: 2 known affected: 394 known not affected: 326 recommended: 402 | 2026-07-25T00:27:15+00:00 | Vulnerability · Source |
| CVE-2025-68226 | suse_vex | SUSE CVE CVE-2025-68226 | known not affected: 418 | 2026-07-25T00:27:09+00:00 | Vulnerability · Source |
| CVE-2025-68227 | suse_vex | SUSE CVE CVE-2025-68227 | first fixed: 2 known affected: 602 known not affected: 154 recommended: 307 | 2026-07-25T00:27:07+00:00 | Vulnerability · Source |
| CVE-2025-68229 | suse_vex | SUSE CVE CVE-2025-68229 | known affected: 444 known not affected: 6 | 2026-07-25T00:27:05+00:00 | Vulnerability · Source |
| CVE-2025-68230 | suse_vex | SUSE CVE CVE-2025-68230 | first fixed: 2 known affected: 490 known not affected: 266 recommended: 307 | 2026-07-25T00:27:03+00:00 | Vulnerability · Source |
| CVE-2025-68235 | suse_vex | SUSE CVE CVE-2025-68235 | first fixed: 2 known affected: 394 known not affected: 321 recommended: 402 | 2026-07-25T00:27:00+00:00 | Vulnerability · Source |
| CVE-2025-68237 | suse_vex | SUSE CVE CVE-2025-68237 | first fixed: 2 known affected: 394 known not affected: 321 recommended: 402 | 2026-07-25T00:26:58+00:00 | Vulnerability · Source |
| CVE-2025-68238 | suse_vex | SUSE CVE CVE-2025-68238 | first fixed: 2 known affected: 394 known not affected: 321 recommended: 402 | 2026-07-25T00:26:55+00:00 | Vulnerability · Source |
| CVE-2025-68239 | suse_vex | SUSE CVE CVE-2025-68239 | first fixed: 2 known affected: 657 known not affected: 99 recommended: 307 | 2026-07-25T00:26:53+00:00 | Vulnerability · Source |
| CVE-2025-68240 | suse_vex | SUSE CVE CVE-2025-68240 | known not affected: 453 | 2026-07-25T00:26:51+00:00 | Vulnerability · Source |
| CVE-2025-68241 | suse_vex | SUSE CVE CVE-2025-68241 | first fixed: 2 known affected: 718 known not affected: 6 recommended: 344 | 2026-07-25T00:26:49+00:00 | Vulnerability · Source |
| CVE-2025-68244 | suse_vex | SUSE CVE CVE-2025-68244 | first fixed: 2 known affected: 506 known not affected: 209 recommended: 402 | 2026-07-25T00:26:47+00:00 | Vulnerability · Source |
| CVE-2025-68245 | suse_vex | SUSE CVE CVE-2025-68245 | first fixed: 2 known affected: 718 known not affected: 6 recommended: 344 | 2026-07-25T00:26:44+00:00 | Vulnerability · Source |
| CVE-2025-68249 | suse_vex | SUSE CVE CVE-2025-68249 | first fixed: 2 known affected: 506 known not affected: 209 recommended: 402 | 2026-07-25T00:26:42+00:00 | Vulnerability · Source |
| CVE-2025-68252 | suse_vex | SUSE CVE CVE-2025-68252 | first fixed: 2 known affected: 394 known not affected: 321 recommended: 402 | 2026-07-25T00:26:40+00:00 | Vulnerability · Source |
| CVE-2025-68255 | suse_vex | SUSE CVE CVE-2025-68255 | first fixed: 2 known affected: 602 known not affected: 154 recommended: 313 | 2026-07-25T00:26:37+00:00 | Vulnerability · Source |
| CVE-2025-68256 | suse_vex | SUSE CVE CVE-2025-68256 | first fixed: 2 known affected: 394 known not affected: 360 recommended: 313 | 2026-07-25T00:26:34+00:00 | Vulnerability · Source |
| CVE-2025-68257 | suse_vex | SUSE CVE CVE-2025-68257 | first fixed: 2 known affected: 506 known not affected: 209 recommended: 408 | 2026-07-25T00:26:32+00:00 | Vulnerability · Source |
| CVE-2025-68258 | suse_vex | SUSE CVE CVE-2025-68258 | first fixed: 2 known affected: 394 known not affected: 319 recommended: 408 | 2026-07-25T00:26:29+00:00 | Vulnerability · Source |
| CVE-2025-68261 | suse_vex | SUSE CVE CVE-2025-68261 | first fixed: 2 known affected: 704 known not affected: 20 recommended: 350 | 2026-07-25T00:26:27+00:00 | Vulnerability · Source |
| CVE-2025-68262 | suse_vex | SUSE CVE CVE-2025-68262 | known not affected: 418 recommended: 6 | 2026-07-25T00:26:25+00:00 | Vulnerability · Source |
| CVE-2025-68263 | suse_vex | SUSE CVE CVE-2025-68263 | known not affected: 431 recommended: 6 | 2026-07-25T00:26:24+00:00 | Vulnerability · Source |
| CVE-2025-68265 | suse_vex | SUSE CVE CVE-2025-68265 | first fixed: 2 known affected: 184 known not affected: 266 recommended: 172 | 2026-07-25T00:26:22+00:00 | Vulnerability · Source |
| CVE-2025-68283 | suse_vex | SUSE CVE CVE-2025-68283 | first fixed: 2 known affected: 722 known not affected: 6 recommended: 332 | 2026-07-25T00:26:19+00:00 | Vulnerability · Source |
| CVE-2025-68286 | suse_vex | SUSE CVE CVE-2025-68286 | first fixed: 2 known affected: 584 known not affected: 126 recommended: 425 | 2026-07-25T00:26:17+00:00 | Vulnerability · Source |
| CVE-2025-68289 | suse_vex | SUSE CVE CVE-2025-68289 | first fixed: 2 known affected: 561 known not affected: 154 recommended: 402 | 2026-07-25T00:26:14+00:00 | Vulnerability · Source |
| CVE-2025-68290 | suse_vex | SUSE CVE CVE-2025-68290 | first fixed: 2 known affected: 506 known not affected: 209 recommended: 402 | 2026-07-25T00:26:13+00:00 | Vulnerability · Source |
| CVE-2025-68296 | suse_vex | SUSE CVE CVE-2025-68296 | first fixed: 2 known affected: 724 recommended: 344 | 2026-07-25T00:26:10+00:00 | Vulnerability · Source |
| CVE-2025-68297 | suse_vex | SUSE CVE CVE-2025-68297 | first fixed: 2 known affected: 552 known not affected: 209 recommended: 307 | 2026-07-25T00:26:09+00:00 | Vulnerability · Source |
| CVE-2025-68307 | suse_vex | SUSE CVE CVE-2025-68307 | first fixed: 2 known affected: 394 known not affected: 326 recommended: 402 | 2026-07-25T00:26:05+00:00 | Vulnerability · Source |
| CVE-2025-68319 | suse_vex | SUSE CVE CVE-2025-68319 | known affected: 17 known not affected: 431 | 2026-07-25T00:26:02+00:00 | Vulnerability · Source |
| CVE-2025-68320 | suse_vex | SUSE CVE CVE-2025-68320 | first fixed: 2 known affected: 490 known not affected: 266 recommended: 307 | 2026-07-25T00:26:01+00:00 | Vulnerability · Source |
| CVE-2025-68325 | suse_vex | SUSE CVE CVE-2025-68325 | first fixed: 2 known affected: 490 known not affected: 266 recommended: 313 | 2026-07-25T00:25:59+00:00 | Vulnerability · Source |
| CVE-2025-68327 | suse_vex | SUSE CVE CVE-2025-68327 | first fixed: 2 known affected: 394 known not affected: 367 recommended: 307 | 2026-07-25T00:25:57+00:00 | Vulnerability · Source |
| CVE-2025-68328 | suse_vex | SUSE CVE CVE-2025-68328 | first fixed: 2 known affected: 506 known not affected: 214 recommended: 402 | 2026-07-25T00:25:55+00:00 | Vulnerability · Source |
| CVE-2025-68332 | suse_vex | SUSE CVE CVE-2025-68332 | first fixed: 2 known affected: 394 known not affected: 326 recommended: 408 | 2026-07-25T00:25:53+00:00 | Vulnerability · Source |
| CVE-2025-68335 | suse_vex | SUSE CVE CVE-2025-68335 | first fixed: 2 known affected: 394 known not affected: 326 recommended: 408 | 2026-07-25T00:25:51+00:00 | Vulnerability · Source |
| CVE-2025-68337 | suse_vex | SUSE CVE CVE-2025-68337 | first fixed: 2 known affected: 729 recommended: 350 | 2026-07-25T00:25:50+00:00 | Vulnerability · Source |
| CVE-2025-68339 | suse_vex | SUSE CVE CVE-2025-68339 | first fixed: 2 known affected: 394 known not affected: 346 recommended: 402 | 2026-07-25T00:25:48+00:00 | Vulnerability · Source |
| CVE-2025-68342 | suse_vex | SUSE CVE CVE-2025-68342 | first fixed: 2 known affected: 394 known not affected: 436 recommended: 172 | 2026-07-25T00:25:46+00:00 | Vulnerability · Source |
| CVE-2025-68344 | suse_vex | SUSE CVE CVE-2025-68344 | first fixed: 2 known affected: 394 known not affected: 404 recommended: 178 | 2026-07-25T00:25:45+00:00 | Vulnerability · Source |
| CVE-2025-68345 | suse_vex | SUSE CVE CVE-2025-68345 | first fixed: 2 known affected: 506 known not affected: 214 recommended: 408 | 2026-07-25T00:25:43+00:00 | Vulnerability · Source |
| CVE-2025-68346 | suse_vex | SUSE CVE CVE-2025-68346 | first fixed: 2 known affected: 561 known not affected: 159 recommended: 408 | 2026-07-25T00:25:41+00:00 | Vulnerability · Source |
| CVE-2025-68347 | suse_vex | SUSE CVE CVE-2025-68347 | first fixed: 2 known affected: 394 known not affected: 326 recommended: 428 | 2026-07-25T00:25:40+00:00 | Vulnerability · Source |
| CVE-2025-68348 | suse_vex | SUSE CVE CVE-2025-68348 | first fixed: 2 known affected: 5 known not affected: 431 recommended: 178 | 2026-07-25T00:25:38+00:00 | Vulnerability · Source |