AIDE through 0.19.4 can ignore hash changes past a null byte
October 22: the oss-security notice describes the null-byte hash bypass; no fix or CVE is named.
AIDE 0.19.4 and earlier can treat a crafted file as unchanged when its hash matches through the first null byte; no CVE yet.
AIDE, a host-based file and directory integrity checker, improperly compares hash values that contain a null byte, according to a notice posted by Hannes von Haugwitz. Versions through 0.19.4 treat a file as unchanged if its hash matches the stored value through the first 0x00 byte, so the difference is silently ignored. A local user could use that to bypass detection of malicious files. The issue is tracked as GHSA-6wc9-4w69-5jc5. No fixed version is stated, and a CVE is still pending.
- Affected versions are AIDE 0.19.4 and earlier.
- Hash comparison is unreliable at the first null byte.
- Advisory identifier is GHSA-6wc9-4w69-5jc5.
- No CVE number has been assigned.
- Hannes von Haugwitz posted the notice on October 22.
Timeline
dated events in the reporting · oldest first- Oct 22, 2026Null-byte hash comparison bypass disclosed · oss-security
What each outlet adds
beyond the shared facts- oss-securityNames GHSA-6wc9-4w69-5jc5 and the pending CVE status.
Coverage
oldest first · one row per article · UTCAIDE 0.16 through 0.19.4 ignores invalid UTF-8 file names
A local user can hide files or directories from the integrity checker; a CVE is still pending.
AIDE through 0.19.4 can ignore hashes containing a null byte
A local user can match a stored hash up to the first 0x00 byte and hide a changed file.