How severe is CVE-2009-0217?

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

Which packages are affected by CVE-2009-0217?

CVE-2009-0217 affects the following packages: org.apache.santuario:xmlsec (Maven). Ecosystems affected: Maven.

How do I fix CVE-2009-0217?

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

How do I detect CVE-2009-0217 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-2009-0217 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-2009-0217?

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

Is CVE-2009-0217 actively exploited in the wild?

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

CVE-2009-0217 has an EPSS (Exploit Prediction Scoring System) score of 6.4%, 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.

When was CVE-2009-0217 published, and has it been updated?

CVE-2009-0217 was published on July 14, 2009 and was last updated on April 10, 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-2009-0217 — xmlsec

CVE-2009-0217 is a security vulnerability in org.apache.santuario:xmlsec. A fix is available for org.apache.santuario:xmlsec — see the affected versions and patch details below.

Apache XML Security For Java vulnerable to authentication bypass by HMAC truncation

Also known asGHSA-8hfm-837h-hjg5

Published

Jul 14, 2009

Updated

Apr 10, 2026

Affected

1 pkg

Patched

1 / 1

Exploits

None indexed

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

EPSS Exploitation Probability

via FIRST.org ↗

6.4%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

1 pkg affected

☕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

The design of the W3C XML Signature Syntax and Processing (XMLDsig) recommendation, as implemented in multiple products.

The Apache XML Security (Java) is affected by the vulnerability published in US-Cert VU #466161. See: http://www.kb.cert.org/vuls/id/466161 for more information. This bug can allow an attacker to bypass authentication by inserting/modifying a small HMAC truncation length parameter in the XML Signature HMAC based SignatureMethod algorithms.

An inexhaustive list of additional affected products includes:

the Oracle Security Developer Tools component in Oracle Application Server 10.1.2.3, 10.1.3.4, and 10.1.4.3IM;
the WebLogic Server component in BEA Product Suite 10.3, 10.0 MP1, 9.2 MP3, 9.1, 9.0, and 8.1 SP6;
Mono before 2.4.2.2;
XML Security Library before 1.2.12;
IBM WebSphere Application Server Versions 6.0 through 6.0.2.33, 6.1 through 6.1.0.23, and 7.0 through 7.0.0.1;
Sun JDK and JRE Update 14 and earlier;
Microsoft .NET Framework 3.0 through 3.0 SP2, 3.5, and 4.0; and other products uses a parameter that defines an HMAC truncation length (HMACOutputLength) but does not require a minimum for this length, which allows attackers to spoof HMAC-based signatures and bypass authentication by specifying a truncation length with a small number of bits.

Affected Packages

1 total 1 fixed

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

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.3 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2009-0217 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-2009-0217 can be triaged on real exposure rather than presence alone.

Tailored to CVE-2009-0217. 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
Extras for RHEL 4	`java-1.6.0-sun-1:1.6.0.15-1jpp.1.el4`	RHSA-2009:1200
Extras for RHEL 4	`java-1.6.0-ibm-1:1.6.0.7-1jpp.3.el4`	RHSA-2009:1694
JBEAP 4.2.0 for RHEL 4	`glassfish-javamail-0:1.4.2-0jpp.ep1.5.el4`	RHSA-2009:1637
JBEAP 4.2.0 for RHEL 5	`glassfish-jsf-0:1.2_13-2.1.ep1.el5`	RHSA-2009:1650
Red Hat Enterprise Linux 4	`xmlsec1-0:1.2.6-3.1`	RHSA-2009:1428
Red Hat Enterprise Linux 5	`java-1.6.0-openjdk-1:1.6.0.0-1.2.b09.el5`	RHSA-2009:1201
Red Hat JBoss Enterprise Application Platform 4.3 for RHEL 4	`glassfish-javamail-0:1.4.2-0jpp.ep1.5.el4`	RHSA-2009:1636
Red Hat JBoss Enterprise Application Platform 4.3 for RHEL 5	`glassfish-jaxb-0:2.1.4-1.12.patch03.1.ep1.el5`	RHSA-2009:1649

Ubuntu

USN-826-1Ubuntu USN-903-1Ubuntu USN-814-1Ubuntu

Frequently Asked Questions

The design of the W3C XML Signature Syntax and Processing (XMLDsig) recommendation, as implemented in multiple products. The Apache XML Security (Java) is affected by the vulnerability published in US-Cert VU #466161. See: http://www.kb.cert.org/vuls/id/466161 for more information. This bug can allow an attacker to bypass authentication by inserting/modifying a small HMAC truncation length parameter in the XML Signature HMAC based SignatureMethod algorithms. An inexhaustive list of additional affected products includes: 1. the Oracle Security Developer Tools component in Oracle Application

O3 Security · Impact-Aware SCA

Is CVE-2009-0217 in your dependencies?

O3 Security finds CVE-2009-0217 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