cve.bz

CVE-2026-78384 apache cxf

7.5 highEPSS 0.4%

High (7.5) in apache cxf. EPSS 0.4% estimated probability of exploitation activity in the next 30 days.

On this page
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.

Severity

CVSS 3.1

7.5 high
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
EPSS
0.4% (unchanged from 0.4% a week ago; 0.3% 30 days ago) estimated probability of exploitation activity in the next 30 days; 31st percentile. Scored 2026-11-15. A forecast for this CVE across the internet, not for your own systems.
CISA's assessment (SSVC)
Exploitation: none · Automatable: yes · Technical impact: partial, assessed 2026-10-15. From CISA's Vulnrichment in the CVE List: whether it is exploited, whether exploiting it can be automated, and how much control it gives.
CWE
CWE-409 Improper Handling of Highly Compressed Data (Data Amplification)
Published
Modified
NVD analysis
Analyzed
Record from
the NVD, synced

Fix and patched versions

Ask an AI about this CVE

Show the promptExplain CVE-2026-78384 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2026-78384?via=ask-ai-copy and https://cve.bz/cve/CVE-2026-78384?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2026-78384 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.

Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.

Badge for a README or a site

CVE-2026-78384

An image that stays current: it is drawn from the data each time it is fetched (a host that proxies images, as GitHub does, may show its copy for a while). Markdown:

[![CVE-2026-78384](https://cve.bz/cve/badge/CVE-2026-78384.svg)](https://cve.bz/cve/CVE-2026-78384)

HTML:

<a href="https://cve.bz/cve/CVE-2026-78384"><img src="https://cve.bz/cve/badge/CVE-2026-78384.svg" alt="CVE-2026-78384"></a>

Affected

Versions

From the CNA's record in the CVE List.

ProductAffected
Apache Software Foundation Apache CXFfrom 4.2.0 before 4.2.4
Apache Software Foundation Apache CXFfrom 4.0.0 before 4.1.9
Apache Software Foundation Apache CXFbefore 3.6.13

Red Hat

Red Hat rates this Important.

Red Hat's statement

A denial of service flaw of important severity was found in the Apache CXF cxf-core component shipped in Red Hat middleware products, including Red Hat JBoss Fuse 7, Red Hat JBoss EAP 7.4 and 8.1, Red Hat JBoss Web Server 5, Red Hat Single Sign-On 7, and Red Hat build of Apache Camel. The CompressionUtils.inflate() method decompressed attacker-controlled DEFLATE-compressed data without any limit on the decompressed output size. A remote, unauthenticated attacker could submit a small, specially crafted compressed token, for example a JWE token using DEFLATE compression or a SAML redirect/POST binding token, that expands to a very large amount of heap memory. Because decompression happens before and independently of trust and signature validation, no authentication or user interaction is required, and the resulting heap exhaustion can crash the affected service. Red Hat scored this flaw CVSS 3.1 7.5 (AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H), reflecting an availability-only impact; the separately issued CISA score of 7.5 attributes the impact to confidentiality, which is not supported by the technical evidence for this flaw. For the affected in-support product streams, fixes are being pursued through the responsible engineering teams. The Red Hat JBoss EAP 7.4 and Red Hat JBoss Web Server 5 streams are affected but out of active support scope; for Red Hat Single Sign-On 7 no fix is planned; and the Red Hat JBoss EAP XP 6 stream is not affected because the cxf-core component is not present in it.

Red Hat's mitigation

Mitigation for this issue is either not available or the currently available options do not meet the Red Hat Product Security criteria comprising ease of use and deployment, applicability to widespread installation base, or stability.

ProductPackageStateAdvisory
Red Hat build of Apache Camel 4 for Quarkus 3cxf-coreAffected
Red Hat build of Apache Camel for Spring Boot 4cxf-coreAffected
Red Hat Fuse 7cxf-coreNot affected
Red Hat JBoss Enterprise Application Platform 7cxf-coreOut of support scope
Red Hat JBoss Enterprise Application Platform 7jboss-eap-7/eap74-els-openjdk11-openshift-rhel8Out of support scope
Red Hat JBoss Enterprise Application Platform 7jboss-eap-7/eap74-els-openjdk17-openshift-rhel8Out of support scope
Red Hat JBoss Enterprise Application Platform 7jboss-eap-7/eap74-els-openjdk8-openshift-rhel8Out of support scope
Red Hat JBoss Enterprise Application Platform 8cxf-coreAffected
Red Hat JBoss Enterprise Application Platform Expansion Packcxf-coreNot affected
Red Hat JBoss Web Server 5cxf-coreOut of support scope
Red Hat Single Sign-On 7cxf-coreWill not fix

Contains Red Hat Security Data © Red Hat, Inc., licensed under CC BY 4.0. Source: https://access.redhat.com/security/data. Modified: reformatted. Red Hat's page for CVE-2026-78384.

References

Check your stackJSON