CVE-2026-65625

published 26 Oct 2026 · updated 19 Nov 2026

Attacker-controlled AES-GCM authentication tag length allows tag forgery in jose

5.9MediumCVSS 5.9EPSS 0%

No exploitation in the wild has been reported. EPSS puts the chance of exploitation in the next 30 days at 0%. Fixed in 1.11.13 and 3fa1f8e3efda0da5ce6f4c9984789f979dc02740.

The pure-Erlang AES-GCM fallback in jose_jwa_aes derives the number of verified authentication tag bits from the attacker-supplied tag itself. In the {aes_gcm, Bits} clause of block_decrypt/4, the incoming tag is guarded only by is_binary/1, with no check on its length. Verification in gcm_block_decrypt/6 then computes TBits = bit_size(T) and compares only those bits of the real 128-bit tag. An attacker who controls a JWE token can truncate the authentication tag to as little as 8 bits, so only 8 bits are ever checked. This reduces forgery resistance from 2^-128 to 2^-8, and a forged ciphertext is reliably accepted as authentic within 256 attempts without knowledge of the key (an authentication tag forgery and integrity bypass). Supplying a tag longer than 128 bits instead causes a badmatch that crashes the decrypting process. The fallback is reached through the public JWE decryption path whenever AES-GCM is not provided by a native crypto NIF, for example on FIPS or stripped or older OTP builds. This issue affects jose: from 1.2.0 before 1.11.13.

Affected

Vendors, products and packages with version ranges

VendorProductVersionsFixed
potatosalad>=1.2.0 <1.11.13, >=8848b172575fb7d7e1e2977e8ae0a21678d2157a <3fa1f8e3efda0da5ce6f4c9984789f979dc027401.11.13, 3fa1f8e3efda0da5ce6f4c9984789f979dc02740

Timeline

Every event on this vulnerability

Embed

A live severity badge for an advisory, README or ticket

CVE-2026-65625 severity on Zeptric[![CVE-2026-65625](https://zeptric.io/badge/cve/CVE-2026-65625.svg)](https://zeptric.io/cve/CVE-2026-65625)