Vulnerabilities

Vulnerability · CVE-2026-78384

CompressionUtils.inflate() decompressed attacker-controlled DEFLATE data with no output-size cap.

Published Oct 9, 2026 · catalog updated Oct 15, 2026 · CompressionUtils.inflate() decompressed attacker-controlled DEFLATE

Check if you run it

No confirmed exploitation is on record for CVE-2026-78384. EPSS is 0.28%. Act only if a listed version of CompressionUtils.inflate() decompressed attacker-controlled DEFLATE is installed.

Gaps on this record

  • The stored product name is a package slug. The name on this page is taken from the title (CompressionUtils.inflate() decompressed attacker-controlled DEFLATE).
  • No version range is stored. A customer cannot check an installed version against this record.
  • No vendor fix or required action is stored. Compare the linked advisory before you change production.
Severity
High7.5
Known exploitation
Not in CISA/VulnCheck KEV
EPSS
0.28%
Remediation
Advisory link
Affected products
See sources for product scope

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.

No affected version ranges are stored yet. Use the vendor advisory before you decide this record does not apply.

How to fix CVE-2026-78384

What to do

Three questions, each answered from this record only. Confirm the vendor advisory before you patch.

Should you patch?

No confirmed exploitation is on record for CVE-2026-78384. EPSS is 0.28%. Act only if a listed version of CompressionUtils.inflate() decompressed attacker-controlled DEFLATE is installed.

Which versions are affected?

Affected version ranges are not on this record. Compare the installed version with the linked vendor advisory before you change production.

What should an analyst verify?

CWE-409. EPSS 0.28%. There is no CISA KEV listing. No Exploit-DB or Metasploit reference is linked. Use the source links for the original advisory.

Code

The project this record applies to. Exploit listings stay in References.

No public source repository is identified for this product.

Timeline

Detection, updates, and resolution for this record.

  1. Oct 9, 2026 · NIST NVD

    Detected

    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: Ad

  2. Oct 15, 2026 · NIST NVD

    Updated

    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: Ad

Sources

  • CVE.orgVulnerability recordCVE-2026-78384

    Official CVE identifier

    cve.org
  • FIRST EPSSExploitation probabilityCVE-2026-78384

    30-day exploitation probability 0.3%

    first.org
  • NIST NVDVulnerability recordCVE-2026-78384

    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 red

    nvd.nist.gov

References

Freshness

Last verified in this catalog Oct 18, 2026. Significant claims (KEV, EPSS, CVSS, affected ranges) come from the source rows above — open the original publisher for the authoritative advisory.