dbcve.org
Information ExposureWeakness · CWE-200

CVE-2026-32315

MEDIUM · 5.5 CVSS v3.1 Published 2026-06-24
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
57/100
Remediation priority · Elevated
Zero-click 8 weeks old

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

motionEye versions prior to 0.44.0 create configuration files (/etc/motioneye/motion.conf and camera-*.conf) with overly permissive 644 permissions, making them world-readable. These files contain sensitive data including SHA1 password hashes that can be cracked offline or chained with other vulnerabilities (GHSA-45h7-499j-7ww3 for authentication bypass and CVE-2025-60787 for command injection) to achieve full system compromise.

MitigationUpgrade motionEye to version 0.44.0 or later to remediate the insecure file permissions. Additionally, rotate any exposed credentials as a precautionary measure.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Local
Complexity
Low
Privileges
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
None
Availability
None

CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify motionEye installation and version
    Run command: pip show motioneye or check /usr/local/lib/python*/dist-packages/motioneye/version.py, or look for motionEye in package manager listings
    Affected if Version is present and less than 0.44.0 (e.g., 0.43.1, 0.42.0, etc.)
  2. Locate motionEye configuration files
    Check for /etc/motioneye/motion.conf and ls /etc/motioneye/camera-*.conf
    Affected if Configuration files exist at these paths (default installation location)
  3. Inspect file permissions on motion.conf
    Run: ls -la /etc/motioneye/motion.conf
    Affected if Permissions show -rw-r--r-- (644) or more permissive (e.g., 666), meaning world-readable
  4. Inspect file permissions on camera configuration files
    Run: ls -la /etc/motioneye/camera-*.conf
    Affected if Any camera-*.conf files have 644 or more permissive permissions (world-readable)
  5. Verify sensitive content in config files
    Run: cat /etc/motioneye/motion.conf | grep -i password or grep hash
    Affected if SHA1 password hashes or plaintext credentials are present in the configuration files

A user is affected if motionEye version is below 0.44.0 AND configuration files at /etc/motioneye/ have world-readable permissions (644 or higher), exposing sensitive credential data.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Upgrade motionEye to version 0.44.0 or later to remediate the insecure file permissions. Additionally, rotate any exposed credentials as a precautionary measure.

Recommended fix High confidence

0.44.0

  1. Upgrade motionEye to version 0.44.0 or later to remediate the information exposure vulnerability
  2. After upgrading, verify that configuration files in /etc/motioneye/ are created with appropriate restrictive permissions (e.g., 640)

Generated from the published advisory — verify against the referenced sources before acting.

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation1.0 h
  • Testing2.0 h
  • Review / QA1.0 h
6.0 hours of engineering $1,060
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,696.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-32315 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-32315 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data