# CVE-2026-55488: motionEye's Absolute Path Traversal in Media File Handlers Allows Arbitrary File Read

> An attacker can read arbitrary files from the filesystem by exploiting absolute path traversal in motionEye's media file handlers.

- **Severity:** High 7.7 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N/E:P`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 24 Jun 2026
- **Updated:** 24 Jun 2026
- **Also known as:** GHSA-rw9q-97r9-8gvh, PYSEC-2026-2667

## What is CVE-2026-55488?

CVE-2026-55488 is a high-severity path traversal vulnerability in motioneye-project motioneye, published on 24 Jun 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

motionEye (mEye) is an online interface for a piece of software called "motion," which is a video surveillance program with motion detection. Versions prior to 0.44.0 contain 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. Version 0.44.0 fixes the issue.

Weakness: CWE-22 (Improper Limitation of a Pathname to a Restricted Directory)

## Which versions are affected by CVE-2026-55488?

3 open source packages ship an affected version, including motioneye.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `motioneye` | PyPI | All versions | 0.44.0 |
| `motioneye` | PyPI | All versions | 0.44.0 |
| `motioneye` | PyPI | All versions | 0.44.0 |

## How do I fix CVE-2026-55488?

Upgrade motioneye to 0.44.0 or later.

## Is CVE-2026-55488 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-55488 exists.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-55488 and fix it if it is affected.

What it is: CVE-2026-55488 is a high-severity path traversal vulnerability in motioneye-project motioneye, published on 24 Jun 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-55488 exists.

Affected packages and fixed versions:
- motioneye (PyPI): affected all versions; fixed in 0.44.0
- motioneye (PyPI): affected all versions; fixed in 0.44.0
- motioneye (PyPI): affected all versions; fixed in 0.44.0

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-55488/ (Markdown: https://insights.sbomify.com/CVE-2026-55488/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-55488
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-55488
- OSV: https://osv.dev/vulnerability/CVE-2026-55488

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-55488/
Summaries are generated and may contain mistakes; the official description above is the record.