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

> Incomplete fix allows remote code execution if untrusted users can configure JMS in Apache CXF.

- **Severity:** High 7.5 (`CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 22 May 2026
- **Updated:** 15 Jul 2026
- **Also known as:** GHSA-2hvc-5c6v-f533

## What is CVE-2026-44417?

CVE-2026-44417 is a high-severity code injection vulnerability in Apache Cxf, published on 22 May 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official 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.

Weakness: CWE-15 (External Control of System or Configuration Setting), CWE-20 (Improper Input Validation)

## Which versions are affected by CVE-2026-44417?

6 open source packages ship an affected version, including org.apache.cxf:cxf-rt-transports-jms. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `org.apache.cxf:cxf-rt-transports-jms` | Maven | All versions | 3.6.11 |
| `org.apache.cxf:cxf-rt-transports-jms` | Maven | All versions | 3.6.11 |
| `org.apache.cxf:cxf-rt-transports-jms` | Maven | From 4.1.0 | 4.1.6 |
| `org.apache.cxf:cxf-rt-transports-jms` | Maven | From 4.1.0 | 4.1.6 |
| `org.apache.cxf:cxf-rt-transports-jms` | Maven | From 4.2.0 | 4.2.1 |
| `org.apache.cxf:cxf-rt-transports-jms` | Maven | From 4.2.0 | 4.2.1 |

Products: Apache Cxf.

## How do I fix CVE-2026-44417?

Upgrade org.apache.cxf:cxf-rt-transports-jms to a fixed version for your release line: 3.6.11, 4.1.6 or 4.2.1.

## Is CVE-2026-44417 being exploited?

There is no known exploitation of CVE-2026-44417 in the wild and no public exploit code.

## Other vulnerabilities in Apache Cxf

- [CVE-2012-2379](https://insights.sbomify.com/CVE-2012-2379/): XML Signature/Encryption Not Validated in Apache CXF (critical 10.0)
- [CVE-2026-66909](https://insights.sbomify.com/CVE-2026-66909/): Apache CXF: Unsafe deserialization of inbound JMS ObjectMessage (critical 9.8)
- [CVE-2026-68079](https://insights.sbomify.com/CVE-2026-68079/): Apache CXF: DefaultEncryptingCodeDataProvider allows unlimited authorization code replay (critical 9.8)
- [CVE-2026-50628](https://insights.sbomify.com/CVE-2026-50628/): Apache CXF: OAuth2: Inverted IP Binding Check Defeats Security Control (critical 9.8)
- [CVE-2025-48913](https://insights.sbomify.com/CVE-2025-48913/): Apache CXF: Untrusted JMS configuration can lead to RCE (critical 9.8)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-44417 and fix it if it is affected.

What it is: CVE-2026-44417 is a high-severity code injection vulnerability in Apache Cxf, published on 22 May 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-44417 in the wild and no public exploit code.

Affected packages and fixed versions:
- org.apache.cxf:cxf-rt-transports-jms (Maven): affected all versions; fixed in 3.6.11
- org.apache.cxf:cxf-rt-transports-jms (Maven): affected all versions; fixed in 3.6.11
- org.apache.cxf:cxf-rt-transports-jms (Maven): affected from 4.1.0; fixed in 4.1.6
- org.apache.cxf:cxf-rt-transports-jms (Maven): affected from 4.1.0; fixed in 4.1.6
- org.apache.cxf:cxf-rt-transports-jms (Maven): affected from 4.2.0; fixed in 4.2.1
- org.apache.cxf:cxf-rt-transports-jms (Maven): affected from 4.2.0; fixed in 4.2.1

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-44417/ (Markdown: https://insights.sbomify.com/CVE-2026-44417/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-44417
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-44417
- OSV: https://osv.dev/vulnerability/CVE-2026-44417

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-44417/
Summaries are generated and may contain mistakes; the official description above is the record.