---
id: CVE-2026-78384
title: >-
  CompressionUtils.inflate() decompressed attacker-controlled DEFLATE data with
  no output-size cap
summary: >-
  CompressionUtils.inflate() decompressed attacker-controlled DEFLATE data with
  no output-size cap. A small (~KB) crafted payload could expand to gigabytes on
  the heap. Reachable via JWE decryption when zip=DEF (e.g.
  JoseSessionTokenProvid…
severity: none
published: '2026-10-09'
updated: '2026-10-09'
sourceUpdated: '2026-10-09T16:33:39.007'
source: NVD
sourceUrl: 'https://nvd.nist.gov/vuln/detail/CVE-2026-78384'
references:
  - url: 'https://lists.apache.org/thread.html/xoh63rlxn0m9koft5j4jxrfd0hf81v3q'
    label: security@apache.org
  - url: 'http://www.openwall.com/lists/oss-security/2026/10/09/6'
    label: af854a3a-2127-422b-91ae-364da2661108
tags:
  - nvd
ingestedAt: '2026-10-09T12:53:29.300Z'
---

## Overview

CompressionUtils.inflate() decompressed attacker-controlled DEFLATE data with no output-size cap. A small (~KB) crafted payload could expand to gigabytes on the heap. Reachable via JWE decryption when zip=DEF (e.g. JoseSessionTokenProvider with RSA-OAEP key wrap) and via SAML redirect/POST binding token inflation — in both cases decompression happens before/independent of trust validation.

Fix: Added a configurable maximum inflated-size cap (default 10 MiB, org.apache.cxf.compression-max-inflated-size system property) to CompressionUtils.inflate(); aborts with DataFormatException once exceeded.
Users are recommended to upgrade to versions 4.2.4 or 4.1.9 or 3.6.13, which fix this issue.

## Remediation

Refer to the linked advisories for vendor-supplied fixes and affected version ranges.