Skip to main content
Menu
CVEs

Netatalk out-of-bounds read in Spotlight search code

CVE-2026-110779Published , updated

4.3MediumCNA
Exploited
No known exploitation
Fix
Fixed in 4.5.2
Who is exposed
Not reported

Summary

Netatalk, a file server suite for Unix-like systems, has a heap out-of-bounds read flaw in its Spotlight search code. A remote attacker with low privileges can send a crafted request that makes the server read eight bytes past the end of a smaller heap allocation, and an unauthenticated client can reach the same path when guest access is enabled.

Written by a model

Original description

Netatalk is a Free and Open Source file server suite for Unix-like operating systems. From 3.1.0 until 4.5.2, sl_createCNIDArray in etc/afpd/spotlight.c assumes every element of kMDQueryItemArray points to an eight-byte uint64_t and copies sizeof(uint64_t) bytes from the indexed p->dd_talloc_array element without validating the element's talloc type or allocation size. An authenticated AFP client with access to a Spotlight-enabled volume can use FPSpotlightRPC to supply a mixed-type sl_array_t containing a shorter boolean, nil, or string element, and an unauthenticated client can reach the same path when the optional guest UAM and a guest-accessible volume are enabled. The resulting eight-byte read extends beyond the shorter element's heap allocation and supplies an internal CNID filter; no confidentiality channel, write primitive, or code execution was demonstrated, while a production crash would require additional heap placement conditions. The container-type validation added for CVE-2023-42464 does not validate each element inside an accepted sl_array_t and therefore does not resolve this issue. This issue is fixed in version 4.5.2.

What to do

Upgrade to a fixed version: 4.5.2.

Check your systems with an agent

Paste this into a coding or ops agent. It checks your systems read-only and reports a table per asset.

Check whether my systems are affected by CVE-2026-110779 (Netatalk: Spotlight sl_createCNIDArray(): type-confusion heap out-of-bounds read on mixed-type kMDQueryItemArray), using the cve.now data below.

Rules: work read-only. Do not run exploit code, proof-of-concept scripts or scanners that send attack payloads, and do not change any configuration, package, image or deployment. Report findings only.

What cve.now has for CVE-2026-110779 (entry last updated 2026-11-20):
Affected:
- Netatalk netatalk: from 3.1.0, fixed in 4.5.2
Fixed versions: 4.5.2.
Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory.
CISA KEV: CVE-2026-110779 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-110779 only. If you also check another CVE, look up its own KEV status; never assume it from this one.

How to check:
- Installed software: check what is actually running, not what a repo declares. Read the version from each host, container image and Kubernetes node (the binary's version output, the OS package database, image layers), and check whether the conditions above hold there. Distribution packages may carry a backported fix under an older version number; confirm against the distribution's own advisory.

Verify against the linked advisories before concluding, and cite the date you read each one:
- https://github.com/Netatalk/netatalk/security/advisories/GHSA-p6fh-q283-9x4v
- https://github.com/Netatalk/netatalk/commit/7aba35c5f03bc48ca706783b5d665c241563605e
- https://github.com/Netatalk/netatalk/commit/7e216cef54d6ec45582e714478394f85e4081980
- https://github.com/Netatalk/netatalk/releases/tag/netatalk-4-5-2
Do not conclude an asset is unaffected unless you checked it and the evidence covers both its version and the conditions above. If you could not check something, mark it unknown and say what is missing.

Report a table with one row per asset and these columns: Asset | Version or build | Status (affected, fixed, not applicable, unknown) | Compensating controls | Exposure (internet-facing, internal, none) | Evidence | Next action.

Entry: https://cve.now/CVE-2026-110779
For follow-up questions, use the cve.now MCP server at https://mcp.cve.now/mcp (no authentication), for example execute with name cve.get and arguments {"id": "CVE-2026-110779"}.

Affected versions

cve.now Index

7Pof 100 · provisional · methodology v3
  • Exploitation?/40Unknown. No CISA SSVC exploitation rating yet
  • Exposure3/25Reachable over the network · Unknown: No advisory context yet
  • Reach?/20Unknown. No tracked technology or package matched
  • Severity4.3/10CVSS 4.3
  • No patch0/5No signal

What would change the score

  • Would score about 62 if added to CISA KEV
  • Would score about 57 if CISA's SSVC rates exploitation active
  • Would score about 26 if advisories confirm default setups are exposed

Timeline

  1. CVE published
  2. First seen by cve.now

Evidence 5

KindSource
Vendor advisory 1Establishes: Affected and fixed versions.
AdvisoryGitHub · Netatalk/netatalk · Advisory GHSA-p6fh-q283-9x4v
CVE record 1Establishes: The identifier and description.
RecordCVE List · CVE-2026-110779
Other links 3
RepositoryGitHub · Netatalk/netatalk · Commit 7aba35c5
RepositoryGitHub · Netatalk/netatalk · Commit 7e216cef
RepositoryGitHub · Netatalk/netatalk · Release netatalk-4-5-2

Questions about CVE-2026-110779

Is CVE-2026-110779 being exploited?

It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.

Source: cve.now feed data

Which versions are affected by CVE-2026-110779?

netatalk: from 3.1.0 before 4.5.2.

Source: cve.now feed data

How do I fix CVE-2026-110779?

Upgrade to a fixed version: 4.5.2.

Source: cve.now feed data

No corrections so far. Something wrong on this page? Report an error.