Connect your agent
AdvisoriesCriticalCheck your lockfilePluginHow it worksPricing Connect your agent

Advisory record · GHSA-pjp7-q6wp-97qx

core-geonetwork has an Open Redirect Bypass

CVSS 4.8 MediumEPSS 0.0065 · 51st percentile

Published by the GitHub Advisory Database at 31 Jul 2026, 22:16 UTC. agentprime has not analysed this yet, so whether it affects any app is not known.

PackageEcosystemAffectedFixed in
org.geonetwork-opensource:geonetworkMaven>=3.12.0, <=3.12.12 || >=4.0.0-alpha.1, <=4.0.6 || >=4.2.0, <4.2.16 || >=4.4.0, <4.4.114.2.16, 4.4.11
Identifiers
GHSA-pjp7-q6wp-97qx · CVE-2026-53573
Weakness (CWE)
CWE-601
Tags
Published
31 Jul 2026
Updated
31 Jul 2026

Machine-written summary

Summary written by Claude Haiku from the source advisory. Not reviewed by a person.

GeoNetwork versions 3.12.0 through 3.12.12, 4.0.0-alpha.1 through 4.0.6, 4.2.0 before 4.2.16, and 4.4.0 before 4.4.11 contain an open redirect bypass in the post-login redirect handling of their OAuth2/OIDC and Keycloak login. An attacker can craft a link to a login endpoint that sends a victim to an external site after login, which can enable phishing, with no effect on authentication or GeoNetwork data. Upgrade to 4.2.16 or 4.4.11; the 3.x and 4.0.x lines are unmaintained and will not receive a fix.

Written 2 Nov 2026.

Not analysed yet

We haven’t published our analysis of this Advisory yet. Once a person has reviewed it, this page will say what’s vulnerable, what has to be true for your app to be affected, and how to check.

Severity and exploitation

ScoreRatingCVSSVectorSource
4.8 Medium 4.0 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 CNA (GitHub_M)
  • CISA KEV Not listed.
  • EPSS 0.0065, the 51st percentile, on 6 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.

Timeline

  1. 31 Oct 2026, 14:19 UTC First seen by agentprime
  2. 31 Oct 2026, 14:19 UTC Confirmed by OSV

Sources

Facts on this page come from the GitHub Advisory Database (CC-BY 4.0), OSV and the other sources listed, as published. We don’t reproduce full advisory descriptions, which can contain exploit code.