# CVE-2026-55863: motionEye: Missing authentication on ActionHandler allows unauthenticated camera action execution > Unauthenticated attackers can trigger camera actions and execute configured scripts via the ActionHandler endpoint in motionEye. - **Severity:** Medium 5.3 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N`) - **Exploited in the wild:** Not known - **Login needed:** Not needed - **Attackable:** Over the internet - **Victim action needed:** Not needed - **Fix available:** Yes - **Published:** 15 Sep 2026 - **Updated:** 16 Sep 2026 - **Also known as:** GHSA-j67x-q29f-qcvv, PYSEC-2026-2665 ## What is CVE-2026-55863? CVE-2026-55863 is a medium-severity missing authorization vulnerability in motioneye-project motioneye, published on 15 Sep 2026. An attacker can exploit it over the internet without logging in, with no action from the victim. ### Official 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, the ActionHandler.post() method in motioneye/handlers/action.py lacks the BaseHandler.auth() decorator, allowing an unauthenticated remote attacker to send requests to /action//. The endpoint can trigger snapshot, record_start, and record_stop actions. When an administrator has configured action scripts, the same endpoint can invoke PTZ controls, alarm actions, lighting actions, and other predefined commands, and configured remote motionEye cameras can allow server-side requests to the remote camera service. This issue is fixed in version 0.44.0. Weakness: CWE-862 (Missing Authorization) ## Which versions are affected by CVE-2026-55863? 3 open source packages ship an affected version, including motioneye. | Package | Ecosystem | Affected | Fixed in | | --- | --- | --- | --- | | `motioneye` | PyPI | All versions | 0.44.0 | | `motioneye` | PyPI | All versions | 0.44.0 | | `motioneye` | PyPI | All versions | 0.44.0 | ## How do I fix CVE-2026-55863? Upgrade motioneye to 0.44.0 or later. ## Is CVE-2026-55863 being exploited? It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-55863 exists. ## Fix prompt for AI coding agents ```text Check this codebase for CVE-2026-55863 and fix it if it is affected. What it is: CVE-2026-55863 is a medium-severity missing authorization vulnerability in motioneye-project motioneye, published on 15 Sep 2026. An attacker can exploit it over the internet without logging in, with no action from the victim. Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-55863 exists. Affected packages and fixed versions: - motioneye (PyPI): affected all versions; fixed in 0.44.0 - motioneye (PyPI): affected all versions; fixed in 0.44.0 - motioneye (PyPI): affected all versions; fixed in 0.44.0 Task: 1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies. 2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it. 3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead. 4. Run the tests and summarise what changed and why. 5. If nothing in the project is affected, say so and change nothing. Reference: https://insights.sbomify.com/CVE-2026-55863/ (Markdown: https://insights.sbomify.com/CVE-2026-55863/index.md) ``` ## Sources - CVE record: https://www.cve.org/CVERecord?id=CVE-2026-55863 - NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-55863 - OSV: https://osv.dev/vulnerability/CVE-2026-55863 --- From sbomify Insights: https://insights.sbomify.com/CVE-2026-55863/ Summaries are generated and may contain mistakes; the official description above is the record.