# CVE-2026-44072: system() after failed chdir()

> A local privileged user can execute unintended commands or disrupt service due to improper error handling after a failed directory change.

- **Severity:** Low 2.5 (`CVSS:3.1/AV:L/AC:H/PR:H/UI:N/S:U/C:N/I:L/A:L`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 21 May 2026
- **Updated:** 22 May 2026
- **Also known as:** DEBIAN-CVE-2026-44072, GHSA-hpgh-hjhq-qx82, UBUNTU-CVE-2026-44072

## What is CVE-2026-44072?

CVE-2026-44072 is a low-severity command injection 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

Netatalk 2.2.1 through 4.4.2 calls system() after a failed chdir() without properly handling the error condition, which allows a local privileged user to execute unintended commands or cause a minor service disruption under specific conditions.

Weakness: CWE-78 (Improper Neutralization of Special Elements used in an OS Command)

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


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

Apply the vendor's patch.

## Is CVE-2026-44072 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-44072 is a low-severity command injection 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-44072 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-44072/ (Markdown: https://insights.sbomify.com/CVE-2026-44072/index.md)
```

## Sources

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

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