Deno's AES GCM authentication tags are not verified

Exploitation

No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.

CVSS 4.0

7.7 · CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:H/VA:N/SC:N/SI:N/SA:N/E:P · score source

EPSS

• CVE-2025-24015: 0.29% estimated exploitation activity in the next 30 days; percentile 21.25 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.

As published by the source; long descriptions are shortened.

Summary This affects AES-256-GCM and AES-128-GCM in Deno, introduced by commit 0d1beed. Specifically, 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 setaad is also affected, as it is incorporated into the GCM hash (ghash) but this too is not validated, rendering AAD checks ineffective. PoC Impact While discovered through experimentation, authentication failures that should raise errors may be silently ignored.

Published by the source

4 Jun 2025, 20:48 UTC

Last modified by the source

4 Jun 2025, 22:56 UTC

Source last checked

26 Oct 2026, 15:38 UTC

1. Revision 1 · created · 26 Oct 2026

   Published from ghsa record GHSA-2x3r-hwv5-p32x

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: CVE-2025-24015

Advisory: Deno's AES GCM authentication tags are not verified
IDs: CVE-2025-24015, GHSA-2x3r-hwv5-p32x
Record: https://patchnext.com/advisories/cve-2025-24015 (revision 1, source checked 26 Oct 2026, 15:38 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: High (CVSS 7.7)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: deno_node 0.125.0; deno 2.1.7. A vendor fix does not mean a deployment is fixed.

## Affected components
- crates.io deno_node: affected >= 0.102.0, < 0.125.0; fixed in 0.125.0
- crates.io deno: affected >= 1.46.0, < 2.1.7; fixed in 2.1.7

## Suggested inspection (read-only)
- crates.io deno_node: check the installed version with your package manager.
- crates.io deno: check the installed version with your package manager.

## Supported action
Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on deno_node, deno.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://github.com/advisories/GHSA-2x3r-hwv5-p32x (GitHub-reviewed advisory GHSA-2x3r-hwv5-p32x lists affected ranges: crates.io deno >=1.46.0 =0.102.0 <0.125.0)

Commands are suggestions: review each one before running it.