CVE-2023-33695 is a high-severity (CVSS 7.1) CWE-732 vulnerability in cn.hutool:hutool-core. 1 public exploit or proof-of-concept reference is indexed, so weaponization risk is real. A fix is available for cn.hutool:hutool-core — see the affected versions and patch details below.
Insecure Temporary File in HuTool
Exploitation Status
No confirmed exploitation observed yet
- A successful exploit gives an attacker total control of the affected component, not partial access.
- 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-2023-33695.
EPSS Exploitation Probability
Probability of exploitation in the next 30 days, from FIRST.org EPSS.
How urgent is this, really
Where this sits among everything scored
Real-World Exposure
cn.hutool:hutool-coreReal-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
Hutool v5.8.17 and below was discovered to contain an information disclosure vulnerability via the File.createTempFile() function at /core/io/FileUtil.java.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| ☕Maven | cn.hutool:hutool-core | all versions | 5.8.19cn.hutool:hutool-core:5.8.19 |
Affected Products
hutoolhutoolResearch use only. For defensive security, authorized penetration testing, and academic research only. Never execute exploit code against systems without explicit written authorization.
Detection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for cn.hutool:hutool-core, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update cn.hutool:hutool-core to 5.8.19 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2023-33695 is resolved across your whole dependency graph.
Workarounds
Assume what was exposed is already known: rotate any credential, token or key that the affected component could return, restrict the endpoint to callers that genuinely need it, and strip sensitive fields from responses and error output at the boundary rather than relying on the client not to read them.
Frequently Asked Questions
Is CVE-2023-33695 in your dependencies?
Find it across Maven, including transitive dependencies.