VulertSecurity VulertSecurity

Vulnerability Database · PyPI · Package report

supervisor: vulnerability history, versions and safety

supervisor is a package in the PyPI ecosystem. Vulert records 4 vulnerabilities for it across 30 releases, from Aug 2017 to May 2022. Each vulnerability names the versions it affects, the fixed version to move to, and a workaround where no fix has been published.

i
4 vulnerabilities recorded H1 U3
i
0 with no fix published

Every vulnerability has a patched version to move to.

i
0 in the last 12 months

Nothing new recorded in the last year.

See the disclosure history →
i
0 malicious-package vulnerabilities

No published version shipped hostile code.

See all supervisor vulnerabilities

Vulert verdict on supervisor 4.3.0 i

Updated on 23 Oct 2026

Good news: 4.3.0, the version you would install today, has no known vulnerabilities. Older releases do — the table below lists all 4.

Package health score 73/100
  • Security Minor issues
  • Maintenance Maintaining
  • Popularity Widely used
  • Community Quiet

What to do: Stay on 4.3.0 or newer. This can change: a vulnerability disclosed tomorrow can affect 4.3.0 too — Vulert watches the package and alerts you if that happens. Monitor it with Vulert →

  • Current release 4.3.0 — unaffected i
  • Vulnerabilities on record 4 over 4 years · 0 in the last year i
  • Latest disclosure 13 May 2022 i
  • Highest CVSS 8.8 i
  • With no published fix 0 i
  • Depended on by 191 packages i
  • Stars 9,144 i
  • OpenSSF scorecard 2/10 i
  • Last release 13 months ago i
  • Licence non-standard i

Version list, release dates, licence and dependants published by PyPI, refreshed 22 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 supervisor, 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
4.3.0 23 Aug 2025 none non-standard — Details →
4.2.5 24 Dec 2022 none non-standard — Details →
4.2.4 30 Dec 2021 none non-standard — Details →
4.2.3 27 Dec 2021 none non-standard — Details →
4.2.2 26 Feb 2021 none non-standard — Details →
4.2.1 20 Aug 2020 none non-standard — Details →
4.2.0 30 Apr 2020 none non-standard — Details →
4.1.0 19 Oct 2019 none non-standard — Details →
4.0.4 15 Jul 2019 none non-standard — Details →
4.0.3 22 May 2019 none non-standard — Details →
4.0.2 17 Apr 2019 U2 non-standard Yes Details →
4.0.1 10 Apr 2019 U2 non-standard Yes Details →
4.0.0 05 Apr 2019 U2 non-standard Yes Details →
3.4.0 05 Apr 2019 U2 non-standard Yes Details →
3.3.5 22 Dec 2018 U2 non-standard Yes Details →
3.3.4 15 Feb 2018 U2 non-standard Yes Details →
3.3.3 24 Jul 2017 U2 non-standard Yes Details →
3.2.4 24 Jul 2017 U2 non-standard Yes Details →
3.1.4 24 Jul 2017 U2 non-standard Yes Details →
3.0.1 24 Jul 2017 U2 non-standard Yes Details →
3.3.2 03 Jun 2017 U3 non-standard Yes Details →
3.3.1 03 Aug 2016 U3 non-standard Yes Details →
3.3.0 14 May 2016 U3 non-standard Yes Details →
3.2.3 20 Mar 2016 U3 non-standard Yes Details →
3.2.2 04 Mar 2016 U3 non-standard Yes Details →
3.2.1 06 Feb 2016 U3 non-standard Yes Details →
3.2.0 01 Dec 2015 U3 non-standard Yes Details →
3.1.3 28 Oct 2014 U3 non-standard Yes Details →
3.1.2 07 Sep 2014 U3 non-standard Yes Details →
3.1.1 11 Aug 2014 U3 non-standard Yes Details →
3.1.0 29 Jul 2014 U3 non-standard Yes Details →
3.0.0 31 Jul 2013 H1 U3 non-standard Yes Details →
3.0.0b2 29 May 2013 H1 U3 non-standard Yes Details →
3.0.0b1 11 Sep 2012 H1 U3 non-standard Yes Details →
3.0.0a12 07 Dec 2011 H1 U3 non-standard Yes Details →
3.0.0a11 07 Dec 2011 H1 U3 non-standard Yes Details →
3.0.0a10 30 Mar 2011 H1 U3 non-standard Yes Details →
3.0.0a9 13 Aug 2010 H1 U3 non-standard Yes Details →
3.0.0a8 20 Jan 2010 H1 U3 non-standard Yes Details →
3.0.0a7 24 May 2009 H1 U3 non-standard Yes Details →

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

02 Disclosure history

How often vulnerabilities are recorded

  • 2017 1
  • 2019 2
  • 2022 1

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

03 Vulnerabilities

Recorded vulnerabilities for supervisor

The 4 most severe of 4 vulnerabilities recorded for this package

Search all 4 in the database →
Vulnerability Severity Fixed version ↓ Disclosed ↓
CVE-2017-11610: Incorrect Default Permissions in Supervisor 8.8 high 3.0.1 13 May 2022
CVE-2017-11610: XML-RPC Command Execution in supervisor N/A unrated 3.0.1 23 Aug 2017
CVE-2019-12105: Supervisor - Unauthenticated User Log File Read or Service Restart N/A unrated 4e334d9cf2a1daff685893e35e72398437df3dcb 10 Sep 2019
CVE-2019-12105: Supervisor - Unauthenticated User Can Read Log Files or Restart Service N/A unrated 4e334d9cf2a1daff685893e35e72398437df3dcb 10 Sep 2019

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 supervisor

Is supervisor safe to use?

Vulert records 4 vulnerabilities for supervisor in PyPI: 0 critical, 1 high, 0 medium and 0 low, plus 3 not yet rated. Every one of them has a published fix, so the practical answer is to run a supported release and keep it patched.

What is supervisor's Vulert package health score?

Vulert scores supervisor 73/100, which reads as in good shape. 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).

Is the latest version of supervisor affected?

No. 4.3.0, the version you would install today, has no vulnerabilities on record against it. Earlier releases do — the version table above lists each release with what affects it.

Which version of supervisor should I use?

4.3.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 supervisor have?

4 vulnerabilities are recorded for supervisor in the PyPI ecosystem: 0 critical, 1 high, 0 medium and 0 low, plus 3 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 supervisor vulnerabilities disclosed?

0 vulnerabilities were recorded for supervisor in the last 12 months, and the oldest entry in this database dates to 23 Aug 2017. 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 supervisor 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 supervisor for upcoming vulnerabilities?

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