GeoNetwork is a catalog application to manage spatially referenced resources. Prior to 4.2.17 and 4.4.12, POST /api/tools/ogc/sld accepted a caller-supplied WMS server URL and performed a server-side HTTP GET without destination validation. An anonymous attacker could make the GeoNetwork server send requests to internal hosts that are not publicly reachable. When the outbound response was XML, the endpoint could store and return the fetched body, making the request forgery non-blind and enabling internal data disclosure, authorization bypass, and network reconnaissance. This issue is fixed in versions 4.2.17 and 4.4.12.
CVE-2026-55864
HIGHPre-NVD 7.87.8—Trending — 3 sources updated this week
EchelonGraph scoreMEDIUM confidence
This high-severity CVE scores 7.8 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.6%, top 53% of all CVEs by exploit prediction. GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).
Triggered by: NVD CVSS baseline
Sources: epss, secondary
7.8EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
- High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 1%CVSS: 7.8Exploit: None knownExposed: 0
No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.
- CVSS v3
- 7.8
- EG Score
- 7.8(medium)
- EG Risk
- 50(Track)EG Risk 50/100SSVC: Track
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 computedSeverity78% × 45%Exploitation1% × 40%Automatability100% × 15%Action: Routine — remediate on your standard cadence. - EPSS PROB
- 1%
- EPSS %ILE
- 47%
- KEV
- Not listed
Published
September 9, 2026
Last Modified
September 16, 2026
Advisory Details (7)
Auto-updated Sep 15, 2026Patch available. Sources: github_pr, github_commit, github_release, github.
github_release Patch Available
GeoNetwork v4.4.12
Patch available: geonetwork/core-geonetwork 4.4.12
https://github.com/geonetwork/core-geonetwork/releases/tag/4.4.12github_release Patch Available
GeoNetwork v4.2.17
Patch available: geonetwork/core-geonetwork 4.2.17
https://github.com/geonetwork/core-geonetwork/releases/tag/4.2.17github_commit Patch Available
commit a80d535c842e (geonetwork/core-geonetwork)
Patch available: geonetwork/core-geonetwork 4.2.17 (contains commit a80d535c842e)
https://github.com/geonetwork/core-geonetwork/commit/a80d535c842e6af589d0bac37e7fe4ba01193757github_commit Patch Available
commit 17fdae28a5a5 (geonetwork/core-geonetwork)
Patch available: geonetwork/core-geonetwork 4.4.12 (contains commit 17fdae28a5a5)
https://github.com/geonetwork/core-geonetwork/commit/17fdae28a5a51996bf5ff7f7e8236332c74eab77github_pr Patch Available
[Backport 4.2.x] Map viewer / WFS filter / remove unused SLD API endpoints
Patch available: geonetwork/core-geonetwork 4.2.17 (PR #9344 merged 2026-06-18)
https://github.com/geonetwork/core-geonetwork/pull/9344github_pr Patch Available
Map viewer / WFS filter / remove unused SLD API endpoints
Patch available: geonetwork/core-geonetwork 4.4.12 (PR #9343 merged 2026-06-18)
https://github.com/geonetwork/core-geonetwork/pull/9343github Patch Available
Unauthenticated Server-Side Request Forgery in SLD Tool · Advisory · geonetwork/core-geonetwork · GitHub
https://github.com/geonetwork/core-geonetwork/security/advisories/GHSA-5hx7-j24v-rffjVendor Advisories for CVE-2026-55864(1)
These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.
Affected Packages
(1 across 1 ecosystem)
Maven(1)
| Package | Vulnerable range | Fixed in | Dependents |
|---|---|---|---|
| org.geonetwork-opensource:gn-web-app | — | 4.4.12 | — |
Weakness Classification(1)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
Data Freshness Timeline
(refreshed 14× in last 7d / 15× in last 30d)
Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. 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. Most recent first.
- 2026-09-20 23:43 UTCEG score recompute
- 2026-09-20 20:16 UTCEPSS rescore
- 2026-09-20 00:49 UTCEG score recompute
- 2026-09-19 02:00 UTCEG score recompute
- 2026-09-18 19:28 UTCEPSS rescore
- 2026-09-18 03:10 UTCEG score recompute
- 2026-09-17 19:31 UTCEPSS rescore
- 2026-09-16 16:57 UTCEG score recompute
- 2026-09-16 15:50 UTCEG score recompute
- 2026-09-16 15:35 UTCEG score recompute
- 2026-09-16 14:08 UTCEPSS rescore
- 2026-09-15 16:35 UTCEG score recompute
- 2026-09-15 15:43 UTCEG score recompute▲ 7.80
- 2026-09-15 15:42 UTCMITRE cvelistV5CVSS v3 → 7.8 · CVSS v4 → 7.8
- 2026-09-10 00:25 UTCEG score recompute
Related CVEs(same CWE)
Same CWE
10 shownCWE-918
Frequently asked(5)
What is CVE-2026-55864?
CVE-2026-55864 is a high vulnerability published on September 9, 2026. GeoNetwork is a catalog application to manage spatially referenced resources. Prior to 4.2.17 and 4.4.12, POST /api/tools/ogc/sld accepted a caller-supplied WMS server URL and performed a server-side HTTP GET without destination validation. An anonymous attacker could make the GeoNetwork server…
When was CVE-2026-55864 disclosed?
CVE-2026-55864 was first published in the National Vulnerability Database on September 9, 2026, with the most recent update on September 16, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-55864 actively exploited?
CVE-2026-55864 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 1% probability of exploitation in the next 30 days, which ranks it in the top 53.3% of all scored CVEs.
What is the CVSS score of CVE-2026-55864?
CVE-2026-55864 has a CVSS v3 base score of 7.8 (NVD).
How do I remediate CVE-2026-55864?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-55864, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.
Dependency Blast Radius
See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-55864
Is Your Infrastructure Affected by CVE-2026-55864?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.