Is org.apache.santuario:xmlsec 3.0 vulnerable?
Maven · 7 releases from 3.0.0 to 3.0.6 · latest org.apache.santuario:xmlsec is 4.0.4 · checked 18 Nov 2026
No known advisories in the last release
org.apache.santuario:xmlsec 3.0.6, the last 3.0 release, has no known advisories. 1 advisory affects earlier 3.0.x releases, so update to 3.0.6.
mvn versions:use-dep-version -Dincludes=org.apache.santuario:xmlsec -DdepVersion=3.0.6 -DforceVersion=trueIs your project on an affected org.apache.santuario:xmlsec?
Look after several Java apps? Indie watches up to 15 repos, private ones too, for $5 a month. See Indie
Fixed within 3.0.x, affecting earlier releases
Apache Santuario - XML Security for Java are vulnerable to private key disclosure
- Affected
- >=2.3.0 <2.3.4 · <2.2.6 · >=3.0.0 <3.0.3
- Fixed in
- 2.2.6, 2.3.4, 3.0.3
Every org.apache.santuario:xmlsec 3.0.x release
Affected: 3.0.0 to 3.0.2. 3.0.3 and later are not affected. Latest org.apache.santuario:xmlsec: 4.0.4.
| Version | Known advisories |
|---|---|
| org.apache.santuario:xmlsec 3.0.6 | None |
| org.apache.santuario:xmlsec 3.0.5 | None |
| org.apache.santuario:xmlsec 3.0.4 | None |
| org.apache.santuario:xmlsec 3.0.3 | None |
| org.apache.santuario:xmlsec 3.0.2 | CVE-2023-44483 |
| org.apache.santuario:xmlsec 3.0.1 | CVE-2023-44483 |
| org.apache.santuario:xmlsec 3.0.0 | CVE-2023-44483 |
Which of your client projects are still on org.apache.santuario:xmlsec 3.0?
NPMscan reads the lockfiles in every GitHub repo you pick, finds the exact org.apache.santuario:xmlsec version each one installs, and checks it against these advisories. Each finding comes with the command that fixes it.
Other org.apache.santuario:xmlsec versions
Advisory data from OSV.dev (opens OSV.dev in a new tab), which includes the GitHub Advisory Database. Release list from the Maven registry. Refreshed daily.