LiveActive security incident?Get immediate response
CVE Record

CVE-2026-44417: Apache CXF: Incomplete fix for CVE-2025-48913 (Untrusted JMS configuration can lead to RCE)

The fix for CVE-2025-48913: Apache CXF: Untrusted JMS configuration can lead to RCE was not complete, meaning that another path in the code might lead to code execution capabilities, if untrusted users are allowed to configure JMS for Apache CXF. Users are recommended to upgrade to versions 4.2.1, 4.1.6 or 3.6.11, which fix this issue.

HighCVSS 7.5Not KEV-listedUpdated
Discuss exposureBack to CVEs
Glexia's TakeAutomated analysishigh

Security readout for executives and security teams

Plain-English summary

Apache CXF has an incomplete prior fix where untrusted JMS configuration may still lead to code execution. The business risk is highest for applications that let non-administrators or tenants influence JMS settings. Apache recommends upgrading to fixed CXF versions.

Executive priority

Treat as high priority where Apache CXF JMS configuration can be influenced by untrusted users. For environments without CXF JMS or without delegated configuration, urgency is lower but inventory and upgrade planning are still warranted.

Technical view

CVE-2026-44417 is an incomplete fix for CVE-2025-48913 in Apache CXF JMS transport. If untrusted users can configure JMS for CXF, another code path may allow code execution. CVSS 3.1 is 7.5 with network access, low privileges, high complexity, and high confidentiality, integrity, and availability impact.

Likely exposure

Exposure is likely limited to Apache CXF deployments using JMS transport, especially org.apache.cxf:cxf-rt-transports-jms, where JMS configuration is user-controlled or tenant-controlled. Systems without CXF JMS usage, or where only trusted administrators control JMS configuration, appear less exposed based on the provided sources.

Exploitation context

The source bundle does not cite active exploitation, and KEV is false. Exploitation requires low privileges and no user interaction, but has high attack complexity and depends on untrusted JMS configuration being permitted.

Researcher notes

The key condition is not simply CXF presence; it is CXF JMS configuration exposed to untrusted users. The provided affected-version data is sparse, but fixed versions are explicit. Avoid assuming exploitability without confirming JMS transport usage and configuration control boundaries.

Mitigation direction

  • Upgrade Apache CXF to 4.2.1, 4.1.6, or 3.6.11.
  • Inventory uses of org.apache.cxf:cxf-rt-transports-jms across applications.
  • Remove untrusted user control over JMS configuration.
  • Review Apache and Red Hat advisories for distribution-specific guidance.
  • Prioritize externally reachable or tenant-configurable CXF services first.

Validation and detection

  • Check SBOMs and dependency manifests for Apache CXF JMS transport.
  • Confirm deployed CXF versions are 4.2.1, 4.1.6, 3.6.11, or later fixed releases.
  • Review application roles that can create or modify JMS configuration.
  • Verify no public or tenant workflow can supply JMS settings.
  • Track Red Hat errata applicability for packaged deployments.
Prepared
Confidence
high
Sources
7

Public sources used

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cwe · low confidence lookup

CWE-15: Exact CWE lookup

Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.

Open ATT&CK lookup
cwe · low confidence lookup

CWE-20: Exact CWE lookup

Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.

Open ATT&CK lookup
description · low confidence lookup

Execution behavior lookup

The CVE wording references code or command execution, so execution technique review may help defensive triage. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.

Open ATT&CK lookup
cve · low confidence lookup

CVE-2026-44417 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
High
CVSS
7.5 (3.1)
Known Exploited
No
Published

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

Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

2CVSS vectors
5Timeline events
2ADP providers
6Source links

SSVC decision data

CISA-ADPCISA Coordinator
Timestamp
Version
2.0.3
Exploitation: noneAutomatable: noTechnical Impact: total

CVSS vector scores

2 official scores

We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.

ScoreVersionSeverityVectorExploitImpactSource
7.5CVSS 3.1HighCVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H1.65.9CISA-ADP
7.5CVSS 3.1HighCVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H1.65.9redhat-SADP

Vulnerability scoring details

Base CVSS 3.1 score

7.5High
CVSS 3.1 vector shape for CVE-2026-44417Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

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

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Privileges Required
NoneLowHigh
User Interaction
NoneRequired
Scope
ChangedUnchanged
Confidentiality Impact
HighLowNone
Integrity Impact
HighLowNone
Availability Impact
HighLowNone

Vulnerability timeline

Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.

  1. CVE reservedCVE Program

    The CVE ID was reserved by the assigning CNA.

  2. ADP timelineredhat-SADP

    Made public.

  3. CVE publishedCVE Program

    The CVE record was published.

  4. ADP timelineredhat-SADP

    Reported to Red Hat.

  5. CVE updatedCVE Program

    The CVE record metadata indicates this as the latest update time.

ADP provider summaries

CISA-ADPCISA ADP Vulnrichment
cvssV3_1other:ssvc
redhat-SADPorg.apache.cxf/cxf-rt-transports-jms: Apache CXF: Remote Code Execution via untrusted JMS configuration
other:Red Hat severity ratingcvssV3_1
  • 2026-05-22T13:00:55.251Z: Reported to Red Hat.
  • 2026-05-22T12:17:25.102Z: Made public.

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
Apache Software FoundationApache CXForg.apache.cxf:cxf-rt-transports-jms, 4.2.0, 4.0.0, 0unaffected
Weakness

CWE details

CWE-15CWE-20

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.