Vulnerability in gdal (CVE-2026-49014)
Summary
Vulnerability in gdal (CVE-2026-49014). Successful exploitation can lead to full system takeover. Mitigation: upgrade to 3.13.1 or later.
Original description
The description as published by the source.
In GDAL 3.1.0 through 3.13.0, scanForGeometryContainers in the netCDF driver allows code execution via a stack-based buffer overflow. It reads a geometry attribute into a fixed-size stack buffer without validating the attribute length. The attacker embeds the exploit as an oversized geometry attribute in a crafted NetCDF file. This achieves arbitrary code execution on the server running GDAL. This is in frmts/netcdf/netcdfsg.cpp.
Source: GitHub Security Advisories (Global) NVD GitHub Advisory
Auto-generated summary
Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.
A vulnerability tracked as CVE-2026-49014 has been found in gdal.
Successful exploitation can lead to full system takeover. CVSS score: 7.4/10.
What to do: upgrade gdal to 3.13.1 or later.
If unsure, ask your IT team or search "gdal CVE-2026-49014" on the vendor's site.
CVE-2026-49014 (gdal) — CWE-121 / CVSS v3 7.4
Attack vector: local / unauthenticated / no user interaction
Patched: 3.13.1 — apply immediately
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.
A vulnerability (CWE-121) exists in gdal.
Check the vendor advisory for the affected versions of gdal.
Severity: High (CVSS 7.4/10). Successful exploitation can lead to full system takeover.
Update to 3.13.1.
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run grep -r 'gdal' . against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.
Response actions
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1Identify exposure identify
grep -r 'gdal' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で
gdalを grep し、稼働しているサービス・バージョンを把握する。 -
2Apply patch patch
Upgrade gdal to 3.13.1ステージング環境で 3.13.1 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
-
3Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。
Affected packages
Fix status by distribution
Fixed packages published by each distribution for this CVE
- Debian DEBIAN-CVE-2026-49014 gdal
- Ubuntu UBUNTU-CVE-2026-49014 gdal
References
- advisory nvd.nist.gov
- package github.com
- web github.com
- web github.com
- web github.com
- web github.com
- web github.com
- web github.com