Sign in Sign up
JA · EN · FR
SecPulse
Categories
CVE-2026-49875 critical CVSS 9.8

XXE (XML External Entity) in org.apache.cxf:cxf-core (CVE-2026-49875)

Summary

Vulnerability in org.apache.cxf:cxf-core (CVE-2026-49875). Successful exploitation can lead to full system takeover. Mitigation: upgrade to 4.1.7 or later.

Original description

The description as published by the source.

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, which fix this issue.

Source: NIST National Vulnerability Database NVD GitHub Advisory

Auto-generated summary

Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.

A vulnerability tracked as CVE-2026-49875 has been found in org.apache.cxf:cxf-core.
Successful exploitation can lead to full system takeover. CVSS score: 9.8/10.
What to do: upgrade org.apache.cxf:cxf-core to 4.1.7 or later.
If unsure, ask your IT team or search "org.apache.cxf:cxf-core CVE-2026-49875" on the vendor's site.

CVE-2026-49875 (org.apache.cxf:cxf-core) — CWE-611 / CVSS v3 9.8
Attack vector: remote (network-reachable) / unauthenticated / no user interaction
Patched: 4.1.7 — apply immediately
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.

❓ What is the problem

A vulnerability (CWE-611) exists in org.apache.cxf:cxf-core.

📍 Affected scope

Check the vendor advisory for the affected versions of org.apache.cxf:cxf-core.

🔥 Severity

Severity: Critical (CVSS 9.8/10). Successful exploitation can lead to full system takeover.

🔧 How to fix

Update to 4.1.7.

🛡️ Workaround

Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.

🔍 Detection

Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Audit SBOM/dependencies to find affected services.

Response actions

Concrete steps and command examples for SOC/SRE teams to execute in order

  1. 1
    Identify exposure identify 
    Audit SBOM/dependencies for affected components.

    資産台帳・SBOM・依存マニフェストで org.apache.cxf:cxf-core を使っているサービスとバージョンを洗い出す。

  2. 2
    Apply patch patch 
    Upgrade org.apache.cxf:cxf-core to 4.1.7

    ステージング環境で 4.1.7 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。

  3. 3
    Post-deployment verification verify 
    Confirm patched version is live in production

    パッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。

Affected packages

maven org.apache.cxf:cxf-core
[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"4.1.7"}]}]

References

We use cookies for analytics and ad measurement. This setting applies to all Game co., Ltd. sites. Details