CVE-2025-48795

Apache CXF stores large stream based messages as temporary files on the local filesystem. A bug was introduced which means that the entire temporary file is read into memory and then logged. An attacker might be able to exploit this to cause a denial of service attack by causing an out of memory exception. In addition, it is possible to configure CXF to encrypt temporary files to prevent sensitive credentials from being cached unencrypted on the local filesystem, however this bug means that the cached files are written out to logs unencrypted.

Users are recommended to upgrade to versions 3.5.11, 3.6.6, 4.0.7 or 4.1.1, which fixes this issue.

Crafted input forces the application to consume excessive CPU, memory, or other resources, degrading or denying service. Typical impact: denial of service.

CVE-2025-48795 has a CVSS score of 5.6 (Medium). The vector is network-reachable, no privileges required, and no user interaction. A CVSS score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether this affects your application depends on whether the vulnerable code is present and reachable in your environment. A fixed version is available (3.5.11, 3.6.6, 4.1.1, 4.0.7); upgrading removes the vulnerable code path.

Kodem intelligence

1. What is CVE-2025-48795? CVE-2025-48795 is a medium-severity uncontrolled resource consumption vulnerability in org.apache.cxf:cxf-core (maven), affecting versions < 3.5.11. It is fixed in 3.5.11, 3.6.6, 4.1.1, 4.0.7. Crafted input forces the application to consume excessive CPU, memory, or other resources, degrading or denying service.
2. How severe is CVE-2025-48795? CVE-2025-48795 has a CVSS score of 5.6 (Medium). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.
3. Which versions of org.apache.cxf:cxf-core are affected by CVE-2025-48795? org.apache.cxf:cxf-core (maven) versions < 3.5.11 is affected.
4. Is there a fix for CVE-2025-48795? Yes. CVE-2025-48795 is fixed in 3.5.11, 3.6.6, 4.1.1, 4.0.7. Upgrade to this version or later.
5. Is CVE-2025-48795 exploitable, and should I be worried? Whether CVE-2025-48795 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
6. What actually determines whether CVE-2025-48795 is exploitable, and how bad it is? Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
7. How do I fix CVE-2025-48795?
   • Upgrade org.apache.cxf:cxf-core to 3.5.11 or later
   • Upgrade org.apache.cxf:cxf-core to 3.6.6 or later
   • Upgrade org.apache.cxf:cxf-core to 4.1.1 or later
   • Upgrade org.apache.cxf:cxf-core to 4.0.7 or later