Open Redirect in org.geonetwork-opensource:geonetwork (CVE-2026-53573)
Summary
Vulnerability in org.geonetwork-opensource:geonetwork (CVE-2026-53573). Risk of unauthorized operations or information disclosure. Mitigation: upgrade to 4.4.11 or later.
Original description
The description as published by the source.
Summary
GeoNetwork's post-login redirect handling can be bypassed to redirect users to an attacker-controlled external site, even though the code attempts to restrict redirect targets to relative, in-application URLs. This affects both supported SSO login methods: OAuth2/OIDC and Keycloak.
Details
Both the OAuth2/OIDC and Keycloak login filters validate the client-supplied post-login redirect target before forwarding the browser to it, but the validation does not correctly reject every kind of URL that causes the browser to leave the GeoNetwork origin. As a result, a value that is treated as a safe, in-application relative path by the filter can still cause the browser to be redirected to an external, attacker-controlled host.
Impact
An attacker can craft a link to a legitimate GeoNetwork OAuth2/OIDC or Keycloak login endpoint that, after the login flow completes, redirects the victim to an arbitrary external site. This can be used for phishing (e.g., presenting a fake login form) or to chain into other attacks hosted externally. This does not bypass authentication or expose GeoNetwork data directly; the impact is Open Redirect (CWE-601).
GeoNetwork 3.x and 4.0.x are archived/unmaintained and will not receive a fix for this issue. Instances running those lines should upgrade to a supported release (4.2.16 or later, or 4.4.11 or later).
Source: GitHub Security Advisories (Global) 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-53573 has been found in org.geonetwork-opensource:geonetwork.
Risk of unauthorized operations or information disclosure.
What to do: upgrade org.geonetwork-opensource:geonetwork to 4.4.11 or later.
If unsure, ask your IT team or search "org.geonetwork-opensource:geonetwork CVE-2026-53573" on the vendor's site.
CVE-2026-53573 (org.geonetwork-opensource:geonetwork) — CWE-601
Attack vector: remote (network-reachable) / unauthenticated / no user interaction
Patched: 4.4.11 — 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.
A vulnerability (CWE-601) exists in org.geonetwork-opensource:geonetwork.
Check the vendor advisory for the affected versions of org.geonetwork-opensource:geonetwork.
Severity: ?. Risk of unauthorized operations or information disclosure.
Update to 4.4.11.
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. 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:geonetwork を使っているサービスとバージョンを洗い出す。
-
2Apply patch patch
Upgrade org.geonetwork-opensource:geonetwork to 4.4.11ステージング環境で 4.4.11 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
-
3Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。
Affected packages
References
- package github.com
- web github.com
- web github.com
- web github.com
- web github.com
- web github.com
- web github.com
- web github.com
- web github.com