# CVE-2026-53573: core-geonetwork has an Open Redirect Bypass > An attacker can bypass redirect validation to force users to external sites after login, potentially facilitating phishing attacks. - **Severity:** Medium 4.8 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:A/VC:N/VI:N/VA:N/SC:N/SI:L/SA:N`) - **Exploited in the wild:** Not known - **Login needed:** Any signed-in user - **Attackable:** Over the internet - **Victim action needed:** A user has to click or open something - **Fix available:** Yes - **Published:** 31 Jul 2026 - **Updated:** 3 Aug 2026 - **Also known as:** GHSA-pjp7-q6wp-97qx ## What is CVE-2026-53573? CVE-2026-53573 is a medium-severity vulnerability in core-geonetwork, published on 31 Jul 2026. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link. ### Official description GeoNetwork is a catalog application to manage spatially referenced resources. From 3.12.0 until 4.2.16 and 4.4.11, unsafe redirect validation in GeonetworkOAuth2LoginAuthenticationFilter and KeycloakAuthenticationProcessingFilter permits an attacker-controlled external redirect after login. This issue is fixed in versions 4.2.16 and 4.4.11. Weakness: CWE-601 (URL Redirection to Untrusted Site) ## Which versions are affected by CVE-2026-53573? 8 open source packages ship an affected version, including org.geonetwork-opensource:geonetwork. | Package | Ecosystem | Affected | Fixed in | | --- | --- | --- | --- | | `org.geonetwork-opensource:geonetwork` | Maven | From 3.12.0 to 3.12.12 | None | | `org.geonetwork-opensource:geonetwork` | Maven | From 3.12.0 to 3.12.12 | None | | `org.geonetwork-opensource:geonetwork` | Maven | From 4.0.0-alpha.1 to 4.0.6 | None | | `org.geonetwork-opensource:geonetwork` | Maven | From 4.0.0-alpha.1 to 4.0.6 | None | | `org.geonetwork-opensource:geonetwork` | Maven | From 4.2.0 | 4.2.16 | | `org.geonetwork-opensource:geonetwork` | Maven | From 4.2.0 | 4.2.16 | | `org.geonetwork-opensource:geonetwork` | Maven | From 4.4.0 | 4.4.11 | | `org.geonetwork-opensource:geonetwork` | Maven | From 4.4.0 | 4.4.11 | ## How do I fix CVE-2026-53573? Upgrade org.geonetwork-opensource:geonetwork to a fixed version for your release line: 4.2.16 or 4.4.11. ## Is CVE-2026-53573 being exploited? There is no known exploitation of CVE-2026-53573 in the wild and no public exploit code. ## Fix prompt for AI coding agents ```text Check this codebase for CVE-2026-53573 and fix it if it is affected. What it is: CVE-2026-53573 is a medium-severity vulnerability in core-geonetwork, published on 31 Jul 2026. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link. Exploitation: There is no known exploitation of CVE-2026-53573 in the wild and no public exploit code. Affected packages and fixed versions: - org.geonetwork-opensource:geonetwork (Maven): affected from 3.12.0 up to 3.12.12; no fix listed - org.geonetwork-opensource:geonetwork (Maven): affected from 3.12.0 up to 3.12.12; no fix listed - org.geonetwork-opensource:geonetwork (Maven): affected from 4.0.0-alpha.1 up to 4.0.6; no fix listed - org.geonetwork-opensource:geonetwork (Maven): affected from 4.0.0-alpha.1 up to 4.0.6; no fix listed - org.geonetwork-opensource:geonetwork (Maven): affected from 4.2.0; fixed in 4.2.16 - org.geonetwork-opensource:geonetwork (Maven): affected from 4.2.0; fixed in 4.2.16 - org.geonetwork-opensource:geonetwork (Maven): affected from 4.4.0; fixed in 4.4.11 - org.geonetwork-opensource:geonetwork (Maven): affected from 4.4.0; fixed in 4.4.11 Task: 1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies. 2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it. 3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead. 4. Run the tests and summarise what changed and why. 5. If nothing in the project is affected, say so and change nothing. Reference: https://insights.sbomify.com/CVE-2026-53573/ (Markdown: https://insights.sbomify.com/CVE-2026-53573/index.md) ``` ## Sources - CVE record: https://www.cve.org/CVERecord?id=CVE-2026-53573 - NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-53573 - OSV: https://osv.dev/vulnerability/CVE-2026-53573 --- From sbomify Insights: https://insights.sbomify.com/CVE-2026-53573/ Summaries are generated and may contain mistakes; the official description above is the record.