Skip to main content
VulnerabilityPublished Updated

CVE-2026-25644: datahub · Improper Certificate Validation

Affects datahubSource CVE Database V5

0

Not known to be exploited · CVSS 7.5 High : upgrade to 1.3.1.8 soon.

Data as of 26 Oct 2026, 10:12 UTC

CVSS 3.1 base score
7.5High
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.3% chance of exploitation in 30 days – higher than 27% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch
Available – fixed in 1.3.1.8
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 6 Feb 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponised: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq 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.

What to do

Upgrade datahub and datahub-project/datahub to 1.3.1.8.

Affected software

ProductAffectedFixed in
datahub-projectdatahubAffected
  • <1.3.1.8
Fixed in
  • 1.3.1.8
GitHubdatahub-project/datahubpkg:github/datahub-project/datahubOther threatsAffected
  • <1.3.1.8
Fixed in
  • 1.3.1.8

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

AI-suggested

European organizations should immediately upgrade any DataHub deployments to version 1.3.1.8 or later to apply the official patch that fixes the improper certificate validation issue. Beyond upgrading, organizations should enforce strict TLS configurations for LDAP connections, including disabling legacy or weak TLS versions and cipher suites to prevent downgrade attacks. Network segmentation should be implemented to limit exposure of LDAP traffic to trusted network zones only. Employing network monitoring and intrusion detection systems to detect unusual LDAP traffic patterns or potential MITM attempts can provide early warnings. Organizations should also conduct regular audits of their DataHub configurations and ensure that certificate validation is enabled and correctly configured. Where possible, use mutual TLS authentication between DataHub and LDAP servers to strengthen trust. Finally, educating network administrators and security teams about the risks of TLS downgrade attacks and proper certificate validation practices will help maintain a secure environment.

Description

DataHub is an open-source metadata platform. Prior to version 1.3.1.8, the LDAP ingestion source is vulnerable to MITM attack through TLS downgrade. This issue has been patched in version 1.3.1.8.

References

Community reviews

Loading reviews…