VulertSecurity VulertSecurity

Vulnerability Database · PyPI · Package report

motioneye: vulnerability history, versions and safety

motioneye is a package in the PyPI ecosystem. Vulert records 21 vulnerabilities for it across 67 releases, from Feb 2022 to Jul 2026. Each vulnerability names the versions it affects, the fixed version to move to, and a workaround where no fix has been published.

i
21 vulnerabilities recorded C3 H6 M3 U9
i
3 with no fix published

No patched version yet — these are the ones to plan around.

See the unfixed vulnerabilities →
i
15 in the last 12 months

Most recent disclosure 13 Jul 2026.

See the disclosure history →
i
0 malicious-package vulnerabilities

No published version shipped hostile code.

See all motioneye vulnerabilities

Vulert verdict on motioneye 0.44.0 i

Updated on 23 Oct 2026

Careful: 0.44.0 has 3 known vulnerabilities, and 3 have no fix yet. Use an earlier safe version, or the workaround listed for each one.

Package health score 54/100
  • Security Unfixed issues
  • Maintenance Sustainable
  • Popularity Niche
  • Community Active

The current release has a vulnerability with no published fix, which caps this score.

What to do: Pin an earlier, unaffected release if you can, and apply the workaround each vulnerability lists until a fix is published. No fix yet: Vulert alerts you the moment one is published. Monitor it with Vulert →

  • Current release 0.44.0 — affected i
  • Vulnerabilities on record 21 over 4 years · 15 in the last year i
  • Latest disclosure 13 Jul 2026 i
  • Highest CVSS 10.0 i
  • With no published fix 3 i
  • Stars 4,717 i
  • Last release 4 months ago i
  • Licence GPL-3.0-or-later i

Version list, release dates, licence and dependants published by PyPI, refreshed 23 Oct 2026. Licence information is not legal advice.

Concerned about your application's security?

Vulert continues monitoring your dependencies and alerts you when new vulnerabilities are disclosed. No installation and no source-code access required.

01 Versions

Which versions are affected

Every version Vulert tracks for motioneye, newest first, with the vulnerabilities recorded against each one. A version showing none has no vulnerability in the Vulert database — open it for the full picture on that release.

