CVE-2026-44052: Netatalk LDAP password exposure in log output

CVE-2026-44052 · Severity: high · CVSS 7.5 · Published 2026-05-21

Netatalk, an open-source implementation of the Apple Filing Protocol (AFP) used for file sharing, contains a security flaw where LDAP passwords are recorded in plain text within system logs. If an LDAP connection fails, sensitive service account credentials may be exposed to anyone with access to the server's log files. This could allow an unauthorized individual to gain administrative access to directory services or other connected systems.

Technologies: Netatalk. Vendors: Netatalk.

Quick answers

Is CVE-2026-44052 exploited in the wild?
No. Junglewise Threat Intelligence has no report of CVE-2026-44052 being exploited in the wild.
How severe is CVE-2026-44052?
High severity, with a CVSS score of 7.5, published 21 May 2026.
Which products and versions are affected?
Netatalk 2.1.0 through 4.4.2.
Is there a fix for CVE-2026-44052?
A patch was published on 2026-05-21: Fixed in version 4.4.3 Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
How is CVE-2026-44052 attacked?
It is attacked over the network, in a software library.
Am I affected by CVE-2026-44052?
Check whether you run Netatalk at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

Technical details

A CWE-532 (Insertion of Sensitive Information into Log File) vulnerability exists in Netatalk versions 2.1.0 through 4.4.2. When the software is configured to use LDAP for authentication, a 'simple-bind' failure triggers a logging event that includes the cleartext password in the output. This typically occurs during LDAP service outages or restarts. An attacker with read access to the logs can recover service account credentials, leading to potential lateral movement or further compromise of the directory service. The issue is resolved in Netatalk version 4.4.3 or by applying a specific security patch to version 4.4.2.

Affected products

  • Netatalk Netatalk 2.1.0 through 4.4.2

Timeline

  • 2026-05-13: disclosed
  • 2026-05-21: advisory: NVD publication date
  • 2026-05-21: patched: Fixed in version 4.4.3

References

This page as Markdown. Free to reuse under CC BY 4.0 with a link back.