Out-of-Bounds Read in Adaguc-server (CVE-2026-50126)
Summary
Vulnerability in Adaguc-server (CVE-2026-50126). Risk of unauthorized operations or information disclosure. Exploitable via polygon.u.array.length.
Original description
The description as published by the source.
Adaguc-server is an open source geographical information system to visualize, combine, compare and share real-time meteorological, climatological and remote sensing data via OGC standards. Versions prior to 7.2.2 crash with a memory-safety fault when it parses a GeoJSON document whose geometry contains a malformed coordinate. The coordinate parser in adagucserverEC/CConvertGeoJSON.cpp indexes pt.u.array.values[0] and pt.u.array.values[1] and uses polygon.u.array.length as a loop bound without first validating the JSON node type or the coordinate length. A coordinate that is an empty array, a one-element array, a scalar, or null leads to an out-of-bounds heap read or a NULL pointer dereference. The same unchecked pattern is present in four geometry branches: Polygon, LineString, MultiLineString and MultiPolygon. The vulnerable parser runs whenever the server processes a local GeoJSON file, either a configured GeoJSON dataset or a GeoJSON file exposed through the AutoResource feature and requested by an unauthenticated WMS request. A crafted GeoJSON file reliably crashes the backend process that handles that request. Version 7.2.2 patches the vulnerability.
Source: NIST National Vulnerability Database 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-50126 has been found in Adaguc-server.
Attackers can target a specific entry point like polygon.u.array.length over the network to misuse the product.
Risk of unauthorized operations or information disclosure. CVSS score: 4.0/10.
What to do: apply the vendor's official patched release.
If unsure, ask your IT team or search "Adaguc-server CVE-2026-50126" on the vendor's site.
CVE-2026-50126 (Adaguc-server) — CWE-125 / CVSS v3 4.0
Attack vector: local / unauthenticated / no user interaction
Attack surface: polygon.u.array.length / null / Polygon / LineString
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.
Out-of-bounds read (CWE-125) exists in Adaguc-server. Attackers reach the vulnerable code path via polygon.u.array.length without authentication.
Check the vendor advisory for the affected versions of Adaguc-server. Attack surface: polygon.u.array.length / null / Polygon / LineString.
Severity: Medium (CVSS 4.0/10). Risk of unauthorized operations or information disclosure.
Update to the patched release per vendor advisory.
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 'Adaguc-server' . 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 'Adaguc-server' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で
Adaguc-serverを grep し、稼働しているサービス・バージョンを把握する。 -
2Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。
References
- advisory github.com
- advisory github.com
- advisory nvd.nist.gov
- patch github.com
- patch github.com
- web github.com