CVE-2025-48913 is a critical-severity (CVSS 9.8) 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: Untrusted JMS configuration can lead to RCE
Exploitation Status
No confirmed exploitation observed yet
- CISA assesses this as automatable — exploitation doesn’t require manual, per-target effort, which raises the odds of mass scanning and opportunistic attacks.
- 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-2025-48913.
EPSS Exploitation Probability
Probability of exploitation in the next 30 days, from FIRST.org EPSS.
How urgent is this, really
Where this sits among everything scored
Real-World Exposure
org.apache.cxf:cxf-rt-transports-jms☕org.apache.cxf:cxf-rt-transports-jms☕org.apache.cxf:cxf-rt-transports-jmsReal-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
If untrusted users are allowed to configure JMS for Apache CXF, previously they could use RMI or LDAP URLs, potentially leading to code execution capabilities. This interface is now restricted to reject those protocols, removing this possibility.
Users are recommended to upgrade to versions 3.6.8, 4.0.9 or 4.1.3, which fix this issue.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| ☕Maven | org.apache.cxf:cxf-rt-transports-jms | all versions | 3.6.8org.apache.cxf:cxf-rt-transports-jms:3.6.8 |
| ☕Maven | org.apache.cxf:cxf-rt-transports-jms | ≥ 4.0.0&&< 4.0.9 | 4.0.9org.apache.cxf:cxf-rt-transports-jms:4.0.9 |
| ☕Maven | org.apache.cxf:cxf-rt-transports-jms | ≥ 4.1.0&&< 4.1.3 | 4.1.3org.apache.cxf:cxf-rt-transports-jms:4.1.3 |
Affected Products
cxfapacheDetection & mitigation playbook
Open-source dependencyDetect
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.
Fix
Update org.apache.cxf:cxf-rt-transports-jms to 3.6.8 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2025-48913 is resolved across your whole dependency graph.
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.
This flaw should be considered Important because the impact goes beyond a simple denial of service or configuration misuse. By allowing untrusted users to configure JMS with RMI or LDAP URLs, attackers could achieve remote code execution by loading attacker-controlled classes or objects. Although this requires the…
To reduce risk, deployments should restrict the allowed protocols in JMS configuration to trusted and expected values only. In particular, disallow the use of rmi:// and ldap:// URLs, which could be abused for remote class loading and code execution.Source: Red Hat security advisory for CVE-2025-48913 (CC BY 4.0)
| Product | Fixed in | Advisory |
|---|---|---|
| Red Hat JBoss Enterprise Application Platform 7.1 EUS for RHEL 7 | eap7-apache-cxf-0:3.1.16-6.redhat_00006.1.ep7.el7 | RHSA-2026:6012 |
| Red Hat JBoss Enterprise Application Platform 7.3 EUS for RHEL 7 | eap7-apache-cxf-0:3.4.10-3.SP2_redhat_00003.1.el7eap | RHSA-2026:6011 |
| Red Hat JBoss Enterprise Application Platform 7.4.24 | org.apache.cxf/cxf-rt-transports-jms:3.5.11.SP1-redhat-00001 | RHSA-2026:4924 |
| Red Hat JBoss Enterprise Application Platform 7.4 ELS on RHEL 7 | eap7-apache-cxf-0:3.5.11-1.SP1_redhat_00001.1.el7eap | RHSA-2026:4915 |
| Red Hat JBoss Enterprise Application Platform 7.4 ELS on RHEL 8 | eap7-apache-cxf-0:3.5.11-1.SP1_redhat_00001.1.el8eap | RHSA-2026:4916 |
| Red Hat JBoss Enterprise Application Platform 7.4 ELS on RHEL 9 | eap7-apache-cxf-0:3.5.11-1.SP1_redhat_00001.1.el9eap | RHSA-2026:4917 |
| Red Hat JBoss Enterprise Application Platform 8.0.9 | cxf | RHSA-2025:17318 |
| Red Hat JBoss Enterprise Application Platform 8.0 for RHEL 8 | eap8-apache-cxf-0:4.0.9-5.redhat_00002.1.el8eap | RHSA-2025:17317 |
Frequently Asked Questions
Is CVE-2025-48913 in your dependencies?
Find it across Maven, including transitive dependencies.