# Apache CXF is vulnerable to DoS attacks as entire files are read into memory and logged

Advisory record · `GHSA-36wv-v2qp-v4g4`

- **Identifiers:** `GHSA-36wv-v2qp-v4g4` · `CVE-2025-48795`
- **State:** Confirmed
- **Severity:** CVSS 5.6 Medium
- **Critical:** No
- **Weakness (CWE):** [CWE-400](https://cwe.mitre.org/data/definitions/400.html)
- **Tags:** [Denial of service](https://agentprime.io/advisories/tag/dos.md)
- **Published:** 15 Jul 2025
- **Updated:** 10 Sept 2026
- **Reviewed by a person:** No

Published by the GitHub Advisory Database at 15 Jul 2025, 15:31 UTC. agentprime has not analysed this yet, so whether it affects any app is not known.

## Affected packages

- `org.apache.cxf:cxf-core` (Maven): affected `<3.5.11 || >=3.6.0, <3.6.6 || >=4.0.0, <4.0.7 || >=4.1.0, <4.1.1`; fixed in `3.5.11`, `3.6.6`, `4.0.7`, `4.1.1`

## Machine-written summary

Summary written by Claude Haiku from the source advisory. Not reviewed by a person.

> Apache CXF cxf-core versions before 3.5.11, from 3.6.0 before 3.6.6, from 4.0.0 before 4.0.7, and from 4.1.0 before 4.1.1 are affected. A bug causes the entire temporary file for large stream-based messages to be read into memory and logged, which an attacker may be able to trigger to cause a denial of service through an out-of-memory condition, and it can also write cached files that are meant to be encrypted into logs unencrypted. Users should upgrade to cxf-core 3.5.11, 3.6.6, 4.0.7, or 4.1.1.

Written 2 Nov 2026.

## Not analysed yet

We haven’t published our analysis of this Advisory yet. Once a person has reviewed it, this page will say what’s vulnerable, what has to be true for your app to be affected, and how to check.

## Severity and exploitation

- 5.6 Medium, CVSS 3.1: `CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:L/A:L`, from GitHub Advisory Database

- **CISA KEV:** Not listed.
- **EPSS:** 0.0073, the 54th percentile, on 13 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.

## Timeline

- 31 Oct 2026, 14:17 UTC: First seen by agentprime
- 31 Oct 2026, 14:17 UTC: [Confirmed by OSV](https://osv.dev/vulnerability/GHSA-36wv-v2qp-v4g4)

## Sources

- [GitHub Advisory Database: GHSA-36wv-v2qp-v4g4](https://github.com/advisories/GHSA-36wv-v2qp-v4g4)
- [OSV: GHSA-36wv-v2qp-v4g4](https://osv.dev/vulnerability/GHSA-36wv-v2qp-v4g4)
- <https://nvd.nist.gov/vuln/detail/CVE-2025-48795>
- <https://github.com/apache/cxf/pull/2258>
- <https://github.com/apache/cxf/commit/1c1d687f8e295f433a3592a3bc0b0a63c432bfde>
- <https://github.com/apache/cxf>
- <https://lists.apache.org/thread/vo5qv02mvv5plmb6z2xf1ktjmrpv3jmn>
- <http://www.openwall.com/lists/oss-security/2025/07/15/3>

Facts on this page come from the GitHub Advisory Database (CC-BY 4.0), OSV and the other sources listed, as published. We don’t reproduce full advisory descriptions, which can contain exploit code.

## Check whether this affects you

A Match means an installed version is in the affected range above. Most don’t affect the app; agentprime hasn’t analysed this one yet.

- With the agentprime MCP server (<https://api.agentprime.io/mcp>), ask your agent to check the project: `check_lockfile` sends a lockfile, `check_packages` a list of installed packages, and both return the Matches and the upgrades that clear them. `get_advisory` returns this record. Setup: <https://agentprime.io/mcp.md>
- In a browser: <https://agentprime.io/check/> reads your lockfile in the browser, never uploading it.
- Whether it touches your code, with file and line: the Claude Code plugin, <https://agentprime.io/plugin.md>
- As JSON: <https://api.agentprime.io/v1/advisories/GHSA-36wv-v2qp-v4g4>, or `POST https://api.agentprime.io/v1/match` with your packages (<https://agentprime.io/api.md>)

---

The web page: <https://agentprime.io/advisories/GHSA-36wv-v2qp-v4g4/>. Everything for agents: <https://agentprime.io/llms.txt>.