Vulnerability in Deno
CVE-2025-24015
Deno is a JavaScript, TypeScript, and WebAssembly runtime. Versions 1.46.0 through 2.1.6 have an issue that affects AES-256-GCM and AES-128-GCM in Deno in which the authentication tag is not being validated. This means tampered ciphertexts or incorrect keys might not be detected, which breaks the guarantees expected from AES-GCM. Older versions of Deno correctly threw errors in such cases, as does Node.js. Without authentication tag verification, AES-GCM degrades to essentially CTR mode, removing integrity protection. Authenticated data set with set_aad is also affected, as it is incorporated into the GCM hash (ghash) but this too is not validated, rendering AAD checks ineffective. Version 2.1.7 includes a patch that addresses this issue.
Published · last modified .
CVSS v3 metric
CVSS v3 base score 5.3 (Medium). Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N.
EPSS exploit prediction
EPSS 0.003, 21.4th percentile (scored ); unchanged over 30 days. About EPSS.
Affected products
- Deno
- Denoland Deno — versions >= 1.46.0, < 2.1.7
Weakness classification (CWE)
References
- https://github.com/denoland/deno/security/advisories/GHSA-2x3r-hwv5-p32x (Exploit, Patch, Vendor Advisory)
- https://github.com/denoland/deno/commit/0d1beed (Patch)
- https://github.com/denoland/deno/commit/4f27d7cdc02e3edfb9d36275341fb8185d6e99ed (Patch)
- https://github.com/denoland/deno/commit/a4003a5292bd0affefad3ecb24a8732886900f67 (Patch)