Quick answers
- Is This vulnerability exploited in the wild?
- No. Junglewise Threat Intelligence has no report of This vulnerability being exploited in the wild.
- How severe is This vulnerability?
- Critical severity, with a CVSS score of 9.8, published 23 June 2026.
- Which products and versions are affected?
- motioneye (PyPI) < 0.44.0.
- Is there a fix for This vulnerability?
- A patch was published on 2026-06-23. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is This vulnerability attacked?
- It is attacked over the network, in a network appliance.
- Am I affected?
- Check whether you run motioneye (PyPI) at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
Technical details
The vulnerability is a chain of four distinct issues: 1) Local File Inclusion (LFI) in the picture download endpoint due to improper path sanitization, allowing absolute path traversal. 2) A 'pass-the-hash' flaw where the application accepts request signatures generated with password hashes instead of plaintext. 3) An unsafe configuration restore function that extracts unsanitized tarballs into the configuration directory. 4) Missing authentication on the action execution handler. An attacker can use LFI to steal the admin password hash, authenticate as admin, upload a malicious executable via the restore function, and trigger its execution via the unauthenticated action endpoint. This results in full Remote Code Execution (RCE). The issue is patched in version 0.44.0.
Affected products
- motioneye-project motionEye < 0.44.0
Timeline
- 2026-06-20: disclosed
- 2026-06-23: advisory
- 2026-06-23: patched