LDAP credential exposure via failed-bind logging
Published May 21, 2026 · Updated May 21, 2026
Sensitive-data logging in Netatalk 2.1.0 through 4.4.2 allows attackers with log access to obtain LDAP credentials after bind failures. In libatalk/acl/ldap.c, the LDAP bind-failure path writes the simple-bind password to an error-level log message without redaction. Exposure requires LDAP simple-bind use, a bind failure such as an LDAP outage or restart, and access to Netatalk logs; it does not alter data or interrupt service.
Summary
What happened
Sensitive-data logging in Netatalk 2.1.0 through 4.4.2 allows attackers with log access to obtain LDAP credentials after bind failures. In libatalk/acl/ldap.c, the LDAP bind-failure path writes the simple-bind password to an error-level log message without redaction. Exposure requires LDAP simple-bind use, a bind failure such as an LDAP outage or restart, and access to Netatalk logs; it does not alter data or interrupt service.
The record
- CVE
- CVE-2026-44052
- Published
- May 21, 2026
- Updated
- May 21, 2026
- Vendor
- Netatalk
- Product
- Netatalk
- Classifications
- CWE-532, T1552.001
- Attack vector
- Unavailable
- Privileges
- Unavailable
Timeline
How it unfolded
- May 21, 2026CVE publishedPublication date reported by the CVE source.
- May 21, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=2.1.0 <=4.4.2
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo