# CVE-2026-44047: SQL injection in MySQL CNID backend

> Remote authenticated attackers can exploit SQL injection in Netatalk's MySQL backend to read, modify data, or cause denial of service.

- **Severity:** High 8.8 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H`)
- **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:** 22 May 2026
- **Also known as:** DEBIAN-CVE-2026-44047, GHSA-p2g3-q382-2rhw, UBUNTU-CVE-2026-44047

## What is CVE-2026-44047?

CVE-2026-44047 is a high-severity SQL injection 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

An SQL injection vulnerability in the MySQL CNID backend in Netatalk 3.1.0 through 4.4.2 allows a remote authenticated attacker to obtain unauthorized access to data, modify data, or cause a denial of service.

Weakness: CWE-89 (Improper Neutralization of Special Elements used in an SQL Command)

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


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

Upgrade to a fixed version.

## Is CVE-2026-44047 being exploited?

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

## Fix prompt for AI coding agents

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

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

## Sources

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

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