Is org.apache.santuario:xmlsec 2.3 vulnerable?

Maven · 6 releases from 2.3.0 to 2.3.5 · latest org.apache.santuario:xmlsec is 4.0.4 · checked 18 Nov 2026

No known advisories in the last release

org.apache.santuario:xmlsec 2.3.5, the last 2.3 release, has no known advisories. 1 advisory affects earlier 2.3.x releases, so update to 2.3.5.

Update within 2.3:mvn versions:use-dep-version -Dincludes=org.apache.santuario:xmlsec -DdepVersion=2.3.5 -DforceVersion=true

Is your project on an affected org.apache.santuario:xmlsec?

Private repo? Upload its lockfile instead, or connect GitHub to check every repo.

Look after several Java apps? Indie watches up to 15 repos, private ones too, for $5 a month. See Indie

Fixed within 2.3.x, affecting earlier releases

  • MediumCVE-2023-44483GHSA-xfrj-6vvc-3xm220 Oct 2023

    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 2.3.x release

Affected: 2.3.0 to 2.3.3. 2.3.4 and later are not affected. Latest org.apache.santuario:xmlsec: 4.0.4.

VersionKnown advisories
org.apache.santuario:xmlsec 2.3.5None
org.apache.santuario:xmlsec 2.3.4None
org.apache.santuario:xmlsec 2.3.3CVE-2023-44483
org.apache.santuario:xmlsec 2.3.2CVE-2023-44483
org.apache.santuario:xmlsec 2.3.1CVE-2023-44483
org.apache.santuario:xmlsec 2.3.0CVE-2023-44483

Which of your client projects are still on org.apache.santuario:xmlsec 2.3?

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.