CVE-2026-32315

MEDIUMPre-NVD 5.55.5
EchelonGraph scoreMEDIUM confidence

“—” beside the score: it is equal to the CVSS score beside it.

This medium-severity CVE scores 5.5 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 2.9% (86th percentile of EPSS-scored CVEs). No GitHub Security Advisory CVSS is on record for this CVE.

Triggered by: Headline CVSS from a secondary CVSS source
Sources: EPSS, a secondary CVSS source
Trending — 3 sources updated this weekElevated
5.5EG
EchelonGraph verdictPlan a fixRemediate within your standard update timelines (the SSVC decision on this page).
  • CISA's Vulnrichment rates exploitation as PoC; EchelonGraph holds no exploit-code reference for it
CISA-KEV: Not listedEPSS PROB: 2.9%CVSS: 5.5Exploit: No code on recordExposed services: Not assessed

A fix is available — apply it.

motionEye (mEye) is an online interface for motion software, a video surveillance program with motion detection. Versions prior to 0.44.0 create the configuration file /etc/motioneye/motion.conf with 644 permissions (-rw-r--r--), making it readable by any local user on the system. This file contains sensitive data including the admin password hash, which can be leveraged by other vulnerabilities to escalate privileges. Additionally, per-camera configuration files (camera-*.conf) are also created with the same 644 permissions, potentially exposing camera-specific credentials and settings. The exposed SHA1 admin password hash can be cracked offline to recover the plaintext password, used directly to forge authenticated admin API requests via the signature authentication weakness (GHSA-45h7-499j-7ww3), and chained with the OS command injection flaw (CVE-2025-60787) to escalate a local unprivileged user to the Motion daemon user (often root), enabling full system compromise. This issue has been fixed in version 0.44.0.

