dbcve.org
CxfApplication · Apache

CVE-2026-49875

CRITICAL · 9.8 CVSS v3.1 Published 2026-06-12
Fix available
A fix is available. Upgrade to 4.1.7 / 4.2.2 or later.
See remediation →
100/100
Remediation priority · Urgent
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's EndpointReferenceUtils and W3CMultiSchemaFactory classes construct a SAXParserFactory without the necessary JAXP hardening configurations, enabling out-of-band (OOB) external entity resolution. Users are recommended to upgrade to versions 4.2.2 or 4.1.7 or 3.6.12, which fix 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's EndpointReferenceUtils and W3CMultiSchemaFactory classes instantiate SAXParserFactory without applying JAXP security hardening configurations, leaving them vulnerable to XML External Entity (XXE) injection through out-of-band (OOB) external entity resolution. This allows attackers to exploit XML parsing to access local files, perform SSRF, or denial-of-service attacks via malicious XML documents.

MitigationUpgrade Apache CXF to version 4.2.2 or 4.1.7 which contain the fix, or manually harden SAXParserFactory by disabling external DTDs and external entity resolution in existing deployments.

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:< 4.1.7>= 4.2.0, < 4.2.2

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
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

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

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 installation
    Search for CXF JAR files in your application's lib/classpath directories, or review your build configuration (pom.xml, build.gradle) for CXF dependencies
    Affected if Apache CXF is present in the application and the version is < 4.1.7 or >= 4.2.0 but < 4.2.2
  2. Determine CXF version
    Inspect the CXF JAR file name (e.g., cxf-core-4.x.x.jar) or check the version in your dependency management file
    Affected if The installed version falls within < 4.1.7 or >= 4.2.0, < 4.2.2
  3. Locate usage of vulnerable classes
    Search your codebase for imports and usage of org.apache.cxf.endpoint.EndpointReferenceUtils and org.apache.cxf.wsdl11.WSDLManagerFactory$W3CMultiSchemaFactory
    Affected if Code directly instantiates or calls these classes to process XML input
  4. Identify XML parsing paths
    Review code that uses the vulnerable classes to process XML from untrusted sources (REST/SOAP endpoints, file uploads, external APIs)
    Affected if The vulnerable CXF classes process XML originating from external or untrusted sources without additional validation
  5. Verify JAXP security configuration
    Inspect code that creates SAXParserFactory instances and check if it explicitly disables external entities via setFeature for http://xml.org/sax/features/external-general-entities and http://xml.org/sax/features/external-parameter-entities, or sets system properties javax.xml.parsers.SAXParserFactory and/or access restrictions via ACCESS_EXTERNAL_DTD and ACCESS_EXTERNAL_SCHEMA
    Affected if SAXParserFactory instances used by CXF lack XXE protection features and accept default parser settings

You are affected if Apache CXF version is below 4.1.7 or between 4.2.0 and 4.2.2 (exclusive) AND your application uses EndpointReferenceUtils or W3CMultiSchemaFactory to parse untrusted XML without explicit XXE protection configured on the SAXParserFactory.

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
Upgrade available Upgrade to 4.1.7 / 4.2.2 or later
Fixed in 4.1.74.2.2
Interim mitigation

Upgrade Apache CXF to version 4.2.2 or 4.1.7 which contain the fix, or manually harden SAXParserFactory by disabling external DTDs and external entity resolution in existing deployments.

Recommended fix High confidence

CXF 4.1.7 (for 4.1.x line) or CXF 4.2.2 (for 4.2.x line)

  1. 1. Identify the current Apache CXF version in use by checking project dependencies (e.g., pom.xml for Maven, build.gradle for Gradle, or JAR manifest files)
  2. 2. If using a 4.1.x version: upgrade to CXF 4.1.7 by updating the dependency version
  3. 3. If using a 4.2.0 or 4.2.1 version: upgrade to CXF 4.2.2 by updating the dependency version
  4. 4. For Maven projects, update the version in pom.xml: <artifactId>cxf-core</artifactId><version>4.1.7</version> or <version>4.2.2</version>
  5. 5. Rebuild and redeploy the application
  6. 6. Verify the fix by confirming the CXF version loaded matches the patched release
Caveat Minor/patch upgrades typically have low risk, but review release notes for any deprecation notices or behavioral changes

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

Fix this in Cxf Scoped from the published advisory
  • Consultation4.0 h
  • Implementation2.0 h
  • Testing8.0 h
  • Review / QA3.0 h
17.0 hours of engineering $2,900
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-49875 — 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-2026-49875 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