CVE-2026-44047
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedAn 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.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceSQL injection vulnerability in the MySQL CNID (Common Netatalk Info Database) backend of Netatalk versions 3.1.0-4.4.2 allows remote authenticated attackers to inject malicious SQL queries. The vulnerability exists in how user-supplied input is handled when interacting with the MySQL database storing CNID information, enabling data exfiltration, modification, or DoS.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Identify installed Netatalk versionRun 'netatalk -V' or 'apt list --installed | grep netatalk' or check package manager for netatalk versionAffected if Installed version is lower than 4.4.3
-
Confirm MySQL CNID backend is in useInspect Netatalk configuration file (typically /etc/netatalk/netatalk.conf or afp.conf) and look for 'cnid' or 'CNID' parameters set to MySQL backend (e.g., 'cnid_mysql' or similar MySQL-specific CNID configuration)Affected if CNID backend is configured to use MySQL database (cnid_mysql module)
-
Verify AFP service accessibilityCheck network listeners with 'netstat -tlnp | grep 548' or 'ss -tlnp | grep 548' to see if AFP port 548 is bound to a non-localhost interface; review firewall rules for inbound access to port 548Affected if AFP service (port 548) is accessible from network addresses other than localhost/127.0.0.1
You are affected if Netatalk version is below 4.4.3 AND the MySQL CNID backend is configured AND the AFP service is network-accessible to untrusted users.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
dbcve · scopedUpgrade Netatalk to version beyond 4.4.2 when available, or disable the MySQL CNID backend and use an alternative backend (e.g., dbd) with proper input validation if upgrade is not immediately feasible.
Netatalk 4.4.3 or later (latest stable release)
- 1. Identify the current Netatalk version installed: `netatalk -V` or check your package manager
- 2. If running Netatalk 3.1.0 through 4.4.2, plan for upgrade to version 4.4.3 or later
- 3. Backup the current Netatalk configuration and MySQL CNID database before upgrading
- 4. Upgrade Netatalk using your system's package manager (e.g., `apt update && apt upgrade netatalk` for Debian/Ubuntu, or `yum update netatalk` for RHEL/CentOS), or compile from source if using a manual installation
- 5. Verify the upgrade was successful by checking the version: `netatalk -V`
- 6. Restart the Netatalk service: `systemctl restart netatalk` or equivalent
- 7. Verify the MySQL CNID backend is functioning correctly and test AFP/CNID operations
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation4.0 h
- Testing4.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,328.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-44047 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2026-44047 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data