# CVE-2026-44060: Integer underflow in dsi_writeinit() leads to denial of service

> A remote unauthenticated attacker can cause a denial of service in Netatalk via a crafted DSI write request exploiting an integer underflow.

- **Severity:** High 7.5 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **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-44060, GHSA-9vrg-f3g5-fg4c, UBUNTU-CVE-2026-44060

## What is CVE-2026-44060?

CVE-2026-44060 is a high-severity vulnerability in Netatalk, published on 21 May 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

An integer underflow in dsi_writeinit() in Netatalk 1.5.0 through 4.4.2 allows a remote unauthenticated attacker to cause a denial of service via a crafted DSI write request.

Weakness: CWE-191 (Integer Underflow (Wrap or Wraparound))

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


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

Upgrade to a fixed version.

## Is CVE-2026-44060 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-44060 is a high-severity vulnerability in Netatalk, published on 21 May 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-44060 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-44060/ (Markdown: https://insights.sbomify.com/CVE-2026-44060/index.md)
```

## Sources

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

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