CVE-2026-46488: motioneye · Plaintext Storage of a Password
Affects motioneyeSource CVE Database V5
Not known to be exploited · CVSS 9.1 Critical : upgrade to 0.44.0 as a priority.
Data as of 30 Oct 2026, 11:52 UTC
- EPSS
- 0.4% chance of exploitation in 30 days – higher than 40% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
- Patch
- Available – fixed in 0.44.0
CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:H/VI:H/VA:N/SC:N/SI:N/SA:NExploitation evidence
Disclosed: evidence found.
CVE published 15 Sep 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 30 Oct 2026.
What to do
Upgrade motioneye and motioneye-project/motioneye to 0.44.0.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| motioneye-projectmotioneye | Affected
| Fixed in
|
GitHubmotioneye-project/motioneyepkg:github/motioneye-project/motioneyeOther threats | Affected
| Fixed in
|
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
AI-suggested
Upgrade motionEye to version 0.44.0 or later, where this vulnerability is fixed. Prior versions are vulnerable. There is no indication of alternative mitigations or temporary fixes. Restrict file permissions on /etc/motioneye/motion.conf to prevent unauthorized local access as a defense-in-depth measure.
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.
References
- github.com/motioneye-project/motioneye/security/advisories/GHSA-r3cw-c95m-wfh9 (opens in a new tab)
- github.com/motioneye-project/motioneye/pull/3332 (opens in a new tab)
- github.com/motioneye-project/motioneye/commit/0d5cb9c238a87447dae29812e5bf2ccf323cf3dc (opens in a new tab)
- github.com/motioneye-project/motioneye/releases/tag/0.44.0 (opens in a new tab)