CriticalCVE-2026-46488

    motionEye: Authentication possible via password hash (CVE-2026-46488)

    Published Last modified Sources: CVE.org, OSV, Hersteller, EUVD

    Share

    What is affected, what to do

    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.

    Update Motioneye to version 0.44.0.

    Affected
    • Motioneye lt *..0.44.0
    Fixed in
    • Motioneye 0.44.0

    Not sure whether and how you are affected? Ask a question about this vulnerability

    Metrics

    9.1

    XIEM Effective CVSS

    Highest available CVSS rating from NVD and vendor data.

    Source: Vendor (CNA), CVSS v4

    9.1

    CVSS v4

    Severity Critical on the scale from 0 to 10.

    Source: CVE.org, OSV, Hersteller, EUVD

    0.5 %

    EPSS score

    Low — model estimates < 1% exploitation likelihood.

    Source: FIRST EPSS, percentile 40.8

    Show all metrics
    Severity
    Critical
    Priority (0–325)

    The priority score is a consolidated metric that condenses several individual signals into a single, action-guiding ranking: technical severity (CVSS), exploitation likelihood (EPSS), known-exploited status (KEV) and the context of the affected asset. The aim is to answer the only truly important question in vulnerability management: what first?

    Read in glossary
    84.01 Methodology
    Exploit maturity

    An exploit is code or a technique that specifically uses a concrete vulnerability to force unintended behaviour — such as executing code or escalating privileges. It is the tool that turns a theoretical flaw into a practical attack.

    Read in glossary
    no public PoC known
    XIEM Effective CVSS

    XIEM® is the tiered managed-security operating model from NEOSEC and a registered trademark of NEOSEC GmbH. It extends classic SIEM — the central collection, normalisation and correlation of security-relevant events — with endpoint forensics, network visibility and deception technology, and consolidates them into three building tiers: Sentry, Orchestrate and Command.

    Read in glossary
    9.1 Methodology
    CVSS v4

    CVSS is the globally established, open standard for assessing the technical severity of a vulnerability on a scale from 0 to 10. It describes how easily a flaw can be exploited and what damage it can cause — but not how likely its actual exploitation is. CVSS and the complementary EPSS deliberately answer different questions.

    Read in glossary
    9.1
    EPSS score

    The EPSS score is the absolute model output for an individual vulnerability: the estimated probability of real-world exploitation within the next 30 days, expressed as a value between 0 and 1 (i.e. 0 % to 100 %). A score of 0.42 means „the model estimates a 42 % chance of real-world exploitation within 30 days“.

    Read in glossary
    0.5 %
    Low — model estimates < 1% exploitation likelihood.
    EPSS percentile

    The EPSS percentile is the relative position of a vulnerability within all EPSS-scored CVEs, expressed as a value between 0 and 1. A percentile of 0.90 means „this CVE has a higher EPSS score than 90 % of all other scored CVEs“. Unlike the EPSS score, it is not a probability — but a positioning within a ranking.

    Read in glossary
    40.8
    High — this CVE ranks above the median of all CVEs scored today (rank ≥ 36%).
    KEV status

    The KEV catalogue is a list maintained by the US authority CISA of vulnerabilities for which active exploitation in the wild has been confirmed. It answers not the question „how severe?“ but „is it already being attacked?“ — thereby sharply prioritising patching.

    Read in glossary
    —
    Published
    CISA assessment (SSVC)
    Exploitation: proof of concept · automatable · Technical impact: total
    Source: CISA Vulnrichment, as of 17 September 2026
    CWE

    CWE is a catalogue of typical weakness types in software and hardware — such as flawed input validation, unsafe memory handling or poor authentication. Where a CVE names a concrete vulnerability in a concrete product, a CWE describes the underlying class of defect.

    Read in glossary
    CWE-256, CWE-287, CWE-328, CWE-836

    Detection rules

    No NEOSEC detection rule is available for this vulnerability yet.

    Classification under NIS2 and CRA

    Rule-based classification from exploitation status and severity. It does not replace a case-by-case assessment.

    NIS2

    NIS2 is EU Directive (EU) 2022/2555 to raise the level of cybersecurity across the Union. It substantially broadens obligations compared with the first NIS directive: more sectors, mandatory risk management, staged reporting duties and personal accountability of senior management.

    Read in glossary
    High technical severity: assess and remediate the vulnerability in vulnerability handling under Art. 21(2)(e) NIS2 and document the decision.
    CRA

    The CRA is EU Regulation (EU) 2024/2847 setting horizontal cybersecurity requirements for „products with digital elements“ — from industrial controllers and software to connected consumer devices. For the first time manufacturers must ensure security across the entire product lifecycle, handle vulnerabilities and provide security updates.

    Read in glossary
    From 11.12.2027, Annex I Part II CRA requires manufacturers of affected products with digital elements to handle vulnerabilities without delay and provide security updates.
    ISO/IEC 27001

    ISO/IEC 27001 is the internationally leading standard for an information security management system (ISMS). It describes a risk-based, process-oriented framework to systematically plan, implement, review and improve information security.

    Read in glossary
    Control A.8.8, management of technical vulnerabilities: assess relevance to your systems, plan remediation and keep evidence.

    Description

    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.

    Source: cvelistv5, OSV (Open Source Vulnerabilities), NVD (NIST), CVE.org (MITRE), GitHub Security Advisories, ENISA EUVD

    Affected products

    The following versions are affected. Older releases of the same product line are also vulnerable unless stated otherwise.

    Affected products
    Affected versionsFixed in
    motioneye-projectmotioneye
    • < 0.44.0
    • 0.44.0
    pypimotioneye
    • 0.40rc5
    • 0.31.4
    • 0.39.3
    • 0.37
    • 0.33.1
    • 0.43.1b5
    • 0.28.3
    • 0.28.1
    • 0.39
    • 0.39.2
    • 0.44.0b3
    • 0.42.1
    • 0.43.1b4
    • 0.40rc2
    • 0.29rc2
    • 0.29rc1
    • 0.31.2
    • 0.29
    • 0.27.1
    • 0.35
    • 0.29.1
    • 0.40rc1
    • 0.30
    • 0.35.1
    • 0.32.2
    • 0.35.2
    • 0.38.1
    • 0.31.5
    • 0.34
    • 0.32
    • 0.41rc1
    • 0.34rc1
    • 0.32.1
    • 0.28
    • 0.40
    • 0.40rc3
    • 0.30rc2
    • 0.36
    • 0.33.4
    • 0.41
    • 0.38
    • 0.36.1
    • 0.43.1b2
    • 0.31
    • 0.40rc4
    • 0.33.3
    • 0.43.1b1
    • —
    • —
    • —
    • —
    • —
    • —
    • —
    • —
    • —
    • —
    • —
    • —
    • —
    • —
    • —
    • —
    • —
    • —
    • —
    • —
    • —
    • —
    • —
    • —
    • —
    • —
    • —
    • —
    • —
    • —
    • —
    • —
    • —
    • —
    • —
    • —
    • —
    • —
    • —
    • —
    • —
    • —
    • —
    • —
    • —
    • —
    • —

    Vendors and products

    Weakness classes (CWE)

    • CWE-256Plaintext Storage of a Password

      Base

      The product stores a password in plaintext within resources such as memory or files.

      Entry at MITRE CWE-256

    • CWE-287Improper Authentication

      Class

      When an actor claims to have a given identity, the product does not prove or insufficiently proves that the claim is correct.

      Entry at MITRE CWE-287

    • CWE-328Use of Weak Hash

      Base

      The product uses an algorithm that produces a digest (output value) that does not meet security expectations for a hash function that allows an adversary to reasonably determine the original input (preimage attack), find another input that can produce the same hash (2nd preimage attack), or find multiple inputs that evaluate to the same hash (birthday attack).

      Entry at MITRE CWE-328

    • CWE-836Use of Password Hash Instead of Password for Authentication

      Base

      The product records password hashes in a data store, receives a hash of a password from a client, and compares the supplied hash to the hash obtained from the data store.

      Entry at MITRE CWE-836

    References & sources

    • github.commotioneye-project/motioneye/security/advisories/GHSA-r3cw-c95m-…web, x_refsource_CONFIRM, euvd
    • github.commotioneye-project/motioneyepackage
    • pypi.orgproject/motioneyepackage
    • GitHub Security Advisoriesadvisories/GHSA-r3cw-c95m-wfh9advisory
    • NVD (NIST)vuln/detail/CVE-2026-46488advisory
    • github.commotioneye-project/motioneye/pull/3332x_refsource_MISC, euvd
    • github.commotioneye-project/motioneye/commit/0d5cb9c238a87447dae29812e5bf…x_refsource_MISC, euvd
    • github.commotioneye-project/motioneye/releases/tag/0.44.0x_refsource_MISC, euvd

    Changes to this CVE

    Who changed this CVE and when: NVD (analysis, affected products, CVSS), the CVE publisher (CNA) and additional providers such as CISA (ADP).

    1. Record modifiedCISA ADP

      CISA assessment (SSVC): exploitation: proof of concept, automatable: yes

      Show 2 original changes
      Individual changes of this event as published by NVD
      TypeActionBeforeAfter
      Referenceadded
      —
      https://github.com/motioneye-project/motioneye/security/advisories/GHSA-r3cw-c95m-wfh9
      SSVC assessmentadded
      —
      {"id":"CVE-2026-46488","role":"CISA Coordinator","options":[{"exploitation":"poc"},{"automatable":"yes"},{"technicalImpact":"total"}],"version":"2.0.3","timestamp":"2026-09-17T16:14:49.348748Z"}

      Source identifier: 134c704f-9b21-4f2e-91b3-4a467353bcc0

    2. ReceivedGitHub

      CVSS V4.0: AV:N/AC:L/AT:P/PR:N/UI:N/VC:H/VI:H/VA:N/SC:N/SI:N/SA:N

      Weakness type: CWE-287, CWE-256, CWE-328, CWE-836

      Description added or changed

      Show 11 original changes
      Individual changes of this event as published by NVD
      TypeActionBeforeAfter
      Descriptionadded
      —
      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.
      CVSSadded
      —
      AV:N/AC:L/AT:P/PR:N/UI:N/VC:H/VI:H/VA:N/SC:N/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X
      Weakness type (CWE)added
      —
      CWE-287
      Weakness type (CWE)added
      —
      CWE-256
      Weakness type (CWE)added
      —
      CWE-328
      Weakness type (CWE)added
      —
      CWE-836
      Affected versions (publisher)added
      —
      New affected value received. <a href="https://github.com/CVEProject/cvelistV5/blob/main/cves/2026/46xxx/CVE-2026-46488.json">CVE-2026-46488</a>
      Referenceadded
      —
      https://github.com/motioneye-project/motioneye/commit/0d5cb9c238a87447dae29812e5bf2ccf323cf3dc
      Referenceadded
      —
      https://github.com/motioneye-project/motioneye/pull/3332
      Referenceadded
      —
      https://github.com/motioneye-project/motioneye/releases/tag/0.44.0
      Referenceadded
      —
      https://github.com/motioneye-project/motioneye/security/advisories/GHSA-r3cw-c95m-wfh9

      Source identifier: security-advisories@github.com

    Embed badge

    Show the severity and KEV status of this vulnerability on your site – with a link back here. The image is updated hourly.

    Badge preview for CVE-2026-46488
    <a href="https://intel.neosec.eu/en/cve/CVE-2026-46488"><img src="https://intel.neosec.eu/badge/cve/CVE-2026-46488.svg?lang=en" alt="CVE-2026-46488 – NEOSEC Intel" height="20"></a>