i
Version Released Vulert vulnerabilities Licence Fix published Details
0.44.0 20 Jun 2026 H2 U1 GPL-3.0-or-later No Details →
0.44.0b3 19 Jun 2026 C3 H1 M3 U5 GPL-3.0-or-later Yes Details →
0.44.0b2 23 May 2026 C3 H1 M3 U5 GPL-3.0-or-later Yes Details →
0.44.0b1 11 Mar 2026 C3 H1 M3 U5 GPL-3.0-or-later Yes Details →
0.43.1 27 Dec 2025 C3 H1 M3 U5 GPL-3.0-or-later Yes Details →
0.43.1b5 01 Nov 2025 C3 H2 M3 U5 GPL-3.0-or-later No Details →
0.43.1b4 14 May 2025 C3 H3 M3 U6 GPL-3.0 No Details →
0.43.1b3 02 May 2025 C3 H4 M3 U7 GPL-3.0 No Details →
0.43.1b2 30 Jun 2024 C3 H4 M3 U7 GPL-3.0 No Details →
0.43.1b1 24 Dec 2023 C3 H4 M3 U7 GPL-3.0 No Details →
0.42.1 06 Jun 2020 C3 H5 M3 U8 GPL-3.0 No Details →
0.42.0 15 Dec 2019 C3 H5 M3 U8 GPL-3.0 No Details →
0.41.0 29 Aug 2019 C3 H5 M3 U8 GPL-3.0 No Details →
0.41.0rc1 11 Aug 2019 C3 H5 M3 U8 GPL-3.0 No Details →
0.40.0 27 Apr 2019 C3 H5 M3 U8 GPL-3.0 No Details →
0.40.0rc5 20 Mar 2019 C3 H5 M3 U8 GPL-3.0 No Details →
0.40.0rc4 18 Mar 2019 C3 H5 M3 U8 GPL-3.0 No Details →
0.40.0rc3 11 Mar 2019 C3 H5 M3 U8 GPL-3.0 No Details →
0.40.0rc2 10 Mar 2019 C3 H5 M3 U8 GPL-3.0 No Details →
0.40.0rc1 07 Mar 2019 C3 H5 M3 U8 GPL-3.0 No Details →
0.39.3 29 Jul 2018 C3 H5 M3 U8 GPL-3.0 No Details →
0.39.2 24 Jun 2018 C3 H5 M3 U8 GPL-3.0 No Details →
0.39.1 02 Jun 2018 C3 H5 M3 U8 GPL-3.0 No Details →
0.39.0 31 Mar 2018 C3 H5 M3 U8 GPL-3.0 No Details →
0.38.1 23 Feb 2018 C3 H5 M3 U8 GPL-3.0 No Details →
0.38.0 31 Oct 2017 C3 H5 M3 U8 GPL-3.0 No Details →
0.37.1 09 Sep 2017 C3 H5 M3 U8 GPL-3.0 No Details →
0.37.0 26 Aug 2017 C3 H5 M3 U8 GPL-3.0 No Details →
0.37.0rc1 05 Aug 2017 C3 H5 M3 U8 GPL-3.0 No Details →
0.36.1 06 Jul 2017 C3 H5 M3 U8 GPL-3.0 No Details →
0.36.0 10 Jun 2017 C3 H5 M3 U8 GPL-3.0 No Details →
0.35.2 11 Feb 2017 C3 H5 M3 U8 GPL-3.0 No Details →
0.35.1 24 Nov 2016 C3 H5 M3 U8 GPL-3.0 No Details →
0.35.0 03 Nov 2016 C3 H5 M3 U8 GPL-3.0 No Details →
0.35.0rc1 01 Nov 2016 C3 H5 M3 U8 GPL-3.0 No Details →
0.34.1 26 Oct 2016 C3 H5 M3 U8 GPL-3.0 No Details →
0.34.0 25 Oct 2016 C3 H5 M3 U8 GPL-3.0 No Details →
0.34.0rc1 04 Oct 2016 C3 H5 M3 U8 GPL-3.0 No Details →
0.33.4 13 Sep 2016 C3 H5 M3 U8 GPL-3.0 No Details →
0.33.3 12 Sep 2016 C3 H5 M3 U8 GPL-3.0 No Details →
0.33.2 20 Aug 2016 C3 H5 M3 U8 GPL-3.0 No Details →
0.33.1 14 Aug 2016 C3 H5 M3 U8 GPL-3.0 No Details →
0.33.0 31 Jul 2016 C3 H5 M3 U8 GPL-3.0 No Details →
0.32.2 04 Jul 2016 C3 H5 M3 U8 GPL-3.0 No Details →
0.32.1 02 Jul 2016 C3 H5 M3 U8 GPL-3.0 No Details →
0.32.0 12 Jun 2016 C3 H5 M3 U8 GPL-3.0 No Details →
0.31.5 18 May 2016 C3 H5 M3 U8 GPL-3.0 No Details →
0.31.4 18 Mar 2016 C3 H5 M3 U8 GPL-3.0 No Details →
0.31.3 06 Mar 2016 C3 H5 M3 U8 GPL-3.0 No Details →
0.31.2 04 Mar 2016 C3 H5 M3 U8 GPL-3.0 No Details →
0.31.1 28 Feb 2016 C3 H5 M3 U8 GPL-3.0 No Details →
0.31.0 21 Feb 2016 C3 H5 M3 U8 GPL-3.0 No Details →
0.30.0 26 Dec 2015 C3 H5 M3 U8 GPL-3.0 No Details →
0.30.0rc2 20 Dec 2015 C3 H5 M3 U8 GPL-3.0 No Details →
0.30.0rc1 13 Dec 2015 C3 H5 M3 U8 GPL-3.0 No Details →
0.29.1 12 Dec 2015 C3 H5 M3 U8 GPL-3.0 No Details →
0.29.0 03 Dec 2015 C3 H5 M3 U8 GPL-3.0 No Details →
0.29.0rc2 27 Nov 2015 C3 H5 M3 U8 GPL-3.0 No Details →
0.29.0rc1 26 Nov 2015 C3 H5 M3 U8 GPL-3.0 No Details →
0.28.3 01 Nov 2015 C3 H5 M3 U8 GPL-3.0 No Details →
0.28.2 20 Oct 2015 C3 H5 M3 U8 GPL-3.0 No Details →
0.28.1 12 Oct 2015 C3 H5 M3 U8 GPL-3.0 No Details →
0.28.0 04 Oct 2015 C3 H5 M3 U8 GPL-3.0 No Details →
0.27.0.post1 — C3 H5 M3 U8 GPL-3.0 No Details →
0.27.1.post1 — C3 H5 M3 U8 GPL-3.0 No Details →
0.27.1.post2 — C3 H5 M3 U8 GPL-3.0 No Details →
0.27.2.post2 — C3 H5 M3 U8 GPL-3.0 No Details →

