How severe is CVE-2019-12400?

CVE-2019-12400 has a CVSS score of 5.5/10, rated MEDIUM. Review your exposure and patch according to your risk tolerance.

Which packages are affected by CVE-2019-12400?

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

How do I fix CVE-2019-12400?

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

How do I detect CVE-2019-12400 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-2019-12400 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-2019-12400 actively exploited in the wild?

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

CVE-2019-12400 has an EPSS (Exploit Prediction Scoring System) score of 0.8%, placing it in the 56th 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-2019-12400?

CVE-2019-12400 is classified as Improper Input Validation (CWE-20). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation.

When was CVE-2019-12400 published, and has it been updated?

CVE-2019-12400 was published on August 23, 2019 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.

CVE-2019-12400: xmlsec — Fixed in 2.1.4

EPSS Exploitation Probability

via FIRST.org ↗

0.8%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs56th percentile — riskier than 56% of all scored CVEsHighest risk

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

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

In version 2.0.3 Apache Santuario XML Security for Java, a caching mechanism was introduced to speed up creating new XML documents using a static pool of DocumentBuilders. However, if some untrusted code can register a malicious implementation with the thread context class loader first, then this implementation might be cached and re-used by Apache Santuario - XML Security for Java, leading to potential security flaws when validating signed documents, etc. The vulnerability affects Apache Santuario - XML Security for Java 2.0.x releases from 2.0.3 and all 2.1.x releases before 2.1.4.

Affected Packages

1 total 1 fixed

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

Affected Products

3 products · 5 configurations

Application

santuario xml security for javaapache

≥ 2.1.0 && ≤ 2.0.10

range

Application

weblogic serveroracle

2 versions

12.2.1.4.014.1.1.0.0

Application

jboss enterprise application platformredhat

1 version

7.2

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 2.1.4 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2019-12400 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 Fuse 7.7.0	`camel-xmlsecurity`	RHSA-2020:3192
Red Hat JBoss EAP 7.2	`xmlsec`	RHSA-2020:0811
Red Hat JBoss Enterprise Application Platform 7.2 for RHEL 6	`eap7-activemq-artemis-0:2.9.0-2.redhat_00009.1.el6eap`	RHSA-2020:0804
Red Hat JBoss Enterprise Application Platform 7.2 for RHEL 7	`eap7-activemq-artemis-0:2.9.0-2.redhat_00009.1.el7eap`	RHSA-2020:0805
Red Hat JBoss Enterprise Application Platform 7.2 for RHEL 8	`eap7-activemq-artemis-0:2.9.0-2.redhat_00009.1.el8eap`	RHSA-2020:0806
Red Hat Single Sign-On 7.3	`xmlsec`	RHSA-2020:0951
Text-Only RHOAR	see advisory	RHSA-2020:2067

Frequently Asked Questions

In version 2.0.3 Apache Santuario XML Security for Java, a caching mechanism was introduced to speed up creating new XML documents using a static pool of DocumentBuilders. However, if some untrusted code can register a malicious implementation with the thread context class loader first, then this implementation might be cached and re-used by Apache Santuario - XML Security for Java, leading to potential security flaws when validating signed documents, etc. The vulnerability affects Apache Santuario - XML Security for Java 2.0.x releases from 2.0.3 and all 2.1.x releases before 2.1.4.

O3 Security · Impact-Aware SCA

Is CVE-2019-12400 in your dependencies?

Find it across Maven, including transitive dependencies.

Scan my dependencies How O3 SCA works

CVE-2019-12400 — xmlsec

EPSS Exploitation Probability

How urgent is this, really

Where this sits among everything scored

Real-World Exposure

Description

Affected Packages

Affected Products

Detection & mitigation playbook

Detect

Fix

Workarounds

Fixing This On Your OS

Frequently Asked Questions

Is CVE-2019-12400 in your dependencies?