CVE-2026-32315 motionEye: World-Readable Configuration File Exposes Admin Password Hash
Local attackers can read world-readable configuration files to obtain admin password hashes, enabling offline cracking and subsequent privilege escalation.
- Exploited in the wild
- Not known
- Login needed
- Any signed-in user
- Attackable
- Local or same network only
- Victim action needed
- Not needed
- Fix
- Available
What is CVE-2026-32315?
CVE-2026-32315 is a medium-severity vulnerability in motioneye-project motioneye, published on 24 Jun 2026. It can only be exploited from the same machine or local network, with no action from the victim.
Official description
motionEye (mEye) is an online interface for motion software, a video surveillance program with motion detection. Versions prior to 0.44.0 create the configuration file /etc/motioneye/motion.conf with 644 permissions (-rw-r--r--), making it readable by any local user on the system. This file contains sensitive data including the admin password hash, which can be leveraged by other vulnerabilities to escalate privileges. Additionally, per-camera configuration files (camera-*.conf) are also created with the same 644 permissions, potentially exposing camera-specific credentials and settings. The exposed SHA1 admin password hash can be cracked offline to recover the plaintext password, used directly to forge authenticated admin API requests via the signature authentication weakness (GHSA-45h7-499j-7ww3), and chained with the OS command injection flaw (CVE-2025-60787) to escalate a local unprivileged user to the Motion daemon user (often root), enabling full system compromise. This issue has been fixed in version 0.44.0.
Which versions are affected by CVE-2026-32315?
3 open source packages ship an affected version, including motioneye.
| Package | Affected | Fixed in |
|---|---|---|
motioneye PyPI | All versions | 0.44.0 |
motioneye PyPI | All versions | 0.44.0 |
motioneye PyPI | All versions | 0.44.0 |
How do I fix CVE-2026-32315?
Upgrade motioneye to 0.44.0 or later.
Is CVE-2026-32315 being exploited?
It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-32315 exists.
Sources
Also known as GHSA-rhgp-6wq6-9j67, PYSEC-2026-2666.