VulertSecurity VulertSecurity

Vulnerability Database · PyPI · Package report

pydrive2: vulnerability history, versions and safety

pydrive2 is a package in the PyPI ecosystem. Vulert records 2 vulnerabilities for it across 57 releases, first recorded in Dec 2023. 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 L1 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 pydrive2 vulnerabilities

Vulert verdict on pydrive2 1.21.3 i

Updated on 23 Oct 2026

Careful: 1.21.3 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 Some issues to review
  • Maintenance Maintaining
  • Popularity Niche
  • 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.21.3 — affected i
  • Vulnerabilities on record 2 over 1 year · 0 in the last year i
  • Latest disclosure 05 Dec 2023 i
  • Highest CVSS 7.8 i
  • With no published fix 1 i
  • Depended on by 52 packages i
  • Stars 668 i
  • OpenSSF scorecard 2/10 i
  • Last release 22 months ago i
  • Licence Apache-2.0 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 pydrive2, 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.21.3 29 Nov 2024 L1 Apache-2.0 No Details →
1.21.2 28 Nov 2024 L1 Apache-2.0 No Details →
1.21.1 02 Nov 2024 L1 Apache-2.0 No Details →
1.20.0 15 Jul 2024 L1 Apache-2.0 No Details →
1.19.0 03 Jan 2024 L1 Apache-2.0 No Details →
1.18.1 18 Dec 2023 L1 Apache-2.0 No Details →
1.18.0 07 Dec 2023 L1 Apache-2.0 No Details →
1.16.2 28 Nov 2023 L1 Apache-2.0 No Details →
1.17.0 15 Aug 2023 L1 Apache-2.0 No Details →
1.16.1 05 Jul 2023 U1 Apache-2.0 Yes Details →
1.16.0 23 Jun 2023 U1 Apache-2.0 Yes Details →
1.15.4 21 May 2023 U1 Apache-2.0 Yes Details →
1.15.3 09 Apr 2023 U1 Apache-2.0 Yes Details →
1.15.2 31 Mar 2023 U1 Apache-2.0 Yes Details →
1.15.1 21 Feb 2023 U1 Apache-2.0 Yes Details →
1.15.0 15 Nov 2022 U1 Apache-2.0 Yes Details →
1.14.0 22 Jul 2022 U1 Apache-2.0 Yes Details →
0.14.0 22 Jul 2022 U1 Apache-2.0 Yes Details →
1.13.0 21 Jul 2022 U1 Apache-2.0 Yes Details →
1.12.1 19 Jul 2022 U1 Apache-2.0 Yes Details →
1.12.0 18 Jul 2022 U1 Apache-2.0 Yes Details →
1.11.2 18 Jul 2022 U1 Apache-2.0 Yes Details →
1.11.1 18 Jul 2022 U1 Apache-2.0 Yes Details →
1.11.0 18 Jul 2022 U1 Apache-2.0 Yes Details →
1.10.2 17 Jul 2022 U1 Apache-2.0 Yes Details →
1.10.1 19 Apr 2022 U1 Apache-2.0 Yes Details →
1.10.0 22 Sep 2021 U1 Apache-2.0 Yes Details →
1.9.4 17 Sep 2021 U1 Apache-2.0 Yes Details →
1.9.3 08 Sep 2021 U1 Apache-2.0 Yes Details →
1.9.2 03 Sep 2021 U1 Apache-2.0 Yes Details →
1.9.1 16 Aug 2021 U1 Apache-2.0 Yes Details →
1.9.0 09 Aug 2021 U1 Apache-2.0 Yes Details →
1.8.3 24 May 2021 U1 Apache-2.0 Yes Details →
1.8.2 17 Apr 2021 U1 Apache-2.0 Yes Details →
1.8.1 08 Mar 2021 U1 Apache-2.0 Yes Details →
1.8.0 21 Feb 2021 U1 Apache-2.0 Yes Details →
1.7.3 16 Feb 2021 U1 Apache-2.0 Yes Details →
1.7.2 05 Feb 2021 U1 Apache-2.0 Yes Details →
1.7.0 16 Nov 2020 U1 Apache-2.0 Yes Details →
1.6.3 22 Oct 2020 U1 Apache-2.0 Yes Details →
1.6.2 21 Sep 2020 U1 Apache-2.0 Yes Details →
1.6.1 15 Sep 2020 U1 Apache-2.0 Yes Details →
1.6.0 01 Aug 2020 U1 Apache-2.0 Yes Details →
1.4.14 30 May 2020 U1 Apache-2.0 Yes Details →
1.4.13 07 May 2020 U1 Apache-2.0 Yes Details →
1.4.12 06 May 2020 U1 Apache-2.0 Yes Details →
1.4.11 05 May 2020 U1 Apache-2.0 Yes Details →
1.4.10 11 Apr 2020 U1 Apache-2.0 Yes Details →
1.4.9 04 Apr 2020 U1 Apache-2.0 Yes Details →
1.4.8 24 Mar 2020 U1 Apache-2.0 Yes Details →
1.4.7 12 Mar 2020 U1 Apache-2.0 Yes Details →
1.4.6 05 Mar 2020 U1 Apache-2.0 Yes Details →
1.4.5 09 Feb 2020 U1 Apache-2.0 Yes Details →
1.4.4 31 Jan 2020 U1 Apache-2.0 Yes Details →
1.4.2 27 Jan 2020 U1 Apache-2.0 Yes Details →
1.4.1 24 Jan 2020 U1 Apache-2.0 Yes Details →
1.4.0 15 Jan 2020 U1 Apache-2.0 Yes Details →

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

02 Disclosure history

How often vulnerabilities are recorded

  • 2023 2

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 pydrive2

The 2 most severe of 2 vulnerabilities recorded for this package

Search all 2 in the database →
Vulnerability Severity Fixed version ↓ Disclosed ↓
CVE-2023-49297: PyDrive2 Arbitrary Code Execution via Unsafe YAML Deserialization 7.8 high c57355dc2033ad90b7050d681b2c3ba548ff0004 05 Dec 2023
CVE-2023-49297: PyDrive2's unsafe YAML deserialization allows arbitrary code execution 3.3 low No fix published 05 Dec 2023

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 pydrive2

Is pydrive2 safe to use?

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

Vulert scores pydrive2 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 pydrive2 affected?

Yes. 1.21.3, 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 pydrive2 should I use?

1.21.3 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 pydrive2 have?

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

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

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