Connect your agent
AdvisoriesCriticalCheck your lockfilePluginHow it worksPricing Connect your agent

Advisory record · GHSA-36wv-v2qp-v4g4

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

CVSS 5.6 MediumEPSS 0.0073 · 54th percentile

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.

PackageEcosystemAffectedFixed in
org.apache.cxf:cxf-coreMaven<3.5.11 || >=3.6.0, <3.6.6 || >=4.0.0, <4.0.7 || >=4.1.0, <4.1.13.5.11, 3.6.6, 4.0.7, 4.1.1
Identifiers
GHSA-36wv-v2qp-v4g4 · CVE-2025-48795
Weakness (CWE)
CWE-400
Tags
Published
15 Jul 2025
Updated
10 Sept 2026

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

ScoreRatingCVSSVectorSource
5.6 Medium 3.1 CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:L/A:L 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

  1. 31 Oct 2026, 14:17 UTC First seen by agentprime
  2. 31 Oct 2026, 14:17 UTC Confirmed by OSV

Sources

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.