VEX records
Browse vendor VEX statements available in this Vulnerability-Lookup instance and pivot to the related vulnerability.
286924 VEX records
API response| Vulnerability | Source | Title | Product status | Imported | Links |
|---|---|---|---|---|---|
| CVE-2025-68184 | suse_vex | SUSE CVE CVE-2025-68184 | first fixed: 2 known affected: 484 known not affected: 266 recommended: 283 | 2026-07-31T00:58:58+00:00 | Vulnerability · Source |
| CVE-2025-68207 | suse_vex | SUSE CVE CVE-2025-68207 | first fixed: 2 known affected: 394 known not affected: 358 recommended: 283 | 2026-07-31T00:58:54+00:00 | Vulnerability · Source |
| CVE-2025-68215 | suse_vex | SUSE CVE CVE-2025-68215 | first fixed: 2 known affected: 394 known not affected: 374 recommended: 283 | 2026-07-31T00:58:52+00:00 | Vulnerability · Source |
| CVE-2025-68232 | suse_vex | SUSE CVE CVE-2025-68232 | known not affected: 418 | 2026-07-31T00:58:49+00:00 | Vulnerability · Source |
| CVE-2025-68234 | suse_vex | SUSE CVE CVE-2025-68234 | known affected: 394 known not affected: 386 recommended: 37 | 2026-07-31T00:58:47+00:00 | Vulnerability · Source |
| CVE-2025-68246 | suse_vex | SUSE CVE CVE-2025-68246 | known not affected: 432 | 2026-07-31T00:58:44+00:00 | Vulnerability · Source |
| CVE-2025-68260 | suse_vex | SUSE CVE CVE-2025-68260 | known not affected: 418 recommended: 6 | 2026-07-31T00:58:41+00:00 | Vulnerability · Source |
| CVE-2025-68294 | suse_vex | SUSE CVE CVE-2025-68294 | known not affected: 418 | 2026-07-31T00:58:36+00:00 | Vulnerability · Source |
| CVE-2025-68301 | suse_vex | SUSE CVE CVE-2025-68301 | first fixed: 2 known affected: 547 known not affected: 209 recommended: 410 | 2026-07-31T00:58:35+00:00 | Vulnerability · Source |
| CVE-2025-68302 | suse_vex | SUSE CVE CVE-2025-68302 | first fixed: 2 known affected: 762 known not affected: 6 recommended: 283 | 2026-07-31T00:58:33+00:00 | Vulnerability · Source |
| CVE-2025-68315 | suse_vex | SUSE CVE CVE-2025-68315 | known affected: 10 known not affected: 430 | 2026-07-31T00:58:30+00:00 | Vulnerability · Source |
| CVE-2025-68321 | suse_vex | SUSE CVE CVE-2025-68321 | known affected: 284 known not affected: 52 | 2026-07-31T00:58:27+00:00 | Vulnerability · Source |
| CVE-2025-68336 | suse_vex | SUSE CVE CVE-2025-68336 | known affected: 301 known not affected: 154 recommended: 6 | 2026-07-31T00:58:24+00:00 | Vulnerability · Source |
| CVE-2025-68341 | suse_vex | SUSE CVE CVE-2025-68341 | first fixed: 2 known not affected: 431 recommended: 172 | 2026-07-31T00:58:21+00:00 | Vulnerability · Source |
| CVE-2025-68349 | suse_vex | SUSE CVE CVE-2025-68349 | first fixed: 2 known affected: 709 known not affected: 22 recommended: 452 | 2026-07-31T00:58:17+00:00 | Vulnerability · Source |
| CVE-2025-68360 | suse_vex | SUSE CVE CVE-2025-68360 | first fixed: 2 known affected: 5 known not affected: 431 recommended: 178 | 2026-07-31T00:58:13+00:00 | Vulnerability · Source |
| CVE-2025-68724 | suse_vex | SUSE CVE CVE-2025-68724 | first fixed: 2 known affected: 622 known not affected: 66 recommended: 548 | 2026-07-31T00:58:07+00:00 | Vulnerability · Source |
| CVE-2025-68726 | suse_vex | SUSE CVE CVE-2025-68726 | known not affected: 453 recommended: 6 | 2026-07-31T00:58:05+00:00 | Vulnerability · Source |
| CVE-2025-68730 | suse_vex | SUSE CVE CVE-2025-68730 | known affected: 81 known not affected: 374 recommended: 6 | 2026-07-31T00:58:02+00:00 | Vulnerability · Source |
| CVE-2025-68745 | suse_vex | SUSE CVE CVE-2025-68745 | first fixed: 2 known affected: 382 known not affected: 22 recommended: 178 | 2026-07-31T00:57:56+00:00 | Vulnerability · Source |
| CVE-2025-68748 | suse_vex | SUSE CVE CVE-2025-68748 | first fixed: 2 known affected: 453 known not affected: 379 recommended: 178 | 2026-07-31T00:57:52+00:00 | Vulnerability · Source |
| CVE-2025-68761 | suse_vex | SUSE CVE CVE-2025-68761 | known not affected: 353 recommended: 6 | 2026-07-31T00:57:48+00:00 | Vulnerability · Source |
| CVE-2025-68774 | suse_vex | SUSE CVE CVE-2025-68774 | known affected: 562 known not affected: 79 recommended: 37 | 2026-07-31T00:57:43+00:00 | Vulnerability · Source |
| CVE-2025-68782 | suse_vex | SUSE CVE CVE-2025-68782 | known affected: 355 | 2026-07-31T00:57:39+00:00 | Vulnerability · Source |
| CVE-2025-68793 | suse_vex | SUSE CVE CVE-2025-68793 | known not affected: 336 | 2026-07-31T00:57:35+00:00 | Vulnerability · Source |
| CVE-2025-68799 | suse_vex | SUSE CVE CVE-2025-68799 | first fixed: 2 known not affected: 146 recommended: 172 | 2026-07-31T00:57:31+00:00 | Vulnerability · Source |
| CVE-2025-68800 | suse_vex | SUSE CVE CVE-2025-68800 | first fixed: 2 known affected: 549 known not affected: 93 recommended: 410 | 2026-07-31T00:57:29+00:00 | Vulnerability · Source |
| CVE-2025-68805 | suse_vex | SUSE CVE CVE-2025-68805 | known not affected: 336 | 2026-07-31T00:57:24+00:00 | Vulnerability · Source |
| CVE-2025-68811 | suse_vex | SUSE CVE CVE-2025-68811 | first fixed: 2 known affected: 5 known not affected: 331 recommended: 255 | 2026-07-31T00:57:20+00:00 | Vulnerability · Source |
| CVE-2025-70888 | suse_vex | SUSE CVE CVE-2025-70888 | recommended: 5 | 2026-07-31T00:57:09+00:00 | Vulnerability · Source |
| CVE-2025-70950 | suse_vex | SUSE CVE CVE-2025-70950 | No product status | 2026-07-31T00:57:07+00:00 | Vulnerability · Source |
| CVE-2025-71066 | suse_vex | SUSE CVE CVE-2025-71066 | first fixed: 2 known affected: 396 known not affected: 93 recommended: 810 | 2026-07-31T00:57:03+00:00 | Vulnerability · Source |
| CVE-2025-71070 | suse_vex | SUSE CVE CVE-2025-71070 | known not affected: 336 | 2026-07-31T00:57:00+00:00 | Vulnerability · Source |
| CVE-2025-71072 | suse_vex | SUSE CVE CVE-2025-71072 | known affected: 22 known not affected: 333 | 2026-07-31T00:56:57+00:00 | Vulnerability · Source |
| CVE-2025-71074 | suse_vex | SUSE CVE CVE-2025-71074 | known affected: 355 | 2026-07-31T00:56:55+00:00 | Vulnerability · Source |
| CVE-2025-71080 | suse_vex | SUSE CVE CVE-2025-71080 | first fixed: 2 known affected: 399 known not affected: 274 recommended: 283 | 2026-07-31T00:56:51+00:00 | Vulnerability · Source |
| CVE-2025-71085 | suse_vex | SUSE CVE CVE-2025-71085 | first fixed: 2 known affected: 439 known not affected: 20 recommended: 853 | 2026-07-31T00:56:47+00:00 | Vulnerability · Source |
| CVE-2025-71092 | suse_vex | SUSE CVE CVE-2025-71092 | known not affected: 336 recommended: 27 | 2026-07-31T00:56:44+00:00 | Vulnerability · Source |
| CVE-2025-71127 | suse_vex | SUSE CVE CVE-2025-71127 | known affected: 140 known not affected: 200 recommended: 27 | 2026-07-31T00:56:35+00:00 | Vulnerability · Source |
| CVE-2025-71159 | suse_vex | SUSE CVE CVE-2025-71159 | known not affected: 336 | 2026-07-31T00:56:26+00:00 | Vulnerability · Source |
| CVE-2025-71201 | suse_vex | SUSE CVE CVE-2025-71201 | known not affected: 336 recommended: 42 | 2026-07-31T00:56:22+00:00 | Vulnerability · Source |
| CVE-2025-71204 | suse_vex | SUSE CVE CVE-2025-71204 | known not affected: 336 | 2026-07-31T00:56:19+00:00 | Vulnerability · Source |
| CVE-2025-71238 | suse_vex | SUSE CVE CVE-2025-71238 | first fixed: 2 known affected: 166 known not affected: 75 recommended: 397 | 2026-07-31T00:56:15+00:00 | Vulnerability · Source |
| CVE-2025-71261 | suse_vex | SUSE CVE CVE-2025-71261 | No product status | 2026-07-31T00:56:13+00:00 | Vulnerability · Source |
| CVE-2025-71300 | suse_vex | SUSE CVE CVE-2025-71300 | known affected: 411 known not affected: 278 recommended: 27 | 2026-07-31T00:56:07+00:00 | Vulnerability · Source |
| CVE-2025-71311 | suse_vex | SUSE CVE CVE-2025-71311 | known affected: 17 known not affected: 278 | 2026-07-31T00:56:04+00:00 | Vulnerability · Source |
| CVE-2025-71314 | suse_vex | SUSE CVE CVE-2025-71314 | known affected: 394 known not affected: 238 recommended: 98 | 2026-07-31T00:56:01+00:00 | Vulnerability · Source |
| CVE-2026-0865 | suse_vex | SUSE CVE CVE-2026-0865 | known affected: 450 recommended: 938 | 2026-07-31T00:55:58+00:00 | Vulnerability · Source |
| CVE-2026-1299 | suse_vex | SUSE CVE CVE-2026-1299 | known affected: 465 recommended: 884 | 2026-07-31T00:55:53+00:00 | Vulnerability · Source |
| CVE-2026-2297 | suse_vex | SUSE CVE CVE-2026-2297 | known affected: 409 known not affected: 238 recommended: 531 | 2026-07-31T00:55:50+00:00 | Vulnerability · Source |