VulertSecurity VulertSecurity

Vulnerability Database · PyPI · Package report

future: vulnerability history, versions and safety

future is a package in the PyPI ecosystem. Vulert records 3 vulnerabilities for it across 52 releases, from Dec 2022 to Aug 2025. Each vulnerability names the versions it affects, the fixed version to move to, and a workaround where no fix has been published.

i
3 vulnerabilities recorded H2 U1
i
1 with no fix published

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

See the unfixed vulnerabilities →
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 future vulnerabilities

Vulert verdict on future 1.0.0 i

Updated on 23 Oct 2026

Careful: 1.0.0 has 1 known vulnerability, and 1 has no fix yet. Use an earlier safe version, or the workaround listed for each one.

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

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 1.0.0 — affected i
  • Vulnerabilities on record 3 over 2 years · 0 in the last year i
  • Latest disclosure 14 Aug 2025 i
  • Highest CVSS 7.5 i
  • With no published fix 1 i
  • Depended on by 7,637 packages i
  • Stars 1,192 i
  • OpenSSF scorecard 4/10 i
  • Last release 32 months ago i
  • Licence MIT 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 future, 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
1.0.0 21 Feb 2024 H1 MIT No Details →
0.18.3 13 Jan 2023 H1 MIT No Details →
0.18.2 31 Oct 2019 H2 U1 MIT No Details →
0.18.1 17 Oct 2019 H2 U1 MIT No Details →
0.18.0 10 Oct 2019 H2 U1 MIT No Details →
0.17.1 31 Oct 2018 H2 U1 MIT No Details →
0.17.0 25 Oct 2018 H2 U1 MIT No Details →
0.16.0 27 Oct 2016 H2 U1 MIT No Details →
0.15.2 11 Sep 2015 H2 U1 MIT No Details →
0.15.1 09 Sep 2015 H2 U1 MIT No Details →
0.15.0 25 Jul 2015 H2 U1 MIT No Details →
0.14.3 14 Dec 2014 H2 U1 MIT No Details →
0.14.2 21 Nov 2014 H2 U1 MIT No Details →
0.14.1 02 Oct 2014 H2 U1 MIT No Details →
0.14.0 02 Oct 2014 H2 U1 MIT No Details →
0.13.1 23 Sep 2014 H1 U1 MIT Yes Details →
0.13.0 13 Aug 2014 H1 U1 MIT Yes Details →
0.12.4 18 Jul 2014 H1 U1 MIT Yes Details →
0.12.3 19 Jun 2014 H1 U1 MIT Yes Details →
0.12.2 25 May 2014 H1 U1 MIT Yes Details →
0.12.1 14 May 2014 H1 U1 MIT Yes Details →
0.12.0 05 May 2014 H1 U1 MIT Yes Details →
0.11.4 24 Mar 2014 H1 U1 MIT Yes Details →
0.11.3 28 Feb 2014 H1 U1 MIT Yes Details →
0.11.2 28 Jan 2014 H1 U1 MIT Yes Details →
0.11.1 28 Jan 2014 H1 U1 MIT Yes Details →
0.11.0 28 Jan 2014 H1 U1 MIT Yes Details →
0.10.2 11 Jan 2014 H1 U1 MIT Yes Details →
0.10.1 07 Dec 2013 H1 U1 MIT Yes Details →
0.10.0 01 Dec 2013 H1 U1 MIT Yes Details →
0.9.0 15 Nov 2013 H1 U1 MIT Yes Details →
0.8.2 30 Oct 2013 H1 U1 MIT Yes Details →
0.8.1 29 Oct 2013 H1 U1 MIT Yes Details →
0.8.0 28 Oct 2013 H1 U1 MIT Yes Details →
0.7.0 24 Oct 2013 H1 U1 MIT Yes Details →
0.6.0 02 Oct 2013 H1 U1 MIT Yes Details →
0.5.2 24 Sep 2013 H1 U1 MIT Yes Details →
0.5.1 21 Sep 2013 H1 U1 MIT Yes Details →
0.5.0 18 Sep 2013 H1 U1 MIT Yes Details →
0.4.1 12 Sep 2013 H1 U1 MIT Yes Details →
0.4.0 09 Aug 2013 H1 U1 MIT Yes Details →
0.3.5 08 Aug 2013 H1 U1 MIT Yes Details →
0.3.4 08 Aug 2013 H1 U1 MIT Yes Details →
0.3.3 05 Aug 2013 H1 U1 MIT Yes Details →
0.3.2 04 Aug 2013 H1 U1 MIT Yes Details →
0.3.1 04 Aug 2013 H1 U1 MIT Yes Details →
0.3.0 28 Jul 2013 H1 U1 MIT Yes Details →
0.2.0 26 Jul 2013 H1 U1 MIT Yes Details →
0.1.0 22 Jul 2013 H1 U1 MIT Yes Details →
0.0.3 21 Jul 2013 H1 U1 MIT Yes Details →
0.0.2 20 Jul 2013 H1 U1 MIT Yes Details →
0.0.1 14 Jul 2013 H1 U1 MIT Yes Details →

All 52 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 2
  • 2025 1

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

03 Vulnerabilities

Recorded vulnerabilities for future

The 3 most severe of 3 vulnerabilities recorded for this package

Search all 3 in the database →
Vulnerability Severity Fixed version ↓ Disclosed ↓
CVE-2022-40899: Python Charmers Future Denial of Service Vulnerability 7.5 high 0.18.3 23 Dec 2022
CVE-2025-50817: Python-Future Module Arbitrary Code Execution via Unintended Import of test.py 7.3 high No fix published 14 Aug 2025
CVE-2022-40899: Denial of Service Vulnerability in Python Charmers Future N/A unrated 0.18.3 23 Dec 2022

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 future

Is future safe to use?

Vulert records 3 vulnerabilities for future in PyPI: 0 critical, 2 high, 0 medium and 0 low, plus 1 not yet rated. 1 of them has no published fix yet, so that is the one to avoid or mitigate.

What is future's Vulert package health score?

Vulert scores future 60/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 future affected?

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

Which version of future should I use?

1.0.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 future have?

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

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

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