CVE-2025-59952 — minio
Fix: minio/minio-java@f7a98d0CVE-2025-59952 is a Improper Input Validation vulnerability in io.minio:minio. A fix is available for io.minio:minio — see the affected versions and patch details below.
minio-java Client XML Tag is Vulnerable to Value Substitution
Exploitation Status
No confirmed exploitation observed yet
- CISA assesses this as automatable — exploitation doesn’t require manual, per-target effort, which raises the odds of mass scanning and opportunistic attacks.
- CISA’s own triage has not observed active exploitation or public proof-of-concept code for this CVE as of its last assessment.
Exploitation and automatability from CISA’s SSVC triage for CVE-2025-59952.
EPSS Exploitation Probability
EPSS (Exploit Prediction Scoring System) is a daily probability model maintained by FIRST.org. It estimates the likelihood a CVE will be exploited in production environments within the next 30 days, derived from real-world threat intelligence signals.
Real-World Exposure
io.minio:minioReal-time download stats are indexed for npm and PyPI packages. This vulnerability affects Maven packages — download data is not available via public APIs for these ecosystems.
Description
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.
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.
Patches
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.
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.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| ☕Maven | io.minio:minio | all versions | 8.6.0io.minio:minio:8.6.0 |
Detection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for io.minio:minio, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update io.minio:minio to 8.6.0 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2025-59952 is resolved across your whole dependency graph.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.
How O3 protects you
O3 Security's impact-aware SCA analyses which vulnerable code paths your application actually calls, so a match like CVE-2025-59952 can be triaged on real exposure rather than presence alone.
Tailored to CVE-2025-59952. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.
Fixing This On Your OS
If you run this on a Linux distribution, patch through your package manager against the distro's own security advisory below — it tracks the exact backported fix for your release, which can ship on a different timeline (and sometimes a different severity) than the upstream project.
| Product | Fixed in | Advisory |
|---|---|---|
| Red Hat build of Apache Camel 4.10.7 for Spring Boot 3.4.10 | io.minio/minio | RHSA-2025:18028 |
| Red Hat Build of Apache Camel 4.14 for Quarkus 3.27 | io.minio/minio | RHSA-2025:19095 |
Frequently Asked Questions
Is CVE-2025-59952 in your dependencies?
O3 Security finds CVE-2025-59952 across Maven dependencies, including transitive ones, and its impact-aware SCA ranks findings by whether your code actually calls the vulnerable path.