CVE-2026-32315: Motioneye MotionEye's World-Readable Configuration File Exposes Vulnerability

MODERATE
Advisory Identifier: GHSA-rhgp-6wq6-9j67
CVSS 5.5
CWE-732
Published
Advisory Summary

CVE-2026-32315 is a MODERATE (CVSS 5.5) motioneye's world-readable configuration file exposes vulnerability (CWE-732: Incorrect Permission Assignment for Critical Resource) affecting Motioneye libraries in the PyPI ecosystem. The issue involves motioneye's world-readable configuration file exposes admin password hash. Remediation is available by upgrading affected packages to version 0.44.0.

CVE-2026-32315 at a Glance

CVE Identifier CVE-2026-32315
GHSA Identifier GHSA-rhgp-6wq6-9j67
Severity MODERATE
CVSS v3.1 Base Score 5.5
CWE Classification CWE-732: Incorrect Permission Assignment for Critical Resource
Affected Product Motioneye
Package Ecosystem PyPI
Published Date
Last Updated

Security Impact

CVSS: 5.5

The security impact metrics below are parsed directly from the CVSS v3.1 vector string (CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N).

Attack Vector Local (AV:L)
Attack Complexity Low (AC:L)
Privileges Required Low (PR:L)
User Interaction None (UI:N)
Scope Unchanged (S:U)
Confidentiality High (C:H)
Integrity None (I:N)
Availability None (A:N)

How to Fix CVE-2026-32315

To remediate this vulnerability, upgrade all affected Motioneye dependencies to a patched release. Both direct and transitive dependencies should be checked, as frameworks or security libraries may pull in vulnerable versions transitively.

motioneye fixed: 0.44.0
pip install motioneye>=0.44.0
Verify Direct and Transitive Dependencies

Run the following command in your project directory to verify that all resolved dependencies use the patched release:

pip show motioneye

How to Check if You Are Affected

To determine whether your Python environment is affected by CVE-2026-32315, inspect your installed packages using pip:

pip show motioneye

Analyze the terminal output to locate any version of Motioneye in your dependency tree. If any resolved version matches the vulnerable ranges listed in the table below (for example, versions earlier than 0.44.0), your application is affected.

Note: The pip show motioneye command checks currently installed packages in your active Python environment.

Technical Details

Vulnerability Mechanism & Technical Analysis

This vulnerability is classified under CWE-732: Incorrect Permission Assignment for Critical Resource, where the product specifies permissions for a security-critical resource in a way that allows that resource to be read or modified by unintended actors. In Motioneye, software state validation or input boundaries are circumvented during processing. Review the official source advisory statement below for specific affected components, classes, and reproduction details.

Source Advisory Statement

# 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 `@admin_password` field: ``` # @admin_username admin # @admin_password c18006fc138809314751cd1991f1e0b820fabd37 ``` Any local user can read this hash without elevated privileges: ```bash $ sudo -u testuser cat /etc/motioneye/motion.conf # @admin_password c18006fc138809314751cd1991f1e0b820fabd37 ``` 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: ```bash # Verify the file permissions $ ls -la /etc/motioneye/motion.conf -rw-r--r-- 1 motion motion 255 Mar 11 15:42 /etc/motioneye/motion.conf # Read the hash as an unprivileged user $ sudo -u testuser cat /etc/motioneye/motion.conf | grep admin_password # @admin_password c18006fc138809314751cd1991f1e0b820fabd37 # Verify the hash matches the admin password (SHA1) $ sudo -u testuser python3 -c "import hashlib; print(hashlib.sha1(b'testpassword123').hexdigest())" c18006fc138809314751cd1991f1e0b820fabd37 ``` ### Verified Output The following output was captured on a fresh motionEye v0.43.1b4 installation (official `motioneye_init` method, admin password set to `testpassword123`): ``` $ ls -la /etc/motioneye/motion.conf -rw-r--r-- 1 motion motion 255 Mar 11 15:42 /etc/motioneye/motion.conf $ sudo -u testuser cat /etc/motioneye/motion.conf | grep admin_password # @admin_password c18006fc138809314751cd1991f1e0b820fabd37 $ sudo -u testuser python3 -c "import hashlib; print(hashlib.sha1(b'testpassword123').hexdigest())" c18006fc138809314751cd1991f1e0b820fabd37 ``` 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 1. 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 ``` 2. Set an admin password via the web UI at `http://localhost:8765` 3. 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 ``` 4. As an unprivileged user, read the hash: ```bash sudo -u testuser cat /etc/motioneye/motion.conf # @admin_password c18006fc138809314751cd1991f1e0b820fabd37 ``` ### Method 2: Official `motioneye_init` Installation 1. Install motionEye using the official init script: ```bash sudo pip install motioneye sudo motioneye_init ``` 2. The `motioneye_init` 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` 3. 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. 4. Confirm as an unprivileged user: ```bash sudo -u testuser cat /etc/motioneye/motion.conf # @admin_password 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 `image_file_name`, which requires admin authentication. When chained with both this vulnerability and GHSA-45h7-499j-7ww3, enables local privilege escalation to root ## Suggested Remediation 1. **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

