CVE-2026-65625
Medium 5.9No known exploitationFix availableAttacker-controlled AES-GCM authentication tag length allows tag forgery in jose
Record last updated
CVSS score
Medium on a 0 to 10 scale
EPSS, chance of exploitation in 30 days
Higher than 2% of scored CVEs. A prediction, not evidence.
CISA remediation deadline
Not in the KEV catalog
Description
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.
Weakness: CWE-354
Patching and mitigation
- Patch status
- Fix available (source: Microsoft MSRC)
- Fix documented (source date)
- Mitigation
- Ensure the runtime provides a crypto provider with native AES-GCM support (a standard Erlang/OTP build linked against OpenSSL) so that JOSE dispatches AES-GCM to the native crypto NIF instead of the jose_jwa_aes fallback. Source (opens in a new tab)
- Vendor guidance
- github.com (opens in a new tab)
Affected products
| Vendor | Product | Affected versions | Fixed in | Per |
|---|---|---|---|---|
| Microsoft | azl3 rabbitmq-server 3.13.7-10 on Azure Linux 3.0 | Not documented | Not documented | Microsoft MSRC |
| potatosalad | jose | from 1.2.0 before 1.11.13 | 1.11.13 | CVE Program |
| potatosalad | jose | from 8848b172575fb7d7e1e2977e8ae0a21678d2157a before 3fa1f8e3efda0da5ce6f4c9984789f979dc02740 | 3fa1f8e3efda0da5ce6f4c9984789f979dc02740 | CVE Program |
Timeline
Disclosure
CVE record published by EEF
Source: CVE Program (opens in a new tab)
Advisory
Microsoft advisory published
Advisory change
Microsoft advisory revised (2.0): Information published.
Advisory change
Microsoft advisory revised (3.0): Information published.
Patch
Fix documented by Microsoft MSRC
Vendor guidance and references
- Fix commit 3fa1f8e in potatosalad/erlang-jose (opens in a new tab)patch
- https://github.com/potatosalad/erlang-jose/security/advisories/GHSA-6gxw-6f7r-cjr6 (opens in a new tab)vendor-advisory, related
- Microsoft Security Update Guide (opens in a new tab)vendor-advisory
- EEF CNA record for CVE-2026-65625 (opens in a new tab)related
- Introducing commit 8848b17 in potatosalad/erlang-jose (opens in a new tab)related
- OSV record EEF-CVE-2026-65625 (opens in a new tab)related