motioneye

CVE-2026-55488

CVE-2026-55488 is a high-severity path traversal vulnerability in motioneye (pip), affecting versions < 0.44.0. It is fixed in 0.44.0.

Key facts
CVSS score
N/A
High
Attack vector
Not available
Issuing authority
GitHub Advisory Database
Affected package
motioneye
Fixed in
0.44.0
Disclosed
2026

Summary

Summary mEye contains an absolute path traversal vulnerability in multiple media file handlers that allows an attacker to read arbitrary files from the filesystem. The affected handlers accept a user-controlled filename parameter and construct filesystem paths using os.path.join(). When an absolute path is supplied, Python discards the configured media directory and returns the attacker-supplied path directly. The application then bypasses Tornado's built-in path validation by overriding the relevant safety checks. As a result, an attacker can access files outside of the configured camera media directory, subject to the permissions of the motionEye process. Details The issue exists in the media playback and download functionality. The filename parameter is passed to mediafiles.getmediapath(): When path is an absolute path (e.g. /etc/motioneye/motion.conf), Python's os.path.join() discards targetdir entirely and returns the absolute path as-is. This would normally be caught by Tornado's StaticFileHandler path validation, but MoviePlaybackHandler explicitly overrides both safety checks (movieplayback.py lines 111-115): This allows reading any file on the filesystem that the motionEye process can access. The same path traversal exists in the movie download, picture download, and picture preview handlers: GET /movie/<cameraid>/download/<filename> GET /picture/<cameraid>/download/<filename> GET /picture/<camera_id>/preview/<filename> PoC Fix Do not allow absolute paths supplied by user input. Validate that the fully resolved canonical path remains within the configured camera media directory before serving a file. Additionally, Tornado’s built-in path validation should not be bypassed unless equivalent validation is performed by motionEye.

Impact

What is path traversal?

Input manipulates file paths to reach files outside the intended directory, such as configuration or credential files. Typical impact: unauthorized file read or write outside the intended directory.

Affected versions

pip

  • motioneye (< 0.44.0)

Security releases

  • motioneye → 0.44.0 (pip)
Kodem intelligence

Severity tells you how bad this could be in the worst case. It does not tell you whether you are exposed. Exploitability and impact are functions of runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A vulnerable package can sit in your dependency tree and never run.

Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter instead of chasing every advisory.

Kodem's runtime-powered SCA identifies whether CVE-2026-55488 is reachable in your applications. Explore open-source security for your team.

See if CVE-2026-55488 is reachable in your applications. Get a demo

Already deployed Kodem? See CVE-2026-55488 in your environment

Remediation advice

Upgrade motioneye to 0.44.0 or later to resolve this vulnerability.

Kodem Kai can prioritize this vulnerability in your dependency tree and generate a fix recommendation.

Frequently asked questions about CVE-2026-55488

What is CVE-2026-55488?

CVE-2026-55488 is a high-severity path traversal vulnerability in motioneye (pip), affecting versions < 0.44.0. It is fixed in 0.44.0. Input manipulates file paths to reach files outside the intended directory, such as configuration or credential files.

Which versions of motioneye are affected by CVE-2026-55488?

motioneye (pip) versions < 0.44.0 is affected.

Is there a fix for CVE-2026-55488?

Yes. CVE-2026-55488 is fixed in 0.44.0. Upgrade to this version or later.

Is CVE-2026-55488 exploitable, and should I be worried?

Whether CVE-2026-55488 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo

What actually determines whether CVE-2026-55488 is exploitable, and how bad it is?

Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.

How do I fix CVE-2026-55488?

Upgrade motioneye to 0.44.0 or later.

Stop the waste.
Protect your environment with Kodem.