CVE-2025-68637
Uniffle HTTP client trusts all certs and disables hostname verification, enabling MITM.
Is CVE-2025-68637 being exploited?
Not confirmed. CVE-2025-68637 does not appear in CISA's Known Exploited Vulnerabilities catalog, which records only exploitation that has been observed and reported publicly. That is evidence of absence of a report, not evidence the flaw is unattacked. EPSS currently estimates a 0.25% probability of exploitation in the next 30 days.
How severe is CVE-2025-68637?
CVE-2025-68637 is rated Critical with a CVSS score of 9.1. Severity describes how bad exploitation would be, not how likely it is: pair it with exploitation evidence before deciding what to patch first.
Is there a patch for CVE-2025-68637?
Yes. A fix has been recorded for CVE-2025-68637. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.
What does CVE-2025-68637 affect?
CVE-2025-68637 affects Uniffle HTTP client, Uniffle Coordinator service, Uniffle CLI. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.
What should I do about CVE-2025-68637?
Upgrade to 0.10.0; enable TLS verification
Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.
MITM risk: attackers can intercept/modify REST API traffic between Uniffle CLI and Coordinator due to insecure TLS checks.
Immediate action required
- affected< 0.10.0
As published in the CVE Program record. A version outside these ranges is not a statement that it is unaffected — vendors sometimes understate a range, and distribution-backported builds carry upstream numbers that do not reflect what was patched into them.