# CVE-2026-44067: EA header parsing heap over-read

> A remote authenticated attacker can read limited memory or disrupt service via crafted extended attribute data in Netatalk.

- **Severity:** Low 3.7 (`CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:L/I:N/A:L`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 21 May 2026
- **Updated:** 21 May 2026
- **Also known as:** DEBIAN-CVE-2026-44067, GHSA-cwgp-4xrf-xr6q, UBUNTU-CVE-2026-44067

## What is CVE-2026-44067?

CVE-2026-44067 is a low-severity vulnerability in Netatalk, published on 21 May 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

A heap over-read in extended attribute (EA) header parsing in Netatalk 2.1.0 through 4.4.2 allows a remote authenticated attacker to obtain limited information or cause a minor service disruption via crafted EA data.

Weakness: CWE-125 (Out-of-bounds Read)

## Which versions are affected by CVE-2026-44067?


## How do I fix CVE-2026-44067?

Upgrade to a fixed version.

## Is CVE-2026-44067 being exploited?

There is no known exploitation of CVE-2026-44067 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-44067 and fix it if it is affected.

What it is: CVE-2026-44067 is a low-severity vulnerability in Netatalk, published on 21 May 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-44067 in the wild and no public exploit code.

Affected product: Netatalk. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-44067/ (Markdown: https://insights.sbomify.com/CVE-2026-44067/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-44067
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-44067
- OSV: https://osv.dev/vulnerability/CVE-2026-44067

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-44067/
Summaries are generated and may contain mistakes; the official description above is the record.