Authenticated arbitrary file write via traversal filename
Published May 12, 2026 · Updated May 12, 2026
Path traversal in Heym before 0.0.21 allows remote authenticated users to write files outside the upload storage directory. The upload_file handler passes the multipart filename to store_file, which joins it into a filesystem path without rejecting path components or checking resolved-path containment. Any signed-in user can supply traversal segments to write attacker-controlled bytes as the backend process user; reads and deletion depend on subsequent access to the planted path.
Summary
What happened
Path traversal in Heym before 0.0.21 allows remote authenticated users to write files outside the upload storage directory. The upload_file handler passes the multipart filename to store_file, which joins it into a filesystem path without rejecting path components or checking resolved-path containment. Any signed-in user can supply traversal segments to write attacker-controlled bytes as the backend process user; reads and deletion depend on subsequent access to the planted path.
The record
- CVE
- CVE-2026-45225
- Published
- May 12, 2026
- Updated
- May 12, 2026
- Vendor
- Heym
- Product
- Heym
- Classifications
- CWE-22, T1190
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- May 12, 2026CVE publishedPublication date reported by the CVE source.
- May 12, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=0 <0.0.21
What conditions does exploitation require?
What is affected?
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
- Upstream file-upload traversal reproductionproof of concept · demonstrated
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo