Live Exposure Defense: From CVE to Confirmed Exposure in 12 Hours – See more

New CVE Detected

CVE-2026-55488 – Unauthenticated Arbitrary File Read – motionEye prior to 0.44.0

Be the first to know when new zero-days emerge:

Summary

CVE-2026-55488 is a high-severity absolute path traversal vulnerability in motionEye (mEye), a web-based surveillance camera management interface, affecting all versions prior to 0.44.0. The flaw allows unauthenticated remote attackers to read arbitrary files from the host filesystem by supplying absolute paths to media file handler endpoints. It carries a CVSS 4.0 score of 7.7 (High) and a public proof-of-concept is available.

Technical details

  • Root cause: Multiple media file handlers invoke mediafiles.get_media_path(), which constructs filesystem paths using Python’s os.path.join(target_dir, path). When an attacker supplies an absolute path as the filename parameter, Python discards the configured media directory prefix entirely and returns the attacker-supplied path directly.
  • Tornado bypass: The application overrides Tornado’s built-in path safety methods — get_absolute_path() and validate_absolute_path() — in the MoviePlaybackHandler without implementing equivalent security checks, nullifying the web framework’s protections.
  • Affected endpoints: GET /movie/<camera_id>/playback/, GET /movie/<camera_id>/download/, GET /picture/<camera_id>/download/, and GET /picture/<camera_id>/preview/.
  • Attack vector: Network-reachable, no authentication required (Privileges Required: None), no user interaction needed.
  • Impact: Unauthenticated reading of arbitrary files from the filesystem, constrained only by the OS-level permissions of the motionEye process. Accessible sensitive files include system credential and configuration files.

Affected software

  • motionEye (motioneye-project/motioneye) — all versions prior to 0.44.0

Severity

  • CVSS 4.0 Base Score: 7.7 (High)
  • Vector: CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N/E:P
  • Weakness: CWE-22 – Improper Limitation of a Pathname to a Restricted Directory (Path Traversal)

Mitigation and recommended actions

  • Immediate: Upgrade motionEye to version 0.44.0 or later, which resolves the issue by rejecting absolute paths in user input and ensuring resolved canonical paths remain within the configured media directory.
  • If immediate patching is not possible: Restrict network access to the motionEye web interface — place it behind a firewall or VPN to prevent direct internet exposure. Additionally, ensure the motionEye process runs under a dedicated least-privilege user account rather than root, to limit the scope of readable files.

IONIX Status

The IONIX research team is tracking ongoing exploitation attempts and recommends immediate patching. Potentially affected assets are outlined in this post.

References

Are you exposed?

Get a free report of your organization’s exposure to this CVE and threat

How IONIX’s External Exposure Management Platform Detects and Validates
Zero-Days to Shrink MTTR

1

Map your entire attack surface (continously)

IONIX uses multi-factor discovery methods, including DNS analysis, certificate mapping, metadata inspection, and more, to automatically map every internet-facing asset across your environment. This includes cloud instances, third-party platforms, shadow IT, and even forgotten infrastructure that traditional tools miss.

2

Monitor for new CVEs

Dozens of threat intel feeds using agentic technology are continuously analyzed to detect the appearance of proof-of-concept code, exploit kits, and indicators of active targeting. IONIX goes further by applying AI to proactively evaluate whether emerging vulnerabilities are likely to be exploited, even before PoCs go public.

3

Identify Potential External Exposures

Not all CVEs matter. IONIX filters vulnerabilities by asking attacker-centric questions: Can it be reached from the internet? Does it require authentication? Is it being exploited in the wild? This dramatically reduces noise and focuses teams on threats that can actually be weaponized.

4

Create Safe, Scalable Exploit Validations

IONIX transforms real-world PoCs into safe, non-intrusive test payloads that can be run in production environments without disruption. These simulations are precisely targeted to the systems that are vulnerable, ensuring rapid validation without unnecessary load.

5

Execute Exploit Validations

By combining context about software stack, versioning, exposure status, and reachability, IONIX ensures that only the right payloads are executed against the right assets, maximizing efficiency and minimizing risk.

6

Drive Fast and Actionable Remediation

Results are routed through integrations with ticketing, SOAR, and SIEM tools. Issues are written in plain language, bundled into remediation clusters, and prioritized based on asset criticality, exploitability, and blast radius. This shortens mean time to remediation (MTTR) and empowers teams to act with confidence.

Are you exposed?

Get a free report of your organization’s exposure to this CVE and threat

Subscribe to Threat Center RSS

Copy/paste the link below into your preferred RSS reader or follow these instructions to subscribe to Slack alerts.

Get Real-Time CVE Alerts to Your Email

Be the first to know when new zero-days emerge