CVE-2026-50126: adaguc-server GeoJSON coordinate parser (CConvertGeoJSON.cpp) vulnerable to out-of-bounds read and NULL pointer dereference
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.
Affected Software
Remediation
Recommended actions to resolve this vulnerability, in priority order.
- Upgrade
Upgrade
adaguc-serverto a version that resolves this vulnerability.Fixed in 7.2.2 - Compensating control
Limit unauthenticated access to WMS endpoints that can serve GeoJSON via the AutoResource feature, so crafted GeoJSON files cannot be submitted through requests to the backend GeoJSON parser.
Event History
Frequently Asked Questions
Which deployments are exposed?
Servers running versions earlier than 7.2.2 are affected when they process a local GeoJSON file. Exposure includes configured GeoJSON datasets and GeoJSON files made available through the AutoResource feature.
What is required to trigger the crash?
An attacker needs a crafted GeoJSON file with a malformed coordinate, such as an empty or one-element array, a scalar, or null. Where AutoResource exposes the file, an unauthenticated WMS request can trigger parsing and crash the backend process handling that request.
What version fixes the issue?
Update adaguc-server to version 7.2.2. The provided information does not identify an alternative mitigation for systems that cannot be patched immediately.
How can I identify potentially dangerous GeoJSON inputs?
Review local GeoJSON files used as configured datasets or exposed through AutoResource for malformed coordinates in Polygon, LineString, MultiLineString, and MultiPolygon geometries. Affected coordinate values include empty arrays, arrays with only one element, scalar values, and null.