CVE-2023-44483: Apache Santuario · Sensitive Data in Logs
Affects Apache SantuarioSource CVE Database V5
Not known to be exploited · fixed in 3.0.3 : patch Apache Santuario soon.
Data as of 25 Oct 2026, 22:43 UTC
Rated High by the CNA (apache) · No CVSS score from NVD or the CNA
- EPSS
- 1.5% chance of exploitation in 30 days – higher than 74% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
- Patch
- Available – fixed in 3.0.3, 2.3.4, 2.2.6
Exploitation evidence
Disclosed: evidence found.
CVE published 20 Oct 2023
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 2026-10-25.
What to do
Upgrade org.apache.santuario/xmlsec to 3.0.3, 2.3.4 or 2.2.6.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
Mavenorg.apache.santuario/xmlsecpkg:maven/org.apache.santuario/xmlsecOther threats | Affected
| Fixed in
|
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
AI-suggested
Users should upgrade Apache Santuario to version 2.2.6, 2.3.4, or 3.0.3 or later to remediate this vulnerability. Disabling debug-level logging when generating XML Signatures can reduce the risk of sensitive information disclosure until the upgrade is applied.
Description
Apache Santuario XML Security for Java versions prior to 2.2.6, 2.3.4, and 3.0.3 contain a vulnerability where private keys may be logged when debug logging is enabled during XML Signature generation using the JSR 105 API. This can lead to sensitive information disclosure through log files. The issue is fixed in versions 2.2.6, 2.3.4, and 3.0.3.