Machine-written summary
Summary written by Claude Haiku from the source advisory. Not reviewed by a person.
motionEye versions >=0.43.1b1 and <0.43.1b4 are vulnerable to remote code execution through the add_camera function, which runs unsanitized device path input in a subprocess. An attacker with motionEye admin credentials could execute arbitrary shell commands as the user running motionEye, which is motion by default. Upgrade to motionEye 0.43.1b4, which fixes the issue.
Not analysed yet
We haven’t published our analysis of this Advisory yet. Once a person has reviewed it, this page will say what’s vulnerable, what has to be true for your app to be affected, and how to check.
Severity and exploitation
| Score | Rating | CVSS | Vector | Source |
|---|---|---|---|---|
| 8.9 | High | 4.0 | CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N/E:P | CNA (GitHub_M) |
- CISA KEV Not listed.
- EPSS 0.0052, the 44th percentile, on 17 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.
Timeline
- 31 Oct 2026, 14:29 UTC First seen by agentprime
- 31 Oct 2026, 14:29 UTC Confirmed by OSV
Sources
- GitHub Advisory Database: GHSA-g5mq-prx7-c588
- OSV: GHSA-g5mq-prx7-c588
- github.com/motioneye-project/motioneye/security/advisories/GHSA-g5mq-prx7-c588
- nvd.nist.gov/vuln/detail/CVE-2025-47782
- github.com/motioneye-project/motioneye/issues/3142
- github.com/motioneye-project/motioneye/pull/3143
- github.com/motioneye-project/motioneye
- github.com/pypa/advisory-database/tree/main/vulns/motioneye/PYSEC-2025-39.yaml