CVE-2026-65627

Decompression bomb via unbounded zlib:inflate in jose_jwe_zip:uncompress/2

  • Medium 6.9

Description

Improper Handling of Highly Compressed Data (Data Amplification) vulnerability in potatosalad jose (erlang-jose) allows a remote attacker to exhaust a node's memory with a small crafted JWE token. The jose_jwe_zip:uncompress/2 function in src/jwe/jose_jwe_zip.erl decompresses the DEFLATE-compressed plaintext of a JWE that carries the optional zip: DEF header by calling zlib:inflate/2 on the entire attacker-controlled stream, with no bound on the output size or the inflation ratio. Raw DEFLATE reaches ratios around 1000:1 on highly repetitive input, so a few-kilobyte token inflates to hundreds of megabytes or gigabytes in a single call. Decompression runs automatically during decryption through jose_jwe:block_decrypt/2 (JOSE.JWE.block_decrypt/2 in Elixir), before the recipient can inspect or reject the payload. With the common asymmetric key-management algorithms (RSA-OAEP, ECDH-ES) an attacker needs only the recipient's public key to craft such a token, so no authentication or secret material is required. A single small token can exhaust the node's memory and crash the BEAM, denying service to all users. This issue affects jose: from 1.0.0 before 1.11.13.

Key facts

Published
26 Oct 2026
Last changed
2 Nov 2026
Assigned by
EEF
EPSS
0.249% likely to be exploited in the next 30 days, higher than 16.308% of CVEs (scores for 17 Nov 2026)
SSVC (CISA)
Exploitation: poc; Automatable: no; Technical impact: partial

Severity scores

Each score is shown as its source gave it. They are not averaged or merged.

  • 6.9CVSS 4.0, Mediumfrom the CNA (EEF)CVSS:4.0/AV:L/AC:L/AT:N/PR:N/UI:N/VC:N/VI:N/VA:H/SC:N/SI:N/SA:N

What to do

  • Reject JWE tokens that carry a zip header before passing them to jose_jwe:block_decrypt/2. DEFLATE compression is rarely used in legitimate JWE traffic, so untrusted tokens whose protected header contains zip: DEF can be inspected and filtered out before decryption.CNA workaround statement

Historical context and remediation

This reference retains the original CVE publication date. A recent record update does not mean a new attack occurred.

CAPEC-130 Excessive Allocation (CNA impact statement)

Version statuses below come from the CNA. An “unaffected” version is not necessarily a currently supported release or proof of a patch date. EPSS is a dated risk estimate, not a count of historical attacks.

Read the original CVE record.

Affected products

VendorProductVersions
potatosaladjose
  • Default status: unaffected
  • 1.0.0 up to but excluding 1.11.13 (affected)
potatosaladjose
  • Default status: unaffected
  • a7746ecd4950f85a393136e449a91dac62b5c429 up to but excluding 857eb8e7f2d33e2c9ca2189e77226561cacaf2ad (affected)

Timeline

  1. 26 Oct 2026 Published

Weakness

References