Vulnerability EEF-CVE-2026-81319

Unknown
UNKNOWN RISK
Vulnerabilities without an assigned CVSS score. Severity is not determinable from available data.
2 months ago
August 30, 2026 at 06:05 PM UTC
Unsafe deserialization of decrypted terms enables node DoS in AshCloak
0.1.0 - 0.3.1
0.1.0 - 0.3.1

Summary

Unsafe deserialization of decrypted terms enables node DoS in AshCloak

Details

Summary

Deserialization of Untrusted Data vulnerability in ash-project ash_cloak allows an attacker who can influence the bytes of an encrypted column to crash the BEAM node, by triggering unbounded atom creation or a decompression bomb during decryption.

AshCloak.Calculations.Decrypt decodes the decrypted binary with Ash.Helpers.non_executable_binary_to_term/1 without the :safe option, so atoms in the payload are interned during the decode and never garbage collected, and the term format's compressed form is inflated transparently. vault.decrypt!() is the only barrier and stops tampering only for an authenticated cipher. Cloak also ships the unauthenticated AES.CTR, whose ciphertext an attacker who knows their own plaintext can XOR into any same-length payload without the key, so an ordinary read of the forged column reaches the decoder. A few hundred kilobytes of distinct atoms exhausts the atom table, or a small compressed payload inflates to gigabytes.

This issue affects ash_cloak: from 0.1.0 before 0.4.0.

Configurations

An application must use ash_cloak with an unauthenticated vault cipher (for example the AES.CTR cipher shipped by Cloak), or run in a deployment where the stored ciphertext can be modified, and read a cloaked field so the decrypt calculation runs.

Impacted packages

Timeline

Published
2 months ago
August 30, 2026 at 06:05 PM UTC
Fixed (0.4.0)
2 months ago
August 30, 2026 at 03:45 PM UTC
Last Modified
1 day ago
November 20, 2026 at 05:23 PM UTC