CVE-2026-32315: motionEye insecure file permissions in motion.conf

CVE-2026-32315 · Severity: medium · CVSS 5.5 · Published 2026-06-24

motionEye is a web-based interface for managing video surveillance and motion detection cameras. In affected versions, the software saves sensitive configuration files with insecure permissions that allow any user on the same computer to read them. This could allow a low-privileged user to steal administrator password hashes and camera credentials, potentially leading to full control over the surveillance system or the underlying server.

Technologies: motioneye (PyPI). Vendors: PyPI.

Quick answers

Is CVE-2026-32315 exploited in the wild?
No. Junglewise Threat Intelligence has no report of CVE-2026-32315 being exploited in the wild.
How severe is CVE-2026-32315?
Medium severity, with a CVSS score of 5.5, published 24 June 2026.
Which products and versions are affected?
motioneye (PyPI) < 0.44.0, ECOSYSTEM:introduced=0,fixed=0.44.0.
Is there a fix for CVE-2026-32315?
Yes. motioneye (PyPI): upgrade to 0.44.0 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
How is CVE-2026-32315 attacked?
It is attacked with local access, in a network appliance.
Am I affected by CVE-2026-32315?
Check whether you run motioneye (PyPI) at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

How to fix

  • motioneye (PyPI): upgrade to 0.44.0 or later
    pip install "motioneye>=0.44.0"

Technical details

motionEye versions prior to 0.44.0 create the main configuration file (/etc/motioneye/motion.conf) and per-camera files (camera-*.conf) with 644 (-rw-r--r--) permissions. This root cause allows any local unprivileged user to read the '@admin_password' field, which contains a SHA1 hash of the administrator password. An attacker can crack this hash offline or use it to forge API requests by exploiting a separate signature authentication weakness. When chained with other vulnerabilities like CVE-2025-60787, this can lead to local privilege escalation to the Motion daemon user (often root). The issue is resolved in version 0.44.0 by enforcing 0600 permissions on these files.

Affected products

  • motioneye-project motionEye < 0.44.0

Identifiers

  • CVE-2026-32315
  • GHSA-rhgp-6wq6-9j67
  • PYSEC-2026-2666

Timeline

  • 2026-03-11: disclosed: Vulnerability discovered and vendor notified
  • 2026-03-12: other: Vendor acknowledged and confirmed fix in beta
  • 2026-06-20: patched: Version 0.44.0 released
  • 2026-06-24: advisory: NVD and GitHub advisories published

References

This page as Markdown. Free to reuse under CC BY 4.0 with a link back.