# CVE-2026-44058: Authentication bypass via admin auth user

> Remote privileged users can bypass authentication to log in as arbitrary users in Netatalk, requiring an upgrade to secure the file server.

- **Severity:** Medium 6.4 (`CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 21 May 2026
- **Updated:** 22 May 2026
- **Also known as:** DEBIAN-CVE-2026-44058, GHSA-3jh8-xjh7-hwv3, UBUNTU-CVE-2026-44058

## What is CVE-2026-44058?

CVE-2026-44058 is a medium-severity authentication bypass vulnerability in Netatalk, published on 21 May 2026. An attacker needs administrator access to exploit it, with no action from the victim.

### Official description

An authentication bypass vulnerability in Netatalk 2.2.2 through 4.4.2 allows a remote privileged user to authenticate as an arbitrary user via the admin auth user mechanism.

Weakness: CWE-287 (Improper Authentication)

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


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

Upgrade to a fixed version.

## Is CVE-2026-44058 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-44058 is a medium-severity authentication bypass vulnerability in Netatalk, published on 21 May 2026. An attacker needs administrator access to exploit it, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-44058 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-44058/ (Markdown: https://insights.sbomify.com/CVE-2026-44058/index.md)
```

## Sources

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

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