CVE-2026-32315 is a medium-severity incorrect permission assignment for critical resource vulnerability in motioneye (pip), affecting versions < 0.44.0. It is fixed in 0.44.0.
Security Advisory: World-Readable Configuration File Exposes Admin Password Hash in motionEye Summary motionEye v0.43.1 and prior versions 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. Affected Versions motionEye <= 0.43.1b4 Fixed in motionEye 0.44.0b1 (applies 0600 mode to motion.conf and camera-.conf files) Vulnerability Details World-Readable Configuration File (CWE-732) When motionEye writes its configuration, the file /etc/motioneye/motion.conf is created with 644 permissions regardless of the installation method. This file contains the admin password hash in the @adminpassword field: Any local user can read this hash without elevated privileges: Additionally, per-camera configuration files (camera-.conf) are also created with the same 644 permissions, potentially exposing camera-specific credentials and settings. Impact The exposed admin password hash enables several attack paths: Offline password cracking: The SHA1 hash can be cracked to recover the plaintext admin password Authentication bypass: When combined with the signature authentication weakness (see GHSA-45h7-499j-7ww3), the hash can be used directly to forge authenticated admin API requests Full system compromise: When further chained with CVE-2025-60787 (OS command injection), a local unprivileged user can escalate to the Motion daemon user (often root) Proof of Concept The following demonstrates that an unprivileged user can read the admin password hash from the config file and verify it matches the admin's password: Verified Output The following output was captured on a fresh motionEye v0.43.1b4 installation (official motioneyeinit method, admin password set to testpassword123): The hash extracted by the unprivileged testuser matches the SHA1 of the admin password, confirming full credential exposure. Reproduction Steps This vulnerability has been tested and confirmed with both installation methods described in the official motionEye documentation. Method 1: Manual Installation Install motionEye on a Linux system: bash sudo pip install motioneye mkdir -p /etc/motioneye /var/log/motioneye /var/lib/motioneye /run/motioneye cp /usr/local/lib/python3.12/dist-packages/motioneye/extra/motioneye.conf.sample /etc/motioneye/motioneye.conf sudo meyectl startserver -c /etc/motioneye/motioneye.conf Set an admin password via the web UI at http://localhost:8765 Verify the config file is world-readable: bash ls -la /etc/motioneye/motion.conf # -rw-r--r-- 1 root root 255 ... /etc/motioneye/motion.conf As an unprivileged user, read the hash: bash sudo -u testuser cat /etc/motioneye/motion.conf # @adminpassword c18006fc138809314751cd1991f1e0b820fabd37 Method 2: Official motioneyeinit Installation Install motionEye using the official init script: bash sudo pip install motioneye sudo motioneyeinit The motioneyeinit script automatically creates the required directories, installs the systemd service, and starts motionEye. Set an admin password via the web UI at http://localhost:8765 Verify the config file is still world-readable: bash ls -la /etc/motioneye/motion.conf # -rw-r--r-- 1 motion motion 255 ... /etc/motioneye/motion.conf Note that while the ownership changes to motion:motion (instead of root:root in the manual method), the permissions remain 644, meaning any local user can still read the file. Confirm as an unprivileged user: bash sudo -u testuser cat /etc/motioneye/motion.conf # @adminpassword c18006fc138809314751cd1991f1e0b820fabd37 Both installation methods produce the same vulnerable state, confirming this is the default behavior of the software and not a user misconfiguration. Related Vulnerabilities GHSA-45h7-499j-7ww3: Password hash accepted as API signing key (CWE-836), which allows the hash exposed by this vulnerability to be used for forging authenticated admin API requests CVE-2025-60787: OS command injection via imagefile_name, which requires admin authentication. When chained with both this vulnerability and GHSA-45h7-499j-7ww3, enables local privilege escalation to root Suggested Remediation Fix file permissions: Create motion.conf and camera-*.conf with 600 permissions (-rw-------), readable only by the motionEye service user (addressed in motionEye 0.44.0b1) Timeline 2026-03-11: Vulnerability discovered during security research 2026-03-11: Vendor notified via GitHub Security Advisory 2026-03-12: Vendor acknowledged, confirmed fix in motionEye 0.44.0b1
A file, directory, or other resource is assigned permissions that allow broader access than intended. Typical impact: unauthorized read, modification, or execution of the resource.
CVE-2026-32315 has a CVSS score of 5.5 (Medium). The vector is requires local access, low privileges required, and no user interaction. A CVSS score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether this affects your application depends on whether the vulnerable code is present and reachable in your environment.
A fixed version is available (0.44.0). Upgrading removes the vulnerable code path.
pip
motioneye (< 0.44.0)motioneye → 0.44.0 (pip)Severity tells you how bad this could be in the worst case. It does not tell you whether you are exposed. Exploitability and impact are functions of runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A vulnerable package can sit in your dependency tree and never run.
Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter instead of chasing every advisory.
Kodem's runtime-powered SCA identifies whether CVE-2026-32315 is reachable in your applications. Explore open-source security for your team.
See if CVE-2026-32315 is reachable in your applications. Get a demo
Already deployed Kodem? See CVE-2026-32315 in your environment →Upgrade motioneye to 0.44.0 or later to resolve this vulnerability.
Kodem Kai can prioritize this vulnerability in your dependency tree and generate a fix recommendation.
CVE-2026-32315 is a medium-severity incorrect permission assignment for critical resource vulnerability in motioneye (pip), affecting versions < 0.44.0. It is fixed in 0.44.0. A file, directory, or other resource is assigned permissions that allow broader access than intended.
CVE-2026-32315 has a CVSS score of 5.5 (Medium). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.
motioneye (pip) versions < 0.44.0 is affected.
Yes. CVE-2026-32315 is fixed in 0.44.0. Upgrade to this version or later.
Whether CVE-2026-32315 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
Upgrade motioneye to 0.44.0 or later.