Skip to main content
Public proof of conceptFix available

CVE-2026-32315

A public proof of concept exists; no exploitation attested.

  • Published2026-06-24
  • Fixed in0.44.0
  • WeaknessCWE-200 · CWE-522 · CWE-732

Am I affected?

With a domain, we read the version its public headers and pages expose. A distribution build can carry the fix under an older number.

Description

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.

Timeline

dates in UTC
  1. 2026-06-2421:16CVE publishedNVD

Observed activity

isMalicious corpus · updated 2026-11-04 15:37 UTC
Indicators tagged with this CVE, per day0 indicators over 7 days
Block these indicators
  • Firewall list (EDL, text): https://api.ismalicious.com/edl/cve/CVE-2026-32315?format=txt
  • CSV export: https://api.ismalicious.com/edl/cve/CVE-2026-32315?format=csv
  • TAXII collection of exploited CVEs
  • The EDL and CSV take an API key on the Pro plan.

Versions per branch

OSV
motioneye
BranchAffectedFixed in
0.44< 0.44.00.44.0

as publishedRanges as NVD and OSV publish them; a distribution’s build can be fixed under an older number.

Products declared by the CNA1 product

As GitHub_M, the CNA that assigned this CVE, declared them in the CVE record; versions as written.

  • motioneye-project motioneye
    Affected
    • = < 0.44.0no fix stated

Source: the CNA record (CVE Program), © The MITRE Corporation,CVE Terms of UseCVE recordupdated 2026-06-24

Fix

  1. Update motioneye to 0.44.0

Detection

Nuclei template
none so far
ProjectDiscovery
Exploit-DB
no entry
Exploit-DB
Proof-of-concept repositories
none listed
PoC-in-GitHub
Metasploit modules
none listed
Metasploit Framework

Sources

  • NVDCVE recordread 2026-10-26
  • CISA-ADPSSVC decisionpoc2026-06-25
  • OpenCVESSVC decisionpoc—
  • CNACVSS 3.15.5known since 2026-10-26
  • CNAweakness (CWE)CWE-200, CWE-522, CWE-732known since 2026-10-26
  • FIRST EPSSEPSS score1.7 %2026-11-03
  • OSVaffected packages—
  • GitHub AdvisoriesadvisoryMODERATE2026-06-22

Identifiers

Technical details

CVSS v3 Vector
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N
Published
2026-06-24
Last Modified
2026-10-25
NVD status
Deferred
GitHub Advisory
GHSA-rhgp-6wq6-9j67

Frequently asked questions

What is CVE-2026-32315?

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.

Is CVE-2026-32315 actively exploited?

A proof-of-concept exploit exists for CVE-2026-32315, but active exploitation has not been confirmed at this time.

What is the CVSS score for CVE-2026-32315?

CVE-2026-32315 has a CVSS v3 base score of 5.5 (MEDIUM severity), with vector string CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N.

Running motioneye? Hear about its next vulnerability

Surveillance reads the versions in your stack — a domain, a lockfile or a list — checks each CVE against the ranges its sources publish, and alerts you when one you run is exploited or enters CISA KEV. A version it cannot read stays « version not verified ».

Get alerts for this productCISA KEV additions, November 2026Search CVEs

No credit card required · No monthly cap on website lookups · 250 API requests/month

Go further

Related vulnerabilities

Same product first, then the same vendor advisory and the same publication week.

Back to CVE Database

Sources for this record