# CVE-2025-48795: Apache CXF: Denial of Service and sensitive data exposure in logs > An attacker can cause a denial of service via memory exhaustion and expose sensitive data in logs due to improper handling of temporary files in Apache CXF. - **Severity:** Medium 5.6 (`CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:L/A:L`) - **Exploited in the wild:** Not known - **Login needed:** Not needed - **Attackable:** Over the internet - **Victim action needed:** Not needed - **Fix available:** Yes - **Published:** 15 Jul 2025 - **Updated:** 4 Nov 2025 - **Also known as:** CLSA-2026-1768262918, GHSA-36wv-v2qp-v4g4, MINI-2mmg-72mg-4g8h, MINI-2q9r-crq8-pqpq ## What is CVE-2025-48795? CVE-2025-48795 is a medium-severity denial of service vulnerability in Apache Cxf, published on 15 Jul 2025. An attacker can exploit it over the internet without logging in, with no action from the victim. ### Official description 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. Weakness: CWE-400 (Uncontrolled Resource Consumption) ## Which versions are affected by CVE-2025-48795? 8 open source packages ship an affected version, including org.apache.cxf:cxf-core. It affects 1 product. | Package | Ecosystem | Affected | Fixed in | | --- | --- | --- | --- | | `org.apache.cxf:cxf-core` | Maven | All versions | 3.5.11 | | `org.apache.cxf:cxf-core` | Maven | All versions | 3.5.11 | | `org.apache.cxf:cxf-core` | Maven | From 3.6.0 | 3.6.6 | | `org.apache.cxf:cxf-core` | Maven | From 3.6.0 | 3.6.6 | | `org.apache.cxf:cxf-core` | Maven | From 4.0.0 | 4.0.7 | | `org.apache.cxf:cxf-core` | Maven | From 4.0.0 | 4.0.7 | | `org.apache.cxf:cxf-core` | Maven | From 4.1.0 | 4.1.1 | | `org.apache.cxf:cxf-core` | Maven | From 4.1.0 | 4.1.1 | Products: Apache Cxf. ## How do I fix CVE-2025-48795? Upgrade org.apache.cxf:cxf-core to a fixed version for your release line: 3.5.11, 3.6.6, 4.0.7 or 4.1.1. ## Is CVE-2025-48795 being exploited? There is no known exploitation of CVE-2025-48795 in the wild and no public exploit code. ## Other vulnerabilities in Apache Cxf - [CVE-2012-2379](https://insights.sbomify.com/CVE-2012-2379/): XML Signature/Encryption Not Validated in Apache CXF (critical 10.0) - [CVE-2026-66909](https://insights.sbomify.com/CVE-2026-66909/): Apache CXF: Unsafe deserialization of inbound JMS ObjectMessage (critical 9.8) - [CVE-2026-68079](https://insights.sbomify.com/CVE-2026-68079/): Apache CXF: DefaultEncryptingCodeDataProvider allows unlimited authorization code replay (critical 9.8) - [CVE-2026-50628](https://insights.sbomify.com/CVE-2026-50628/): Apache CXF: OAuth2: Inverted IP Binding Check Defeats Security Control (critical 9.8) - [CVE-2025-48913](https://insights.sbomify.com/CVE-2025-48913/): Apache CXF: Untrusted JMS configuration can lead to RCE (critical 9.8) ## Fix prompt for AI coding agents ```text Check this codebase for CVE-2025-48795 and fix it if it is affected. What it is: CVE-2025-48795 is a medium-severity denial of service vulnerability in Apache Cxf, published on 15 Jul 2025. An attacker can exploit it over the internet without logging in, with no action from the victim. Exploitation: There is no known exploitation of CVE-2025-48795 in the wild and no public exploit code. Affected packages and fixed versions: - org.apache.cxf:cxf-core (Maven): affected all versions; fixed in 3.5.11 - org.apache.cxf:cxf-core (Maven): affected all versions; fixed in 3.5.11 - org.apache.cxf:cxf-core (Maven): affected from 3.6.0; fixed in 3.6.6 - org.apache.cxf:cxf-core (Maven): affected from 3.6.0; fixed in 3.6.6 - org.apache.cxf:cxf-core (Maven): affected from 4.0.0; fixed in 4.0.7 - org.apache.cxf:cxf-core (Maven): affected from 4.0.0; fixed in 4.0.7 - org.apache.cxf:cxf-core (Maven): affected from 4.1.0; fixed in 4.1.1 - org.apache.cxf:cxf-core (Maven): affected from 4.1.0; fixed in 4.1.1 Task: 1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies. 2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it. 3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead. 4. Run the tests and summarise what changed and why. 5. If nothing in the project is affected, say so and change nothing. Reference: https://insights.sbomify.com/CVE-2025-48795/ (Markdown: https://insights.sbomify.com/CVE-2025-48795/index.md) ``` ## Sources - CVE record: https://www.cve.org/CVERecord?id=CVE-2025-48795 - NVD: https://nvd.nist.gov/vuln/detail/CVE-2025-48795 - OSV: https://osv.dev/vulnerability/CVE-2025-48795 --- From sbomify Insights: https://insights.sbomify.com/CVE-2025-48795/ Summaries are generated and may contain mistakes; the official description above is the record.