How severe is CVE-2013-2172?

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

Which packages are affected by CVE-2013-2172?

CVE-2013-2172 affects the following packages: org.apache.santuario:xmlsec (Maven), org.apache.santuario:xmlsec (Maven). Ecosystems affected: Maven.

How do I fix CVE-2013-2172?

Update org.apache.santuario:xmlsec to 1.4.8 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2013-2172 is resolved across your whole dependency graph.

How do I detect CVE-2013-2172 in my Maven dependencies?

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

How do I mitigate CVE-2013-2172 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.

How does O3 Security protect against CVE-2013-2172?

O3 Security's impact-aware SCA analyses which vulnerable code paths your application actually calls, so a match like CVE-2013-2172 can be triaged on real exposure rather than presence alone.

Is CVE-2013-2172 actively exploited in the wild?

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

CVE-2013-2172 has an EPSS (Exploit Prediction Scoring System) score of 5.9%, 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-2013-2172?

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

When was CVE-2013-2172 published, and has it been updated?

CVE-2013-2172 was published on August 20, 2013 and was last updated on April 16, 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

CVE-2013-2172 — xmlsec

Fix: apache/santuario-java@25e0e11

CVE-2013-2172 is a CWE-310 vulnerability in org.apache.santuario:xmlsec. A fix is available for org.apache.santuario:xmlsec — see the affected versions and patch details below.

Inefficient Algorithmic Complexity in Apache Santuario XML Security

Also known asGHSA-r237-w2w6-jq3p

Published

Aug 20, 2013

Updated

Apr 16, 2026

Affected

2 pkgs

Patched

2 / 2

Exploits

None indexed

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

EPSS Exploitation Probability

via FIRST.org ↗

5.9%probability of exploitation in next 30 days

Lower Risk0.00%

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

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.

Real-World Exposure

2 pkgs affected

☕org.apache.santuario:xmlsec☕org.apache.santuario:xmlsec

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

jcp/xml/dsig/internal/dom/DOMCanonicalizationMethod.java in Apache Santuario XML Security for Java 1.4.x before 1.4.8 and 1.5.x before 1.5.5 allows context-dependent attackers to spoof an XML Signature by using the CanonicalizationMethod parameter to specify an arbitrary weak "canonicalization algorithm to apply to the SignedInfo part of the Signature."

Affected Packages

2 total 2 fixed

Ecosystem	Package	Vulnerable range	Fix
☕Maven	`org.apache.santuario:xmlsec`	≥ 1.4.0&&< 1.4.8	1.4.8`org.apache.santuario:xmlsec:1.4.8`
☕Maven	`org.apache.santuario:xmlsec`	≥ 1.5.0&&< 1.5.5	1.5.5`org.apache.santuario:xmlsec:1.5.5`

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.santuario:xmlsec, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update org.apache.santuario:xmlsec to 1.4.8 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2013-2172 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-2013-2172 can be triaged on real exposure rather than presence alone.

Tailored to CVE-2013-2172. 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.

Red HatModerate

Product	Fixed in	Advisory
Fuse ESB Enterprise 7.1.0	see advisory	RHSA-2014:1369
JBEWP 5 for RHEL 5	`xml-security-0:1.5.1-3_patch01.ep5.el5`	RHSA-2013:1219
JBoss Enterprise BRMS Platform 5.3	`xmlsec`	RHSA-2013:1375
Red Hat JBoss Enterprise Application Platform 5.2	see advisory	RHSA-2013:1218
Red Hat JBoss Enterprise Application Platform 5 for RHEL 5	`xml-security-0:1.5.1-3_patch01.ep5.el5`	RHSA-2013:1217
Red Hat JBoss Enterprise Application Platform 6.1	`xmlsec`	RHSA-2013:1209
Red Hat JBoss Enterprise Application Platform 6 for RHEL 5	`apache-commons-beanutils-0:1.8.3-12.redhat_3.2.ep6.el5`	RHSA-2013:1207
Red Hat JBoss Enterprise Application Platform 6 for RHEL 6	`apache-commons-beanutils-0:1.8.3-12.redhat_3.2.ep6.el6`	RHSA-2013:1208

Ubuntu

USN-2028-1Ubuntu

Frequently Asked Questions

O3 Security · Impact-Aware SCA

Is CVE-2013-2172 in your dependencies?

O3 Security finds CVE-2013-2172 across Maven dependencies, including transitive ones, and its impact-aware SCA ranks findings by whether your code actually calls the vulnerable path.

Scan my dependencies How O3 SCA works