VulertSecurity VulertSecurity

Vulnerability Database · PyPI · Package report

gdal: vulnerability history, versions and safety

gdal is a package in the PyPI ecosystem. Vulert records 15 vulnerabilities for it across 120 releases, from Oct 2019 to May 2026. Each vulnerability names the versions it affects, the fixed version to move to, and a workaround where no fix has been published.

i
15 vulnerabilities recorded H1 L3 U11
i
2 with no fix published

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

See the unfixed vulnerabilities →
i
11 in the last 12 months

Most recent disclosure 27 May 2026.

See the disclosure history →
i
0 malicious-package vulnerabilities

No published version shipped hostile code.

See all gdal vulnerabilities

Vulert verdict on gdal 3.13.3 i

Updated on 23 Oct 2026

Careful: 3.13.3 has 4 known vulnerabilities, and 2 have no fix yet. Use an earlier safe version, or the workaround listed for each one.

Package health score 60/100
  • Security Unfixed issues
  • Maintenance Sustainable
  • Popularity Widely used
  • Community Active

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 3.13.3 — affected i
  • Vulnerabilities on record 15 over 6 years · 11 in the last year i
  • Latest disclosure 27 May 2026 i
  • Highest CVSS 9.8 i
  • With no published fix 2 i
  • Depended on by 466 packages i
  • Stars 6,109 i
  • OpenSSF scorecard 8/10 i
  • Last release 2 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 gdal, 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
