/

CVE-2026-25644

Severity:

HIGH RISK

(7.5)

Improper Certificate Validation / TLS Downgrade

CVE-2026-25644

Analyzed

Vulnerability type

Category:

Improper Certificate Validation / TLS Downgrade

CWE:

CWE-295

Impact:

Confidentiality and Integrity Compromise via Man-in-the-Middle

Severity:

HIGH RISK

(7.5)

CVSS version:

3.1

Catch this CVE while code is being written

Detect vulnerable code directly in pull requests, so CVEs are fixed before merge.

Summary

DataHub's LDAP ingestion source, in versions prior to 1.3.1.8, is vulnerable to a man-in-the-middle (MITM) attack due to a TLS downgrade weakness.

Under specific network and configuration conditions, an attacker positioned on the network path could intercept and potentially tamper with LDAP metadata ingestion traffic by forcing or leveraging weaker transport security.

Affected context

The vulnerability affects DataHub deployments that use the LDAP ingestion source to pull identity or directory metadata from an LDAP server over what is assumed to be a secure (TLS/SSL) channel.

It is relevant when:

  • LDAP ingestion is configured to use TLS or STARTTLS, and
  • The environment is susceptible to active network interception (e.g., shared networks, untrusted segments, or compromised infrastructure), and
  • TLS negotiation, certificate validation, or protocol enforcement does not strictly guarantee an authenticated, encrypted channel.

In such scenarios, an attacker on the network path may be able to interfere with the TLS negotiation, leading to downgraded or spoofed connections.

Exploit preconditions

  • Attack surface: Network path between the DataHub LDAP ingestion component and the LDAP server.
  • Required access: Ability to intercept, modify, or inject traffic between DataHub and the LDAP endpoint (e.g., via ARP spoofing, DNS poisoning, compromised router, or control of an intermediate proxy).
  • Trigger point: Execution of an LDAP ingestion job that initiates a connection believed to be protected by TLS.
  • Why exploitation is possible: The LDAP ingestion source does not fully enforce strong TLS guarantees (such as strict certificate validation or resistance to protocol downgrades), enabling an attacker to present downgraded or spoofed TLS parameters and impersonate the LDAP server or force weaker transport security.

Why this happens

The underlying issue corresponds to CWE-295: Improper Certificate Validation, combined with weak enforcement of TLS properties in the LDAP ingestion path.

Conceptually, the LDAP client logic either:

  • Does not consistently verify the authenticity of the server certificate, or
  • Accepts downgraded or weaker TLS modes without failing closed, or
  • Permits configurations that bypass strict TLS validation.

This insecure pattern allows a network attacker to position themselves as an apparent, but unauthenticated, LDAP endpoint or to reduce the security level of the connection, thereby undermining the expected confidentiality and integrity of the metadata ingestion channel.

Potential impact

  • An attacker could intercept LDAP metadata transmitted between DataHub and the LDAP server.
  • An attacker could alter directory information being ingested, potentially leading to inaccurate or malicious metadata in DataHub.
  • An attacker could capture credentials or tokens transmitted over the weakened channel (if such data is sent in a way exposed by the downgrade).
  • An attacker could impersonate the LDAP server to feed crafted entries, impacting access models, ownership metadata, or auditability within DataHub.
  • An attacker could gain insights into the structure of the organization's directory and identities, aiding further reconnaissance.

General mitigation guidance

Mitigation centers around treating all directory connections as untrusted until cryptographically authenticated and enforcing robust TLS policies.

Common defensive patterns include:

  • Enforcing strict certificate validation, including hostname verification, for all LDAP-over-TLS or STARTTLS connections.
  • Configuring clients to reject protocol downgrades and insecure cipher suites, failing closed when strong TLS is not available.
  • Pinning certificates or trusted certificate authorities where operationally feasible, especially in internal environments.
  • Segregating LDAP ingestion traffic to trusted network segments and minimizing opportunities for on-path adversaries.
  • Applying least-privilege principles to LDAP accounts used for ingestion so that compromise of the channel yields minimal directory access.
  • Documenting and reviewing TLS-related configuration options to avoid "insecure but convenient" modes such as disabling certificate checks.

How teams detect issues like this

Effective detection involves both code-centric and environment-centric measures:

  • Static analysis and code review:
  • Look for LDAP client configurations that disable certificate verification, skip hostname checks, or accept all certificates.
  • Identify uses of TLS/SSL libraries with flags or options that allow insecure protocols or cipher suites.
  • Review ingestion configuration defaults to ensure secure settings are used by default rather than requiring optional hardening.
  • Runtime and network monitoring:
  • Monitor for LDAP traffic occurring in cleartext or using downgraded protocols where TLS is expected.
  • Use IDS/IPS or network monitoring to detect anomalous TLS handshakes, unusual certificate issuers, or sudden shifts to non-TLS connections.
  • Log and alert on connection failures related to TLS validation to ensure that future misconfigurations are visible rather than silently bypassed.
  • Automated tooling:
  • Employ security scanners or automated configuration checks to flag non-secure LDAP or TLS configurations in deployment manifests and CI/CD pipelines.

Sources

SourceLink
github.comgithub.com/datahub-project/datahub/security/advisories/GHSA-j34h-x7qg-4qw5

Frequently asked

questions

It can be, if the LDAP ingestion traffic traverses networks an attacker can influence (including the public internet or poorly segmented internal networks). The attacker needs to be able to intercept or manipulate the traffic path between DataHub and the LDAP server; it is not exploitable purely through the application's public HTTP interface.

The attacker must have on-path network capabilities between the DataHub LDAP ingestion component and the LDAP server, such as control of a router, switch, proxy, or the ability to perform techniques like ARP or DNS spoofing within the relevant network segment.

Enforce strong, fail-closed TLS semantics for all LDAP connections: require TLS, validate server certificates and hostnames, disallow insecure protocols and cipher suites, and ensure configuration cannot silently bypass these safeguards.

Treat transport security as part of the core design rather than an optional feature: adopt secure-by-default TLS configurations, routinely review certificate validation logic, leverage well-maintained TLS libraries with safe defaults, and integrate configuration and code checks into CI/CD pipelines to prevent the reintroduction of insecure TLS behaviors.

Find out what's already
exploitable in your codebase.