Skip to content
Applications

CVE-2026-44047

8.8
High
EPSS 0.37%May 21, 2026

SQL injection in Netatalk CNID backend (MySQL) allows authenticated remote data access and DoS.

common questions

Is CVE-2026-44047 being exploited?

Not confirmed. CVE-2026-44047 does not appear in CISA's Known Exploited Vulnerabilities catalog, which records only exploitation that has been observed and reported publicly. That is evidence of absence of a report, not evidence the flaw is unattacked. EPSS currently estimates a 0.37% probability of exploitation in the next 30 days.

How severe is CVE-2026-44047?

CVE-2026-44047 is rated High with a CVSS score of 8.8. Severity describes how bad exploitation would be, not how likely it is: pair it with exploitation evidence before deciding what to patch first.

Is there a patch for CVE-2026-44047?

Not known from our data. No patch reference has been recorded for CVE-2026-44047, which is not the same as no patch existing — a fix may have shipped without a tagged reference, or after this record was written. The vendor advisory is the only authority on whether a fix exists, and mitigations may be available regardless.

What does CVE-2026-44047 affect?

CVE-2026-44047 affects Netatalk CNID backend with MySQL (v3.1.0–v4.4.2). Confirm the exact affected versions against the vendor advisory before deciding you are exposed.

What should I do about CVE-2026-44047?

Patch when released; restrict CNID/MySQL access; monitor for anomalies.

Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.

executive summary
technical analysis
affected
Netatalk CNID backend with MySQL (v3.1.0–v4.4.2)
impact

Authenticated attacker can read/modify CNID data and cause DoS via SQL injection.

action required

Patch when possible

affected versions
Netatalk Netatalk
  • affected>= 3.1.0 and <= 4.4.2
vendor says fixed in4.4.3

As published in the CVE Program record. A version outside these ranges is not a statement that it is unaffected — vendors sometimes understate a range, and distribution-backported builds carry upstream numbers that do not reflect what was patched into them.

how to fix
Remediation steps are tailored for users whose stack is affected. Add this technology to your stack to see the fix checklist.
references
get alerted

Track only the vulnerabilities that affect your infrastructure.

start for free