SSRF (Server-Side Request Forgery) in org.geonetwork-opensource:gn-web-app (CVE-2026-55864)
Summary
SSRF in org.geonetwork-opensource:gn-web-app (CVE-2026-55864). Risk of unauthorized operations or information disclosure. Exploitable via POST /api/tools/ogc/sld. Mitigation: upgrade to 4.2.17 or later.
Original description
The description as published by the source.
Summary
An unauthenticated server-side request forgery vulnerability lets any anonymous user make the GeoNetwork server issue arbitrary outbound HTTP requests. This gives an external attacker a position inside the server's network, making it possible to make internal requests no matter if the response is XML-type or not.
The SLD tooling endpoint POST /api/tools/ogc/sld takes a caller-supplied WMS server URL and performs a server-side HTTP GET to it, with no validation. The fetched body can also be stored and downloaded if the output of the outbound request is in XML format, making the SSRF non-blind.
Impact
Any unauthenticated user can make the server send arbitrary HTTP requests to internal hosts it would never expose publicly, and read the responses back if the request responses are XML. This enables internal data disclosure, for example, configuration files that return as XML, authorization bypass, and reconnaissance of the internal network all from an anonymous position.
Resolution
Patched releases:
- 4.4.12
- 4.2.17
Resources
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-55864 has been found in org.geonetwork-opensource:gn-web-app.
Attackers can target a specific entry point like POST /api/tools/ogc/sld over the network to misuse the product.
Risk of unauthorized operations or information disclosure.
What to do: upgrade org.geonetwork-opensource:gn-web-app to 4.2.17 or later.
If unsure, ask your IT team or search "org.geonetwork-opensource:gn-web-app CVE-2026-55864" on the vendor's site.
CVE-2026-55864 (org.geonetwork-opensource:gn-web-app) — CWE-918
Attack surface: POST /api/tools/ogc/sld
Patched: 4.2.17 — apply immediately
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.
SSRF (CWE-918) exists in org.geonetwork-opensource:gn-web-app. Attackers reach the vulnerable code path via POST /api/tools/ogc/sld.
Check the vendor advisory for the affected versions of org.geonetwork-opensource:gn-web-app. Attack surface: POST /api/tools/ogc/sld.
Severity: ?. Risk of unauthorized operations or information disclosure.
Update to 4.2.17.
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
Search webserver/proxy logs for unusual POST /api/tools/ogc/sld requests with malformed payloads or SQL meta-characters. Audit SBOM/dependencies to find affected services.
Response actions
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1Identify exposure identify
Audit SBOM/dependencies for affected components.資産台帳・SBOM・依存マニフェストで org.geonetwork-opensource:gn-web-app を使っているサービスとバージョンを洗い出す。
-
2Hunt for indicators of compromise detect
grep 'POST /api/tools/ogc/sld' /var/log/nginx/access.log | grep -E '(unusual_payload|sqli_pattern)'アクセスログで
POST /api/tools/ogc/sldへの異常なリクエスト (不正な認証ヘッダ・SQLメタ文字)を過去 30〜90日分捜索。WAF/SIEM があれば該当パスのアラート発火履歴を確認。 -
3Apply patch patch
Upgrade org.geonetwork-opensource:gn-web-app to 4.2.17ステージング環境で 4.2.17 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスと、Step 2 で見つけた異常検知の続報チェックを含めること。
-
4Post-deployment verification verify
Replay attack against POST /api/tools/ogc/sld on staging to confirm patch closes the vectorパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番では Step 2 と同じログクエリでアラート再発が無いか継続監視。