Disclaimer: This content was generated using AI. While we strive for accuracy, please verify critical information with official sources.
Sources: National Vulnerability Database, CISA KEV, Exploit-DB
CVE-2026-78384 Overview
CVE-2026-78384 is a decompression bomb vulnerability in Apache CXF's CompressionUtils.inflate() method. The function decompressed attacker-controlled DEFLATE data without enforcing an output-size cap. A crafted payload of a few kilobytes could expand to gigabytes on the heap, exhausting memory and causing denial of service. The flaw is reachable through JSON Web Encryption (JWE) decryption when zip=DEF is set (for example, JoseSessionTokenProvider with RSA-OAEP key wrap) and through SAML redirect/POST binding token inflation. In both paths, decompression occurs before or independent of trust validation, so unauthenticated attackers can trigger it. The issue is tracked under CWE-409: Improper Handling of Highly Compressed Data.
Critical Impact
Unauthenticated remote attackers can exhaust server heap memory by submitting small crafted DEFLATE payloads to JWE or SAML endpoints, resulting in service outage.
Affected Products
- Apache CXF versions prior to 4.2.4
- Apache CXF versions prior to 4.1.9
- Apache CXF versions prior to 3.6.13
Discovery Timeline
- 2026-10-09 - CVE-2026-78384 published to NVD
- 2026-10-15 - Last updated in NVD database
Technical Details for CVE-2026-78384
Vulnerability Analysis
Apache CXF exposes CompressionUtils.inflate() as a utility for decompressing DEFLATE-encoded byte streams. The implementation allocated output buffers based on the inflated data stream without enforcing an upper bound. An attacker who controls the compressed input can supply a highly compressible stream — for example, long runs of repeating bytes — that expands by several orders of magnitude. A payload under 10 KB can inflate to multiple gigabytes, exhausting the Java Virtual Machine (JVM) heap.
Two attack paths reach the vulnerable function. The first is JWE token decryption when the protected header specifies zip=DEF, as used by JoseSessionTokenProvider with RSA-OAEP key wrapping. The second is SAML single sign-on, where tokens delivered through the HTTP-Redirect and HTTP-POST bindings are DEFLATE-compressed. In both flows, CXF inflates the payload before signature or trust validation, so attackers do not need valid credentials or signing material.
Root Cause
The root cause is the absence of a byte-count limit around the java.util.zip.Inflater loop inside CompressionUtils.inflate(). The method continued consuming inflated bytes until the stream reported completion, allocating heap memory proportional to the attacker-controlled output size. This matches the [CWE-409] weakness class for improper handling of highly compressed data.
Attack Vector
Exploitation requires only network access to a CXF endpoint that accepts JWE or SAML tokens. An attacker crafts a small DEFLATE stream with an extreme compression ratio, embeds it inside a JWE object with zip=DEF or a SAML redirect binding SAMLRequest parameter, and submits it. The CXF server decompresses the payload before validation, allocates gigabytes of heap, and either throws OutOfMemoryError or stalls under garbage collection pressure. Repeated requests amplify impact across a cluster. See the Apache mailing list thread and the Openwall OSS-Security notice for additional context.
Detection Methods for CVE-2026-78384
Indicators of Compromise
- Sudden JVM heap growth or java.lang.OutOfMemoryError: Java heap space events in CXF application logs correlating with inbound JWE or SAML traffic.
- Inbound HTTP requests containing JWE headers with "zip":"DEF" or SAML SAMLRequest parameters where the base64-decoded, inflated size vastly exceeds the compressed size.
- Repeated client requests from a single source producing abnormal garbage collection pauses on CXF service nodes.
Detection Strategies
- Instrument application servers to log and alert on DataFormatException thrown from CompressionUtils.inflate() after patching, which indicates an attempted oversized payload.
- Deploy web application firewall rules that reject SAML and JWE payloads exceeding a reasonable compressed-size threshold at the HTTP layer.
- Monitor JVM metrics for abrupt heap allocation spikes and correlate with request logs for JWE or SAML endpoints.
Monitoring Recommendations
- Track Apache CXF version inventory across services and flag any instance below 4.2.4, 4.1.9, or 3.6.13.
- Capture heap dump telemetry on service crashes and inspect for large byte[] allocations originating from java.util.zip.Inflater call paths.
- Correlate authentication-service availability metrics with upstream traffic patterns to detect low-volume, high-impact probe attempts.
How to Mitigate CVE-2026-78384
Immediate Actions Required
- Upgrade Apache CXF to version 4.2.4, 4.1.9, or 3.6.13 depending on the deployed branch.
- Set the org.apache.cxf.compression-max-inflated-size system property to a value appropriate for your workload; the fixed default is 10 MiB.
- Audit services that consume JWE tokens with zip=DEF and SAML redirect/POST bindings, and restrict exposure to trusted networks where feasible.
Patch Information
The Apache CXF project added a configurable maximum inflated-size cap to CompressionUtils.inflate(). The method now aborts with DataFormatException once the configured limit is exceeded. The cap defaults to 10 MiB and can be tuned through the org.apache.cxf.compression-max-inflated-size system property. Fixed releases are 4.2.4, 4.1.9, and 3.6.13. Review the Apache mailing list thread for release notes.
Workarounds
- Terminate SAML and JWE traffic at a reverse proxy that enforces strict maximum request body sizes before forwarding to CXF.
- Disable support for zip=DEF in JWE processing where business requirements allow, forcing clients to submit uncompressed tokens.
- Apply JVM heap limits and container memory caps so that a single process cannot consume shared host memory, containing blast radius until patching is complete.
# Configuration example: enforce a 2 MiB inflated-size cap on JVM startup
java -Dorg.apache.cxf.compression-max-inflated-size=2097152 \
-Xmx2g \
-jar your-cxf-service.jar
Disclaimer: This content was generated using AI. While we strive for accuracy, please verify critical information with official sources.
Sources: National Vulnerability Database, CISA KEV, Exploit-DB

