Skip to main content

Jwcrypto CVE-2026-39373

| EUVDEUVD-2026-19911 MEDIUM
Improper Handling of Highly Compressed Data (Data Amplification) (CWE-409)
2026-04-07 GitHub_M GHSA-fjrm-76x2-c4q4
5.3
CVSS 3.1 · Vendor: GitHub_M
View

Vulnerability Assessment

Weakness
CWE
ASVS 5.0
V2 - Validation and Business Logic Compression ratio limits
Impact

The CVSS score of 5.3 with attack vector network, low complexity, no privileges required, and low availability impact reflects a moderate denial-of-service severity. The EPSS score and exploitation probability are not explicitly provided but the unauthenticated, network-accessible nature (AV:N/PR:N) and simple attack mechanism (AC:L) suggest practical exploitability. No KEV status is indicated, meaning this is not confirmed as actively exploited by CISA at the time of analysis. The real-world risk is particularly acute for memory-constrained environments (edge devices, containerized services, resource-limited deployments) where a single malicious JWE token can trigger complete service failure. However, the impact is limited to availability (A:L) with no confidentiality or integrity compromise, and the attack requires an application actively processing untrusted JWE tokens with compression enabled. This is a solid priority for services handling JWT/JWE from untrusted sources, especially in resource-limited contexts, but lower urgency than critical RCE or authentication bypass issues.

Exploit ScenarioDerived

An attacker crafts a JWE token with ZIP compression containing a highly-compressible payload (e.g., repetitive data) that is approximately 250KB or less in compressed form but decompresses to ~100MB. The attacker sends this token to a vulnerable JWCrypto application over the network without requiring authentication. When the application processes the JWE token, the library decompresses the payload without enforcing output size limits, causing rapid memory consumption that exhausts available RAM and crashes the service or degrades performance on memory-constrained systems. No public exploit code is explicitly referenced, but the attack is trivial to construct given the compression mechanics.

This Month Plan within 30 days. Why: MEDIUM severity (CVSS 4.0-6.9).
Patch available 0.0% exploitation probability (EPSS)

Get an e-mail when this CVE is exploited, patched or re-scored. Free account.

Alert me

AnalysisAIv1 – Apr 07, 2026

Memory exhaustion in JWCrypto before 1.5.7 allows unauthenticated remote attackers to cause denial of service on memory-constrained systems by sending crafted JWE tokens with ZIP compression that decompress to approximately 100MB despite remaining under the 250KB input size limit. The vulnerability exploits incomplete validation in the upstream CVE-2024-28102 patch, which restricted input token size but failed to enforce decompressed output limits.

RemediationAI

Vendor-released patch: upgrade JWCrypto to version 1.5.7 or later, which implements proper decompression size validation to prevent memory exhaustion from compressed JWE tokens. Applications should ensure they are using the patched version and verify that JWE token processing includes strict decompression limits. Refer to the official advisory at https://github.com/latchset/jwcrypto/security/advisories/GHSA-fjrm-76x2-c4q4 for detailed remediation guidance. As a temporary workaround prior to patching, applications can disable ZIP compression in JWE processing if the use case permits, or implement external request size limits and resource monitoring to detect abnormal decompression behavior.

Affected VersionsENISA

jwcrypto < 1.5.7

Affected Packages

pypi jwcrypto fix: 1.5.7

Source: OSV (Open Source Vulnerabilities)

Affects your stack

Affects 1 package in pypi

Checking this CVE against your own stacks and servers is part of the Basic plan and up.

Technical ContextAI · show details

JWCrypto is a Python library implementing JSON Web Token (JWT), JSON Web Key (JWK), JSON Web Signature (JWS), and JSON Web Encryption (JWE) specifications using the python-cryptography backend. The vulnerability exists in JWE processing when ZIP (DEFLATE) compression is enabled. The root cause is CWE-409 (Improper Handling of Highly Compressed Data), where the library validates the compressed input token size (250KB limit from CVE-2024-28102 remediation) but does not enforce a maximum decompressed size. An attacker can craft a highly-compressible payload that remains under 250KB when compressed but expands to ~100MB when decompressed, exhausting memory when the library processes the token without bounds-checking the decompression output.

Know when Jwcrypto gets its next vulnerability

  • Watch products and get an email when something new is published
  • Check this CVE against your own stack and servers
  • Exploit and PoC references, threat intelligence from 22 sources

No credit card · 7-day full trial

Severity by source

Vendor (GitHub_M) PRIMARY 5.3 MEDIUM
AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L
SUSE MEDIUM
Red Hat 7.5 MEDIUM

Primary rating from Vendor (GitHub_M).

CVSS VectorVendor: GitHub_M

Attack Vector
Network
Attack Complexity
Low
Privileges Required
None
User Interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
None
Availability
Low

Lifecycle Timeline

2
Patch available
Apr 16, 2026 - 05:29 EUVD
1.5.7
CVE Published
Apr 07, 2026 - 19:35 nvd
MEDIUM 5.3

DescriptionCVE.org

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.

Threat Intelligence Overview

EPSS Score
0.0%
Top 89% exploitable
Threat Intel
1
1 source
Data Quality
8 sources
Confidence: High
EUVD NVD CVE.org EPSS Vulnrichment GHSA Vendor GitHub VulDB

How this decision was reached

The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.

SignalValue
Severity MEDIUM
CISA KEV No
Public POC No
EPSS 0.0%
Patch available Yes
Active threat No
Deciding rule
MEDIUM severity (CVSS 4.0-6.9)
What every action level means
Emergency Immediate action required. Criteria: CRITICAL + in CISA KEV (actively exploited) without patch, OR CRITICAL + EPSS > 30% without patch, OR CRITICAL + active threat signals without patch.
Act Now Prioritize within 24-48h. Criteria: in KEV with patch available, OR CRITICAL + public POC, OR HIGH + EPSS > 10%, OR CRITICAL + active threat, OR any CRITICAL severity.
This Week Schedule remediation this week. Criteria: HIGH severity (CVSS 7.0-8.9). Patch within normal change window.
This Month Plan within 30 days. Criteria: MEDIUM severity (CVSS 4.0-6.9), lower exploitation probability. Include in regular patch cycle.
Monitor Track and reassess. Criteria: LOW severity (CVSS 0.1-3.9), minimal exploitation risk. No immediate action needed.

SSVC AssessmentENISA

SSVC Decision· derived
Scheduled
Exploitation
Poc
System Exposure· derived
Open
Automatable
Yes
Human Impact· derived
Medium
Technical Impact
Partial

Priority Score

26
Low Medium High Critical
KEV: 0
EPSS: 0
CVSS: +26
PoC: 0
Weaponized: 0
Threat intel: 0
Gov advisory: 0

Attack Technique

Information disclosure occurs when an application unintentionally exposes sensitive data that aids attackers in reconnaissance or directly compromises security.

Vendor StatusVendor

SUSE

Severity: Medium
Product Status
SUSE Package Hub 15 SP6 Fixed
openSUSE Leap 15.6 Fixed
SUSE Linux Enterprise Server 16.1 Fixed
SUSE Linux Enterprise Server for SAP applications 16.1 Fixed
SUSE Package Hub 15 SP6 Fixed

This site uses cookies essential for authentication and security. No tracking or analytics cookies are used. Privacy Policy