Skip to main content
Press slash or control plus K to focus the search. Use the arrow keys to navigate results and press enter to open a threat.
Reconnecting to live updates…

CVE-2026-25644: CWE-295: Improper Certificate Validation in datahub-project datahub

0
High
VulnerabilityCVE-2026-25644cvecve-2026-25644cwe-295
Published: Fri Feb 06 2026 (02/06/2026, 22:40:12 UTC)
Source: CVE Database V5
Vendor/Project: datahub-project
Product: datahub

Description

CVE-2026-25644 is a high-severity vulnerability in the DataHub open-source metadata platform affecting versions prior to 1. 3. 1. 8. The flaw involves improper certificate validation (CWE-295) in the LDAP ingestion source, allowing a man-in-the-middle (MITM) attacker to exploit a TLS downgrade attack. This vulnerability enables attackers to intercept and potentially manipulate metadata ingestion traffic without requiring authentication or user interaction. Although no known exploits are currently reported in the wild, the vulnerability poses a significant confidentiality risk. The issue has been patched in version 1. 3. 1.

AI-Powered Analysis

AILast updated: 02/06/2026, 23:14:57 UTC

Technical Analysis

CVE-2026-25644 is a vulnerability identified in the DataHub open-source metadata platform, specifically affecting the LDAP ingestion source component in versions prior to 1.3.1.8. The root cause is improper certificate validation (CWE-295), which allows an attacker to perform a TLS downgrade attack. In this scenario, an attacker positioned between the client and server can force the communication to use a weaker or no encryption protocol, bypassing the intended TLS protections. This vulnerability does not require any privileges or user interaction, making it remotely exploitable over the network. The impact is primarily on confidentiality, as an attacker can intercept sensitive metadata being ingested via LDAP, potentially exposing organizational data lineage, schema, and other metadata critical for data governance. The vulnerability has a CVSS v3.1 base score of 7.5, reflecting its high severity due to network attack vector, no required privileges, and no user interaction. The issue was addressed and patched in DataHub version 1.3.1.8 by enforcing proper certificate validation and preventing TLS downgrade attempts. No public exploits have been reported yet, but the vulnerability's nature makes it a significant risk for organizations relying on DataHub for metadata management.

Potential Impact

For European organizations, this vulnerability could lead to unauthorized disclosure of sensitive metadata, which may include data lineage, classification, and access policies. Such exposure can undermine data governance, compliance efforts (e.g., GDPR), and intellectual property protection. Attackers exploiting this flaw could gain insights into organizational data structures, potentially aiding further attacks or data exfiltration. Since the vulnerability allows MITM attacks without authentication, any organization using vulnerable DataHub versions on networks accessible to attackers (including internal networks with insufficient segmentation) is at risk. This is particularly critical for sectors with stringent data privacy requirements such as finance, healthcare, and government. The confidentiality breach could also damage trust and lead to regulatory penalties. Availability and integrity are not directly impacted, but the confidentiality loss alone justifies urgent remediation.

Mitigation Recommendations

The primary mitigation is to upgrade DataHub to version 1.3.1.8 or later, where the vulnerability is patched. Organizations should audit their DataHub deployments to identify and remediate any instances running affected versions. Network-level protections such as enforcing strict TLS configurations and disabling legacy protocols can reduce exposure. Implementing network segmentation and monitoring LDAP traffic for anomalies can help detect potential MITM attempts. Additionally, organizations should review their certificate management practices to ensure proper validation and pinning where feasible. Employing intrusion detection systems capable of identifying TLS downgrade attempts can provide early warning. Finally, educating administrators about the risks of using outdated software and enforcing timely patch management policies will reduce future vulnerabilities.

Need more detailed analysis?Upgrade to Pro Console

Technical Details

Data Version
5.2
Assigner Short Name
GitHub_M
Date Reserved
2026-02-04T05:15:41.791Z
Cvss Version
3.1
State
PUBLISHED

Threat ID: 69867278f9fa50a62f39d4f7

Added to database: 2/6/2026, 11:00:08 PM

Last enriched: 2/6/2026, 11:14:57 PM

Last updated: 2/7/2026, 12:08:33 AM

Views: 4

Community Reviews

0 reviews

Crowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.

Sort by
Loading community insights…

Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.

Actions

PRO

Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.

Please log in to the Console to use AI analysis features.

Need more coverage?

Upgrade to Pro Console in Console -> Billing for AI refresh and higher limits.

For incident response and remediation, OffSeq services can help resolve threats faster.

Latest Threats