CVE-2025-61911: python-ldap has sanitization bypass in ldap.filter.escape_filter_chars
Noroxi assessment
Priority: Monitor (action score 22/100)
- The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
- Probability of exploitation in the next 30 days: 0.32% (FIRST EPSS).
- Anyone who can reach it over the internet can trigger it. No account or password is required. No user action is required. No special conditions are required; it is repeatable.
- Fixed version: py3-ldap (Alpine:v3.24) 3.4.5-r0; python-ldap (Debian:12) 3.4.3-2+deb12u1; python-ldap (Debian:13) 3.4.4-1+deb13u1.
Low priority for now. Upgrade to py3-ldap (Alpine:v3.24) 3.4.5-r0; python-ldap (Debian:12) 3.4.3-2+deb12u1; python-ldap (Debian:13) 3.4.4-1+deb13u1 or later.
Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it
Primary sources: NVD · CVE.org · FIRST EPSS
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`.
- Published
- Oct 10, 2025
- Updated
- Oct 19, 2026
- EPSS
- 0.3% · 25th percentile
- CWE
- CWE-75
Report tools
Action score
22
Low priority for now.
- CVSS
- 22 / 40 · 5.5 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.3%
CISA SSVC decision
- Exploitation
- proof of concept
- Automatable
- no
- Technical impact
- partial
Vulnrichment: CISA's decision-tree inputs.
CNA vs NVD score
- NVD
- —
- CNA · GitHub_M
- 5.5
- NVD has not scored this yet; the score shown is the CNA’s.
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:L/VI:L/VA:N/SC:N/SI:N/SA:N/E:P
The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.
Get told when this record changes
- Not in KEV: no record of exploitation in the wild
- No public exploit code on record
- A fix has been released
If any of these changes, we'll tell you in the daily email digest.
Is your version affected? Check itNoroxi analysis
What does it mean in your environment?
The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.
We use this product, ask for helpAffected systems
Is your version affected?
Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.
| Vendor | Product | CPE |
|---|---|---|
| python-ldap | python-ldap | cpe:2.3:a:python-ldap:python-ldap |
Versions reported by the vendor
Affected version ranges reported by the assigning authority (GitHub_M). Independent of NVD's CPE analysis and usually ahead of it.
python-ldap python-ldap
- < 3.4.5affected
Affected versions
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- python-ldap python-ldapbefore 3.4.5
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| Alpine:v3.24 | py3-ldap | before 3.4.5-r0 | 3.4.5-r0 |
| Debian:12 | python-ldap | before 3.4.3-2+deb12u1 | 3.4.3-2+deb12u1 |
| Debian:13 | python-ldap | before 3.4.4-1+deb13u1 | 3.4.4-1+deb13u1 |
| Debian:14 | python-ldap | before 3.4.5-1 | 3.4.5-1 |
| openSUSE:Leap 15.6 | python-ldap | before 3.4.0-150400.3.3.1 | 3.4.0-150400.3.3.1 |
| openSUSE:Leap 16.0 | python-ldap | before 3.4.4-160000.3.1 | 3.4.4-160000.3.1 |
| openSUSE:Tumbleweed | python-ldap | before 3.4.5-1.1 | 3.4.5-1.1 |
| PyPI | python-ldap | before 3.4.5 | 3.4.5 |
| SUSE:Linux Enterprise Module for Package Hub 15 SP6 | python-ldap | before 3.4.0-150400.3.3.1 | 3.4.0-150400.3.3.1 |
| SUSE:Linux Enterprise Module for Package Hub 15 SP6 | python-ldap | before 3.1.0-150100.3.5.1 | 3.1.0-150100.3.5.1 |
| SUSE:Linux Enterprise Server 16.0 | python-ldap | before 3.4.4-160000.3.1 | 3.4.4-160000.3.1 |
Same product
python-ldap: all recordsOther highest-scoring records for the same primary product.
- CVE-2021-46823python-ldap before 3.4.0 is vulnerable to a denial of service when ldap.schema is used for untrusted schema definitions, because of a…27Monitor
- CVE-2025-61912python-ldap Vulnerable to Improper Encoding or Escaping of Output and Improper Null Termination22Monitor
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
| Product / package | Fixed version | Source |
|---|---|---|
| alpine:py3-ldap | 3.4.5-r0 · Alpine:v3.24 | Package registry (OSV) |
| debian:python-ldap | 3.4.3-2+deb12u1 · Debian:12 | Package registry (OSV) |
| opensuse:python-ldap | 3.4.0-150400.3.3.1 · openSUSE:Leap 15.6 | Package registry (OSV) |
| PyPI:python-ldap | 3.4.5 | Package registry (OSV) |
| suse:python-ldap | 3.1.0-150100.3.5.1 · SUSE:Linux Enterprise Module for Package Hub 15 SP6 | Package registry (OSV) |
| suse:python-ldap | 3.4.0-150400.3.3.1 · SUSE:Linux Enterprise Module for Package Hub 15 SP6 | Package registry (OSV) |
Exploit status
No known public exploit
No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
No dated events beyond publication.
Patch and commit links
Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.
Not on record for this CVE: EPSS history · researcher credit · variant or chain candidate · public bounty program.
Technical details
Attack conditions
- Anyone who can reach it over the internet can trigger it.
- No account or password is required.
- No user action is required.
- No special conditions are required; it is repeatable.
If successful
- Confidentiality
- Integrity
- Availability
- Attack vector
- Network
- Attack complexity
- Low
- Privileges required
- None
- User interaction
- None
- Scope
- X
Weakness class (CWE)
CWE-75 · Failure to Sanitize Special Elements into a Different Plane (Special Element Injection)CVSS vector
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:L/VI:L/VA:N/SC:N/SI:N/SA:N/E:P/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X
nvd-secondary
Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
Attack patterns (CAPEC)
ATT&CK techniques
—
Change log (1)
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (1 more)Show less
Vendor advisories and official records. Exploit/PoC links are deliberately left out.