cve.bz

CVE-2026-65627 potatosalad jose

6.9 mediumEPSS 0.2%Fix available

Medium (6.9) in potatosalad jose. EPSS 0.2% estimated probability of exploitation activity in the next 30 days. Fixed in jose 1.11.13.

On this page
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.

Severity

CVSS 4.0

6.9 medium
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
EPSS
0.2% (unchanged from 0.2% a week ago) estimated probability of exploitation activity in the next 30 days; 16th percentile. Scored 2026-11-17. A forecast for this CVE across the internet, not for your own systems.
CWE
CWE-409 Improper Handling of Highly Compressed Data (Data Amplification)
Published
Modified
NVD analysis
Deferred: the NVD does not plan to analyze it
Record from
the NVD, synced

Fix and patched versions

Ask an AI about this CVE

Show the promptExplain CVE-2026-65627 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2026-65627?via=ask-ai-copy and https://cve.bz/cve/CVE-2026-65627?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2026-65627 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.

Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.

Affected

Versions

From the CNA's record in the CVE List.

ProductAffected
potatosalad josefrom 1.0.0 before 1.11.13

Packages (OSV)

AdvisoryEcosystemPackageAffectedFixed in
EEF-CVE-2026-65627Hexjose>=1.0.0 <1.11.131.11.13
EEF-CVE-2026-656271.11.12, 1.11.11, 1.11.10, 1.11.9, 1.11.8 and 40 moreno fix published

Linux distributions

DistributionReleasePackageFixed inAdvisory
Debian12, 13erlang-joseno fix listedDEBIAN-CVE-2026-65627
Debian14erlang-jose1.11.13-1DEBIAN-CVE-2026-65627
Ubuntu18.04:LTS, 20.04:LTS, 22.04:LTS and 3 morejoseno fix listedUBUNTU-CVE-2026-65627
Red Hathummingbird:1grafana12.40:12.4.13-0.4.hum1RHSA-2026:90388
Red Hathummingbird:1grafana13.10:13.1.8-0.4.hum1RHSA-2026:88537
Red Hathummingbird:1grafana13.20:13.2.4-0.3.hum1RHSA-2026:88541
Red Hathummingbird:1rabbitmq-server4.30:4.3.7-0.1.hum1RHSA-2026:86200
Red Hathummingbird:1rabbitmq-server4.30:4.3.7-0.2.hum1RHSA-2026:91476
Azure Linux3joseno fix listedAZL-111152
Azure Linux3rabbitmq-serverno fix listedAZL-112199

From the distributions' data via OSV.dev: the Debian Security Tracker; Ubuntu Security Notices © Canonical Ltd., CC BY-SA 4.0; Red Hat Security Data © Red Hat, Inc., CC BY 4.0; Microsoft's Azure Linux vulnerability data, MIT. Modified: reformatted and linked to CVE records. Credits. On the distributions' own pages: Debian · Ubuntu · Red Hat.

Red Hat

Red Hat rates this Important.

Red Hat's statement

A decompression bomb vulnerability was discovered in the Erlang and Elixir jose library when handling JSON Web Encryption (JWE) tokens with compression enabled (DEF). The library uncompresses ciphertext using zlib:inflate/2 without bounding the output size or inflation ratio. An unauthenticated remote attacker can exploit this flaw by submitting a small, highly compressed crafted JWE token, causing uncontrolled memory allocation that exhausts system resources and crashes the BEAM virtual machine, resulting in a denial of service.

Red Hat's mitigation

Reject JWE tokens carrying the "zip": "DEF" header at the application gateway or API perimeter before decryption routines are executed.

--- CME Mitigation Guidance (2026-11-02) ---

Disclaimer: The following mitigation solutions are provided as a courtesy, pending the application of an official patch. This content was generated utilizing AI tools in conjunction with data from https://cmetaxonomy.org. Customers are advised to independently evaluate and test these temporary mitigations within their own infrastructure.

The highest-value action is to enforce bounded decompression during JWE block decryption in jose: upgrade to jose 1.11.13 (or the corresponding fixed Red Hat builds), which perform incremental decompression via zlib:safeInflate/2 and abort with a badarg error if output exceeds a configurable ceiling, closing all 2 injection vectors (crafted JWE token with zip DEF header, DEFLATE decompression bomb). Until patched, this is a concern on applications decrypting JWE tokens using jose, so reject JWE tokens carrying the zip DEF header at the application gateway or API perimeter before decryption routines are executed. As a compensating measure, monitor cgroup memory pressure events and PSI to detect rapid memory spikes and out-of-memory pressure caused by decompression bombs. These controls limit blast radius and contain exploitation, but they do not fix the underlying unbounded decompression defect — apply the upstream patch to fully remediate.

Highest-impact CME: CME-1010 cgroup Memory Pressure Monitoring (memory.events / PSI) (medium)

ProductPackageStateAdvisory
Red Hat Hardened Imagesrabbitmq-server4-3-main-4.3.7-0.1.hum1Fixed 2026-10-20RHSA-2026:86200
Red Hat Hardened Imagesgrafana13-1-main-13.1.8-0.4.hum1Fixed 2026-10-23RHSA-2026:88537
Red Hat Hardened Imagesgrafana13-2-main-13.2.4-0.3.hum1Fixed 2026-10-23RHSA-2026:88541
Red Hat Hardened Imagesgrafana12-4-main-12.4.13-0.4.hum1Fixed 2026-10-26RHSA-2026:90388
Red Hat Hardened Imagesrabbitmq-server4-3-main-4.3.7-0.2.hum1Fixed 2026-10-27RHSA-2026:91476
Red Hat Hardened Imagesrabbitmq-server4.2Will not fix
Red Hat OpenStack Platform 17.1rabbitmq-serverAffected
Red Hat OpenStack Platform 18.0rabbitmq-serverAffected

Contains Red Hat Security Data © Red Hat, Inc., licensed under CC BY 4.0. Source: https://access.redhat.com/security/data. Modified: reformatted. Red Hat's page for CVE-2026-65627.

References

Check your stackJSON