CVE-2026-32315 json
motionEye: World-Readable Configuration File Exposes Admin Password Hash
published 2026-06-22 4 mo ago modified 2026-10-25 14 d ago also EUVD-2026-39088 , GHSA-rhgp-6wq6-9j67 , PYSEC-2026-2666
- cvss
- 5.5
- version 3.1, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 1.7%
- EPSS 1.7% chance of exploitation in 30 days, percentile 77%
- public exploits
- 0
- none known
Summary
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.
Patch / fix
- pypi motioneye 0.44.0
- motioneye_project motioneye 0.44.0
CISA SSVC
- Exploitation
- Proof of concept is public
- Automatable
- no
- Technical impact
- partial
- Assessed
- 4 mo ago
Exploit prediction
1.68% chance of exploitation in the next 30 days, higher than 77% of all scored CVEs (FIRST EPSS, 2026-11-08).
Exploits and checks
- github.com https://github.com/motioneye-project/motioneye/security/advisories/GHSA-rhgp-6wq6-9j67 referenced PoC, tagged "exploit" by a source, unverified
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CNA | 3.1 | 5.5 | CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N |
| GitHub | 3.1 | 5.5 | CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N |
| OSV | 3.1 | 5.5 | CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N |
Affected packages
| ecosystem | package | affected | fixed in |
|---|---|---|---|
| pypi | motioneye | <0.44.0 |
0.44.0 |
Affected products
- motioneye-project motioneye
Classification
References
-
github.com
/motioneye-project/motioneye/security/advisories/GHSA-rhgp-6wq6-9j67
exploit, web
- github.com /motioneye-project/motioneye/releases/tag/0.44.0
-
github.com
/motioneye-project/motioneye
package
-
pypi.org
/project/motioneye
package
-
github.com
/advisories/GHSA-rhgp-6wq6-9j67
advisory
-
nvd.nist.gov
/vuln/detail/CVE-2026-32315
advisory
Sources
- CVE List CVE-2026-32315
- GitHub Advisory GHSA-rhgp-6wq6-9j67
- NVD CVE-2026-32315
- OSV PYSEC-2026-2666
Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.
CPEs and fixed versions use Anchore's correction of NVD's data: Added CPE configurations because not yet analyzed by NVD.