3.13.3 18 Aug 2026 U4 MIT No Details →
3.13.2 22 Jul 2026 U4 MIT No Details →
3.13.1 05 Jun 2026 U4 MIT No Details →
3.13.0 08 May 2026 H1 U2 MIT No Details →
3.12.4 24 Apr 2026 H1 L3 U7 MIT No Details →
3.12.3 20 Mar 2026 H1 L3 U7 MIT No Details →
3.12.2 09 Feb 2026 H1 L3 U7 MIT No Details →
3.12.1 18 Dec 2025 H1 L3 U7 MIT No Details →
3.12.0.post1 07 Nov 2025 H1 L3 U7 MIT No Details →
3.11.5 04 Nov 2025 H1 L3 U7 MIT No Details →
3.11.4 11 Sep 2025 H1 L3 U7 MIT No Details →
3.11.3 12 Jul 2025 H1 L3 U7 MIT No Details →
3.11.2 11 Jul 2025 H1 L3 U7 MIT No Details →
3.11.1 01 Jul 2025 H1 L3 U7 MIT No Details →
3.11.0 09 May 2025 H1 L3 U7 MIT No Details →
3.10.3 07 Apr 2025 H1 L3 U7 MIT No Details →
3.10.2 14 Feb 2025 H1 L3 U7 MIT No Details →
3.10.1 13 Jan 2025 H1 L3 U7 MIT No Details →
3.10.0 06 Nov 2024 H1 L3 U7 MIT No Details →
3.9.3 14 Oct 2024 H1 L3 U7 MIT No Details →
3.9.2 16 Aug 2024 H1 L3 U7 MIT No Details →
3.9.1 26 Jun 2024 H1 L3 U7 MIT No Details →
3.9.0 10 May 2024 H1 L3 U7 MIT No Details →
3.8.5 04 Apr 2024 H1 L3 U7 MIT No Details →
3.8.4 18 Feb 2024 H1 L3 U7 MIT No Details →
3.8.3 08 Jan 2024 H1 L3 U7 MIT No Details →
3.8.2 20 Dec 2023 H1 L3 U7 MIT No Details →
3.8.1 30 Nov 2023 H1 L3 U7 MIT No Details →
3.8.0 13 Nov 2023 H1 L3 U7 MIT No Details →
3.7.3 03 Nov 2023 H1 L3 U7 MIT No Details →
3.7.2 13 Sep 2023 H1 L3 U7 MIT No Details →
3.7.1.1 14 Jul 2023 H1 L3 U7 MIT No Details →
3.7.1 13 Jul 2023 H1 L3 U7 MIT No Details →
3.7.0 10 May 2023 H1 L3 U7 MIT No Details →
3.6.4 21 Apr 2023 H1 L3 U7 MIT No Details →
3.6.3 13 Mar 2023 H1 L3 U7 MIT No Details →
3.6.2 05 Jan 2023 H1 L3 U7 MIT No Details →
3.6.1 15 Dec 2022 H1 L3 U7 MIT No Details →
3.6.0.1 16 Nov 2022 H1 L3 U7 MIT No Details →
3.6.0 11 Nov 2022 H1 L3 U7 MIT No Details →
3.5.3 31 Oct 2022 H1 L3 U7 MIT No Details →
3.5.2 12 Sep 2022 H1 L3 U7 MIT No Details →
3.5.1 06 Jul 2022 H1 L3 U7 MIT No Details →
3.5.0.3 03 Jun 2022 H1 L3 U7 MIT No Details →
3.5.0 13 May 2022 H1 L3 U7 MIT No Details →
3.4.3 04 May 2022 H1 L3 U7 MIT No Details →
3.2.2.1 25 Mar 2022 H1 L3 U7 MIT No Details →
3.4.2 14 Mar 2022 H1 L3 U7 MIT No Details →
3.4.1 04 Jan 2022 H1 L3 U7 MIT No Details →
3.4.0 08 Nov 2021 H1 L3 U8 MIT No Details →
3.3.3 29 Oct 2021 H1 L3 U8 MIT No Details →
3.3.2 07 Sep 2021 H1 L3 U8 MIT No Details →
3.3.1 05 Jul 2021 H1 L3 U8 MIT No Details →
3.2.3 04 May 2021 H1 L3 U7 MIT No Details →
3.3.0 03 May 2021 H1 L3 U8 MIT No Details →
3.2.2 10 Mar 2021 H1 L3 U7 MIT No Details →
3.2.1 04 Jan 2021 H1 L3 U7 MIT No Details →
3.2.0 02 Nov 2020 H1 L3 U7 MIT No Details →
3.1.4 23 Oct 2020 H1 L3 U7 MIT No Details →
3.1.3 07 Sep 2020 H1 L3 U7 MIT No Details →
3.1.2 07 Jul 2020 H1 L3 U7 MIT No Details →
3.1.1 29 Jun 2020 H1 L3 U7 MIT No Details →
3.1.0 07 May 2020 H1 L3 U7 MIT No Details →
3.0.4 30 Jan 2020 L3 U7 MIT No Details →
2.4.4 13 Jan 2020 L3 U8 MIT No Details →
3.0.3 13 Jan 2020 L3 U7 MIT No Details →
3.0.2 04 Nov 2019 L3 U7 MIT No Details →
2.4.3 04 Nov 2019 L3 U8 MIT No Details →
3.0.1 05 Jul 2019 L3 U8 MIT No Details →
2.4.2 05 Jul 2019 L3 U8 MIT No Details →
3.0.0 09 May 2019 L3 U8 MIT No Details →
2.4.0 21 Dec 2018 L3 U7 MIT No Details →
2.3.3 20 Dec 2018 L3 U7 MIT No Details →
2.3.2 28 Sep 2018 L3 U7 MIT No Details →
2.3.1 28 Jun 2018 L3 U7 MIT No Details →
2.3.0 11 May 2018 L3 U7 MIT No Details →
2.2.4 21 Mar 2018 L3 U7 MIT No Details →
2.2.3 23 Nov 2017 L3 U7 MIT No Details →
2.2.2 22 Sep 2017 L3 U7 MIT No Details →
2.2.1 30 Jun 2017 L3 U7 MIT No Details →
2.2.0 09 May 2017 L3 U7 MIT No Details →
2.1.3 27 Jan 2017 L3 U7 MIT No Details →
2.1.0 02 May 2016 L3 U7 MIT No Details →
2.0.1 23 Sep 2015 L3 U7 MIT No Details →
2.0.0 18 Jun 2015 L3 U7 MIT No Details →
1.11.2 17 Feb 2015 L3 U7 MIT No Details →
1.11.1 01 Oct 2014 L3 U7 MIT No Details →
1.11.0 02 Jun 2014 L3 U7 MIT No Details →
1.10.0 11 Aug 2013 L3 U7 MIT No Details →
1.9.1 31 May 2012 L3 U7 MIT No Details →
1.9.0 28 Feb 2012 L3 U7 MIT No Details →
1.8.1 21 Sep 2011 L3 U7 MIT No Details →
1.7.1 20 Feb 2010 L3 U7 MIT No Details →
1.7.0 01 Feb 2010 L3 U7 MIT No Details →
1.6.1 05 Jun 2009 L3 U7 MIT No Details →
1.6.0 11 Dec 2008 L3 U7 MIT No Details →
1.5.2 23 Jun 2008 L3 U7 MIT No Details →
1.5.0 28 Dec 2007 L3 U7 MIT No Details →
1.5.0-py2.4-win32 — L3 U9 — No Details →
1.5.0-py2.5-macosx-10.5-i386 — L3 U9 — No Details →
1.5.0-py2.5-win32 — L3 U9 — No Details →
1.5.0.win32-py2.4 — L3 U9 — No Details →
1.5.0.win32-py2.5 — L3 U9 — No Details →
1.5.2-py2.4-win32 — L3 U9 — No Details →
1.5.2-py2.5-macosx-10.5-i386 — L3 U9 — No Details →
1.5.2-py2.5-win32 — L3 U9 — No Details →
1.5.2.win32-py2.4 — L3 U9 — No Details →
1.5.2.win32-py2.5 — L3 U9 — No Details →
1.6.0-py2.4-win32 — L3 U9 — No Details →
1.6.0-py2.5-win32 — L3 U9 — No Details →
1.6.0-py2.6-win32 — L3 U9 — No Details →
1.6.0.win32-py2.4 — L3 U9 — No Details →
1.6.0.win32-py2.5 — L3 U9 — No Details →
1.6.0.win32-py2.6 — L3 U9 — No Details →
1.6.1-py2.4-win32 — L3 U9 — No Details →
1.6.1-py2.5-win32 — L3 U9 — No Details →
1.6.1-py2.6-win32 — L3 U9 — No Details →
1.6.1.win32-py2.4 — L3 U9 — No Details →
1.6.1.win32-py2.5 — L3 U9 — No Details →
1.6.1.win32-py2.6 — L3 U9 — No Details →

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

