CVE-2022-46363 — cxf-core
HIGHCVE-2022-46363 is a high-severity (CVSS 7.5) Improper Input Validation vulnerability in org.apache.cxf:cxf-core. A fix is available for org.apache.cxf:cxf-core — see the affected versions and patch details below.
Apache CXF directory listing / code exfiltration
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.
- 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-2022-46363.
EPSS Exploitation Probability
EPSS (Exploit Prediction Scoring System) is a daily probability model maintained by FIRST.org. It estimates the likelihood a CVE will be exploited in production environments within the next 30 days, derived from real-world threat intelligence signals.
How urgent is this, really
CVE-2022-46363 plotted by exploitation likelihood (EPSS) against impact (CVSS). The shaded corner — EPSS 50%+ and CVSS 7.0+ — is where this CVE doesn't sit, though severity or exploitability alone can still warrant action.
Where this sits among everything scored
Of 378,567 CVEs with a current EPSS score, this one falls in the < 10% band (highlighted). Real counts from FIRST.org, not a sample — log-scaled since the landscape is heavily right-skewed.
Real-World Exposure
org.apache.cxf:cxf-core☕org.apache.cxf:cxf-coreReal-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
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.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| ☕Maven | org.apache.cxf:cxf-core | all versions | 3.4.10org.apache.cxf:cxf-core:3.4.10 |
| ☕Maven | org.apache.cxf:cxf-core | ≥ 3.5.0&&< 3.5.5 | 3.5.5org.apache.cxf:cxf-core:3.5.5 |
Detection & 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-core, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update org.apache.cxf:cxf-core to 3.4.10 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2022-46363 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.
How O3 protects you
O3 Security's impact-aware SCA analyses which vulnerable code paths your application actually calls, so a match like CVE-2022-46363 can be triaged on real exposure rather than presence alone.
Tailored to CVE-2022-46363. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.
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.
| Product | Fixed in | Advisory |
|---|---|---|
| Red Hat Fuse 7.11.1.P1 | cxf | RHSA-2023:0483 |
| Red Hat Fuse 7.12 | see advisory | RHSA-2023:3954 |
| Red Hat JBoss Enterprise Application Platform 7.1 EUS for RHEL 7 | eap7-apache-cxf-0:3.1.16-4.redhat_00003.1.ep7.el7 | RHSA-2025:1746 |
| Red Hat JBoss Enterprise Application Platform 7.3 EUS for RHEL 7 | eap7-hal-console-0:3.2.17-1.Final_redhat_00001.1.el7eap | RHSA-2025:1747 |
| Red Hat JBoss Enterprise Application Platform 7.4.9 | org.apache.cxf/cxf-core:3.4.10.redhat-00001 | RHSA-2023:0556 |
| Red Hat Single Sign-On 7 | cxf | RHSA-2023:1049 |
| Red Hat Single Sign-On 7.6 for RHEL 7 | rh-sso7-keycloak-0:18.0.6-1.redhat_00001.1.el7sso | RHSA-2023:1043 |
| Red Hat Single Sign-On 7.6 for RHEL 8 | rh-sso7-keycloak-0:18.0.6-1.redhat_00001.1.el8sso | RHSA-2023:1044 |
Frequently Asked Questions
Is CVE-2022-46363 in your dependencies?
O3 Security finds CVE-2022-46363 across Maven dependencies, including transitive ones, and its impact-aware SCA ranks findings by whether your code actually calls the vulnerable path.