cve.bz

CVE-2023-49297 iterative pydrive2: Deserialization of Untrusted Data

7.8 highExploit referenceEPSS 0.5%Fix available

High (7.8) in iterative pydrive2. EPSS 0.5% estimated probability of exploitation activity in the next 30 days. Fixed in pydrive2 1.16.2.

On this page
PyDrive2 is a wrapper library of google-api-python-client that simplifies many common Google Drive API V2 tasks. Unsafe YAML deserilization will result in arbitrary code execution. A maliciously crafted YAML file can cause arbitrary code execution if PyDrive2 is run in the same directory as it, or if it is loaded in via `LoadSettingsFile`. This is a deserilization attack that will affect any user who initializes GoogleAuth from this package while a malicious yaml file is present in the same directory. This vulnerability does not require the file to be directly loaded through the code, only present. This issue has been addressed in commit `c57355dc` which is included in release version `1.16.2`. Users are advised to upgrade. There are no known workarounds for this vulnerability.

Severity

CVSS 3.1

7.8 high
CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H
EPSS
0.5% (unchanged from 0.5% a week ago; 0.5% 30 days ago) estimated probability of exploitation activity in the next 30 days; 44th percentile. Scored 2026-11-22. A forecast for this CVE across the internet, not for your own systems.
CWE
CWE-502 Deserialization of Untrusted Data
OWASP Top 10
A08:2025 Software or Data Integrity Failures
Published
Modified
NVD analysis
Analyzed, since modified
Record from
the NVD, synced

Fix and patched versions

Ask an AI about this CVE

Show the promptExplain CVE-2023-49297 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2023-49297?via=ask-ai-copy and https://cve.bz/cve/CVE-2023-49297?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2023-49297 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.

Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.

Affected

Versions

From the NVD's CPE matches.

ProductAffected
iterative:pydrive2before 1.16.2
iterative:pydrive21.17.0

Packages (OSV)

AdvisoryEcosystemPackageAffectedFixed in
GHSA-v5f6-hjmf-9mc5PyPIpydrive21.17.0no fix published
GHSA-v5f6-hjmf-9mc5PyPIpydrive2<1.16.21.16.2
PYSEC-2023-291PyPIpydrive2<1.16.21.16.2

Linux distributions

DistributionReleasePackageFixed inAdvisory
Ubuntu24.04:LTS, 25.10pydrive2no fix listedUBUNTU-CVE-2023-49297
openSUSETumbleweedpython-pydrive21.18.1-2.4openSUSE-SU-2026:12030-1

From the distributions' data via OSV.dev: Ubuntu Security Notices © Canonical Ltd., CC BY-SA 4.0; SUSE security data, CC BY 4.0. Modified: reformatted and linked to CVE records. Credits. On the distributions' own pages: Ubuntu · openSUSE.

Attack patterns (CAPEC)

  • CAPEC-586 Object Injection Likelihood: Medium · Severity: High

The attack patterns MITRE's CAPEC relates to this record's weaknesses, as MITRE names them. Credits.

References

Check your stackJSON