CVE-2026-4738
Buffer Overflow in OSGeo GDAL infback9 Module Allows Memory Corruption
Publication date: 2026-03-24
Last updated on: 2026-03-24
Assigner: Government Technology Agency of Singapore Cyber Security Group (GovTech CSG)
Description
Description
CVSS Scores
EPSS Scores
| Probability: | |
| Percentile: |
Meta Information
Affected Vendors & Products
| Vendor | Product | Version / Range |
|---|---|---|
| osgeo | gdal | to 3.11.0 (exc) |
Helpful Resources
Exploitability
| CWE ID | Description |
|---|---|
| CWE-119 | The product performs operations on a memory buffer, but it reads from or writes to a memory location outside the buffer's intended boundary. This may result in read or write operations on unexpected memory locations that could be linked to other variables, data structures, or internal program data. |
Attack-Flow Graph
AI Powered Q&A
How can this vulnerability be detected on my network or system? Can you suggest some commands?
I don't know
What immediate steps should I take to mitigate this vulnerability?
To mitigate this vulnerability, you should upgrade the OSGeo GDAL software to version 3.11.0 or later, where the security fix has been applied.
The fix involves backporting a patch from the official zlib repository that removes an offset pointer optimization in the vulnerable inftree9.c file, eliminating the improper memory buffer operation.
Ensure that your GDAL installation is updated to include this patch, which was merged into the master branch on May 1, 2025, and targeted for the 3.11.0 release.
Can you explain this vulnerability to me?
This vulnerability is an improper restriction of operations within the bounds of a memory buffer in the OSGeo GDAL project, specifically in the frmts/zlib/contrib/infback9 modules and the file inftree9.c. It relates to cloned functions originally from the madler/zlib library that had similar vulnerabilities. The issue could allow operations that exceed the intended memory buffer limits, potentially leading to security risks.
How can this vulnerability impact me? :
Exploitation of this vulnerability could lead to serious security impacts due to improper memory operations. Given the high CVSS score of 9.4, it indicates a critical severity with network attack vector and low complexity. Potential impacts include unauthorized code execution, data corruption, or denial of service, as the vulnerability involves operations outside the intended memory buffer boundaries.
How does this vulnerability affect compliance with common standards and regulations (like GDPR, HIPAA)?:
I don't know