VulertSecurity VulertSecurity

Vulnerability Database · Debian · Package report

libxml-security-java: vulnerability history, versions and safety

libxml-security-java is a package in the Debian ecosystem. Vulert records 9 vulnerabilities for it across 6 releases, from Aug 2013 to Oct 2023. Each vulnerability names the versions it affects, the fixed version to move to, and a workaround where no fix has been published.

i
9 vulnerabilities recorded U9
i
3 with no fix published

No patched version yet — these are the ones to plan around.

See the unfixed vulnerabilities →
i
0 in the last 12 months

Nothing new recorded in the last year.

See the disclosure history →
i
0 malicious-package vulnerabilities

No published version shipped hostile code.

See all libxml-security-java vulnerabilities

Vulert verdict on libxml-security-java i

Updated on 23 Oct 2026

Careful: 3 of the 9 vulnerabilities Vulert records for this package have no fix yet. Plan around those, or apply the workaround listed for each. The rest have a fixed version to move to.

Long-term outlook: usable, but needs attention 9 vulnerabilities on record across 10 years, none in the last year.

What to do: Plan around the 3 vulnerabilities with no published fix: each lists the affected range and any workaround that reduces exposure. No fix yet: Vulert alerts you the moment one is published. Monitor it with Vulert →

  • Vulnerabilities on record 9 over 10 years · 0 in the last year i
  • Latest disclosure 20 Oct 2023 i
  • Highest CVSS 7.5 i
  • With no published fix 3 i

Concerned about your application's security?

Vulert continues monitoring your dependencies and alerts you when new vulnerabilities are disclosed. No installation and no source-code access required.

01 Versions

Which versions are affected

Every version Vulert holds for libxml-security-java, newest first, with the vulnerabilities that name it. A version with a count of zero has no recorded vulnerabilities; open a version to see the vulnerabilities it is exposed to.

i
Version Vulert vulnerabilities Fix published Details
2.1.8-1 U3 No Details →
2.1.7-3 U3 No Details →
2.1.7-2 U3 No Details →
2.1.7-1 U3 No Details →
2.0.10-2 U5 No Details →
2.0.10-2+deb11u1 U3 No Details →

Newest 6 of 6 versions on record. Severity counts are the vulnerabilities recorded against that exact release.

02 Disclosure history

How often vulnerabilities are recorded

  • 2013 2
  • 2014 2
  • 2019 1
  • 2021 2
  • 2023 2

Counted by the year Vulert recorded each vulnerability — the same date the table below shows as disclosed. 0 of the 9 were recorded in the last 12 months.

03 Vulnerabilities

Recorded vulnerabilities for libxml-security-java

The 5 most severe of 9 vulnerabilities recorded for this package

Search all 9 in the database →
Vulnerability Severity Fixed version ↑ Disclosed ↑
Apache Santuario XML Security for Java Vulnerability in libxml-security-java: KeyInfoReference Misconfiguration 7.5 high 2.0.10-2+deb11u1 19 Sep 2021
Sensitive Key Disclosure in Apache Santuario - XML Security for Java (CVE-2023-44483) 6.5 medium No fix published 20 Oct 2023
Apache Santuario XML Security for Java Vulnerability - Potential Cache Poisoning Risk 5.5 medium No fix published 23 Aug 2019
XML Signature Spoofing Vulnerability in libxml-security-java N/A unrated 1.5.5-2 20 Aug 2013
Denial of Service Vulnerability in libxml-security-java: Apache Santuario XML Security for Java N/A unrated 1.5.6-1 11 Jan 2014

Vulnerability wrong, a fix missing, or a package we should cover? Report it and we will fix the record. Report Vulnerability Provide Feedback

Updated: 23/Oct/2026 · Vulnerabilities in our DB: 524315

Subscribe to Vulert on Telegram
Daily digest of new CVEs, critical and high severity, affected packages and fixes — plus a weekly roundup.
Join the channel →

Questions

About libxml-security-java

Is libxml-security-java safe to use?

Vulert records 9 vulnerabilities for libxml-security-java in Debian: 0 critical, 0 high, 0 medium and 0 low, plus 9 not yet rated. 3 of them have no published fix yet, so those are the ones to avoid or mitigate.

How many vulnerabilities does libxml-security-java have?

9 vulnerabilities are recorded for libxml-security-java in the Debian ecosystem: 0 critical, 0 high, 0 medium and 0 low, plus 9 not yet rated. The ledger on this page lists the same counts next to the date of the most recent disclosure.

How often are new libxml-security-java vulnerabilities disclosed?

0 vulnerabilities were recorded for libxml-security-java in the last 12 months, and the oldest entry in this database dates to 20 Aug 2013. Recency matters more than a lifetime total: it shows how actively new issues are being disclosed for the package you are considering.

Which versions of libxml-security-java are affected?

Each vulnerability on this page lists the affected version range and the fixed version to move to. Open the vulnerability for the version you actually run — fixes are specific to a release line, not to the package as a whole.

How do I monitor libxml-security-java for upcoming vulnerabilities?

Upload the manifest or SBOM for your application at vulert.com/scanner and Vulert keeps checking the libxml-security-java version you actually run against new disclosures, then alerts you when one affects it. There is no installation and no source-code access required.