02 Disclosure history

How often vulnerabilities are recorded

  • 2019 1
  • 2021 1
  • 2022 1
  • 2025 1
  • 2026 11

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

03 Vulnerabilities

Recorded vulnerabilities for gdal

The 5 most severe of 15 vulnerabilities recorded for this package

Search all 15 in the database →
Vulnerability Severity Fixed version ↓ Disclosed ↓
CVE-2019-17545: GDAL - Double Free in OGRExpatRealloc 9.8 critical 148115fcc40f1651a5d15fa34c9a8c528e7147bb 14 Oct 2019
CVE-2026-8087: GDAL Heap-Based Buffer Overflow Vulnerability 7.8 high 3.13.0 07 May 2026
CVE-2026-49014: GDAL Stack-Based Buffer Overflow Vulnerability 7.8 high 3.13.1 27 May 2026
CVE-2026-8086: GDAL Package Heap-Based Buffer Overflow Vulnerability 7.8 high 3.13.0 07 May 2026
CVE-2019-25050: GDAL Stack-Based Buffer Overflow Vulnerability 7.8 high 767e3a56144f676ca738ef8f700e0e56035bd05a 20 Jul 2021

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 gdal

Is gdal safe to use?

Vulert records 15 vulnerabilities for gdal in PyPI: 0 critical, 1 high, 0 medium and 3 low, plus 11 not yet rated. 2 of them have no published fix yet, so those are the ones to avoid or mitigate.

What is gdal's Vulert package health score?

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

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

Which version of gdal should I use?

3.13.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 gdal have?

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

11 vulnerabilities were recorded for gdal in the last 12 months, and the oldest entry in this database dates to 14 Oct 2019. 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 gdal 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 gdal for upcoming vulnerabilities?

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