Track vulnerabilities like this one.
Sign up free to get alerted when software you use is affected.
7.5
JanusGraph Docker images may exhaust memory with crafted compression
published 9 days ago
Summary
The JanusGraph Docker images (versions 1.0, 1.1, and 1.2) use the Netty library to decompress incoming data. Because Netty does not correctly limit the size of data compressed with Brotli, Zstandard or Snappy, an attacker can send a specially crafted request that makes the server allocate unlimited memory, potentially causing it to crash. Update the images to a version that includes Netty 4.2.13.Final or 4.1.133.Final, or apply the vendor's recommended patch, to restore the memory limits.
What to do
The CVE record does not list a fixed version. Check the vendor's site or the advisory links below - a fix may already be released.
Affected software
| Ecosystem | Vendor | Product | Affected versions |
|---|---|---|---|
| Docker Hardened Images:Alpine:3.24 | docker hardened images | janusgraph-1.0 | All versions |
| Docker Hardened Images:Alpine:3.24 | docker hardened images | janusgraph-1.1 | All versions |
| Docker Hardened Images:Alpine:3.24 | docker hardened images | janusgraph-1.2 | All versions |
| Docker Hardened Images:Debian:13 | docker hardened images | janusgraph-1.0 | All versions |
| Docker Hardened Images:Debian:13 | docker hardened images | janusgraph-1.1 | All versions |
| Docker Hardened Images:Debian:13 | docker hardened images | janusgraph-1.2 | All versions |
Original advisory text
Netty is an asynchronous, event-driven network application framework. Prior to 4.2.13.Final and 4.1.133.Final…
Netty is an asynchronous, event-driven network application framework. Prior to 4.2.13.Final and 4.1.133.Final, HttpContentDecompressor accepts a maxAllocation parameter to limit decompression buffer size and prevent decompression bomb attacks. This limit is correctly enforced for gzip and deflate encodings via ZlibDecoder, but is silently ignored when the content encoding is br (Brotli), zstd, or snappy. An attacker can bypass the configured decompression limit by sending a compressed payload with Content-Encoding: br instead of Content-Encoding: gzip, causing unbounded memory allocation and out-of-memory denial of service. The same vulnerability exists in DelegatingDecompressorFrameListener for HTTP/2 connections. This vulnerability is fixed in 4.2.13.Final and 4.1.133.Final.
References
- https://scout.docker.com/v/DHI-6mg7-6q7x-zjre-xres Vendor Advisory
- https://nvd.nist.gov/vuln/detail/CVE-2026-42587 Vendor Advisory
- https://github.com/netty/netty/security/advisories/GHSA-f6hv-jmp6-3vwv Vendor Advisory
- https://security-tracker.debian.org/tracker/CVE-2026-42587 Vendor Advisory
- https://github.com/advisories/GHSA-f6hv-jmp6-3vwv Vendor Advisory
- https://ubuntu.com/security/CVE-2026-42587 Vendor Advisory
- http://people.ubuntu.com/~ubuntu-security/cve/CVE-2026-42587 Vendor Advisory
Internet-facing
14 days
Internal
60 days
- Not known to be exploited
- Can be exploited automatically (estimated)
- Gives an attacker partial control (estimated)
Timeline
Published10 Nov 2026
Updated16 Nov 2026
First seen16 Nov 2026
Sources
DHI-6mg7-6q7x-zjre-xres · OSV
Track software like this
Free during beta