Advisory record · GHSA-p34h-wq7j-h5v6

python-ldap is Vulnerable to Improper Encoding or Escaping of Output and Improper Null Termination

CVSS 5.5 MediumEPSS 0.0046 · 39th percentile

Published by the GitHub Advisory Database at 10 Oct 2025, 22:53 UTC. agentprime has not analysed this yet, so whether it affects any app is not known.

PackageEcosystemAffectedFixed in
python-ldapPyPI<3.4.53.4.5
Identifiers
GHSA-p34h-wq7j-h5v6 · CVE-2025-61912 · PYSEC-2026-1846
Weakness (CWE)
CWE-116 · CWE-170
Published
10 Oct 2025
Updated
10 Sept 2026

Machine-written summary

Summary written by Claude Haiku from the source advisory. Not reviewed by a person.

GHSA-p34h-wq7j-h5v6 affects python-ldap versions before 3.4.5. The ldap.dn.escape_dn_chars() helper escapes a NUL character as a backslash followed by a literal NUL byte instead of the hex form \00, so applications that build DNs from untrusted input with it can fail client-side before any request is sent. An attacker who can supply such input to an affected application can cause a denial of service; the source does not describe other impacts. Upgrade to python-ldap 3.4.5, which contains the fix.

Written 5 Nov 2026.

Not analysed yet

We haven’t published our analysis of this Advisory yet. Once a person has reviewed it, this page will say what’s vulnerable, what has to be true for your app to be affected, and how to check.

Severity and exploitation

ScoreRatingCVSSVectorSource
5.5 Medium 4.0 CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:N/VA:L/SC:N/SI:N/SA:N/E:P CNA (GitHub_M)
  • CISA KEV Not listed.
  • EPSS 0.0046, the 39th percentile, on 5 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.

Timeline

  1. 31 Oct 2026, 14:34 UTC First seen by agentprime
  2. 31 Oct 2026, 14:34 UTC Confirmed by OSV

Sources

Facts on this page come from the GitHub Advisory Database (CC-BY 4.0), OSV and the other sources listed, as published. We don’t reproduce full advisory descriptions, which can contain exploit code.