dbcve.org
UniffleApplication · Apache

CVE-2025-68637

CRITICAL · 9.1 CVSS v3.1 Published 2026-01-07
Fix available
A fix is available. Upgrade to 0.10.0 or later.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
The Uniffle HTTP client is configured to trust all SSL certificates and disables hostname verification by default. This insecure configuration exposes all REST API communication between the Uniffle CLI/client and the Uniffle Coordinator service to potential Man-in-the-Middle (MITM) attacks. This issue affects all versions from before 0.10.0. Users are recommended to upgrade to version 0.10.0, which fixes the issue.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

The Uniffle HTTP client is configured to trust all SSL certificates and disables hostname verification by default. This insecure configuration allows attackers to intercept and manipulate REST API communication between the Uniffle CLI/client and the Coordinator service through Man-in-the-Middle attacks.

MitigationUpgrade Uniffle to version 0.10.0 or later, which fixes the SSL certificate validation issue and re-enables proper hostname verification.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
UniffleApplication
Affected:< 0.10.0

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify Uniffle installation and version
    Locate the Uniffle installation directory and check the version. Common locations include /usr/local/uniffle, /opt/uniffle, or the directory where Uniffle was extracted. Look for a VERSION or version.txt file, or check the pom.xml if source is available. Run: find / -name 'uniffle*' -type d 2>/dev/null | head -5
    Affected if Installed version is lower than 0.10.0 (e.g., 0.9.0, 0.8.0, etc.)
  2. Locate Uniffle client configuration files
    Find configuration files used by the Uniffle HTTP client. Look in the conf/ directory under the Uniffle installation, or in /etc/uniffle/. Search for files containing SSL, HTTPS, or HTTP client settings. Common config names include uniffle-conf.xml, rss.conf, or client.properties.
    Affected if Configuration files exist but do not explicitly enable SSL certificate validation and hostname verification
  3. Check for insecure SSL trust settings
    Search configuration files and Java properties for settings like 'trustAllSSL', 'ssl.trust.all', 'trustAll', 'verifyHostname=false', or similar patterns that disable certificate validation. Use: grep -ri 'trustAll\|ssl\.trust\|verifyHostname' /path/to/uniffle/conf/ 2>/dev/null
    Affected if The configuration contains settings that disable SSL certificate validation (trustAll=true) or hostname verification (verifyHostname=false)
  4. Inspect REST client code or properties for defaults
    Examine the client-side configuration or properties file used when connecting to the Coordinator service. Look for 'rss.coordinator.*' connection settings. Check if ssl.enabled, ssl.client.trustCertification path, or client.ssl settings are absent or set to insecure values.
    Affected if No explicit SSL configuration exists, meaning the default (insecure) behavior applies

A user is affected if Uniffle version is below 0.10.0 AND the HTTP client connects to the Coordinator without explicit SSL certificate and hostname verification configuration.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to 0.10.0 or later
Fixed in 0.10.0
Interim mitigation

Upgrade Uniffle to version 0.10.0 or later, which fixes the SSL certificate validation issue and re-enables proper hostname verification.

Recommended fix High confidence

0.10.0

  1. Upgrade Uniffle to version 0.10.0 or later to resolve the insecure SSL configuration

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Uniffle Scoped from the published advisory
  • Consultation3.0 h
  • Implementation4.0 h
  • Testing4.0 h
  • Review / QA2.0 h
13.0 hours of engineering $2,280
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,648.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-68637 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2025-68637 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data