Description
motionEye (mEye) is an online interface for a piece of software called "motion," which is a video surveillance program with motion detection. Prior to 0.44.0, motionEye accepts the client-controlled meye_username and meye_password_hash cookies as authentication material without server-side session validation. An unauthenticated attacker who knows a target username and corresponding hash can set the cookies manually or cause them to be loaded by submitting blank credentials through the switch-user authentication flow, after which the server authenticates the attacker as that user. The administrator username and password-hash value are stored in /etc/motioneye/motion.conf, which is globally readable by default, allowing a local shell user to obtain reusable administrator credential material. Successful impersonation can enable account lockout, password changes and persistence, data enumeration, data destruction, and data exfiltration. This issue is fixed in version 0.44.0.
Published: 2026-09-15
Score: 9.1 Critical
EPSS: < 1% Very Low
KEV: No
Impact: Impersonation via authentication bypass using password hash
Action: Immediate Patch
AI Analysis

Impact

motionEye (mEye) is an online interface for a piece of software called motion, a video surveillance program with motion detection. Prior to 0.44.0, motionEye accepts the client‑controlled meye_username and meye_password_hash cookies as authentication material without server‑side session validation. An unauthenticated attacker who knows a target username and corresponding hash can set the cookies manually or cause them to be loaded by submitting blank credentials through the switch‑user authentication flow, after which the server authenticates the attacker as that user. The administrator username and password‑hash value are stored in /etc/motioneye/motion.conf, which is globally readable by default, allowing a local shell user to obtain reusable administrator credential material. Successful impersonation can enable account lockout, password changes and persistence, data enumeration, data destruction, and data exfiltration. This issue is fixed in version 0.44.0.

Affected Systems

The vulnerable product is motionEye from the motioneye‑project, with all releases older than version 0.44.0 affected. The administrator credentials are stored in the file /etc/motioneye/motion.conf, which is by default world‑readable, allowing any local shell user to obtain reusable hashed passwords. The issue is confined to the authentication mechanism that relies on the client‑supplied cookies; image streams or other functional components are not directly impacted.

Risk and Exploitability

The CVSS score of 9.1 indicates a severe authentication bypass with the potential for full account takeover. The EPSS score of < 1 % reflects a very low but non‑zero probability of exploitation in the wild, and the vulnerability is not listed in the CISA KEV catalog, indicating limited evidence of active exploitation. The attack can be carried out locally, as any user can read the world‑readable /etc/motioneye/motion.conf to obtain password hashes, or remotely, by manipulating cookies via a web browser or automated script. Successful exploitation permits the attacker to impersonate any user, including administrators, granting the ability to lock accounts, change passwords, maintain persistence, enumerate or delete captured footage, and exfiltrate data. Until a patch is applied, the risk remains critical.

Generated by OpenCVE AI on September 20, 2026 at 15:17 UTC.

Remediation

No solution or workaround provided in the CVE record.

OpenCVE Recommended Actions

  • Upgrade motionEye to version 0.44.0 or newer.
  • Modify /etc/motioneye/motion.conf permissions to 600 (readable only by root) to prevent local shell users from extracting password hashes.
  • Disable or restrict the switch‑user authentication endpoint (or remove client‑supplied meye_username/meee_password_hash parameters) until the application is patched, to eliminate the ability to inject credentials via cookies.

Generated by OpenCVE AI on September 20, 2026 at 15:17 UTC.

Tracking

Sign in to view the affected projects.

Advisories
Source ID Title
Github GHSA Github GHSA GHSA-r3cw-c95m-wfh9 motionEye: Authentication possible via password hash
History

Thu, 17 Sep 2026 17:30:00 +0000

Type Values Removed Values Added
Metrics ssvc

{'options': {'Automatable': 'yes', 'Exploitation': 'poc', 'Technical Impact': 'total'}, 'version': '2.0.3'}


Tue, 15 Sep 2026 21:30:00 +0000

Type Values Removed Values Added
First Time appeared Motioneye Project
Motioneye Project motioneye
Vendors & Products Motioneye Project
Motioneye Project motioneye

Tue, 15 Sep 2026 17:00:00 +0000

Type Values Removed Values Added
Description motionEye (mEye) is an online interface for a piece of software called "motion," which is a video surveillance program with motion detection. Prior to 0.44.0, motionEye accepts the client-controlled meye_username and meye_password_hash cookies as authentication material without server-side session validation. An unauthenticated attacker who knows a target username and corresponding hash can set the cookies manually or cause them to be loaded by submitting blank credentials through the switch-user authentication flow, after which the server authenticates the attacker as that user. The administrator username and password-hash value are stored in /etc/motioneye/motion.conf, which is globally readable by default, allowing a local shell user to obtain reusable administrator credential material. Successful impersonation can enable account lockout, password changes and persistence, data enumeration, data destruction, and data exfiltration. This issue is fixed in version 0.44.0.
Title motionEye: Authentication possible via password hash
Weaknesses CWE-256
CWE-287
CWE-328
CWE-836
References
Metrics cvssV4_0

{'score': 9.1, 'vector': 'CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:H/VI:H/VA:N/SC:N/SI:N/SA:N'}


Subscriptions

Motioneye Project Motioneye
cve-icon MITRE

Status: PUBLISHED

Assigner: GitHub_M

Published:

Updated: 2026-09-17T16:15:44.923Z

Reserved: 2026-05-14T18:06:06.811Z

Link: CVE-2026-46488

cve-icon Vulnrichment

Updated: 2026-09-17T16:15:37.206Z

cve-icon NVD

Status : Deferred

Published: 2026-09-15T17:17:15.200

Modified: 2026-09-30T17:51:56.193

Link: CVE-2026-46488

cve-icon Redhat

No data.

cve-icon OpenCVE Enrichment

Updated: 2026-09-20T15:30:17Z

Weaknesses
  • CWE-256

    Plaintext Storage of a Password

  • CWE-287

    Improper Authentication

  • CWE-328

    Use of Weak Hash

  • CWE-836

    Use of Password Hash Instead of Password for Authentication