Weak cryptography in DHCAST128 UAM

published 2026-05-21 5 mo ago modified 2026-07-23 3 mo ago also EUVD-2026-31232

cvss: 7.4; version 3.1, CNA
cisa kev: Not listed; not in CISA's catalog
epss: 0.3%; EPSS 0.3% chance of exploitation in 30 days, percentile 23%
public exploits: 0; none known

Netatalk 1.5.0 through 4.2.2 uses a broken cryptographic algorithm in the DHCAST128 UAM, which allows a remote attacker to obtain authentication credentials or impersonate a user via cryptanalytic attack.

Patch / fix

fixed in 1 distros 2

Netatalk Netatalk 4.5.0

debian alpine

netatalk Debian 14 4.5.0~ds-1

debian advisories DEBIAN-CVE-2026-44053

netatalk Alpine 3.24 4.5.0-r0

alpine advisories ALPINE-CVE-2026-44053

Alpine secdb © Alpine Linux, from https://secdb.alpinelinux.org via OSV; changed: normalised to fixed package versions per release. CC BY-SA 4.0

Vendor advisories

What the vendors themselves say about their products: affected, fixed or not affected, and what to do.

red hat product security vex CVE-2026-44053 updated 2026-06-28 cvss 7.4

netatalk: Netatalk: Data compromise due to weak cryptography

Red Hat All currently supported Red Hat products
not affected: vulnerable code not present

Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf

CISA SSVC

Exploitation: none
Automatable: no
Technical impact: total
Assessed: 5 mo ago (2026-05-21)

Exploit prediction

0.30% chance of exploitation in the next 30 days, higher than 23% of all scored CVEs (FIRST EPSS, 2026-11-08).

CVSS scores

assigned by	version	score	vector
CNA	3.1	7.4	CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:N

Affected products

Netatalk Netatalk

Classification

Weakness

CWE-327 Use of a Broken or Risky Cryptographic Algorithm

References

netatalk.io /security/CVE-2026-44053
vendor-advisory

Sources

CVE List CVE-2026-44053
NVD CVE-2026-44053

Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.

Summary