How severe is CVE-2015-5253?

No CVSS score has been assigned to CVE-2015-5253 yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by CVE-2015-5253?

CVE-2015-5253 affects the following packages: org.apache.cxf:cxf-rt-rs-security-sso-saml (Maven), org.apache.cxf:cxf-rt-rs-security-sso-saml (Maven), org.apache.cxf:cxf-rt-rs-security-sso-saml (Maven). Ecosystems affected: Maven.

How do I fix CVE-2015-5253?

Update org.apache.cxf:cxf-rt-rs-security-sso-saml to 2.7.18 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2015-5253 is resolved across your whole dependency graph.

How do I detect CVE-2015-5253 in my Maven dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for org.apache.cxf:cxf-rt-rs-security-sso-saml, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

How do I mitigate CVE-2015-5253 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-2015-5253 actively exploited in the wild?

No public exploit code has been indexed for CVE-2015-5253 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-2015-5253?

CVE-2015-5253 has an EPSS (Exploit Prediction Scoring System) score of 5.7%, placing it in the 93th 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-2015-5253?

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

When was CVE-2015-5253 published, and has it been updated?

CVE-2015-5253 was published on May 13, 2022 and was last updated on November 28, 2024. 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

CVE-2015-5253 — cxf-rt-rs-security-sso-sa…

Fix: apache/cxf@02245c6

CVE-2015-5253 is a CWE-264 vulnerability in org.apache.cxf:cxf-rt-rs-security-sso-saml. A fix is available for org.apache.cxf:cxf-rt-rs-security-sso-saml — see the affected versions and patch details below.

Improper Access Control in Apache CXF

Published

May 13, 2022

Updated

Nov 28, 2024

Affected

3 pkgs

Patched

3 / 3

Exploits

None indexed

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

EPSS Exploitation Probability

via FIRST.org ↗

5.7%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs93th percentile — riskier than 93% of all scored CVEsHighest risk

Probability of exploitation in the next 30 days, from FIRST.org EPSS.

Real-World Exposure

3 pkgs affected

☕org.apache.cxf:cxf-rt-rs-security-sso-saml☕org.apache.cxf:cxf-rt-rs-security-sso-saml☕org.apache.cxf:cxf-rt-rs-security-sso-saml

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

The SAML Web SSO module in Apache CXF before 2.7.18, 3.0.x before 3.0.7, and 3.1.x before 3.1.3 allows remote authenticated users to bypass authentication via a crafted SAML response with a valid signed assertion, related to a "wrapping attack."

Affected Packages

3 total 3 fixed

Ecosystem	Package	Vulnerable range	Fix
☕Maven	`org.apache.cxf:cxf-rt-rs-security-sso-saml`	all versions	2.7.18`org.apache.cxf:cxf-rt-rs-security-sso-saml:2.7.18`
☕Maven	`org.apache.cxf:cxf-rt-rs-security-sso-saml`	≥ 3.0.0&&< 3.0.7	3.0.7`org.apache.cxf:cxf-rt-rs-security-sso-saml:3.0.7`
☕Maven	`org.apache.cxf:cxf-rt-rs-security-sso-saml`	≥ 3.1.0&&< 3.1.3	3.1.3`org.apache.cxf:cxf-rt-rs-security-sso-saml:3.1.3`

Affected Products

1 product · 3 configurations

Application

cxfapache

≥ 3.1.0 && < 3.1.3

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-rt-rs-security-sso-saml, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update org.apache.cxf:cxf-rt-rs-security-sso-saml to 2.7.18 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2015-5253 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

RHSA-2016:0321Red Hat JBoss Fuse 6.2

Frequently Asked Questions

O3 Security · Impact-Aware SCA

Is CVE-2015-5253 in your dependencies?

Find it across Maven, including transitive dependencies.

Scan my dependencies How O3 SCA works