Path Traversal in motioneye (CVE-2026-31978)
Summary
Path traversal in motioneye (CVE-2026-31978). Confidential information can be exposed externally. Exploitable via mediafiles.py. Mitigation: upgrade to 0.44.0 or later.
Original description
The description as published by the source.
motionEye (mEye) is an online interface for motion software, which is a video surveillance program with motion detection. Versions prior to 0.44.0 are vulnerable to path traversal in the picture and movie API endpoints, suhc as /picture/{id}/preview/{filename}. Neither the API handlers, nor the mediafiles.py functions such as get_media_preview() check for .. sequences in the filename parameter, except for get_media_content(). This allows an authenticated user with normal (non-admin) privileges to read arbitrary files from the filesystem as the motionEye process user, such as: /etc/passwd, /etc/shadow, motionEye config files containing password hashes and plaintext passwords, SSH keys, and other cameras' surveillance footage. This issue has been fixed in version 0.44.0.
Source: GitHub Security Advisories (Global) NVD GitHub Advisory
Auto-generated summary
Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.
A vulnerability tracked as CVE-2026-31978 has been found in motioneye.
Attackers can target a specific entry point like mediafiles.py over the network to misuse the product.
Confidential information can be exposed externally. CVSS score: 6.5/10.
What to do: upgrade motioneye to 0.44.0 or later.
If unsure, ask your IT team or search "motioneye CVE-2026-31978" on the vendor's site.
CVE-2026-31978 (motioneye) — CWE-22 / CVSS v3 6.5
Attack vector: remote (network-reachable) / no user interaction
Attack surface: mediafiles.py / key
Patched: 0.44.0 — apply immediately
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.
Path traversal (CWE-22) exists in motioneye. Attackers reach the vulnerable code path via mediafiles.py.
Check the vendor advisory for the affected versions of motioneye. Attack surface: mediafiles.py / key.
Severity: Medium (CVSS 6.5/10). Confidential information can be exposed externally.
Update to 0.44.0.
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run grep -r 'motioneye' . against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.
Response actions
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1Identify exposure identify
grep -r 'motioneye' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で
motioneyeを grep し、稼働しているサービス・バージョンを把握する。 -
2Apply patch patch
Upgrade motioneye to 0.44.0ステージング環境で 0.44.0 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
-
3Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。
Affected packages
References
- advisory github.com
- advisory github.com
- advisory nvd.nist.gov
- package github.com
- web github.com
- web github.com