Skip to main content
Mallory
MediumVulnerability

CVE-2026-44618: XXE in Apache CXF WS-Transfer

Published May 22, 2026 · Updated 2 months ago
Trending this weekNot trendingOutside this week’s top 100
Mention activity · 30 daysNo mention activity in the last 30 days.
CVSS5.3Medium · v3.1
EPSS0.31%25th percentile
CISA KEVNoNot listed
In the wildNoneNo exploitation reported
Vendor
Apache Software Foundation
IdentifiersCVE-2026-44618CWE-611 · Improper Restriction of XML…

CVE-2026-44618 is an XML External Entity (XXE) vulnerability in Apache CXF's WS-Transfer module (org.apache.cxf:cxf-rt-ws-transfer). The issue is caused by an insecure XML parser configuration in WS-Transfer request processing, which may allow external entity resolution when parsing attacker-controlled XML. As a result, a remote attacker can supply crafted XML to trigger XXE behavior. Reported affected versions include Apache CXF 4.2.0 before 4.2.1, 4.0.0 before 4.1.6, and versions in the 3.6.x line before 3.6.11.

Do you run this?See affected versions in your environment and whether adversaries are exploiting this vulnerability against assets like yours.
Check your exposure
Analyst brief

Impact, mitigation & remediation

What it means and what to do now: patch path, interim mitigations, and the assume-compromise checklist.

Impact

What an attacker gets, and what they’ve been doing with it.

Successful exploitation may allow unauthorized disclosure of local files accessible to the CXF process and may enable server-side request forgery-style behavior such as probing or mapping internal network resources via external entity resolution. The primary impact described in the available content is sensitive file disclosure and internal network mapping.

Mitigation

If you can’t patch tonight, do this now.

If immediate patching is not possible, reduce exposure by disabling or restricting WS-Transfer functionality where feasible, preventing untrusted parties from submitting XML to affected endpoints, and hardening XML parsing behavior to disallow external entity resolution and related external resource loading. Network egress restrictions may also reduce SSRF/internal discovery impact. The primary recommended mitigation in the provided content is timely patching.

Remediation

Patch, then assume compromise.

Upgrade Apache CXF WS-Transfer deployments to a fixed release: 4.2.1, 4.1.6, or 3.6.11, as applicable to the deployed branch. These versions are identified in the provided content as containing the fix for CVE-2026-44618.

Public exploits

Exploits

No public exploits tracked yet. Mallory keeps watching.

View more in app →
No public exploit code observed for this vulnerability. Mallory keeps watching.
Exposure surface

Affected products & vendors

Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.

VendorProductType
Apache Software FoundationCxfapplication
FAQ

Frequently asked questions

Is CVE-2026-44618 exploited in the wild?
As of Sep 25, 2026, Mallory has no reports of CVE-2026-44618 being exploited in the wild. It is not listed in CISA KEV.
Is there a public exploit for CVE-2026-44618?
As of Sep 25, 2026, Mallory has found no public exploit for CVE-2026-44618.
Is there a patch for CVE-2026-44618?
Upgrade Apache CXF WS-Transfer deployments to a fixed release: 4.2.1, 4.1.6, or 3.6.11, as applicable to the deployed branch. These versions are identified in the provided content as containing the fix for CVE-2026-44618.
What products are affected by CVE-2026-44618?
Apache Software Foundation Cxf.
How severe is CVE-2026-44618?
CVE-2026-44618 has a CVSS v3.1 score of 5.3 (Medium) and an EPSS score of 0.31% (25th percentile) as of Sep 25, 2026.
Activity feed

Recent activity

2 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.

View more in app →
Do you run this?See affected versions in your environment and whether adversaries are exploiting this vulnerability against assets like yours.
Check your exposure
Mallory platform

The version that knows your environment.

This page is what’s public. Mallory adds the parts that aren’t: which of your assets are affected, which adversaries are exploiting it right now, and which detections to deploy tonight.
Exposure mappingQuery your assets running an affected version, and investigate the blast radius.
Threat actor evidenceEvery report linking this CVE to a named adversary.
Associated malwareMalware families linked to this CVE, with evidence and IOCs.
Detection signaturesYARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Vendor-by-vendor mappingCross-references every affected SKU, including bundled OEM variants.
Social activity1Community discussion across Reddit, Mastodon, and other social sources.