CVE-2026-46488

CRITICALPre-NVD 9.19.1
EchelonGraph scoreMEDIUM confidence

This critical-severity CVE scores 9.1 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.3%, top 81% 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
Trending — 3 sources updated this weekElevated
9.1EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 9.1Exploit: Elevated riskExposed: 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 a piece of software called "motion," which is a video surveillance program with motion detection. Prior to 0.44.0, motionEye accepts the client-controlled meye_username and meye_password_hash cookies as authentication material without server-side session validation. An unauthenticated attacker who knows a target username and corresponding hash can set the cookies manually or cause them to be loaded by submitting blank credentials through the switch-user authentication flow, after which the server authenticates the attacker as that user. The administrator username and password-hash value are stored in /etc/motioneye/motion.conf, which is globally readable by default, allowing a local shell user to obtain reusable administrator credential material. Successful impersonation can enable account lockout, password changes and persistence, data enumeration, data destruction, and data exfiltration. This issue is fixed in version 0.44.0.

CVSS v3
9.1
EG Score
9.1(medium)
EG Risk
72(Attend)
EG Risk 72/100SSVC: Attend

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
Severity91% × 45%
Exploitation40% × 40%
Automatability100% × 15%
Action: Remediate soon — notable exploitation risk.
EPSS PROB
0%
EPSS %ILE
19%
KEV
Not listed

Published

June 22, 2026

Last Modified

September 17, 2026

Advisory Details (3)

Auto-updated Sep 15, 2026
🔬 Proof of concept available. Patch available. Sources: github_pr, github_release, github.
github Patch Available🟡 PoC Available

Authentication possible via password hash · Advisory · motioneye-project/motioneye · GitHub

https://github.com/motioneye-project/motioneye/security/advisories/GHSA-r3cw-c95m-wfh9
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
github_pr Patch Available

Replace URL signature auth with sessions and HMAC peer authentication

Patch available: motioneye-project/motioneye 0.44.0b2 (PR #3332 merged 2026-05-21)

https://github.com/motioneye-project/motioneye/pull/3332

Vendor Advisories for CVE-2026-46488(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(4)

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

Data Freshness Timeline

(refreshed 8× in last 7d / 8× 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-09-18 19:28 UTCEPSS rescore
  2. 2026-09-18 11:14 UTCEG score recompute
  3. 2026-09-17 19:31 UTCEPSS rescore
  4. 2026-09-17 18:16 UTCEG score recompute
  5. 2026-09-16 14:08 UTCEPSS rescore
  6. 2026-09-15 17:34 UTCEG score recompute
  7. 2026-09-15 16:53 UTCEG score recompute 9.10
  8. 2026-09-15 16:52 UTCMITRE cvelistV5CVSS v3 → 9.1 · CVSS v4 → 9.1
  9. 2026-08-01 07:47 UTCEG score recompute
  10. 2026-07-26 15:58 UTCEG score recompute
  11. 2026-07-23 03:17 UTCEG score recompute
  12. 2026-06-22 21:39 UTCEG score recompute

Frequently asked(5)

What is CVE-2026-46488?
CVE-2026-46488 is a critical vulnerability published on June 22, 2026. motionEye (mEye) is an online interface for a piece of software called "motion," which is a video surveillance program with motion detection. Prior to 0.44.0, motionEye accepts the client-controlled meyeusername and meyepassword_hash cookies as authentication material without server-side session…
When was CVE-2026-46488 disclosed?
CVE-2026-46488 was first published in the National Vulnerability Database on June 22, 2026, with the most recent update on September 17, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-46488 actively exploited?
CVE-2026-46488 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0% probability of exploitation in the next 30 days, which ranks it in the top 80.7% of all scored CVEs.
What is the CVSS score of CVE-2026-46488?
CVE-2026-46488 has a CVSS v3 base score of 9.1 (NVD).
How do I remediate CVE-2026-46488?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-46488, 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-46488

Explore →

Is Your Infrastructure Affected by CVE-2026-46488?

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