dbcve.org
CxfApplication · Apache

CVE-2025-48795

MEDIUM · 5.6 CVSS v3.1 Published 2025-07-15
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
65/100
Remediation priority · Elevated
Remotely reachable No privileges Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

Apache CXF stores large stream-based messages as temporary files on the local filesystem. A bug causes the entire temporary file to be loaded into memory before being logged, enabling denial of service via out-of-memory exceptions. Additionally, when CXF is configured to encrypt temporary files to protect sensitive credentials, the bug bypasses this protection by writing the files to logs in unencrypted form.

MitigationUpgrade Apache CXF to version 3.5.11, 3.6.6, 4.0.7, or 4.1.1 to resolve both the memory exhaustion and encrypted file bypass issues.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
CxfApplication
Affected:= 3.5.10= 3.6.5= 4.0.6= 4.1.0

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
High
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
Low
Integrity
Low
Availability
Low

CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:L/A:L

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify Apache CXF version
    Locate the CXF jar file (cxf-core-[version].jar) or check the pom.xml dependency version, or run: java -cp 'cxf-core-*.jar' org.apache.cxf.version 2>/dev/null || unzip -p cxf-core-*.jar META-INF/MANIFEST.MF | grep Implementation-Version
    Affected if The version is exactly 3.5.10, 3.6.5, 4.0.6, or 4.1.0
  2. Determine if stream-based messages with large payloads are processed
    Review application logs for CXF message handling or check if the application processes large request/response payloads (XML, JSON, or binary streams) through CXF endpoints
    Affected if The application processes large stream-based messages through CXF that would trigger temporary file creation
  3. Verify if CXF temporary file encryption is configured
    Check CXF configuration files (cxf.xml, beans.xml, or application properties) for settings such as org.apache.cxf.streaming.temp.file.encryption.enabled or similar encryption-related properties for temporary files
    Affected if CXF is configured to encrypt temporary files (this configuration is bypassed by the vulnerability)
  4. Check for memory-related issues in logs
    Review application logs for OutOfMemoryError exceptions or excessive memory usage coinciding with CXF message processing of large payloads
    Affected if OutOfMemoryError exceptions occur when processing large messages through CXF, indicating the entire temp file is being loaded into memory

You are affected if you run Apache CXF exactly version 3.5.10, 3.6.5, 4.0.6, or 4.1.0 AND process large stream-based messages that trigger temporary file creation.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Upgrade Apache CXF to version 3.5.11, 3.6.6, 4.0.7, or 4.1.1 to resolve both the memory exhaustion and encrypted file bypass issues.

Recommended fix High confidence

3.5.11, 3.6.6, 4.0.7, or 4.1.1 (depending on current major.minor version)

  1. 1. Identify the current Apache CXF version in use by checking project dependencies (pom.xml, build.gradle, or similar)
  2. 2. Determine the upgrade path based on current version: if using 3.5.x, upgrade to 3.5.11; if using 3.6.x, upgrade to 3.6.6; if using 4.0.x, upgrade to 4.0.7; if using 4.1.x, upgrade to 4.1.1
  3. 3. Update the dependency version in the project's build configuration file (e.g., pom.xml: change org.apache.cxf:cxf-core to version 3.5.11, 3.6.6, 4.0.7, or 4.1.1 as appropriate)
  4. 4. Rebuild and redeploy the application
  5. 5. Verify the upgrade by checking that CXF version now reports the patched version
  6. 6. Test that message processing continues to work correctly, especially with large messages that would previously trigger the out-of-memory condition
Caveat Review Apache CXF release notes for the target version to check for any breaking changes between current and target version

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Cxf Scoped from the published advisory
  • Consultation4.0 h
  • Implementation4.0 h
  • Testing8.0 h
  • Review / QA4.0 h
20.0 hours of engineering $3,440
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,504.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-48795 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2025-48795 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data