Special Element Injection Affecting python-ldap package, versions *
Threat Intelligence
The probability is the direct output of the EPSS model, and conveys an overall sense of the threat of exploitation in the wild. The percentile measures the EPSS probability relative to all known EPSS scores. Note: This data is updated daily, relying on the latest available EPSS model version. Check out the EPSS documentation for more details.
Do your applications use this vulnerable package?
In a few clicks we can analyze your entire application and see what components are vulnerable in your application, and suggest you quick fixes.
Test your applications- Snyk IDSNYK-DEBIAN13-PYTHONLDAP-13534786
- published12 Oct 2025
- disclosed10 Oct 2025
Introduced: 10 Oct 2025
NewCVE-2025-61911 (opens in a new tab)How to fix?
There is no fixed version for Debian:13 python-ldap.
NVD Description
Note: Versions mentioned in the description apply only to the upstream python-ldap package and not the python-ldap package as distributed by Debian.
See How to fix? for Debian:13 relevant fixed versions and status.
python-ldap is a lightweight directory access protocol (LDAP) client API for Python. In versions prior to 3.4.5, the sanitization method ldap.filter.escape_filter_chars can be tricked to skip escaping of special characters when a crafted list or dict is supplied as the assertion_value parameter, and the non-default escape_mode=1 is configured. The method ldap.filter.escape_filter_chars supports 3 different escaping modes. escape_mode=0 (default) and escape_mode=2 happen to raise exceptions when a list or dict object is supplied as the assertion_value parameter. However, escape_mode=1 computes without performing adequate logic to ensure a fully escaped return value. If an application relies on the vulnerable method in the python-ldap library to escape untrusted user input, an attacker might be able to abuse the vulnerability to launch ldap injection attacks which could potentially disclose or manipulate ldap data meant to be inaccessible to them. Version 3.4.5 fixes the issue by adding a type check at the start of the ldap.filter.escape_filter_chars method to raise an exception when the supplied assertion_value parameter is not of type str.
References
- https://security-tracker.debian.org/tracker/CVE-2025-61911
- https://github.com/python-ldap/python-ldap/commit/3957526fb1852e84b90f423d9fef34c7af25b85a
- https://github.com/python-ldap/python-ldap/releases/tag/python-ldap-3.4.5
- https://github.com/python-ldap/python-ldap/security/advisories/GHSA-r7r6-cc7p-4v5m