CVE-2026-71306: Mikochi: Authenticated path traversal
Mikochi is a minimalist file manager with streaming capabilities. Prior to 1.10.1, authenticated users of bare-metal instances configured with a non-default trailing-slash DATADIR can use the Move endpoint to supply traversal-containing source or destination paths. The affected path validation can resolve those paths outside the configured data directory, allowing files to be written beyond Mikochi's intended storage boundary. Docker deployments that confine the data directory to a mounted volume and configurations whose DATADIR lacks a trailing slash are not affected by the described attack. This issue is fixed in version 1.10.1.
Affected Software
Remediation
Recommended actions to resolve this vulnerability, in priority order.
- Upgrade
Upgrade
Mikochito a version that resolves this vulnerability.Fixed in 1.10.1
Event History
Frequently Asked Questions
Which deployments are exposed to this issue?
Bare-metal Mikochi instances running a version before 1.10.1 are exposed only when DATA_DIR is configured with a trailing slash. Docker deployments that confine the data directory to a mounted volume, and configurations where DATA_DIR has no trailing slash, are not affected by the described attack.
What access does an attacker need?
The attacker must be authenticated to Mikochi and able to use the Move endpoint. Exploitation requires supplying source or destination paths containing traversal sequences.
What is the impact of successful exploitation?
Traversal-containing paths can be resolved outside Mikochi's configured data directory, allowing the attacker to write files beyond the intended storage boundary.
What can be done before upgrading?
Ensure DATA_DIR does not have a trailing slash, or use a Docker deployment that confines the data directory to a mounted volume. Upgrade to version 1.10.1 to apply the fix.