# CVE-2022-46363: Apache CXF directory listing / code exfiltration

> Attackers can perform remote directory listing or code exfiltration in Apache CXF if specific servlet attributes are misconfigured together.

- **Severity:** High 7.5 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 13 Dec 2022
- **Updated:** 22 Apr 2025
- **Also known as:** GHSA-3w37-5p3p-jv92

## What is CVE-2022-46363?

CVE-2022-46363 is a high-severity path traversal vulnerability in Apache Cxf, published on 13 Dec 2022. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

A vulnerability in Apache CXF before versions 3.5.5 and 3.4.10 allows an attacker to perform a remote directory listing or code exfiltration. The vulnerability only applies when the CXFServlet is configured with both the static-resources-list and redirect-query-check attributes. These attributes are not supposed to be used together, and so the vulnerability can only arise if the CXF service is misconfigured.

Weakness: CWE-20 (Improper Input Validation)

## Which versions are affected by CVE-2022-46363?

4 open source packages ship an affected version, including org.apache.cxf:cxf-core. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `org.apache.cxf:cxf-core` | Maven | All versions | 3.4.10 |
| `org.apache.cxf:cxf-core` | Maven | All versions | 3.4.10 |
| `org.apache.cxf:cxf-core` | Maven | From 3.5.0 | 3.5.5 |
| `org.apache.cxf:cxf-core` | Maven | From 3.5.0 | 3.5.5 |

Products: Apache Cxf.

## How do I fix CVE-2022-46363?

Upgrade org.apache.cxf:cxf-core to a fixed version for your release line: 3.4.10 or 3.5.5.

## Is CVE-2022-46363 being exploited?

There is no known exploitation of CVE-2022-46363 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-2022-46363 and fix it if it is affected.

What it is: CVE-2022-46363 is a high-severity path traversal vulnerability in Apache Cxf, published on 13 Dec 2022. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2022-46363 in the wild and no public exploit code.

Affected packages and fixed versions:
- org.apache.cxf:cxf-core (Maven): affected all versions; fixed in 3.4.10
- org.apache.cxf:cxf-core (Maven): affected all versions; fixed in 3.4.10
- org.apache.cxf:cxf-core (Maven): affected from 3.5.0; fixed in 3.5.5
- org.apache.cxf:cxf-core (Maven): affected from 3.5.0; fixed in 3.5.5

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-2022-46363/ (Markdown: https://insights.sbomify.com/CVE-2022-46363/index.md)
```

## Sources

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

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