CVSS v3
5.5
EG Score
5.5MEDIUMmedium confidence
EG Risk
41
EG Risk 41/100

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed (value × EchelonGraph’s weight)
Severity55% × 45%
The EG Score, 5.5 of 10.
Exploitation40% × 40%
EchelonGraph's fixed weight for EG-KEV Tier 3 (Elevated): a constant, not a probability.
Automatability0% × 15%
CISA's SSVC Automatable value: no (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at low or medium mission impact; Track* at high (mission-essential systems).
Exploitation public PoC (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE.
Action: A fix is available. Apply it within your standard update timelines.
EPSS PROB
2.9%
EPSS %ILE
86th
KEV
Not listed

SSVC (CISA's decision table, applied by EchelonGraph)Track at low or medium mission impact; Track* at high (mission-essential systems).

A fix is available. Apply it within your standard update timelines.

Exploitation public PoC (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE. Mission impact is CISA's Mission & Well-being decision point, and only you can judge it. CISA's table makes it high when Mission Prevalence is Essential — the vulnerable component "directly provides capabilities that constitute at least one MEF for at least one entity" (MEF: mission essential function) — or when Public Well-Being Impact is Irreversible: "multiple fatalities are likely", the cyber-physical system "is likely lost or destroyed", "extreme or serious externalities" are imposed on other parties, or social systems such as elections or the financial grid "are destabilized and potentially collapse". CISA's decision table

BOD 26-04 (CISA's remediation timeline, Table 1)60 days if the affected system is publicly exposed; Fix on system upgrade if it is not.

In CISA KEV no (CISA's KEV catalog) · Automatable no (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). Whether your system is publicly exposed is yours to answer. BOD 26-04 binds US Federal Civilian Executive Branch agencies; for anyone else it is CISA's published timeline, a reference rather than an obligation. The directive · how EchelonGraph applies it

Published

June 22, 2026

Last Modified

June 25, 2026

Advisory Details (2)

Auto-updated Jun 24, 2026
Patch available. Sources: github_release, github.
GitHub advisoryMentions a patch (unverified)

World-Readable Configuration File Exposes Admin Password Hash in motionEye · Advisory · motioneye-project/motioneye · GitHub

https://github.com/motioneye-project/motioneye/security/advisories/GHSA-rhgp-6wq6-9j67
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-32315(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 rangeFix by version rangeDependents
motioneye0.27 ... 0.44.0b3 (65 versions)
  • every version up to 0.44.0: fixed in 0.44.0
—

Weakness Classification(3)

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

Data Freshness Timeline

(refreshed 11× in last 7d / 26× in last 30d)

Each row is a time one of our pipelines fetched, updated or re-scored this CVE. 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. An arrow marks a change the record states ("CVSS v3 → 9.1"); EPSS and GHSA rows show the values recorded at that time, not what changed (EPSS values are rounded; hover one for the exact figures). Most recent first.

Showing the most recent 95 of 144 refreshes on record for this CVE.

A repeat, a row identical to one the same pipeline wrote less than 10 seconds earlier, is not a separate refresh and is not counted. 5 repeat rows among the latest 100 are merged into the row they repeat. The 49 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

  1. 2026-10-12 16:34 UTCEPSS rescoreEPSS 2.9% · 86th percentile
  2. 2026-10-12 16:05 UTCEG score recompute
  3. 2026-10-11 19:56 UTCEG score recompute
  4. 2026-10-11 17:10 UTCEG score recompute
  5. 2026-10-11 14:38 UTCEG score recompute
  6. 2026-10-11 13:48 UTCEPSS rescoreEPSS 2.9% · 86th percentile
  7. 2026-10-10 20:00 UTCEPSS rescoreEPSS 2.9% · 86th percentile
  8. 2026-10-09 20:07 UTCEPSS rescoreEPSS 2.9% · 86th percentile
  9. 2026-10-08 17:12 UTCEPSS rescoreEPSS 2.9% · 86th percentile
  10. 2026-10-08 05:24 UTCOSV refresh
  11. 2026-10-07 23:47 UTCEPSS rescoreEPSS 2.9% · 86th percentile
  12. 2026-10-06 15:17 UTCEPSS rescoreEPSS 2.9% · 86th percentile
  13. 2026-10-05 17:42 UTCEPSS rescoreEPSS 2.9% · 86th percentile
  14. 2026-10-03 14:25 UTCEPSS rescoreEPSS 2.9% · 86th percentile
  15. 2026-10-01 19:49 UTCEPSS rescoreEPSS 2.9% · 86th percentile
  16. 2026-09-30 15:03 UTCEPSS rescoreEPSS 2.9% · 86th percentile
  17. 2026-09-28 13:51 UTCEPSS rescoreEPSS 2.9% · 86th percentile
  18. 2026-09-27 13:48 UTCEPSS rescoreEPSS 2.9% · 86th percentile
  19. 2026-09-26 15:58 UTCEPSS rescoreEPSS 2.9% · 86th percentile
  20. 2026-09-26 00:26 UTCEPSS rescoreEPSS 2.9% · 86th percentile
  21. 2026-09-18 19:27 UTCEPSS rescoreEPSS 2.9% · 86th percentile
  22. 2026-09-18 11:18 UTCEG score recompute
  23. 2026-09-17 19:30 UTCEPSS rescoreEPSS 2.9% · 86th percentile
  24. 2026-09-16 14:08 UTCEPSS rescoreEPSS 2.9% · 86th percentile
  25. 2026-09-16 05:15 UTCEPSS rescoreEPSS 2.9% · 86th percentile
Show 70 more
  1. 2026-09-13 16:47 UTCEPSS rescoreEPSS 2.9% · 86th percentile
  2. 2026-09-13 12:45 UTCEG score recompute
  3. 2026-09-12 15:01 UTCEPSS rescoreEPSS 2.9% · 86th percentile
  4. 2026-09-11 14:52 UTCEPSS rescoreEPSS 2.9% · 86th percentile
  5. 2026-09-10 09:34 UTCEPSS rescoreEPSS 2.9% · 86th percentile
  6. 2026-09-08 22:00 UTCEPSS rescoreEPSS 2.9% · 86th percentile
  7. 2026-09-07 16:01 UTCEPSS rescoreEPSS 2.9% · 86th percentile
  8. 2026-09-06 13:47 UTCEPSS rescoreEPSS 2.9% · 86th percentile
  9. 2026-09-04 05:06 UTCEPSS rescoreEPSS 2.9% · 86th percentile
  10. 2026-09-02 14:11 UTCEPSS rescoreEPSS 2.9% · 86th percentile
  11. 2026-09-01 13:53 UTCEPSS rescoreEPSS 2.9% · 86th percentile
  12. 2026-09-01 04:39 UTCEPSS rescoreEPSS 2.9% · 86th percentile
  13. 2026-08-30 20:33 UTCEG score recompute
  14. 2026-08-30 19:17 UTCEPSS rescoreEPSS 2.9% · 86th percentile
  15. 2026-08-30 01:22 UTCEPSS rescoreEPSS 2.9% · 86th percentile
  16. 2026-08-28 21:41 UTCEPSS rescoreEPSS 2.9% · 86th percentile
  17. 2026-08-27 14:25 UTCEPSS rescoreEPSS 2.9% · 86th percentile
  18. 2026-08-26 14:46 UTCEPSS rescoreEPSS 2.9% · 86th percentile
  19. 2026-08-25 13:49 UTCEPSS rescoreEPSS 2.9% · 86th percentile
  20. 2026-08-24 22:14 UTCEG score recompute
  21. 2026-08-24 14:17 UTCEPSS rescoreEPSS 2.9% · 86th percentile
  22. 2026-08-23 16:45 UTCEG score recompute
  23. 2026-08-23 00:19 UTCEPSS rescoreEPSS 1.2% · 65th percentile
  24. 2026-08-22 15:11 UTCEG score recompute
  25. 2026-08-21 23:49 UTCEPSS rescoreEPSS 1.2% · 65th percentile
  26. 2026-08-21 09:25 UTCEG score recompute
  27. 2026-08-20 22:55 UTCEPSS rescoreEPSS 1.2% · 65th percentile
  28. 2026-08-20 07:51 UTCEG score recompute
  29. 2026-08-19 17:03 UTCEPSS rescoreEPSS 1.2% · 65th percentile
  30. 2026-08-19 04:52 UTCEG score recompute
  31. 2026-08-18 13:48 UTCEPSS rescoreEPSS 1.2% · 65th percentile
  32. 2026-08-17 13:47 UTCEPSS rescoreEPSS 1.2% · 65th percentile
  33. 2026-08-17 11:54 UTCEG score recompute
  34. 2026-08-16 14:56 UTCEPSS rescoreEPSS 1.2% · 65th percentile
  35. 2026-08-16 10:20 UTCEG score recompute
  36. 2026-08-16 02:14 UTCEPSS rescoreEPSS 1.2% · 65th percentile
  37. 2026-08-15 08:47 UTCEG score recompute
  38. 2026-08-15 01:30 UTCEPSS rescoreEPSS 1.2% · 65th percentile
  39. 2026-08-14 06:09 UTCEG score recompute
  40. 2026-08-13 22:00 UTCEPSS rescoreEPSS 1.2% · 65th percentile
  41. 2026-08-13 04:35 UTCEG score recompute
  42. 2026-08-12 13:50 UTCEPSS rescoreEPSS 1.2% · 65th percentile
  43. 2026-08-12 03:02 UTCEG score recompute
  44. 2026-08-11 01:27 UTCEG score recompute
  45. 2026-08-11 00:00 UTCEPSS rescoreEPSS 1.2% · 65th percentile
  46. 2026-08-09 23:53 UTCEG score recompute
  47. 2026-08-09 13:46 UTCEPSS rescoreEPSS 1.2% · 65th percentile
  48. 2026-08-08 22:20 UTCEG score recompute
  49. 2026-08-08 16:37 UTCEPSS rescoreEPSS 1.2% · 65th percentile
  50. 2026-08-07 20:45 UTCEG score recompute
  51. 2026-08-06 19:11 UTCEG score recompute
  52. 2026-08-06 13:46 UTCEPSS rescoreEPSS 1.2% · 65th percentile
  53. 2026-08-05 19:17 UTCEPSS rescoreEPSS 1.2% · 65th percentile
  54. 2026-08-04 15:52 UTCEG score recompute
  55. 2026-08-04 15:10 UTCEPSS rescoreEPSS 1.2% · 65th percentile
  56. 2026-08-04 10:38 UTCEPSS rescoreEPSS 1.2% · 65th percentile
  57. 2026-08-03 14:18 UTCEG score recompute
  58. 2026-08-03 10:36 UTCEPSS rescoreEPSS 1.2% · 65th percentile
  59. 2026-08-02 09:21 UTCEG score recompute
  60. 2026-08-02 02:27 UTCEPSS rescoreEPSS 1.2% · 65th percentile
  61. 2026-08-01 07:47 UTCEG score recompute
  62. 2026-08-01 04:16 UTCEPSS rescoreEPSS 1.2% · 65th percentile
  63. 2026-07-31 04:29 UTCEG score recompute
  64. 2026-07-30 16:28 UTCEPSS rescoreEPSS 1.2% · 65th percentile
  65. 2026-07-30 02:55 UTCEG score recompute
  66. 2026-07-30 01:30 UTCEPSS rescoreEPSS 1.2% · 64th percentile
  67. 2026-07-29 01:21 UTCEG score recompute
  68. 2026-07-27 17:57 UTCEG score recompute
  69. 2026-07-26 16:00 UTCEG score recompute
  70. 2026-07-26 14:54 UTCEPSS rescoreEPSS 1.2% · 64th percentile

Related CVEs(same product + same CWE)

Frequently asked(5)

What is CVE-2026-32315?
CVE-2026-32315 is a medium-severity vulnerability; its CVE record was published on June 22, 2026. motionEye (mEye) is an online interface for motion software, a video surveillance program with motion detection. Versions prior to 0.44.0 create the configuration file /etc/motioneye/motion.conf with 644 permissions (-rw-r--r--), making it readable by any local user on the system. This file…
When was the CVE record for CVE-2026-32315 published?
The CVE record for CVE-2026-32315 was published on June 22, 2026. That is the record's publication date; the vulnerability itself may have been made public earlier. EchelonGraph's copy of the record carries a last-modified date of June 25, 2026; the record at its source may have been updated since.
Is CVE-2026-32315 actively exploited?
CVE-2026-32315 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 2.9% probability of exploitation in the next 30 days (86th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-32315?
CVE-2026-32315 has a CVSS base score of 5.5 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-32315?
A fix for CVE-2026-32315 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-32315 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

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

Explore →

Is Your Infrastructure Affected by CVE-2026-32315?

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

Book a Demo →Browse All CVEs