VulnerabilityPublished 7 Jan 2026

CVE-2025-68637: Apache Uniffle · Improper Validation of Certificate with Host Mismatch

Affects Apache UniffleSource CVE Database V5

Not known to be exploited · CVSS 9.1 Critical : upgrade to 0.10.0 as a priority.

Data as of 26 Oct 2026, 15:59 UTC

CVSS 3.1 base score

9.1Critical

How severe the flaw is on the 0–10 CVSS scale.

EPSS: 0.2% chance of exploitation in 30 days – higher than 16% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch: Available – fixed in 0.10.0

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

Attack Vector: Network
Attack Complexity: Low
Privileges Required: None
User Interaction: None
Scope: Unchanged
Confidentiality: High
Integrity: High
Availability: None

Bold values are the worst case: easiest to exploit or largest impact.

Attack Vector: Network: The vulnerable component is bound to the network stack and the set of possible attackers extends beyond the other options listed, up to and including the entire Internet. Such a vulnerability is often termed 'remotely exploitable' and can be thought of as an attack being exploitable at the protocol level one or more network hops away (e.g., across one or more routers).
Attack Complexity: Low: Specialized access conditions or extenuating circumstances do not exist. An attacker can expect repeatable success against the vulnerable component.
Privileges Required: None: The attacker is unauthorized prior to attack, and therefore does not require any access to settings or files to carry out an attack.
User Interaction: None: The vulnerable system can be exploited without any interaction from any user.
Scope: Unchanged: An exploited vulnerability can only affect resources managed by the same security authority. In this case, the vulnerable component and the impacted component are either the same, or both are managed by the same security authority.
Confidentiality: High: There is total loss of confidentiality, resulting in all resources within the impacted component being divulged to the attacker. Alternatively, access to only some restricted information is obtained, but the disclosed information presents a direct, serious impact.
Integrity: High: There is a total loss of integrity, or a complete loss of protection. For example, the attacker is able to modify any/all files protected by the impacted component. Alternatively, only some files can be modified, but malicious modification would present a direct, serious consequence to the impacted component.
Availability: None: There is no impact to availability within the impacted component.

Definitions: FIRST CVSS v3.1 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 7 Jan 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponised: Public exploit code exists in Metasploit or Exploit-DB, or CISA SSVC or the CVSS exploit maturity reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

Upgrade Apache Uniffle and org.apache.uniffle/uniffle to 0.10.0.

Affected software

Product	Affected	Fixed in
Apache Software FoundationApache Uniffle	Affected <0.10.0	Fixed in 0.10.0
Mavenorg.apache.uniffle/uniffle`pkg:maven/org.apache.uniffle/uniffle`Other threats	Affected <0.10.0	Fixed in 0.10.0

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

The primary mitigation is to upgrade Apache Uniffle to version 0.10.0 or later, where proper SSL certificate validation and hostname verification are enforced by default. Until the upgrade can be applied, organizations should implement network-level protections such as enforcing strict TLS inspection policies, deploying network segmentation to isolate Uniffle components, and using VPNs or secure tunnels to protect REST API traffic. Additionally, administrators should audit existing configurations to ensure no overrides disable hostname verification or trust all certificates. Monitoring network traffic for anomalous SSL certificates or unexpected connections to Uniffle Coordinator services can help detect potential MITM attempts. Incorporating certificate pinning or mutual TLS authentication, if supported, can further harden communications. Finally, organizations should review and update incident response plans to address potential exploitation scenarios involving data interception or manipulation in distributed systems.

Description

CVE-2025-68637 is a critical vulnerability in Apache Uniffle versions prior to 0.10.0 where the HTTP client disables hostname verification and trusts all SSL certificates by default. This misconfiguration allows attackers to perform Man-in-the-Middle (MITM) attacks on REST API communications between the Uniffle CLI/client and the Uniffle Coordinator service. The vulnerability has a CVSS score of 9.1, indicating high severity with potential for complete confidentiality and integrity compromise without requiring authentication or user interaction. Upgrading to version 0.10.0 mitigates this issue by enforcing proper certificate validation. European organizations using Apache Uniffle, especially in data-intensive or distributed computing environments, should prioritize patching to prevent interception or manipulation of sensitive data.

Impact

For European organizations, this vulnerability poses a significant risk to the confidentiality and integrity of data transmitted within distributed computing environments that utilize Apache Uniffle. Potential impacts include unauthorized data disclosure, data tampering, and disruption of data processing workflows. Organizations handling sensitive or regulated data, such as financial institutions, healthcare providers, and critical infrastructure operators, could face compliance violations and reputational damage if exploited. The vulnerability could also facilitate lateral movement within networks if attackers leverage intercepted credentials or session tokens. Given the critical CVSS rating and the lack of authentication requirements, the threat surface is broad, especially in environments where network segmentation or encryption is insufficient. The absence of user interaction requirements further increases the risk of automated exploitation. European entities relying on Apache Uniffle for big data analytics, cloud services, or edge computing should consider this vulnerability a high priority for remediation to maintain secure operations and data integrity.

CWE-297Improper Validation of Certificate with Host Mismatch (opens in a new tab)
Variant weaknessLikelihood of exploit: HighOWASP Top 10 A07:2025: Authentication Failures (opens in a new tab)
The product communicates with a host that provides a certificate, but the product does not properly ensure that the certificate is actually associated with that host.
Architecture and Design
Fully check the hostname of the certificate and provide the user with adequate information about the nature of the problem and how to proceed.
Implementation
If certificate pinning is being used, ensure that all relevant properties of the certificate are fully validated before the certificate is pinned, including the hostname.
OWASP Cheat Sheets
OWASP Authentication (opens in a new tab)
OWASP ASVS 4.0.3
V1.14.1 (opens in a new tab)
V2.8.5 (opens in a new tab)
V2.8.4 (opens in a new tab)
From MITRE CWE, MITRE CAPEC and OWASP (Top 10, OpenCRE).

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 14 Jan 2026, 16:00 UTC

WeaknessesCWE-297

Technical details

References

Community reviews

Related threats