Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
ReconCraft malformed HDF4 grid file
-
DeliveryPlace file in accessible location
-
ExploitTrigger GDAL HDF4 processing
-
InstallGDSDfldsrch reads FieldList
-
C2Unsafe string manipulation executes
-
ExecuteHeap buffer overflow
-
ImpactMemory corruption or crash
Vulnerability Assessment
| Weakness |
CWE
ASVS 5.0
V15 - Secure Coding and Architecture Bounds checking, buffer size validation
MITRE ATT&CK
2 techniques across 2 tactics: Execution, Privilege Escalation The technique list with ATT&CK links and the kill-chain view is part of the Basic plan and up. |
| Exploitation Conditions | Exploitation requires the following specific conditions: (1) GDAL library must be compiled with HDF4 support (Grid File Handler component enabled), (2) an authenticated local user or process with file read/write permissions must invoke a GDAL function that calls GDSDfldsrch (typically during HDF4 grid file reading/processing), (3) a specially crafted HDF4 file with malformed FieldList metadata (e.g., missing surrounding quotes or extremely short length) must be provided to GDAL. The vulnerability does NOT affect systems where HDF4 support is disabled in GDAL, systems that do not process HDF4 files, or systems without local user access. Remote exploitation is not possible (AV:L confirms local-only attack vector). Exploitation is limited to the context of HDF4 Grid File processing and does not affect other GDAL formats or non-spatial data processing. The CVSS indicates PR:L (low privilege required), meaning the attacking user must have login/local access but does not require administrative rights, however they must have file access permissions to invoke GDAL processing. |
| Impact | The risk assessment presents a complex picture requiring careful interpretation of conflicting signals. CVSS 4.0 vector (AV:L/AC:L/PR:L) indicates local attack vector requiring low privilege and low complexity, with low confidentiality/integrity/availability impact (VC:L/VI:L/VA:L)-all confidentiality impact marked as 'L' rather than 'H' suggests information disclosure rather than code execution potential. However, the vulnerability is classified as a heap-based buffer overflow, which traditionally carries exploitation for code execution. The low CVSS impact ratings (1.9 score) contradict the severity typically associated with heap overflows; this likely reflects the HDF4 processing context where reading a malformed file causes a crash rather than achieving reliable code execution. The publicly available POC and disclosure to the security community increase practical exploitation likelihood despite low CVSS. The AC:L (Low Complexity) rating indicates straightforward exploitation via a crafted HDF4 file. Exploitation requires local file access and an authenticated user with privileges to invoke GDAL HDF4 reading functions-this limits scope to system administrators, GIS analysts, or processes running with elevated privileges. The EPSS score is not provided; without it, real-world exploitation prevalence cannot be quantitatively assessed. KEV (CISA Known Exploited Vulnerabilities) status is not indicated in the provided data. CRITICAL CONFLICT: CWE-119 and 'heap-based buffer overflow' description suggest potential code execution risk, but CVSS impact ratings (VC:L/VI:L/VA:L, no IC/II/IA fields) indicate only low severity impact. Verify with vendor whether this is remote code execution potential or denial-of-service/information disclosure. The presence of public POC code substantially increases practical risk compared to the CVSS score alone. |
| Exploit ScenarioDerived | An authenticated local user or administrator crafts a malicious HDF4 grid file (.he4) with a malformed FieldList metadata entry (missing or improperly formatted quotes). When a GDAL application or script invokes GDSDfldsrch to process the grid's field metadata, the unsafe string manipulation code writes out-of-bounds into heap memory. Depending on heap layout and memory contents, this can trigger a crash (denial of service) or, in specific conditions, allow reading or writing adjacent heap memory. A process running GIS analysis tools (QGIS, ArcGIS, or custom geospatial processing scripts) using the vulnerable GDAL library is exploited when such a file is passed to it. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – May 09, 2026
Heap-based buffer overflow in OSGeo GDAL's Grid File Handler (GDSDfldsrch function in frmts/hdf4/hdf-eos/GDapi.c) affects versions up to 3.13.0dev-4, allowing authenticated local attackers to cause memory corruption through malformed HDF4 grid files. The vulnerability results from unsafe string manipulation that fails to validate metadata field list format before performing memory operations. Publicly available exploit code exists; vendor-released patch available in version 3.13.0RC1.
RemediationAI
Upgrade to OSGeo GDAL version 3.13.0RC1 or later, which includes the security fix (commit 3e04c0385630e4d42517046d9a4967dfccfeb7fd). The patch adds validation to the GDSDfldsrch function in frmts/hdf4/hdf-eos/GDapi.c to check string length and quote character presence before performing memory operations. For users unable to upgrade immediately, restrict access to HDF4 files (.he4 format) to trusted sources only and avoid processing HDF4 grids from untrusted or external sources until patched. Disable HDF4 support in GDAL if the Grid File Handler component is not required for your application (this may require recompilation). Monitor for malicious HDF4 files in input data pipelines; the vulnerability is triggered only when reading specially crafted HDF4 grid files with malformed metadata. The public POC code demonstrates triggering the condition via files issue_14399.he4 and similar test cases; examine any similar files in your systems for potential exploitation.
Affected VersionsENISA
Affected Packages
Source: OSV (Open Source Vulnerabilities)
Affects your stack
Affects 1 package in pypi
Checking this CVE against your own stacks and servers is part of the Basic plan and up.
Technical ContextAI · show details
The vulnerability exists in the HDF4 (Hierarchical Data Format version 4) Grid File Handler component of GDAL, a geospatial data abstraction library. The GDSDfldsrch function in GDapi.c processes field metadata by retrieving a 'FieldList' value from HDF4 metadata structures and performing string manipulation to strip leading and trailing quote characters. The root cause (CWE-119: Improper Restriction of Operations within the Bounds of a Memory Buffer) stems from the code performing memmove(name, name + 1, strlen(name) - 2) without first validating that the retrieved string is actually quoted or that its length is sufficient for the assumed structure. If a malformed HDF4 file provides a FieldList without proper quotes or of insufficient length, the length calculation (strlen(name) - 2) can underflow or cause out-of-bounds memory access. The fix validates both the string length (len >= 2) and the presence of surrounding quotes before performing the unsafe memory move operation.
Know when Gdal gets its next vulnerability
- Watch products and get an email when something new is published
- Check this CVE against your own stack and servers
- Exploit and PoC references, threat intelligence from 22 sources
No credit card · 7-day full trial
Severity by source
CVSS:4.0/AV:L/AC:L/AT:N/PR:L/UI:N/VC:L/VI:L/VA:L/SC:N/SI:N/SA:N/E:P
Primary rating from Vendor (vuldb) · only source for this CVE.
CVSS VectorVendor: vuldb
DescriptionCVE.org
A vulnerability has been found in OSGeo gdal up to 3.13.0dev-4. Affected by this issue is the function GDSDfldsrch of the file frmts/hdf4/hdf-eos/GDapi.c of the component Grid File Handler. The manipulation leads to heap-based buffer overflow. An attack has to be approached locally. The exploit has been disclosed to the public and may be used. Upgrading to version 3.13.0RC1 can resolve this issue. The identifier of the patch is 3e04c0385630e4d42517046d9a4967dfccfeb7fd. It is suggested to upgrade the affected component.
Threat Intelligence Overview
How this decision was reached
The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.
What every action level means
SSVC AssessmentENISA
Priority Score
Attack Technique
A buffer overflow occurs when a program writes more data to a memory buffer than it was allocated to hold, causing the excess data to spill into adjacent memory regions.
GDAL through 3.0.1 has a poolDestroy double free in OGRExpatRealloc in ogr/ogr_expat.cpp when the 10MB threshold is exce
Buffer Overflow vulnerability in gdal 3.10.2 allows a local attacker to cause a denial of service via the OGRSpatialRefe
A buffer overflow vulnerability in GDAL versions before 3.11.0 within the zlib infback9 module allows remote attackers t
tif_getimage.c in LibTIFF through 4.0.10, as used in GDAL through 3.0.1 and other products, has an integer overflow that
Arbitrary code execution in GDAL 3.1.0 through 3.13.0 arises from a stack-based buffer overflow in the netCDF driver's s
Heap-based buffer overflow in OSGeo GDAL up to version 3.13.0dev-4 allows local authenticated attackers to corrupt memor
Out-of-bounds read in OSGeo GDAL up to version 3.13.0dev-4 occurs in the HDF-EOS Grid File Handler when parsing malforme
Heap-based buffer overflow in GDAL's HDF4-EOS SWSDfldsrch function (frmts/hdf4/hdf-eos/SWapi.c) allows local authenticat
Heap-based buffer overflow in OSGeo GDAL up to 3.13.0dev-4 within the SWnentries function of the HDF4-EOS module allows
Out-of-bounds read in OSGeo GDAL up to version 3.13.0dev-4 affects the GDfieldinfo function in HDF-EOS module when proce
EUVD-2026-28949
GHSA-8q76-c96g-j64j
NVD
CVE.org
EPSS
Vulnrichment
VulDB
Exploit-DB