CVE-2026-39373

JWCrypto: JWE ZIP decompression bomb

Published Apr 7, 2026 CVSS 3.1 · 5.3 Medium EPSS < 1% KEV · Not listed
Description
JWCrypto implements JWK, JWS, and JWE specifications using python-cryptography. Prior to 1.5.7, an unauthenticated attacker can exhaust server memory by sending crafted JWE tokens with ZIP compression. The existing patch for CVE-2024-28102 limits input token size to 250KB but does not validate the decompressed output size. An unauthenticated attacker can cause memory exhaustion on memory-constrained systems. A token under the 250KB input limit can decompress to approximately 100MB. This vulnerability is fixed in 1.5.7.

Analysis

AI-generated

Technical impact

JWCrypto is a Python library implementing JSON Web Key, Signature, and Encryption. A flaw allows an unauthenticated attacker to send a crafted JWE token that is limited to 250 KB on input but can decompress to about 100 MB. When processed by the library, the large decompressed payload consumes server memory and can cause the process to crash or become unresponsive. This type of attack is a decompression bomb scenario, and the vulnerability is classified as CWE‑409 and CWE‑770.

Affected Systems

Any installation of latchset:jwcrypto before version 1.5.7 is affected. Systems that incorporate this library to handle JWTs—such as web services or authentication back‑ends—may be exposed if the library remains outdated.

Risk and Exploitability

The CVSS score of 5.3 indicates medium severity. An EPSS score is not provided, and the vulnerability is not listed in the CISA KEV catalog. Exploitation requires only that an attacker transmit a compliant JWE token to the vulnerable system; the attack is unauthenticated and can occur over any channel that delivers the token. On memory‑constrained servers, the resulting exhaustion can cause a denial‑of‑service condition. The likely attack vector is inferred to be any input pathway that allows the attacker to supply a large compressed JWE.

Remediation

No solution or workaround provided in the CVE record.

OpenCVE Recommended Actions

  • Upgrade latchset:jwcrypto to version 1.5.7 or newer, which enforces a decompressed output size limit.

Generated by OpenCVE AI on April 8, 2026 at 02:25 UTC.

Tracking

Sign in to view the affected projects.

Advisories

Source ID Title
Github GHSA Github GHSA GHSA-fjrm-76x2-c4q4 JWCrypto: JWE ZIP decompression bomb
History
Type Values Removed Values Added
CPEs cpe:2.3:a:latchset:jwcrypto:*:*:*:*:*:*:*:*
Type Values Removed Values Added
First Time appeared Latchset
Latchset jwcrypto
Vendors & Products Latchset
Latchset jwcrypto
Type Values Removed Values Added
Metrics ssvc

{'options': {'Automatable': 'yes', 'Exploitation': 'poc', 'Technical Impact': 'partial'}, 'version': '2.0.3'}

Type Values Removed Values Added
Description JWCrypto implements JWK, JWS, and JWE specifications using python-cryptography. Prior to 1.5.7, an unauthenticated attacker can exhaust server memory by sending crafted JWE tokens with ZIP compression. The existing patch for CVE-2024-28102 limits input token size to 250KB but does not validate the decompressed output size. An unauthenticated attacker can cause memory exhaustion on memory-constrained systems. A token under the 250KB input limit can decompress to approximately 100MB. This vulnerability is fixed in 1.5.7.
Title JWCrypto: JWE ZIP decompression bomb
Weaknesses CWE-409
References
Metrics cvssV3_1

{'score': 5.3, 'vector': 'CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L'}

Weaknesses
  • CWE-409

    Improper Handling of Highly Compressed Data (Data Amplification)

  • CWE-770

    Allocation of Resources Without Limits or Throttling

Sources

Status
PUBLISHED
Assigner
GitHub_M
Published
Updated
Apr 7, 2026, 8:22 PM
Reserved
Apr 6, 2026, 9:29 PM
Status
Analyzed
Published
Apr 7, 2026, 8:16 PM
Modified
Jul 24, 2026, 9:10 PM
Severity
Important
Public date
Apr 7, 2026, 7:35 PM