CVE-2026-50126

MEDIUMPre-NVD 4.04.0
EchelonGraph scoreMEDIUM confidence

“—” beside the score: it is equal to the CVSS score beside it.

This medium-severity CVE scores 4.0 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.2% (6th percentile of EPSS-scored CVEs). No GitHub Security Advisory CVSS is on record for this CVE.

Triggered by: Headline CVSS from a secondary CVSS source
Sources: EPSS, a secondary CVSS source
Elevated
4.0EG
EchelonGraph verdictPlan a fixRemediate within your standard update timelines (the SSVC decision on this page).
  • CISA's Vulnrichment rates exploitation as PoC; EchelonGraph holds no exploit-code reference for it
CISA-KEV: Not listedEPSS PROB: 0.2%CVSS: 4.0Exploit: No code on recordExposed services: Not assessed

A fix is available — apply it.

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.

CVSS v3
4.0
EG Score
4.0MEDIUMmedium confidence
EG Risk
34
EG Risk 34/100

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed (value × EchelonGraph’s weight)
Severity40% × 45%
The EG Score, 4.0 of 10.
Exploitation40% × 40%
EchelonGraph's fixed weight for EG-KEV Tier 3 (Elevated): a constant, not a probability.
Automatability0% × 15%
CISA's SSVC Automatable value: no (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at low or medium mission impact; Track* at high (mission-essential systems).
Exploitation public PoC (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE.
Action: A fix is available. Apply it within your standard update timelines.
EPSS PROB
0.2%
EPSS %ILE
6th
KEV
Not listed

SSVC (CISA's decision table, applied by EchelonGraph)Track at low or medium mission impact; Track* at high (mission-essential systems).

A fix is available. Apply it within your standard update timelines.

Exploitation public PoC (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE. Mission impact is CISA's Mission & Well-being decision point, and only you can judge it. CISA's table makes it high when Mission Prevalence is Essential — the vulnerable component "directly provides capabilities that constitute at least one MEF for at least one entity" (MEF: mission essential function) — or when Public Well-Being Impact is Irreversible: "multiple fatalities are likely", the cyber-physical system "is likely lost or destroyed", "extreme or serious externalities" are imposed on other parties, or social systems such as elections or the financial grid "are destabilized and potentially collapse". CISA's decision table

BOD 26-04 (CISA's remediation timeline, Table 1)60 days if the affected system is publicly exposed; Fix on system upgrade if it is not.

In CISA KEV no (CISA's KEV catalog) · Automatable no (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). Whether your system is publicly exposed is yours to answer. BOD 26-04 binds US Federal Civilian Executive Branch agencies; for anyone else it is CISA's published timeline, a reference rather than an obligation. The directive · how EchelonGraph applies it

Published

August 18, 2026

Last Modified

September 18, 2026

Advisory Details (4)

Auto-updated Aug 18, 2026
Patch available. Sources: github_commit, github_release, github, github_pr.
GitHub release Patch Available

7.2.2

Patch available: KNMI/adaguc-server 7.2.2

https://github.com/KNMI/adaguc-server/releases/tag/7.2.2
GitHub commit Patch Available

commit 30dffde1a177 (KNMI/adaguc-server)

Patch available: KNMI/adaguc-server 7.2.2 (contains commit 30dffde1a177)

https://github.com/KNMI/adaguc-server/commit/30dffde1a1776b994d60026f41ca620f7cad72e9
GitHub pull request Patch Available

CVE_GHSA_mwgv_59vv_rp2m as found by Sebastian Alba Vives

Patch available: KNMI/adaguc-server 7.2.2 (PR #710 merged 2026-05-28)

https://github.com/KNMI/adaguc-server/pull/710
GitHub advisoryMentions a patch (unverified)

Out-of-bounds read and NULL pointer dereference in adaguc-server GeoJSON coordinate parser (CConvertGeoJSON.cpp) · Advisory · KNMI/adaguc-server · GitHub

https://github.com/KNMI/adaguc-server/security/advisories/GHSA-mwgv-59vv-rp2m

Weakness Classification(2)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 11× in last 7d / 46× in last 30d)

Each row is a time one of our pipelines fetched, updated or re-scored this CVE. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. An arrow marks a change the record states ("CVSS v3 → 9.1"); EPSS and GHSA rows show the values recorded at that time, not what changed (EPSS values are rounded; hover one for the exact figures). Most recent first.

  1. 2026-10-13 16:34 UTCEPSS rescoreEPSS 0.2% · 6th percentile
  2. 2026-10-12 16:34 UTCEPSS rescoreEPSS 0.2% · 6th percentile
  3. 2026-10-12 15:59 UTCEG score recompute
  4. 2026-10-11 19:42 UTCEG score recompute
  5. 2026-10-11 16:57 UTCEG score recompute
  6. 2026-10-11 14:21 UTCEG score recompute
  7. 2026-10-11 13:49 UTCEPSS rescoreEPSS 0.2% · 6th percentile
  8. 2026-10-10 20:00 UTCEPSS rescoreEPSS 0.2% · 6th percentile
  9. 2026-10-09 20:07 UTCEPSS rescoreEPSS 0.2% · 6th percentile
  10. 2026-10-08 17:12 UTCEPSS rescoreEPSS 0.2% · 6th percentile
  11. 2026-10-07 23:48 UTCEPSS rescoreEPSS 0.2% · 6th percentile
  12. 2026-10-07 08:51 UTCEG score recompute
  13. 2026-10-06 15:18 UTCEPSS rescoreEPSS 0.2% · 6th percentile
  14. 2026-10-06 08:22 UTCEG score recompute
  15. 2026-10-05 17:43 UTCEPSS rescoreEPSS 0.2% · 6th percentile
  16. 2026-10-04 23:22 UTCEPSS rescoreEPSS 0.2% · 6th percentile
  17. 2026-10-03 17:38 UTCEG score recompute
  18. 2026-10-03 14:26 UTCEPSS rescoreEPSS 0.2% · 6th percentile
  19. 2026-10-02 17:56 UTCEPSS rescoreEPSS 0.2% · 6th percentile
  20. 2026-10-02 15:08 UTCEG score recompute
  21. 2026-10-01 19:50 UTCEPSS rescoreEPSS 0.2% · 6th percentile
  22. 2026-10-01 10:16 UTCEG score recompute
  23. 2026-09-30 15:03 UTCEPSS rescoreEPSS 0.2% · 6th percentile
  24. 2026-09-30 09:48 UTCEG score recompute
  25. 2026-09-28 13:51 UTCEPSS rescoreEPSS 0.2% · 6th percentile
Show 63 more
  1. 2026-09-28 08:31 UTCEG score recompute
  2. 2026-09-27 13:48 UTCEPSS rescoreEPSS 0.2% · 6th percentile
  3. 2026-09-27 07:56 UTCEG score recompute
  4. 2026-09-26 15:59 UTCEPSS rescoreEPSS 0.2% · 6th percentile
  5. 2026-09-26 00:27 UTCEPSS rescoreEPSS 0.2% · 6th percentile
  6. 2026-09-25 01:27 UTCEG score recompute
  7. 2026-09-23 23:30 UTCEG score recompute
  8. 2026-09-23 17:53 UTCEPSS rescoreEPSS 0.2% · 13th percentile
  9. 2026-09-22 22:22 UTCEG score recompute
  10. 2026-09-21 21:52 UTCEG score recompute
  11. 2026-09-20 21:24 UTCEG score recompute
  12. 2026-09-20 20:16 UTCEPSS rescoreEPSS 0.2% · 13th percentile
  13. 2026-09-19 20:50 UTCEG score recompute
  14. 2026-09-18 20:21 UTCEG score recompute
  15. 2026-09-18 19:28 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  16. 2026-09-18 08:15 UTCEG score recompute
  17. 2026-09-17 07:46 UTCEG score recompute
  18. 2026-09-16 14:08 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  19. 2026-09-16 06:47 UTCEG score recompute
  20. 2026-09-16 05:15 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  21. 2026-09-15 06:18 UTCEG score recompute
  22. 2026-09-14 05:49 UTCEG score recompute
  23. 2026-09-13 16:47 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  24. 2026-09-13 05:21 UTCEG score recompute
  25. 2026-09-12 04:53 UTCEG score recompute
  26. 2026-09-11 14:53 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  27. 2026-09-11 04:24 UTCEG score recompute
  28. 2026-09-10 09:35 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  29. 2026-09-09 03:25 UTCEG score recompute
  30. 2026-09-08 22:01 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  31. 2026-09-07 16:01 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  32. 2026-09-07 10:25 UTCEG score recompute
  33. 2026-09-06 13:47 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  34. 2026-09-06 08:46 UTCEG score recompute
  35. 2026-09-05 08:17 UTCEG score recompute
  36. 2026-09-04 07:48 UTCEG score recompute
  37. 2026-09-04 05:06 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  38. 2026-09-02 06:02 UTCEG score recompute
  39. 2026-09-01 13:54 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  40. 2026-09-01 05:18 UTCEG score recompute
  41. 2026-09-01 04:40 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  42. 2026-08-31 04:49 UTCEG score recompute
  43. 2026-08-30 19:17 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  44. 2026-08-30 04:20 UTCEG score recompute
  45. 2026-08-30 01:22 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  46. 2026-08-29 03:49 UTCEG score recompute
  47. 2026-08-28 21:41 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  48. 2026-08-27 23:00 UTCEG score recompute
  49. 2026-08-27 14:25 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  50. 2026-08-25 22:02 UTCEG score recompute
  51. 2026-08-25 13:49 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  52. 2026-08-24 21:32 UTCEG score recompute
  53. 2026-08-22 20:19 UTCEG score recompute
  54. 2026-08-21 23:49 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  55. 2026-08-21 19:50 UTCEG score recompute
  56. 2026-08-20 22:55 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  57. 2026-08-19 18:52 UTCEG score recompute
  58. 2026-08-19 17:04 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  59. 2026-08-18 18:23 UTCEG score recompute
  60. 2026-08-18 17:57 UTCEG score recompute
  61. 2026-08-18 17:21 UTCEG score recompute
  62. 2026-08-18 16:50 UTCEG score recomputeFirst assessed: 4.0 MEDIUM
  63. 2026-08-18 16:49 UTCMITRE cvelistV5first tracked

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2026-50126?
CVE-2026-50126 is a medium-severity vulnerability; its CVE record was published on August 18, 2026. 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…
When was the CVE record for CVE-2026-50126 published?
The CVE record for CVE-2026-50126 was published on August 18, 2026. That is the record's publication date; the vulnerability itself may have been made public earlier. EchelonGraph's copy of the record carries a last-modified date of September 18, 2026; the record at its source may have been updated since.
Is CVE-2026-50126 actively exploited?
CVE-2026-50126 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.2% probability of exploitation in the next 30 days (6th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-50126?
CVE-2026-50126 has a CVSS base score of 4.0 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-50126?
A fix for CVE-2026-50126 is available: update to the fixed version the vendor names in its advisory.

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2026-50126

Explore →

Is Your Infrastructure Affected by CVE-2026-50126?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Book a Demo →Browse All CVEs