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 DATA_DIR 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 DATA_DIR lacks a trailing slash are not affected by the described attack. This issue is fixed in version 1.10.1.
Severity
CVSS 3.1
5.8 medium
CVSS:3.1/AV:N/AC:H/PR:H/UI:N/S:C/C:N/I:H/A:N
EPSS
0.3% estimated probability of exploitation activity in the next 30 days; 28th percentile. Scored 2026-11-17. A forecast for this CVE across the internet, not for your own systems.
CWE
CWE-22Improper Limitation of a Pathname to a Restricted Directory (Path traversal)
Show the promptExplain CVE-2026-71306 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2026-71306?via=ask-ai-copy and https://cve.bz/cve/CVE-2026-71306?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2026-71306 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.
Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.