VulertSecurity VulertSecurity

Vulnerability Database · PyPI · Package report

tweepy: vulnerability history, versions and safety

tweepy is a package in the PyPI ecosystem. Vulert records 2 vulnerabilities for it across 58 releases, from Nov 2012 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
2 vulnerabilities recorded M1 U1
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 tweepy vulnerabilities

Vulert verdict on tweepy 4.17.0 i

Updated on 23 Oct 2026

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

Package health score 84/100
  • Security Minor issues
  • Maintenance Sustainable
  • Popularity Key ecosystem project
  • Community Moderate

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

  • Current release 4.17.0 — unaffected i
  • Vulnerabilities on record 2 over 9 years · 0 in the last year i
  • Latest disclosure 17 May 2022 i
  • Highest CVSS 5.3 i
  • With no published fix 0 i
  • Depended on by 306 packages i
  • Stars 11,186 i
  • OpenSSF scorecard 3/10 i
  • Last release 3 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 tweepy, 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.17.0 02 Jul 2026 none MIT — Details →
4.16.0 22 Jun 2025 none MIT — Details →
4.15.0 15 Jan 2025 none MIT — Details →
4.14.0 24 Apr 2023 none MIT — Details →
4.13.0 09 Mar 2023 none MIT — Details →
4.12.1 06 Nov 2022 none MIT — Details →
4.12.0 28 Oct 2022 none MIT — Details →
4.11.0 24 Oct 2022 none MIT — Details →
4.10.1 23 Aug 2022 none MIT — Details →
4.10.0 20 May 2022 none MIT — Details →
4.9.0 05 May 2022 none MIT — Details →
4.8.0 24 Mar 2022 none MIT — Details →
4.7.0 17 Mar 2022 none MIT — Details →
4.6.0 24 Feb 2022 none MIT — Details →
4.5.0 25 Jan 2022 none MIT — Details →
4.4.0 17 Nov 2021 none MIT — Details →
4.3.0 03 Nov 2021 none MIT — Details →
4.2.0 29 Oct 2021 none MIT — Details →
4.1.0 07 Oct 2021 none MIT — Details →
4.0.1 01 Oct 2021 none MIT — Details →
4.0.0 25 Sep 2021 none MIT — Details →
3.10.0 26 Dec 2020 none MIT — Details →
3.9.0 11 Jul 2020 none MIT — Details →
3.8.0 15 Jul 2019 none MIT — Details →
3.7.0 28 Nov 2018 none MIT — Details →
3.6.0 02 Mar 2018 none MIT — Details →
3.5.0 20 Nov 2015 none MIT — Details →
3.4.0 14 Aug 2015 none MIT — Details →
3.3.0 21 Feb 2015 none MIT — Details →
3.2.0 28 Jan 2015 none MIT — Details →
3.1.0 01 Dec 2014 none MIT — Details →
3.0.0 30 Nov 2014 none MIT — Details →
2.3.0 27 Apr 2014 M1 U1 MIT Yes Details →
2.2.0 20 Jan 2014 M1 U1 MIT Yes Details →
2.1.0 14 Jul 2013 M1 U1 MIT Yes Details →
2.0.0 10 Feb 2013 M1 U1 MIT Yes Details →
1.13.0 17 Jan 2013 M1 U1 MIT Yes Details →
1.12.0 08 Nov 2012 M1 U1 MIT Yes Details →
1.11.0 15 Aug 2012 M1 U1 MIT Yes Details →
1.10.0 09 Jul 2012 M1 U1 MIT Yes Details →
1.9.0 17 Mar 2012 M1 U1 MIT Yes Details →
1.8.0 01 Nov 2011 M1 U1 MIT Yes Details →
1.7.1 25 May 2010 M1 U1 MIT Yes Details →
1.6.0 19 Mar 2010 M1 U1 MIT Yes Details →
1.5.0 13 Jan 2010 M1 U1 MIT Yes Details →
1.4.0 10 Dec 2009 M1 U1 MIT Yes Details →
1.3.0 14 Nov 2009 M1 U1 MIT Yes Details →
1.2.0 19 Oct 2009 M1 U1 MIT Yes Details →
1.1.0 14 Oct 2009 M1 U1 MIT Yes Details →
1.1-py2.5 — M1 U1 — Yes Details →
1.1-py2.6 — M1 U1 — Yes Details →
1.10-py2.5 — M1 U1 — Yes Details →
1.10-py2.6 — M1 U1 — Yes Details →
1.10-py2.7 — M1 U1 — Yes Details →
1.13-py2.6 — M1 U1 — Yes Details →
1.13-py2.7 — M1 U1 — Yes Details →
1.2-py2.4 — M1 U1 — Yes Details →
1.2-py2.5 — M1 U1 — Yes Details →
1.2-py2.6 — M1 U1 — Yes Details →
1.2.win32-py2.5 — M1 U1 — Yes Details →
1.3-py2.4 — M1 U1 — Yes Details →
1.3-py2.5 — M1 U1 — Yes Details →
1.3-py2.6 — M1 U1 — Yes Details →
1.4-py2.4 — M1 U1 — Yes Details →
1.4-py2.5 — M1 U1 — Yes Details →
1.4-py2.6 — M1 U1 — Yes Details →
1.5-py2.4 — M1 U1 — Yes Details →
1.5-py2.5 — M1 U1 — Yes Details →
1.5-py2.6 — M1 U1 — Yes Details →
1.6-py2.4 — M1 U1 — Yes Details →
1.6-py2.5 — M1 U1 — Yes Details →
1.6-py2.6 — M1 U1 — Yes Details →
1.7.1-py2.4 — M1 U1 — Yes Details →
1.7.1-py2.5 — M1 U1 — Yes Details →
1.7.1-py2.6 — M1 U1 — Yes Details →
1.8-py2.5 — M1 U1 — Yes Details →
1.8-py2.6 — M1 U1 — Yes Details →
1.8-py2.7 — M1 U1 — Yes Details →
1.9-py2.5 — M1 U1 — Yes Details →
1.9-py2.6 — M1 U1 — Yes Details →
1.9-py2.7 — M1 U1 — Yes Details →
2.0-py2.6 — M1 U1 — Yes Details →
2.0-py2.7 — M1 U1 — Yes Details →
2.1-py2.6 — M1 U1 — Yes Details →
2.1-py2.7 — M1 U1 — Yes Details →
2.2-py2.6 — M1 U1 — Yes Details →
2.2-py2.7 — M1 U1 — Yes Details →
2.3.0-py2.6 — M1 U1 — Yes Details →
2.3.0-py2.7 — M1 U1 — Yes Details →
3.0.linux-x86_64 — M1 — Yes Details →

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

