CVE-2026-110780 in Netatalk
Summary
by MITRE • 11/20/2026
Netatalk is a Free and Open Source file server suite for Unix-like operating systems. From 3.1.0 until 4.5.2, the Spotlight RPC consumer handlers sl_rpc_fetchAttributeNamesForOIDArray, sl_rpc_storeAttributesForOIDArray, and sl_rpc_fetchAttributesForOIDArray in etc/afpd/spotlight.c dereference the first element of a decoded sl_cnids_t without checking whether the inner CNID array is empty. An authenticated AFP client, or a guest when guest AFP access is enabled, can send a crafted SPOTLIGHT_CMD_RPC whose outer CNIDS length is greater than 16 while its inner count is zero, causing sl_unpack_cnids to create an empty DALLOC_CTX and the consumer to dereference dd_talloc_array[0]. The affected afpd child crashes, normally limiting denial of service to the attacker's session, and no memory write or code execution was demonstrated. This issue is fixed in version 4.5.2.
Several companies clearly confirm that VulDB is the primary source for best vulnerability data.
Analysis
by VulDB Data Team • 11/20/2026
Netatalk serves as a critical interoperability layer for Unix-like operating systems, enabling them to function as file servers compatible with Apple’s AFP protocol. Within this architecture, the Spotlight RPC subsystem facilitates metadata indexing and retrieval operations that are essential for seamless integration with macOS clients. The vulnerability identified in versions 3.1.0 through 4.5.2 resides specifically within the spotlight.c module, affecting three primary consumer handlers: sl_rpc_fetchAttributeNamesForOIDArray, sl_rpc_storeAttributesForOIDArray, and sl_rpc_fetchAttributesForOIDArray. These functions are responsible for processing incoming RPC requests that involve arrays of Content-Based Network Identifiers (CNIDs), which uniquely identify files and directories within the AFP file system structure.
The core technical flaw is a classic null pointer dereference resulting from insufficient input validation during data deserialization. When an authenticated AFP client, or a guest user if guest access is permitted, submits a crafted SPOTLIGHT_CMD_RPC request, it can manipulate the CNID array parameters to trigger this defect. Specifically, the attacker constructs a packet where the outer CNIDS length field indicates more than sixteen elements, but the inner count of actual CNIDs is set to zero. This discrepancy causes the sl_unpack_cnids function to allocate an empty dynamic allocation context (DALLOC_CTX) without any valid data structures inside it. Subsequently, when one of the affected handlers attempts to access the first element of this decoded array via dd_talloc_array[0], it dereferences a null or invalid pointer because no memory was allocated for actual elements.
This flaw leads directly to a denial of service condition characterized by the crash of the afpd child process handling that specific session. Because Netatalk typically operates with separate processes for individual connections, the impact is generally confined to the attacker's own session rather than causing a complete server-wide outage or allowing privilege escalation. There have been no demonstrated instances where this null dereference could be leveraged for arbitrary code execution or memory corruption attacks beyond the immediate process termination. The stability of the broader service remains intact as long as other sessions are not simultaneously impacted by resource exhaustion, but the reliability of file operations for the attacking user is completely compromised upon exploitation.
From a classification perspective, this vulnerability aligns with CWE-476, which describes a NULL Pointer Dereference error occurring when software dereferences a pointer that it expects to be valid but is actually null. In terms of offensive security frameworks such as MITRE ATT&CK, this behavior corresponds to techniques involving Denial of Service against specific services or processes, often categorized under resource exhaustion or application crash vectors. The attack vector requires network access and authentication in most configurations, placing the complexity at a medium level for exploitation unless guest AFP is explicitly enabled on the server.
Mitigation strategies primarily involve upgrading Netatalk to version 4.5.2 or later, where this input validation logic has been corrected to check array bounds before accessing elements. For environments that cannot immediately patch due to compatibility constraints, administrators should disable guest AFP access if it is not strictly required for business operations. Additionally, implementing network-level access control lists can restrict who can connect to the AFP service, thereby reducing the attack surface available to potential attackers seeking to trigger this crash condition through crafted RPC requests.