All 67 versions Vulert tracks for this package. Severity counts are the vulnerabilities recorded against that exact release.

02 Disclosure history

How often vulnerabilities are recorded

  • 2022 3
  • 2025 4
  • 2026 14

Counted by the year Vulert recorded each vulnerability — the same date the table below shows as disclosed. 15 of the 21 were recorded in the last 12 months.

03 Vulnerabilities

Recorded vulnerabilities for motioneye

The 5 most severe of 21 vulnerabilities recorded for this package

Search all 21 in the database →
Vulnerability Severity Fixed version ↓ Disclosed ↓
Critical Partial Authentication Bypass in motionEye: Unauthenticated Admin Credential Theft via Path Traversal 10.0 critical 0.44.0 23 Jun 2026
Critical Remote Code Execution Vulnerability in motionEye: LFI and Unsafe Config Restore 9.8 critical 0.44.0 23 Jun 2026
CVE-2026-46488: motionEye Authentication Bypass via Password Hash Manipulation 9.1 critical 0.44.0 22 Jun 2026
CVE-2026-46488: motionEye Authentication Bypass via Password Hash Manipulation 9.1 critical 0.44.0 29 Jun 2026
CVE-2025-47782: motionEye RCE Vulnerability in add_camera Function 8.9 high 0.43.1b4 15 May 2025

Vulnerability wrong, a fix missing, or a package we should cover? Report it and we will fix the record. Report Vulnerability Provide Feedback

Updated: 23/Oct/2026 · Vulnerabilities in our DB: 524315

Subscribe to Vulert on Telegram
Daily digest of new CVEs, critical and high severity, affected packages and fixes — plus a weekly roundup.
Join the channel →

Questions

About motioneye

Is motioneye safe to use?

Vulert records 21 vulnerabilities for motioneye in PyPI: 3 critical, 6 high, 3 medium and 0 low, plus 9 not yet rated. 3 of them have no published fix yet, so those are the ones to avoid or mitigate.

What is motioneye's Vulert package health score?

Vulert scores motioneye 54/100, which reads as usable, but worth attention. The score weighs the vulnerability record (40), maintenance and release cadence (25), adoption from dependents and stars (20) and community signals such as the OpenSSF scorecard and forks (15). The current release has a vulnerability with no published fix, which caps this score.

Is the latest version of motioneye affected?

Yes. 0.44.0, the version you would install today, has 3 known vulnerabilities, and 3 has no published fix yet. Use an earlier unaffected release, or the workaround each vulnerability lists.

Which version of motioneye should I use?

0.44.0 is the version Vulert recommends for the affected releases. The version table above lists every release with the vulnerabilities recorded against it, so you can confirm the range you actually run.

How many vulnerabilities does motioneye have?

21 vulnerabilities are recorded for motioneye in the PyPI ecosystem: 3 critical, 6 high, 3 medium and 0 low, plus 9 not yet rated. The ledger on this page lists the same counts next to the date of the most recent disclosure.

How often are new motioneye vulnerabilities disclosed?

15 vulnerabilities were recorded for motioneye in the last 12 months, and the oldest entry in this database dates to 01 Feb 2022. Recency matters more than a lifetime total: it shows how actively new issues are being disclosed for the package you are considering.

Which versions of motioneye are affected?

Each vulnerability on this page lists the affected version range and the fixed version to move to. Open the vulnerability for the version you actually run — fixes are specific to a release line, not to the package as a whole.

How do I monitor motioneye for upcoming vulnerabilities?

Upload the manifest or SBOM for your application at vulert.com/scanner and Vulert keeps checking the motioneye version you actually run against new disclosures, then alerts you when one affects it. There is no installation and no source-code access required.