Vulnerability Database · Debian · libxml-security-java · Version
libxml-security-java 2.1.8-1
2.1.8-1 is affected by 3 vulnerabilities.
The vulnerabilities that cover this exact version are listed below with the fixed version to move to.
Critical 0 High 0 Medium 2 Low 0 Unrated 1
-
Database updated 23/Oct/2026
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 Vulnerabilities affecting this version
libxml-security-java 2.1.8-1 vulnerabilities
3 vulnerabilities cover libxml-security-java 2.1.8-1. Open the full list in the database.
| Vulnerability | Severity | Fixed version | Disclosed |
|---|---|---|---|
| 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 |
| Sensitive Key Disclosure in libxml-security-java Due to Debug Logging | N/A unrated | No fix published | 20 Oct 2023 |
Looking for another version, or everything Vulert holds for libxml-security-java?
Questions
About libxml-security-java 2.1.8-1
Is libxml-security-java 2.1.8-1 vulnerable?
Yes. 3 vulnerabilities in the Vulert database cover libxml-security-java 2.1.8-1: 0 critical, 0 high, 2 medium and 0 low, plus 1 not yet rated. Each entry above names the fixed version to move to.
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.