CVE-2026-39373 Latchset CVE debrief

Who should care

Users of JWCrypto library, especially those using versions prior to 1.5.7, should be aware of this vulnerability and take necessary precautions to prevent potential memory exhaustion attacks. System administrators and security teams should review system configurations and monitor for potential memory exhaustion attacks.

Technical summary

The vulnerability exists in JWCrypto's handling of JWE tokens with ZIP compression. An attacker can send a crafted token that, when decompressed, can exceed the 250KB input limit and potentially cause memory exhaustion. The vulnerability is fixed in version 1.5.7. Users of JWCrypto library, especially those using versions prior to 1.5.7, should be aware of this vulnerability and take necessary precautions to prevent potential memory exhaustion attacks.

Defensive priority

Medium

Recommended defensive actions

• Upgrade to JWCrypto version 1.5.7 or later
• Implement input validation and size limits for JWE tokens
• Monitor system memory usage and implement alerting for potential memory exhaustion
• Consider implementing compensating controls, such as rate limiting or IP blocking, to prevent potential attacks
• Review system configurations for potential vulnerabilities
• Track exceptions and retest remediated assets
• Check relevant monitoring, detection, and logs for exposed assets that need extra review

Evidence notes

The vulnerability is described in the CVE record and the NVD detail page. The patch for CVE-2024-28102 is mentioned as limiting input token size to 250KB but not validating decompressed output size. An unauthenticated attacker can cause memory exhaustion on memory-constrained systems by sending crafted JWE tokens with ZIP compression. A token under the 250KB input limit can decompress to approximately 100MB. Users should verify system configurations and monitor for potential memory exhaustion attacks.

Official resources