02 Disclosure history

How often vulnerabilities are recorded

  • 2012 1
  • 2022 1

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

03 Vulnerabilities

Recorded vulnerabilities for tweepy

The 2 most severe of 2 vulnerabilities recorded for this package

Search all 2 in the database →
Vulnerability Severity Fixed version ↓ Disclosed ↓
CVE-2012-5825: Tweepy SSL Server Spoofing Vulnerability 5.3 medium 3.0 17 May 2022
CVE-2012-5825: Tweepy SSL Server Spoofing Vulnerability N/A unrated 2.3.1 04 Nov 2012

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 tweepy

Is tweepy safe to use?

Vulert records 2 vulnerabilities for tweepy in PyPI: 0 critical, 0 high, 1 medium and 0 low, plus 1 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 tweepy's Vulert package health score?

Vulert scores tweepy 84/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 tweepy affected?

No. 4.17.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 tweepy should I use?

4.17.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 tweepy have?

2 vulnerabilities are recorded for tweepy in the PyPI ecosystem: 0 critical, 0 high, 1 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 tweepy vulnerabilities disclosed?

0 vulnerabilities were recorded for tweepy in the last 12 months, and the oldest entry in this database dates to 04 Nov 2012. 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 tweepy 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 tweepy for upcoming vulnerabilities?

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