CVE-2026-46488
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.
AI Insight
LLM-synthesized narrative grounded in this CVE's description and references.
Affected packages
Versions sourced from the GitHub Security Advisory.
| Package | Affected versions | Patched versions |
|---|---|---|
motioneyePyPI | < 0.44.0 | 0.44.0 |
Affected products
1- Range: <0.44.0
Patches
Vulnerability mechanics
References
5- github.com/advisories/GHSA-r3cw-c95m-wfh9ghsaADVISORY
- github.com/motioneye-project/motioneye/security/advisories/GHSA-r3cw-c95m-wfh9nvdWEB
- github.com/motioneye-project/motioneye/commit/0d5cb9c238a87447dae29812e5bf2ccf323cf3dcnvd
- github.com/motioneye-project/motioneye/pull/3332nvd
- github.com/motioneye-project/motioneye/releases/tag/0.44.0nvd
News mentions
0No linked articles in our index yet.