CVE-2026-46488

motionEye: Authentication possible via password hash

State
Published
Severity
9.1 Critical
Published
Sep 15, 2026
Updated
Sep 17, 2026
Reserved
May 14, 2026

Read the record on cve.org

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.

Scores

CVSSScoreVectorSource
4.09.1 CriticalCVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:H/VI:H/VA:N/SC:N/SI:N/SA:NGitHub_M

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

Affected Products

ProductVersions
motioneyemotioneye-project
  • < 0.44.0Affected

References

Every record here comes from the CVE Program’s CVE List. © 1999–2026 The MITRE Corporation. CVE is a registered trademark of The MITRE Corporation. The records are reproduced under the CVE Program terms of use.