CVE Tools
Track your stack

CVE-2026-39373

JWCrypto: JWE ZIP decompression bomb

No known exploitation. EPSS puts it in the 24th percentile. A vendor fix is available.

CVSS 3.15.3MediumEPSS percentile24th0.3% chance in 30 daysCISA KEVNot listedNo confirmed exploitation
No public exploit knownFixVendor fixNo build named by the sources
Check it yourself

OpenVAS · 19 checks

e.g. OID 1.3.6.1.4.1.25623.1.1.11.2026.19042

Run the check

Published Updated Sources: CVE.org, NVD, BDU

NVD CVE.org

What to do

The vendor has published a fix. Version details are below where the sources state them.

  • Latchset JwcryptoAffected: < 1.5.7Upgrade to: not statedStated by: CVE record
  • Red Hat Inc. Red Hat Enterprise LinuxAffected: 7Upgrade to: not statedStated by: BDU
  • Сообщество свободного программного обеспечения Debian GNU/LinuxAffected: 11Upgrade to: not statedStated by: BDU
  • ООО «Ред Софт» РЕД ОСAffected: 7.3Upgrade to: not statedStated by: BDU
  • Red Hat Inc. Ansible Automation PlatformAffected: 2.5 for RHEL 8Upgrade to: not statedStated by: BDU

Versions as the sources state them. 1 more product has version data. Full version matrix after sign-in

Check it yourselfA free OpenVAS check exists for this CVE. Run it against your hosts.Is your organisation exposed?Request an assessment to establish which checks fit your systems.

What it is

From the CVE record

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.

In plain language

No plain-language summary for this CVE yet.

Exploitation

Where each signal puts this CVE on the scale from published to confirmed exploited.

EPSS24th
CISA KEV

Not in the catalog. CISA has not confirmed exploitation.

Public exploits

No public exploit or proof of concept found in the sources we track.

EPSS

0.3% chance of exploitation activity in the next 30 days, which ranks it in the 24th percentile of scored CVEs.

Exploit Prediction Scoring System, FIRST.org. A probability, not a confirmation.

Lifecycle

7 events over 108 days, from the signal feeds we watch.

  1. Patch availablerecord updated
  2. OpenVAS check added
  3. Patch availablerecord updated
  4. Publishedweakness classified

Affected products

Technical detail

CVSS 3.1 vector

Open in the CVSS calculator

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L

Scored 5.3 by NVD.

How it is reached

  • Attack Vector NetworkExploitable remotely over the network without any special conditions
  • Attack Complexity LowNo special conditions — the attack can be reliably reproduced
  • Privileges Required NoneNo authentication required — anyone can exploit this
  • User Interaction NoneNo user interaction needed — fully automated exploitation

Scope

  • Scope UnchangedImpact is limited to the vulnerable component itself

Impact if exploited

  • Confidentiality NoneNo confidentiality impact
  • Integrity NoneNo integrity impact
  • Availability LowReduced performance or intermittent disruption of service

Weaknesses

Sources

References in the record

And 3 more references. See all after sign-in

Watch the software you run.

My Stack ranks new CVEs for your products by real-world exploitation, so the next serious one reaches you without reading every advisory.

We'll flag the next CVE, public exploit or patch for Red Hat Enterprise Linux, not every advisory.