Machine-written summary
Summary written by Claude Haiku from the source advisory. Not reviewed by a person.
motionEye versions before 0.44.0 are vulnerable to path traversal in the picture and movie preview endpoints, such as /picture/{id}/preview/{filename}, which do not reject ".." sequences in the filename. An authenticated user with a normal, non-admin account can exploit this to read arbitrary files readable by the motionEye process user, including files outside the media directory. Upgrade to motionEye 0.44.0 or later, where this is fixed. The source gives no workaround.
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 |
|---|---|---|---|---|
| 6.5 | Medium | 3.1 | CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N | CNA (GitHub_M) |
- CISA KEV Not listed.
- EPSS 0.0034, the 27th percentile, on 16 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.
Timeline
- 31 Oct 2026, 15:01 UTC First seen by agentprime
- 31 Oct 2026, 15:01 UTC Confirmed by OSV