CVE-2026-55863

MEDIUMPre-NVD 5.35.3—
EchelonGraph scoreMEDIUM confidence

This medium-severity CVE scores 5.3 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.3%, top 78% 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
Elevated
5.3EG
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 5.3Exploit: 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, 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.

CVSS v3
5.3
EG Score
5.3(medium)
EG Risk
55(Attend)
EG Risk 55/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
Severity53% × 45%
Exploitation40% × 40%
Automatability100% × 15%
Action: Remediate soon — notable exploitation risk.
EPSS PROB
0%
EPSS %ILE
22%
KEV
Not listed

Published

June 23, 2026

Last Modified

September 16, 2026

Advisory Details (3)

Auto-updated Sep 15, 2026
Patch available. Sources: github, github_pr, github_release.
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
github Patch Available

Missing authentication on ActionHandler allows unauthenticated camera action execution · Advisory · motioneye-project/motioneye · GitHub

https://github.com/motioneye-project/motioneye/security/advisories/GHSA-j67x-q29f-qcvv

Vendor Advisories for CVE-2026-55863(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(1)

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

Data Freshness Timeline

(refreshed 7× in last 7d / 7× 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 10:23 UTCEG score recompute
  3. 2026-09-17 19:31 UTCEPSS rescore
  4. 2026-09-16 15:33 UTCEG score recompute
  5. 2026-09-16 15:06 UTCEG score recompute
  6. 2026-09-16 14:08 UTCEPSS rescore
  7. 2026-09-15 17:34 UTCEG score recompute
  8. 2026-07-31 04:11 UTCEG score recompute
  9. 2026-07-26 15:51 UTCEG score recompute
  10. 2026-07-23 03:20 UTCEG score recompute
  11. 2026-06-23 19:21 UTCEG score recompute

Frequently asked(5)

What is CVE-2026-55863?
CVE-2026-55863 is a medium vulnerability published on June 23, 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, the ActionHandler.post() method in motioneye/handlers/action.py lacks the BaseHandler.auth() decorator, allowing an unauthenticated remote…
When was CVE-2026-55863 disclosed?
CVE-2026-55863 was first published in the National Vulnerability Database on June 23, 2026, with the most recent update on September 16, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-55863 actively exploited?
CVE-2026-55863 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 78.3% of all scored CVEs.
What is the CVSS score of CVE-2026-55863?
CVE-2026-55863 has a CVSS v3 base score of 5.3 (NVD).
How do I remediate CVE-2026-55863?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-55863, 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-55863

Explore →

Is Your Infrastructure Affected by CVE-2026-55863?

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

Start Free Scan →Browse All CVEs