Is org.apache.santuario:xmlsec 1.5 vulnerable?

Maven · 9 releases from 1.5.0 to 1.5.8 · latest org.apache.santuario:xmlsec is 4.0.4 · checked 18 Nov 2026

Yes: 2 known advisories

Yes. org.apache.santuario:xmlsec 1.5.8, the last 1.5 release, is affected by 2 known security advisories (1 high, 1 medium), including CVE-2021-40690, CVE-2023-44483. 3 more affect earlier 1.5.x releases. Upgrade to 2.2.6 or later to fix all of them.

Upgrade with:mvn versions:use-dep-version -Dincludes=org.apache.santuario:xmlsec -DdepVersion=2.2.6 -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

Advisories affecting org.apache.santuario:xmlsec 1.5.8

  • 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
  • HighCVE-2021-40690GHSA-j8wc-gxx9-82hx20 Sept 2021

    Exposure of Sensitive Information to an Unauthorized Actor in Apache Santuario

    Affected
    >=2.2.0 <2.2.3 · <2.1.7
    Fixed in
    2.1.7, 2.2.3

Fixed within 1.5.x, affecting earlier releases

  • MediumCVE-2013-5823GHSA-8gwc-x7mg-7p7p14 May 2022

    Apache XML Security For Java vulnerable to Infinite Loop

    Affected
    >=1.4.0 <1.4.8 · >=1.5.0 <1.5.3
    Fixed in
    1.4.8, 1.5.3
  • MediumCVE-2013-2172GHSA-r237-w2w6-jq3p13 May 2022

    Inefficient Algorithmic Complexity in Apache Santuario XML Security

    Affected
    >=1.4.0 <1.4.8 · >=1.5.0 <1.5.5
    Fixed in
    1.4.8, 1.5.5
  • MediumCVE-2013-4517GHSA-4p4w-6h54-g88513 May 2022

    Improper Input Validation in Apache Santuario XML Security

    Affected
    <1.5.6
    Fixed in
    1.5.6

Every org.apache.santuario:xmlsec 1.5.x release

Affected: 1.5.0 to 1.5.8. Latest org.apache.santuario:xmlsec: 4.0.4.

VersionKnown advisories
org.apache.santuario:xmlsec 1.5.8CVE-2023-44483, CVE-2021-40690
org.apache.santuario:xmlsec 1.5.7CVE-2023-44483, CVE-2021-40690
org.apache.santuario:xmlsec 1.5.6CVE-2023-44483, CVE-2021-40690
org.apache.santuario:xmlsec 1.5.5CVE-2023-44483, CVE-2013-4517, CVE-2021-40690
org.apache.santuario:xmlsec 1.5.4CVE-2023-44483, CVE-2013-2172, CVE-2013-4517, CVE-2021-40690
org.apache.santuario:xmlsec 1.5.3CVE-2023-44483, CVE-2013-2172, CVE-2013-4517, CVE-2021-40690
org.apache.santuario:xmlsec 1.5.2CVE-2023-44483, CVE-2013-5823, CVE-2013-2172, CVE-2013-4517, CVE-2021-40690
org.apache.santuario:xmlsec 1.5.1CVE-2023-44483, CVE-2013-5823, CVE-2013-2172, CVE-2013-4517, CVE-2021-40690
org.apache.santuario:xmlsec 1.5.0CVE-2023-44483, CVE-2013-5823, CVE-2013-2172, CVE-2013-4517, CVE-2021-40690

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

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.