Vulnerability in gdal (DEBIAN-CVE-2026-49014)

Summary

Vulnerability in gdal (DEBIAN-CVE-2026-49014). Successful exploitation can lead to full system takeover. Mitigation: upgrade to 3.13.1+dfsg-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: OSV.dev (Open Source Vulnerabilities) OSV

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 DEBIAN-CVE-2026-49014 has been found in gdal.
Successful exploitation can lead to full system takeover.
What to do: upgrade gdal to 3.13.1+dfsg-1 or later.
If unsure, ask your IT team or search "gdal DEBIAN-CVE-2026-49014" on the vendor's site.

DEBIAN-CVE-2026-49014 (gdal)
Attack vector: local / no user interaction
Patched: 3.13.1+dfsg-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.

❓ What is the problem

A vulnerability (unclassified) exists in gdal.

📍 Affected scope

Check the vendor advisory for the affected versions of gdal.

🔥 Severity

Severity: ?. Successful exploitation can lead to full system takeover.

🔧 How to fix

Update to 3.13.1+dfsg-1.

🛡️ Workaround

Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.

🔍 Detection

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

1
Identify exposure identify
```
grep -r 'gdal' . | grep -v node_modules
```
リポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で gdal を grep し、稼働しているサービス・バージョンを把握する。
2
Apply patch patch
```
Upgrade gdal to 3.13.1+dfsg-1
```
ステージング環境で 3.13.1+dfsg-1 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
3
Post-deployment verification verify
```
Confirm patched version is live in production
```
パッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。

Affected packages

Debian:11 gdal

[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}]

Debian:12 gdal

[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}]

Debian:13 gdal

[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}]

Debian:14 gdal

[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"3.13.1+dfsg-1"}]}]

References

advisory security-tracker.debian.org