Your RSA-2048 keys break in 2030. Find every one of them before attackers do.
☕
☕ Maven
Not in CISA KEV
HIGH severity

CVE-2026-44417 — cxf-rt-transports-jms

HIGH

CVE-2026-44417 is a high-severity (CVSS 7.5) Improper Input Validation vulnerability in org.apache.cxf:cxf-rt-transports-jms. A fix is available for org.apache.cxf:cxf-rt-transports-jms — see the affected versions and patch details below.

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

Also known asGHSA-2hvc-5c6v-f533
Published
Updated
Affected
3 pkgs
Patched
3 / 3
Exploits
None indexed
Exploitation data as of Oct 7, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

Exploitation Status

No confirmed exploitation observed yet

  • A successful exploit gives an attacker total control of the affected component, not partial access.
  • CISA’s own triage has not observed active exploitation or public proof-of-concept code for this CVE as of its last assessment.

Exploitation and automatability from CISA’s SSVC triage for CVE-2026-44417.

EPSS Exploitation Probability

via FIRST.org ↗
0.9%probability of exploitation in next 30 days
Lower Risk0.00%
Lower risk than most CVEs59th percentile — riskier than 59% of all scored CVEsHighest risk
0.00%0.47%0.94%1.40%0.2%0.9%Jun 26Sep 26Oct 26

Probability of exploitation in the next 30 days, from FIRST.org EPSS.

How urgent is this, really

CVE-2026-44417 by exploitation likelihood (EPSS) against impact (CVSS). Outside the shaded patch-first corner.

Where this sits among everything scored

Of 384,534 CVEs with a current EPSS score, this one falls in the < 10% band (highlighted). Counts from FIRST.org, log-scaled.

Real-World Exposure

3 pkgs affected
☕org.apache.cxf:cxf-rt-transports-jms☕org.apache.cxf:cxf-rt-transports-jms☕org.apache.cxf:cxf-rt-transports-jms

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects Maven packages — download data is not available via public APIs for these ecosystems.

Description

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.

Affected Packages

3 total 3 fixed
EcosystemPackageVulnerable rangeFix
☕Mavenorg.apache.cxf:cxf-rt-transports-jms≥ 4.2.0&&< 4.2.14.2.1org.apache.cxf:cxf-rt-transports-jms:4.2.1
☕Mavenorg.apache.cxf:cxf-rt-transports-jms≥ 4.1.0&&< 4.1.64.1.6org.apache.cxf:cxf-rt-transports-jms:4.1.6
☕Mavenorg.apache.cxf:cxf-rt-transports-jmsall versions3.6.11org.apache.cxf:cxf-rt-transports-jms:3.6.11

Affected Products

1 product · 3 configurations
Application
cxfapache
≥ 4.0.0 && < 4.1.6
1 version
4.2.0

Detection & mitigation playbook

Open-source dependency
  1. Detect

    Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for org.apache.cxf:cxf-rt-transports-jms, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

  2. Fix

    Update org.apache.cxf:cxf-rt-transports-jms to 4.2.1 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2026-44417 is resolved across your whole dependency graph.

  3. Workarounds

    If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

Fixing This On Your OS

If you run this on a Linux distribution, patch through your package manager against the distro's own security advisory below — it tracks the exact backported fix for your release, which can ship on a different timeline (and sometimes a different severity) than the upstream project.

Red HatImportant

This is an Important flaw in Apache CXF where an incomplete fix for a prior vulnerability allows remote code execution. Exploitation requires that untrusted users have permissions to configure Java Message Service (JMS) within the Apache CXF environment, which is not a default configuration in Red Hat products.…

Workaround published by Red Hat
To mitigate this issue, ensure that only trusted users have permissions to configure Java Message Service (JMS) for Apache CXF. Restrict access to configuration files and management interfaces that control JMS settings. If JMS functionality is not required, consider disabling it to remove the attack vector.
Source: Red Hat security advisory for CVE-2026-44417 (CC BY 4.0)
ProductFixed inAdvisory
Red Hat build of Apache Camel 4.18.1.P1 for Spring Boot 3.5.16cxf-rt-transports-jmsRHSA-2026:37390
Red Hat JBoss Enterprise Application Platform 8.1 for RHEL 10eap8-activemq-artemis-0:2.40.0-8.redhat_00024.1.el10eapRHSA-2026:70230
Red Hat JBoss Enterprise Application Platform 8.1 for RHEL 8eap8-activemq-artemis-0:2.40.0-8.redhat_00024.1.el8eapRHSA-2026:70228
Red Hat JBoss Enterprise Application Platform 8.1 for RHEL 9eap8-activemq-artemis-0:2.40.0-8.redhat_00024.1.el9eapRHSA-2026:70229

Frequently Asked Questions

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.
O3 Security · Impact-Aware SCA

Is CVE-2026-44417 in your dependencies?

Find it across Maven, including transitive dependencies.

CVE-2026-44417: cxf-rt-transports-jms RCE — Fixed in 4.2.1