VEX records
Browse vendor VEX statements available in this Vulnerability-Lookup instance and pivot to the related vulnerability.
104719 VEX records
API response| Vulnerability | Source | Title | Product status | Imported | Links |
|---|---|---|---|---|---|
| CVE-2025-68757 | suse_vex | SUSE CVE CVE-2025-68757 | known affected: 631 known not affected: 61 recommended: 413 | 2026-10-15T15:54:54+00:00 | Vulnerability · Source |
| CVE-2025-68764 | suse_vex | SUSE CVE CVE-2025-68764 | known affected: 520 known not affected: 210 recommended: 295 | 2026-10-15T15:54:52+00:00 | Vulnerability · Source |
| CVE-2025-68765 | suse_vex | SUSE CVE CVE-2025-68765 | known affected: 546 known not affected: 204 recommended: 390 | 2026-10-15T15:54:49+00:00 | Vulnerability · Source |
| CVE-2025-68770 | suse_vex | SUSE CVE CVE-2025-68770 | known affected: 458 known not affected: 312 recommended: 289 | 2026-10-15T15:54:47+00:00 | Vulnerability · Source |
| CVE-2025-68771 | suse_vex | SUSE CVE CVE-2025-68771 | known affected: 562 recommended: 437 | 2026-10-15T15:54:44+00:00 | Vulnerability · Source |
| CVE-2025-68773 | suse_vex | SUSE CVE CVE-2025-68773 | known affected: 453 known not affected: 317 recommended: 289 | 2026-10-15T15:54:42+00:00 | Vulnerability · Source |
| CVE-2025-68774 | suse_vex | SUSE CVE CVE-2025-68774 | known affected: 646 known not affected: 72 recommended: 37 | 2026-10-15T15:54:40+00:00 | Vulnerability · Source |
| CVE-2025-68776 | suse_vex | SUSE CVE CVE-2025-68776 | known affected: 675 known not affected: 4 recommended: 289 | 2026-10-15T15:54:38+00:00 | Vulnerability · Source |
| CVE-2025-68777 | suse_vex | SUSE CVE CVE-2025-68777 | known affected: 485 known not affected: 150 recommended: 289 | 2026-10-15T15:54:35+00:00 | Vulnerability · Source |
| CVE-2025-68778 | suse_vex | SUSE CVE CVE-2025-68778 | known affected: 715 recommended: 280 | 2026-10-15T15:54:33+00:00 | Vulnerability · Source |
| CVE-2025-68780 | suse_vex | SUSE CVE CVE-2025-68780 | known affected: 453 known not affected: 4 recommended: 145 | 2026-10-15T15:54:30+00:00 | Vulnerability · Source |
| CVE-2025-68782 | suse_vex | SUSE CVE CVE-2025-68782 | known affected: 455 | 2026-10-15T15:54:28+00:00 | Vulnerability · Source |
| CVE-2025-68783 | suse_vex | SUSE CVE CVE-2025-68783 | known affected: 673 known not affected: 56 recommended: 312 | 2026-10-15T15:54:26+00:00 | Vulnerability · Source |
| CVE-2025-68784 | suse_vex | SUSE CVE CVE-2025-68784 | known affected: 7 known not affected: 431 recommended: 172 | 2026-10-15T15:54:23+00:00 | Vulnerability · Source |
| CVE-2025-68785 | suse_vex | SUSE CVE CVE-2025-68785 | known affected: 620 known not affected: 153 recommended: 280 | 2026-10-15T15:54:21+00:00 | Vulnerability · Source |
| CVE-2025-68786 | suse_vex | SUSE CVE CVE-2025-68786 | known not affected: 455 | 2026-10-15T15:54:19+00:00 | Vulnerability · Source |
| CVE-2025-68788 | suse_vex | SUSE CVE CVE-2025-68788 | known affected: 710 recommended: 326 | 2026-10-15T15:54:15+00:00 | Vulnerability · Source |
| CVE-2025-68794 | suse_vex | SUSE CVE CVE-2025-68794 | known affected: 620 known not affected: 153 recommended: 280 | 2026-10-15T15:54:13+00:00 | Vulnerability · Source |
| CVE-2025-68795 | suse_vex | SUSE CVE CVE-2025-68795 | known affected: 710 recommended: 312 | 2026-10-15T15:54:12+00:00 | Vulnerability · Source |
| CVE-2025-68797 | suse_vex | SUSE CVE CVE-2025-68797 | known affected: 710 recommended: 326 | 2026-10-15T15:54:10+00:00 | Vulnerability · Source |
| CVE-2025-68798 | suse_vex | SUSE CVE CVE-2025-68798 | known affected: 398 known not affected: 389 recommended: 289 | 2026-10-15T15:54:08+00:00 | Vulnerability · Source |
| CVE-2025-68799 | suse_vex | SUSE CVE CVE-2025-68799 | known affected: 2 known not affected: 223 recommended: 172 | 2026-10-15T15:54:06+00:00 | Vulnerability · Source |
| CVE-2025-68800 | suse_vex | SUSE CVE CVE-2025-68800 | known affected: 562 known not affected: 177 recommended: 392 | 2026-10-15T15:54:04+00:00 | Vulnerability · Source |
| CVE-2025-68803 | suse_vex | SUSE CVE CVE-2025-68803 | known affected: 516 known not affected: 254 recommended: 289 | 2026-10-15T15:54:03+00:00 | Vulnerability · Source |
| CVE-2025-68804 | suse_vex | SUSE CVE CVE-2025-68804 | known affected: 396 known not affected: 178 recommended: 384 | 2026-10-15T15:54:01+00:00 | Vulnerability · Source |
| CVE-2025-68810 | suse_vex | SUSE CVE CVE-2025-68810 | known affected: 461 known not affected: 312 recommended: 280 | 2026-10-15T15:53:59+00:00 | Vulnerability · Source |
| CVE-2025-68811 | suse_vex | SUSE CVE CVE-2025-68811 | known affected: 7 known not affected: 431 recommended: 255 | 2026-10-15T15:53:57+00:00 | Vulnerability · Source |
| CVE-2025-68813 | suse_vex | SUSE CVE CVE-2025-68813 | known affected: 490 known not affected: 34 recommended: 732 | 2026-10-15T15:53:56+00:00 | Vulnerability · Source |
| CVE-2025-68814 | suse_vex | SUSE CVE CVE-2025-68814 | known affected: 516 known not affected: 254 recommended: 289 | 2026-10-15T15:53:54+00:00 | Vulnerability · Source |
| CVE-2025-68816 | suse_vex | SUSE CVE CVE-2025-68816 | known affected: 633 known not affected: 62 recommended: 312 | 2026-10-15T15:53:51+00:00 | Vulnerability · Source |
| CVE-2025-68818 | suse_vex | SUSE CVE CVE-2025-68818 | known affected: 450 known not affected: 150 recommended: 501 | 2026-10-15T15:53:49+00:00 | Vulnerability · Source |
| CVE-2025-68819 | suse_vex | SUSE CVE CVE-2025-68819 | known affected: 509 known not affected: 25 recommended: 384 | 2026-10-15T15:53:47+00:00 | Vulnerability · Source |
| CVE-2025-68820 | suse_vex | SUSE CVE CVE-2025-68820 | known affected: 562 known not affected: 208 recommended: 289 | 2026-10-15T15:53:44+00:00 | Vulnerability · Source |
| CVE-2025-68821 | suse_vex | SUSE CVE CVE-2025-68821 | known affected: 7 known not affected: 431 recommended: 172 | 2026-10-15T15:53:42+00:00 | Vulnerability · Source |
| CVE-2025-68939 | suse_vex | SUSE CVE CVE-2025-68939 | No product status | 2026-10-15T15:53:40+00:00 | Vulnerability · Source |
| CVE-2025-68944 | suse_vex | SUSE CVE CVE-2025-68944 | No product status | 2026-10-15T15:53:39+00:00 | Vulnerability · Source |
| CVE-2025-68945 | suse_vex | SUSE CVE CVE-2025-68945 | No product status | 2026-10-15T15:53:37+00:00 | Vulnerability · Source |
| CVE-2025-68946 | suse_vex | SUSE CVE CVE-2025-68946 | No product status | 2026-10-15T15:53:34+00:00 | Vulnerability · Source |
| CVE-2025-68954 | suse_vex | SUSE CVE CVE-2025-68954 | No product status | 2026-10-15T15:53:33+00:00 | Vulnerability · Source |
| CVE-2025-69199 | suse_vex | SUSE CVE CVE-2025-69199 | No product status | 2026-10-15T15:53:31+00:00 | Vulnerability · Source |
| CVE-2025-69224 | suse_vex | SUSE CVE CVE-2025-69224 | known affected: 394 recommended: 50 | 2026-10-15T15:53:30+00:00 | Vulnerability · Source |
| CVE-2025-69226 | suse_vex | SUSE CVE CVE-2025-69226 | known affected: 394 recommended: 50 | 2026-10-15T15:53:28+00:00 | Vulnerability · Source |
| CVE-2025-69227 | suse_vex | SUSE CVE CVE-2025-69227 | known affected: 394 recommended: 50 | 2026-10-15T15:53:26+00:00 | Vulnerability · Source |
| CVE-2025-69228 | suse_vex | SUSE CVE CVE-2025-69228 | known affected: 394 recommended: 50 | 2026-10-15T15:53:24+00:00 | Vulnerability · Source |
| CVE-2025-69229 | suse_vex | SUSE CVE CVE-2025-69229 | known affected: 394 recommended: 50 | 2026-10-15T15:53:22+00:00 | Vulnerability · Source |
| CVE-2025-69230 | suse_vex | SUSE CVE CVE-2025-69230 | known not affected: 64 recommended: 4 | 2026-10-15T15:53:21+00:00 | Vulnerability · Source |
| CVE-2025-69277 | suse_vex | SUSE CVE CVE-2025-69277 | first fixed: 45 known affected: 567 recommended: 53 | 2026-10-15T15:53:19+00:00 | Vulnerability · Source |
| CVE-2025-69413 | suse_vex | SUSE CVE CVE-2025-69413 | No product status | 2026-10-15T15:53:17+00:00 | Vulnerability · Source |
| CVE-2025-69418 | suse_vex | SUSE CVE CVE-2025-69418 | known affected: 458 known not affected: 343 recommended: 330 | 2026-10-15T15:53:14+00:00 | Vulnerability · Source |
| CVE-2025-69419 | suse_vex | SUSE CVE CVE-2025-69419 | known affected: 458 known not affected: 344 recommended: 329 | 2026-10-15T15:53:12+00:00 | Vulnerability · Source |