CVE-2026-31978

MEDIUMPre-NVD 6.56.5
EchelonGraph scoreMEDIUM confidence

This medium-severity CVE scores 6.5 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.4%, top 66% of all CVEs by exploit prediction. GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).

Triggered by: NVD CVSS baseline
Sources: epss, secondary
6.5
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS: 0%CVSS: 6.5Exploit: NoneExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

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.

CVSS v3
6.5
EG Score
6.5(medium)
EPSS
33.6%
KEV
Not listed

Published

June 22, 2026

Last Modified

June 25, 2026

Advisory Details (2)

Auto-updated Jun 24, 2026
🔬 Proof of concept available. Patch available. Sources: github_release, github.
github Patch Available🟡 PoC Available

Arbitrary File Read via Path Traversal in Picture/Movie API Endpoints · Advisory · motioneye-project/motioneye · GitHub

https://github.com/motioneye-project/motioneye/security/advisories/GHSA-g9fx-5r4h-pcw3
github_release Patch Available

0.44.0

Patch available: motioneye-project/motioneye 0.44.0

https://github.com/motioneye-project/motioneye/releases/tag/0.44.0

Vendor Advisories for CVE-2026-31978(1)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Affected Packages

(1 across 1 ecosystem)
PyPI(1)
PackageVulnerable rangeFixed inDependents
motioneye0.27 ... 0.44.0b3 (65 versions)0.44.0

Weakness Classification(2)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 15× in last 7d / 32× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

  1. 2026-07-06 16:27 UTCEPSS rescore
  2. 2026-07-06 16:27 UTCEPSS rescore
  3. 2026-07-06 06:18 UTCEG score recompute
  4. 2026-07-06 02:23 UTCEPSS rescore
  5. 2026-07-06 02:23 UTCEPSS rescore
  6. 2026-07-05 06:44 UTCEG score recompute
  7. 2026-07-05 02:30 UTCEPSS rescore
  8. 2026-07-04 07:32 UTCEG score recompute
  9. 2026-07-04 06:31 UTCEPSS rescore
  10. 2026-07-03 07:18 UTCEG score recompute
  11. 2026-07-02 08:15 UTCEG score recompute
  12. 2026-07-01 15:06 UTCEPSS rescore
  13. 2026-07-01 09:12 UTCEG score recompute
  14. 2026-06-30 23:22 UTCEPSS rescore
  15. 2026-06-30 10:09 UTCEG score recompute
  16. 2026-06-29 14:06 UTCEPSS rescore
  17. 2026-06-29 14:06 UTCEPSS rescore
  18. 2026-06-29 11:05 UTCEG score recompute
  19. 2026-06-28 14:07 UTCEPSS rescore
  20. 2026-06-28 14:07 UTCEPSS rescore
  21. 2026-06-28 12:02 UTCEG score recompute
  22. 2026-06-28 04:56 UTCEPSS rescore
  23. 2026-06-28 04:56 UTCEPSS rescore
  24. 2026-06-27 12:59 UTCEG score recompute
  25. 2026-06-27 03:08 UTCEPSS rescore
Show 7 more
  1. 2026-06-26 13:56 UTCEG score recompute
  2. 2026-06-25 14:49 UTCEG score recompute
  3. 2026-06-25 13:49 UTCEPSS rescore
  4. 2026-06-25 13:49 UTCEPSS rescore
  5. 2026-06-24 15:46 UTCEG score recompute
  6. 2026-06-23 16:44 UTCEG score recompute
  7. 2026-06-22 17:39 UTCEG score recompute

Frequently asked(5)

What is CVE-2026-31978?
CVE-2026-31978 is a medium vulnerability published on June 22, 2026. 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…
When was CVE-2026-31978 disclosed?
CVE-2026-31978 was first published in the National Vulnerability Database on June 22, 2026, with the most recent update on June 25, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-31978 actively exploited?
CVE-2026-31978 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 33.6% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2026-31978?
CVE-2026-31978 has a CVSS v3 base score of 6.5 (NVD).
How do I remediate CVE-2026-31978?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-31978, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-31978

Explore →

Is Your Infrastructure Affected by CVE-2026-31978?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.