Live › vulnerability › CVE-2026-65625
Go to dashboardThe pure-Erlang AES-GCM fallback in jose accepts an attacker-truncated authentication tag, checking only as few as 8 bits. An attacker who controls a JWE token can forge ciphertext that is accepted as authentic within about 256 attempts, without the key; an oversized tag instead crashes the decrypting process.
Summary written from the sources below. Check the originals before acting.
First seen by InfraStack 2026-10-26 20:50 UTC. All times on this page are UTC.
Applications that decrypt JWE tokens with jose from 1.2.0 before , where the AES-GCM fallback is in use rather than a native crypto NIF. Exposure matters most when the attacker can supply JWE tokens to the decrypting service; systems on a standard OTP build with native AES-GCM, or that never decrypt JWE input, are less exposed. Teams that only sign or verify JWS are not in the described path.
1.11.13No product ranges from the sources yet.
rebar.lock or mix.lock, or run rebar3 tree | grep jose; affected versions are from 1.2.0 before 1.11.13.1.11.13 or later.Each row is the first time that source carried this signal. The analyst’s rows are its own findings.
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.
This page as .md · .json · in your agent: get_signal("CVE-2026-65625")
NVD data is provided by NIST and is public domain. Posts quoted belong to their authors.