Skip to content
Patch Next
Sign inAdd to your agent

← Actionable
Medium, CVSS 4.8amended

core-geonetwork has an Open Redirect Bypass

CVE-2026-53573GHSA-pjp7-q6wp-97qx

What to do

Partial vendor fix. Follow the primary source's mitigation guidance and check back for a fix.

This page has no inventory attached, so it cannot say whether you are affected. A vendor fix is not proof that your deployment is fixed.

Add to your agent

Affected packages

Sources

Severity and exploitation
Exploitation
No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.
CVSS 4.0
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 · score source
EPSS
  • CVE-2026-53573: 0.65% estimated exploitation activity in the next 30 days; percentile 51.10 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.
Source description

As published by the source; long descriptions are shortened.

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…

Dates and revisions
Published by the source
Last modified by the source
Source last checked
  1. Revision 3 · amended ·

    Amended from ghsa record GHSA-pjp7-q6wp-97qx

  2. Revision 2 · amended ·

    Reviewed OSV alias/range/CVSS4 correction; package source scopes and original publication preserved. No customer finding resolved.

  3. Revision 1 · created ·

    Published from osv record GHSA-pjp7-q6wp-97qx

Agent brief

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: CVE-2026-53573

Advisory: core-geonetwork has an Open Redirect Bypass
IDs: CVE-2026-53573, GHSA-pjp7-q6wp-97qx
Record: https://patchnext.com/advisories/cve-2026-53573 (revision 3, source checked 26 Oct 2026, 16:54 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: Medium (CVSS 4.8)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Partial vendor fix; fixed versions by package: org.geonetwork-opensource:geonetwork 4.4.11, 4.2.16. A vendor fix does not mean a deployment is fixed.

## Affected components
- Maven org.geonetwork-opensource:geonetwork: affected >= 3.12.0, <= 3.12.12; >= 4.0.0-alpha.1, <= 4.0.6; >= 4.2.0, <= 4.2.15; >= 4.4.0, <= 4.4.10; fixed in 4.4.11, 4.2.16

## Suggested inspection (read-only)
- Maven org.geonetwork-opensource:geonetwork: check the installed version with your package manager.

## Supported action
No complete vendor fix is recorded. Follow the primary source's mitigation guidance and check this record again before closing anything.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on org.geonetwork-opensource:geonetwork.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://osv.dev/vulnerability/GHSA-pjp7-q6wp-97qx (OSV record GHSA-pjp7-q6wp-97qx lists affected ranges: Maven org.geonetwork-opensource:geonetwork >=3.12.0 =4.0.0-alpha.1 =4.2.0 =4.4.0 <4.4.11 (fixed))
- Verified: https://github.com/advisories/GHSA-pjp7-q6wp-97qx (GitHub-reviewed advisory GHSA-pjp7-q6wp-97qx lists affected ranges: Maven org.geonetwork-opensource:geonetwork >=3.12.0 =4.0.0-alpha.1 =4.2.0 =4.4.0 <=4.4.10)

Commands are suggestions: review each one before running it.

Loading voting…