NVD / CVE Program· CNA apache

CVE-2025-48795: Apache CXF: Denial of Service and sensitive data exposure in logs

Noroxi assessment

Priority: Monitor (action score 22/100)

The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
Probability of exploitation in the next 30 days: 0.73% (FIRST EPSS); higher than 54.1% of all records.
Anyone who can reach it over the internet can trigger it. No account or password is required. No user action is required. Special conditions such as timing or configuration are required.
Fixed version: Apache Software Foundation Apache CXF 3.5.11, 3.6.6, 4.0.7.

Low priority for now. Upgrade to Apache Software Foundation Apache CXF 3.5.11, 3.6.6, 4.0.7 or later.

Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it

Primary sources: NVD · CVE.org · FIRST EPSS

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.

MediumCVSS 5.6 · v3.1—No exploit Fix available

Published: Jul 15, 2025
Updated: Jun 17, 2026
EPSS: 0.7% · 54th percentile
CWE: CWE-400

Report tools

JSON

Action score

Monitor

Low priority for now.

CVSS: 22 / 40 · 5.6 / 10
CISA KEV: 0 / 30 · Not listed
EPSS: 0 / 30 · 0.7%

CISA SSVC decision

Exploitation: none
Automatable: no
Technical impact: partial

Vulnrichment: CISA's decision-tree inputs.

Get told when this record changes

Not in KEV: no record of exploitation in the wild
No public exploit code on record
A fix has been released

If any of these changes, we'll tell you in the daily email digest.

Running WordPress? Scan your site free with WP Lens

Is your version affected? Check it

Noroxi analysis

What does it mean in your environment?

The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.

We use this product, ask for help

Affected systems

Is your version affected?

Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.

Vendor	Product	CPE
apache	cxf	cpe:2.3:a:apache:cxf

Affected versions

NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.

apache cxf3.5.10
apache cxf3.6.5
apache cxf4.0.6
apache cxf4.1.0

Versions reported by the vendor

Affected version ranges reported by the assigning authority (apache). Independent of NVD's CPE analysis and usually ahead of it.

Apache Software Foundation Apache CXF
- 3.5.10 and later · before 3.5.11affected · semver
- 3.6.5 and later · before 3.6.6affected · semver
- 4.0.6 and later · before 4.0.7affected · semver
- 4.1.0 and later · before 4.1.1affected · semver

Package-level exposure

OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.

Ecosystem	Package	Affected range	Fix
Maven	org.apache.cxf:cxf-core	from 3.6.0 · before 3.6.6	3.6.6
Maven	org.apache.cxf:cxf-core	from 4.0.0 · before 4.0.7	4.0.7
Maven	org.apache.cxf:cxf-core	from 4.1.0 · before 4.1.1	4.1.1
Maven	org.apache.cxf:cxf-core	before 3.5.11	3.5.11

Same product

apache: all records

Other highest-scoring records for the same primary product.

CVE-2019-12419Apache CXF before 3.3.4 and 3.2.11 provides all of the components that are required to build a fully fledged OpenId Connect service.
43Plan
CVE-2010-2076Apache CXF 2.0.x before 2.0.13, 2.1.x before 2.1.10, and 2.2.x before 2.2.9, as used in Apache ServiceMix, Apache Camel, Apache Chemistry, A
42Plan
CVE-2012-2379Apache CXF 2.4.x before 2.4.8, 2.5.x before 2.5.4, and 2.6.x before 2.6.1, when a Supporting Token specifies a child WS-SecurityPolicy 1.1 o
41Plan

Published before and after this one in the same product

← EarlierCVE-2024-41172Jul 19, 2024 · Apache CXF: Unrestricted memory consumption in CXF HTTP clients
30Monitor
← EarlierCVE-2025-23184Jan 21, 2025 · Apache CXF: Denial of Service vulnerability with temporary files
31Monitor
Later →CVE-2025-48913Aug 8, 2025 · Apache CXF: Untrusted JMS configuration can lead to RCE
39Monitor

Remediation

Which version to upgrade to

Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.

Product / package	Fixed version	Source
Apache Software Foundation Apache CXF	3.5.11	Vendor (CNA)
Apache Software Foundation Apache CXF	3.6.6	Vendor (CNA)
Apache Software Foundation Apache CXF	4.0.7	Vendor (CNA)
Apache Software Foundation Apache CXF	4.1.1	Vendor (CNA)
Maven:org.apache.cxf:cxf-core	3.5.11	Package registry (OSV)
Maven:org.apache.cxf:cxf-core	3.6.6	Package registry (OSV)
Maven:org.apache.cxf:cxf-core	4.0.7	Package registry (OSV)
Maven:org.apache.cxf:cxf-core	4.1.1	Package registry (OSV)

Exploit status

No known public exploit

No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.

Research context

For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.

Timeline

From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.

No dated events beyond publication.

EPSS, last 120 days

FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).

Patch and commit links

Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.

No commit or PR link among the references.

Credits

All researchers

Finders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.

MAUGIN Thomas https://github.com/Thom-x, Qlikfinder

Variant candidates

Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.

CVE-2025-23184175 days apartApache CXF: Denial of Service vulnerability with temporary files
31Monitor
CVE-2026-50645332 days apartApache CXF: No restriction on attachment headers per message
30Monitor
CVE-2026-57819387 days apartApache CXF: No default restriction on the amount of form parameters per message
30Monitor
CVE-2026-64958387 days apartApache CXF: Denial of service via message header attachments
30Monitor
CVE-2026-86463451 days apartApache CXF: FIQL Query Parser Denial of Service
30Monitor

Chain candidates

An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.

—

Bug bounty scope

No known public program.

Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).

Technical details

Attack conditions

Anyone who can reach it over the internet can trigger it.
No account or password is required.
No user action is required.
Special conditions such as timing or configuration are required.

If successful

Confidentiality: low · data can be read
Integrity: low · data or configuration can be modified
Availability: low · the service can be disrupted

Attack vector: Network
Attack complexity: High
Privileges required: None
User interaction: None
Scope: Unchanged
Confidentiality impact: Low
Integrity impact: Low
Availability impact: Low

Weakness class (CWE)

CWE-400 · Uncontrolled Resource Consumption

CVSS vector

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

nvd-secondary

Root cause

Code that parses nested structures sets no depth or size limit. A small input can turn into a disproportionate processing load.

The bug in code

The whole CWE-400 class

A representative example of this vulnerability class. Not the vendor's source code; it shows the faulty pattern and its fix.

Vulnerable

1function expand(node) {
2  return node.children.map(expand);
3}

Fixed

1const MAX_DEPTH = 32;
2function expand(node, depth = 0) {
3  if (depth > MAX_DEPTH) throw new Error("too deep");
4  return node.children.map((c) => expand(c, depth + 1));
5}