Is CVE-2026-55863 exploited in the wild?

No. Junglewise Threat Intelligence has no report of CVE-2026-55863 being exploited in the wild.

How severe is CVE-2026-55863?

Medium severity, with a CVSS score of 5.3, published 15 September 2026.

Which products and versions are affected?

motioneye (PyPI) < 0.44.0, ECOSYSTEM:introduced=0,fixed=0.44.0.

Is there a fix for CVE-2026-55863?

Yes. motioneye (PyPI): upgrade to 0.44.0 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.

How is CVE-2026-55863 attacked?

It is attacked over the network, in a network appliance.

Am I affected by CVE-2026-55863?

Check whether you run motioneye (PyPI) at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

CVE-2026-55863: motionEye missing authentication in ActionHandler

Q: Which products and versions are affected?

motioneye (PyPI) < 0.44.0, ECOSYSTEM:introduced=0,fixed=0.44.0.

Q: Is there a fix for CVE-2026-55863?

Yes. motioneye (PyPI): upgrade to 0.44.0 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.

Q: How is CVE-2026-55863 attacked?

It is attacked over the network, in a network appliance.

Q: Am I affected by CVE-2026-55863?

Check whether you run motioneye (PyPI) at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

CVE-2026-55863 · Severity: medium · CVSS 5.3 · Published 2026-09-15

motionEye is a web-based interface for managing video surveillance cameras. A security flaw allows unauthorized individuals to remotely trigger camera actions such as taking snapshots, starting or stopping recordings, and controlling physical hardware like alarms or camera movement. This could lead to a breach of physical security or unauthorized monitoring of a facility.

Technologies: motioneye (PyPI). Vendors: PyPI.

Quick answers

Is CVE-2026-55863 exploited in the wild?: No. Junglewise Threat Intelligence has no report of CVE-2026-55863 being exploited in the wild.
How severe is CVE-2026-55863?: Medium severity, with a CVSS score of 5.3, published 15 September 2026.
Which products and versions are affected?: motioneye (PyPI) < 0.44.0, ECOSYSTEM:introduced=0,fixed=0.44.0.
Is there a fix for CVE-2026-55863?: Yes. motioneye (PyPI): upgrade to 0.44.0 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
How is CVE-2026-55863 attacked?: It is attacked over the network, in a network appliance.
Am I affected by CVE-2026-55863?: Check whether you run motioneye (PyPI) at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

How to fix

motioneye (PyPI): upgrade to 0.44.0 or later
```
pip install "motioneye>=0.44.0"
```

Technical details

The ActionHandler.post() method in motioneye/handlers/action.py lacks the @BaseHandler.auth() decorator, resulting in a missing authorization vulnerability (CWE-862). An unauthenticated attacker can send a POST request to the /action/ endpoint to trigger camera functions including snapshots, recording, and PTZ controls. If custom action scripts are configured, this can also lead to the execution of predefined shell scripts. The vulnerability is confirmed in version 0.43.1 and addressed in version 0.44.0.

Affected products

motioneye-project motioneye < 0.44.0

Identifiers

CVE-2026-55863
GHSA-j67x-q29f-qcvv
PYSEC-2026-2665

Timeline

2026-06-20: disclosed
2026-06-23: advisory: GitHub Advisory published

References

This page as Markdown. Free to reuse under CC BY 4.0 with a link back.