How severe is CVE-2017-5656?

CVE-2017-5656 has a CVSS score of 7.5/10, rated HIGH. Immediate patching is strongly recommended.

Which packages are affected by CVE-2017-5656?

CVE-2017-5656 affects the following packages: org.apache.cxf:cxf-core (Maven), org.apache.cxf:cxf-core (Maven). Ecosystems affected: Maven.

How do I fix CVE-2017-5656?

Update org.apache.cxf:cxf-core to 3.1.11 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2017-5656 is resolved across your whole dependency graph.

How do I detect CVE-2017-5656 in my Maven dependencies?

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.

How do I mitigate CVE-2017-5656 if there is no patch (or I can't update yet)?

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.

Is CVE-2017-5656 actively exploited in the wild?

No public exploit code has been indexed for CVE-2017-5656 yet. This does not mean the vulnerability cannot be exploited — absence of public exploits does not imply safety. Apply the recommended fix and use O3 Security to monitor your exposure.

What is the EPSS score for CVE-2017-5656?

CVE-2017-5656 has an EPSS (Exploit Prediction Scoring System) score of 6.8%, placing it in the 94th percentile of all CVEs. EPSS is maintained by FIRST.org and estimates the probability that a vulnerability will be exploited in the wild within the next 30 days. This score indicates relatively lower exploitation probability, though the CVSS severity should still guide your patching priority.

What type of vulnerability is CVE-2017-5656?

CVE-2017-5656 is classified as CWE-384 (CWE-384). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation.

When was CVE-2017-5656 published, and has it been updated?

CVE-2017-5656 was published on April 18, 2017 and was last updated on October 24, 2026. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

☕

☕ Maven

Not in CISA KEV

HIGH severity

CVE-2017-5656 — cxf-core

HIGHFix: apache/cxf@1a4fe22

CVE-2017-5656 is a high-severity (CVSS 7.5) CWE-384 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.

Session Fixation in Apache CXF

Also known asGHSA-v936-x3j5-c76j

Published

Apr 18, 2017

Updated

Oct 24, 2026

Affected

2 pkgs

Patched

2 / 2

Exploits

None indexed

Exploitation data as of Oct 30, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

EPSS Exploitation Probability

via FIRST.org ↗

6.8%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs94th percentile — riskier than 94% of all scored CVEsHighest risk

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

2 pkgs affected

☕org.apache.cxf:cxf-core☕org.apache.cxf:cxf-core

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

Apache CXF's STSClient before 3.1.11 and 3.0.13 uses a flawed way of caching tokens that are associated with delegation tokens, which means that an attacker could craft a token which would return an identifer corresponding to a cached token for another user.

Affected Packages

2 total 2 fixed

Ecosystem	Package	Vulnerable range	Fix
☕Maven	`org.apache.cxf:cxf-core`	≥ 3.1.0&&< 3.1.11	3.1.11`org.apache.cxf:cxf-core:3.1.11`
☕Maven	`org.apache.cxf:cxf-core`	all versions	3.0.13`org.apache.cxf:cxf-core:3.0.13`

Affected Products

1 product · 2 configurations

Application

cxfapache

≥ 3.1.0 && < 3.1.11

range

Detection & mitigation playbook

Open-source dependency

Detect
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.1.11 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2017-5656 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.

Red HatModerate

Product	Fixed in	Advisory
Red Hat JBoss A-MQ 6.3	`cxf`	RHSA-2017:1832
Red Hat Openshift Application Runtimes	see advisory	RHSA-2018:1694

Frequently Asked Questions

O3 Security · Impact-Aware SCA

Is CVE-2017-5656 in your dependencies?

Find it across Maven, including transitive dependencies.

Scan my dependencies How O3 SCA works