CVE-2026-32315 Affected Motioneye Versions

1 component(s)
Fixed Versions:
0.44.0
Product / Package Ecosystem Affected Versions Fixed Version
motioneye
PyPI
< 0.44.0
0.44.0

References

Frequently Asked Questions

What is CVE-2026-32315?
CVE-2026-32315 is a security vulnerability in Motioneye involving motionEye's World-Readable Configuration File Exposes Admin Password Hash under CWE-732: Incorrect Permission Assignment for Critical Resource.
Which Motioneye versions are affected?
Affected versions include releases prior to 0.44.0 across affected packages: motioneye.
What version fixes CVE-2026-32315?
Upgrading to 0.44.0 (or the latest patched release for your respective branch) resolves the vulnerability.
Is motioneye affected?
Yes, motioneye is affected in releases prior to 0.44.0. Upgrade your dependency to 0.44.0 or later.
What is the CVSS score of CVE-2026-32315?
CVE-2026-32315 has a CVSS v3.1 base score of 5.5 (MODERATE) with vector string CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N.
What CWE is associated with CVE-2026-32315?
CVE-2026-32315 is classified under CWE-732: Incorrect Permission Assignment for Critical Resource (The product specifies permissions for a security-critical resource in a way that allows that resource to be read or modified by unintended actors.).
How can I check PyPI dependencies for CVE-2026-32315?
Run the dependency tree command: 'pip show motioneye'. This command lists direct and transitive dependencies in your build configuration so you can verify if a vulnerable version is resolved.
Machine-readable OSV JSON OSV v1.5 Schema
Normalized schema output
{
  "schema_version" : "1.4.0",
  "id" : "GHSA-rhgp-6wq6-9j67",
  "modified" : "2026-06-22T17:11:37Z",
  "published" : "2026-06-22T17:11:36Z",
  "aliases" : [ "CVE-2026-32315" ],
  "summary" : "motionEye's World-Readable Configuration File Exposes Admin Password Hash",
  "details" : "# Security Advisory: World-Readable Configuration File Exposes Admin Password Hash in motionEye\n\n## Summary\n\nmotionEye 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.\n\n## Affected Versions\n\n- motionEye <= 0.43.1b4\n- Fixed in motionEye 0.44.0b1 (applies `0600` mode to `motion.conf` and `camera-*.conf` files)\n\n## Vulnerability Details\n\n### World-Readable Configuration File (CWE-732)\n\nWhen 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 `@admin_password` field:\n\n```\n# @admin_username admin\n# @admin_password c18006fc138809314751cd1991f1e0b820fabd37\n```\n\nAny local user can read this hash without elevated privileges:\n\n```bash\n$ sudo -u testuser cat /etc/motioneye/motion.conf\n# @admin_password c18006fc138809314751cd1991f1e0b820fabd37\n```\n\nAdditionally, per-camera configuration files (`camera-*.conf`) are also created with the same `644` permissions, potentially exposing camera-specific credentials and settings.\n\n## Impact\n\nThe exposed admin password hash enables several attack paths:\n\n- **Offline password cracking:** The SHA1 hash can be cracked to recover the plaintext admin password\n- **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\n- **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)\n\n## Proof of Concept\n\nThe following demonstrates that an unprivileged user can read the admin password hash from the config file and verify it matches the admin's password:\n\n```bash\n# Verify the file permissions\n$ ls -la /etc/motioneye/motion.conf\n-rw-r--r-- 1 motion motion 255 Mar 11 15:42 /etc/motioneye/motion.conf\n\n# Read the hash as an unprivileged user\n$ sudo -u testuser cat /etc/motioneye/motion.conf | grep admin_password\n# @admin_password c18006fc138809314751cd1991f1e0b820fabd37\n\n# Verify the hash matches the admin password (SHA1)\n$ sudo -u testuser python3 -c \"import hashlib; print(hashlib.sha1(b'testpassword123').hexdigest())\"\nc18006fc138809314751cd1991f1e0b820fabd37\n```\n\n### Verified Output\n\nThe following output was captured on a fresh motionEye v0.43.1b4 installation (official `motioneye_init` method, admin password set to `testpassword123`):\n\n```\n$ ls -la /etc/motioneye/motion.conf\n-rw-r--r-- 1 motion motion 255 Mar 11 15:42 /etc/motioneye/motion.conf\n\n$ sudo -u testuser cat /etc/motioneye/motion.conf | grep admin_password\n# @admin_password c18006fc138809314751cd1991f1e0b820fabd37\n\n$ sudo -u testuser python3 -c \"import hashlib; print(hashlib.sha1(b'testpassword123').hexdigest())\"\nc18006fc138809314751cd1991f1e0b820fabd37\n```\n\nThe hash extracted by the unprivileged `testuser` matches the SHA1 of the admin password, confirming full credential exposure.\n\n## Reproduction Steps\n\nThis vulnerability has been tested and confirmed with both installation methods described in the official motionEye documentation.\n\n### Method 1: Manual Installation\n\n1. Install motionEye on a Linux system:\n   ```bash\n   sudo pip install motioneye\n   mkdir -p /etc/motioneye /var/log/motioneye /var/lib/motioneye /run/motioneye\n   cp /usr/local/lib/python3.12/dist-packages/motioneye/extra/motioneye.conf.sample /etc/motioneye/motioneye.conf\n   sudo meyectl startserver -c /etc/motioneye/motioneye.conf\n   ```\n\n2. Set an admin password via the web UI at `http://localhost:8765`\n\n3. Verify the config file is world-readable:\n   ```bash\n   ls -la /etc/motioneye/motion.conf\n   # -rw-r--r-- 1 root root 255 ... /etc/motioneye/motion.conf\n   ```\n\n4. As an unprivileged user, read the hash:\n   ```bash\n   sudo -u testuser cat /etc/motioneye/motion.conf\n   # @admin_password c18006fc138809314751cd1991f1e0b820fabd37\n   ```\n\n### Method 2: Official `motioneye_init` Installation\n\n1. Install motionEye using the official init script:\n   ```bash\n   sudo pip install motioneye\n   sudo motioneye_init\n   ```\n\n2. The `motioneye_init` 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`\n\n3. Verify the config file is still world-readable:\n   ```bash\n   ls -la /etc/motioneye/motion.conf\n   # -rw-r--r-- 1 motion motion 255 ... /etc/motioneye/motion.conf\n   ```\n\n   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.\n\n4. Confirm as an unprivileged user:\n   ```bash\n   sudo -u testuser cat /etc/motioneye/motion.conf\n   # @admin_password c18006fc138809314751cd1991f1e0b820fabd37\n   ```\n\nBoth installation methods produce the same vulnerable state, confirming this is the default behavior of the software and not a user misconfiguration.\n\n## Related Vulnerabilities\n\n- **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\n- **CVE-2025-60787:** OS command injection via `image_file_name`, which requires admin authentication. When chained with both this vulnerability and GHSA-45h7-499j-7ww3, enables local privilege escalation to root\n\n## Suggested Remediation\n\n1. **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)\n\n## Timeline\n\n- **2026-03-11:** Vulnerability discovered during security research\n- **2026-03-11:** Vendor notified via GitHub Security Advisory\n- **2026-03-12:** Vendor acknowledged, confirmed fix in motionEye 0.44.0b1",
  "severity" : [ {
    "type" : "CVSS_V3",
    "score" : "CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N"
  } ],
  "affected" : [ {
    "package" : {
      "ecosystem" : "PyPI",
      "name" : "motioneye"
    },
    "ranges" : [ {
      "type" : "ECOSYSTEM",
      "events" : [ {
        "introduced" : "0"
      }, {
        "fixed" : "0.44.0"
      } ]
    } ]
  } ],
  "references" : [ {
    "type" : "WEB",
    "url" : "https://github.com/motioneye-project/motioneye/security/advisories/GHSA-rhgp-6wq6-9j67"
  }, {
    "type" : "PACKAGE",
    "url" : "https://github.com/motioneye-project/motioneye"
  } ],
  "database_specific" : {
    "cwe_ids" : [ "CWE-732" ],
    "severity" : "MODERATE",
    "github_reviewed" : true,
    "github_reviewed_at" : "2026-06-22T17:11:36Z",
    "nvd_published_at" : null
  }
}