PatchSiren

PatchSiren cyber security CVE debrief

CVE-2026-50126 KNMI CVE debrief

A memory-safety fault in Adaguc-server, an open-source geographical information system, can be triggered by parsing a malformed GeoJSON document. This fault occurs when the server attempts to process a local GeoJSON file, either a configured dataset or one exposed through the AutoResource feature and requested by an unauthenticated WMS request. The vulnerability is patched in version 7.2.2.

Vendor
KNMI
Product
adaguc-server
CVSS
MEDIUM 4
CISA KEV
Not listed in stored evidence
Original CVE published
2026-08-18
Original CVE updated
2026-09-18
Advisory published
2026-08-18
Advisory updated
2026-09-18

Who should care

Defenders managing Adaguc-server installations, especially those exposing the service to untrusted sources, should assess their exposure and prioritize upgrading to version 7.2.2. This includes operators, platform administrators, vulnerability management teams, and security teams who need to verify the presence of affected versions, evaluate potential impacts, and implement necessary mitigations.

Why it matters

Defenders should care about CVE-2026-50126 because it can cause Adaguc-server crashes leading to denial of service, requires verification of server versions and exposure to untrusted GeoJSON sources, and may limit data access during an attack. Upgrading to version 7.2.2 can mitigate the issue.

  • Potential denial of service through crafted GeoJSON files
  • Need for verification of Adaguc-server version and exposure
  • Possible data access limitations due to service unavailability

Technical summary

The Adaguc-server is vulnerable to a memory-safety fault when parsing a GeoJSON document with a malformed coordinate. This occurs due to an unchecked pattern in the coordinate parser of `adagucserverEC/CConvertGeoJSON.cpp`, which leads to an out-of-bounds heap read or a NULL pointer dereference. The vulnerability affects versions prior to 7.2.2 and can be triggered through unauthenticated WMS requests.

Defensive priority

Defenders should prioritize verifying exposure of Adaguc-server installations to untrusted GeoJSON sources and upgrading to version 7.2.2 if possible.

Recommended defensive actions

  • Verify Adaguc-server installations for exposure to untrusted GeoJSON sources
  • Upgrade to version 7.2.2 if possible
  • Monitor for crafted GeoJSON files in server logs
  • Review compensating controls for exposed systems while remediation is scheduled and verified
  • Check relevant monitoring, detection, and logs for exposed assets that need extra review
  • Track exceptions, retest remediated assets, and close the item only after evidence is documented
  • Confirm whether affected product deployments exist in managed environments and assign an owner for follow-up

Evidence notes

The CVE record and NVD entry provide details on the vulnerability, including its description, CVSS score, and affected versions. GitHub references offer additional context on the patch and advisory. Defenders should verify the GeoJSON parsing vulnerability in Adaguc-server installations, especially those exposed to untrusted sources, and assess potential impacts. Evidence from the CVE and NVD suggests that the vulnerability can cause denial of service and data access limitations. To verify exposure, defenders should check server logs,

Sources and references

Verified primary and authoritative sources

  • CVE-2026-50126 CVE Program record

    Publisher, destination, and source semantics verified

    URL: https://www.cve.org/CVERecord?id=CVE-2026-50126

    CVE Program - Official CVE Program record with source-provided CVE metadata.

  • CVE-2026-50126 NVD vulnerability detail

    Publisher, destination, and source semantics verified

    URL: https://nvd.nist.gov/vuln/detail/CVE-2026-50126

    NIST National Vulnerability Database - Official NIST NVD detail page and source-specific vulnerability assessment.

Supplemental references

Methodology and review provenance

AI-assisted synthesis based on stored public vulnerability evidence. System validation, approval state, and publication status do not by themselves establish human review of this revision. PatchSiren helps prioritize defensive review and does not prove exposure or remediation on any system.