cve.bz

CVE-2026-8087 osgeo gdal: Heap-based Buffer Overflow

1.9 lowExploit referenceEPSS 0.2%Fix available

Low (1.9) in osgeo gdal. EPSS 0.2% estimated probability of exploitation activity in the next 30 days. Fixed in gdal 3.13.0.

On this page
A security flaw has been discovered in OSGeo gdal up to 3.13.0dev-4. Impacted is the function GDnentries of the file frmts/hdf4/hdf-eos/GDapi.c. Performing a manipulation of the argument DataFieldName results in heap-based buffer overflow. The attack must be initiated from a local position. The exploit has been released to the public and may be used for attacks. Upgrading to version 3.13.0RC1 is recommended to address this issue. The patch is named 184f77dbcc74118c062c05e464c88161d3c37b9b. You should upgrade the affected component.

Severity

CVSS 4.0

1.9 low
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

CVSS 3.1

7.8 high
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
EPSS
0.2% (unchanged from 0.2% a week ago; 0.3% 30 days ago) estimated probability of exploitation activity in the next 30 days; 13th percentile. Scored 2026-11-21. A forecast for this CVE across the internet, not for your own systems.
CISA's assessment (SSVC)
Exploitation: PoC · Automatable: no · Technical impact: partial, assessed 2026-05-08. From CISA's Vulnrichment in the CVE List: whether it is exploited, whether exploiting it can be automated, and how much control it gives.
CWEs
CWE-119 Improper Restriction of Operations within the Bounds of a Memory Buffer
CWE-122 Heap-based Buffer Overflow
Published
Modified
NVD analysis
Analyzed
Record from
the NVD, synced

Fix and patched versions

Ask an AI about this CVE

Show the promptExplain CVE-2026-8087 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2026-8087?via=ask-ai-copy and https://cve.bz/cve/CVE-2026-8087?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-2026-8087 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
osgeo:gdalthrough 3.12.4
osgeo:gdal3.13.0:beta1
osgeo:gdal3.13.0:beta2

Packages (OSV)

AdvisoryEcosystemPackageAffectedFixed in
GHSA-h9rh-5ffh-h669PyPIgdal<3.13.03.13.0
PYSEC-2026-2155PyPIgdal<3.13.03.13.0

Linux distributions

DistributionReleasePackageFixed inAdvisory
Debian12, 13gdalno fix listedDEBIAN-CVE-2026-8087
Debian14gdal3.13.0+dfsg-1DEBIAN-CVE-2026-8087
Ubuntu25.10gdalno fix listedUBUNTU-CVE-2026-8087
UbuntuPro:14.04:LTSgdal1.10.1+dfsg-5ubuntu1+esm3UBUNTU-CVE-2026-8087 USN-8812-1
UbuntuPro:16.04:LTSgdal1.11.3+dfsg-3ubuntu0.1~esm2UBUNTU-CVE-2026-8087 USN-8812-1
UbuntuPro:18.04:LTSgdal2.2.3+dfsg-2ubuntu0.1~esm1UBUNTU-CVE-2026-8087 USN-8812-1
UbuntuPro:20.04:LTSgdal3.0.4+dfsg-1ubuntu0.1~esm1UBUNTU-CVE-2026-8087 USN-8812-1
UbuntuPro:22.04:LTSgdal3.4.1+dfsg-1ubuntu0.1~esm1UBUNTU-CVE-2026-8087 USN-8812-1
UbuntuPro:24.04:LTSgdal3.8.4+dfsg-3ubuntu3+esm1UBUNTU-CVE-2026-8087 USN-8812-1
UbuntuPro:26.04:LTSgdal3.12.2+dfsg-1ubuntu0.1~esm1UBUNTU-CVE-2026-8087 USN-8812-1
Azure Linux3gdalno fix listedAZL-86229

From the distributions' data via OSV.dev: the Debian Security Tracker; Ubuntu Security Notices © Canonical Ltd., CC BY-SA 4.0; Microsoft's Azure Linux vulnerability data, MIT. Modified: reformatted and linked to CVE records. Credits. On the distributions' own pages: Debian · Ubuntu.

Attack patterns (CAPEC)

  • CAPEC-92 Forced Integer Overflow Likelihood: High · Severity: High

The attack patterns MITRE's CAPEC relates to this record's weaknesses, as MITRE names them. Credits. More on the page of CWE-119 (12).

References

Check your stackJSON