Summary
MinIO Java Client XML Tag Value Substitution Vulnerability
Description
In minio-java versions prior to 8.6.0, XML tag values containing references to system properties or environment variables were automatically substituted with their actual values during processing. This unintended behavior could lead to the exposure of sensitive information, including credentials, file paths, or system configuration details, if such references were present in XML content from untrusted sources.
Affected Versions
- minio-java < 8.6.0
All applications utilizing affected versions of minio-java for parsing XML with potentially untrusted input are vulnerable.
Workarounds
No full workarounds exist without upgrading the library. As interim measures:
- Refrain from processing XML data from untrusted or external sources.
- Implement input sanitization or validation to detect and remove references to
system properties or environment variables in XML content.
Impact
This vulnerability poses a high risk of information disclosure. Attackers could craft malicious XML inputs to extract sensitive data from the system's properties or environment variables, potentially compromising security in applications relying on minio-java for object storage operations.
The application does not adequately validate input before processing it, allowing unexpected values to reach sensitive code paths. Typical impact: varies by context: data corruption, logic bypass, or denial of service.
Affected versions
Security releases
Kodem intelligence
Severity tells you how bad this could be in the worst case. It does not tell you whether you are exposed. Exploitability and impact are functions of runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A vulnerable package can sit in your dependency tree and never run.
Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter. Kodem's runtime-powered SCA identifies whether this CVE is reachable in your applications.
Already deployed Kodem?
See it in your environmentNew to Kodem? Get a demo →Remediation advice
The issue is resolved in minio-java version 8.6.0 and later. In these versions, automatic substitution of XML tag values with system properties or environment variables has been disabled.
Users are strongly advised to upgrade to minio-java 8.6.0 or a newer release to mitigate the vulnerability.
Frequently Asked Questions
- What is CVE-2025-59952? CVE-2025-59952 is a high-severity improper input validation vulnerability in io.minio:minio (maven), affecting versions < 8.6.0. It is fixed in 8.6.0. The application does not adequately validate input before processing it, allowing unexpected values to reach sensitive code paths.
- Which versions of io.minio:minio are affected by CVE-2025-59952? io.minio:minio (maven) versions < 8.6.0 is affected.
- Is there a fix for CVE-2025-59952? Yes. CVE-2025-59952 is fixed in 8.6.0. Upgrade to this version or later.
- Is CVE-2025-59952 exploitable, and should I be worried? Whether CVE-2025-59952 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
- What actually determines whether CVE-2025-59952 is exploitable, and how bad it is? Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
- How do I fix CVE-2025-59952? Upgrade
io.minio:minioto 8.6.0 or later.