# CVE-2026-44065: Off-by-two in papd lp_write()

> An off-by-two error in Netatalk's papd allows adjacent attackers to modify data or disrupt service via crafted print jobs.

- **Severity:** Low 3.7 (`CVSS:3.1/AV:A/AC:H/PR:N/UI:N/S:U/C:N/I:L/A:L`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 21 May 2026
- **Updated:** 21 May 2026
- **Also known as:** DEBIAN-CVE-2026-44065, GHSA-p64q-3rgx-wmvr, UBUNTU-CVE-2026-44065

## What is CVE-2026-44065?

CVE-2026-44065 is a low-severity memory corruption vulnerability in Netatalk, published on 21 May 2026. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

An off-by-two error in lp_write() in papd in Netatalk 2.0.0 through 4.4.2 allows an adjacent network attacker to modify limited data or cause a minor service disruption via crafted print data.

Weakness: CWE-193 (Off-by-one Error)

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


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

Upgrade to a fixed version.

## Is CVE-2026-44065 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-44065 is a low-severity memory corruption vulnerability in Netatalk, published on 21 May 2026. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-44065 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-44065/ (Markdown: https://insights.sbomify.com/CVE-2026-44065/index.md)
```

## Sources

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

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