cve.bz

CVE-2026-53573 geonetwork core-geonetwork: Open Redirect

4.8 mediumEPSS 0.6%Fix available

Medium (4.8) in geonetwork core-geonetwork. EPSS 0.6% estimated probability of exploitation activity in the next 30 days. Fixed in org.geonetwork-opensource:geonetwork 4.2.16, 4.4.11.

On this page
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.

Severity

CVSS 4.0

4.8 medium
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
EPSS
0.6% (unchanged from 0.6% a week ago; 0.6% 30 days ago) estimated probability of exploitation activity in the next 30 days; 52nd percentile. Scored 2026-11-17. A forecast for this CVE across the internet, not for your own systems.
CISA's assessment (SSVC)
Exploitation: none · Automatable: no · Technical impact: partial, assessed 2026-08-03. From CISA's Vulnrichment in the CVE List: whether it is exploited, whether exploiting it can be automated, and how much control it gives.
CWE
CWE-601 URL Redirection to Untrusted Site (Open Redirect)
OWASP Top 10
A01:2025 Broken Access Control
Published
Modified
NVD analysis
Awaiting analysis
Record from
the NVD, synced

Fix and patched versions

  • org.geonetwork-opensource:geonetwork (Maven): fixed in 4.2.16, 4.4.11

Ask an AI about this CVE

Show the promptExplain CVE-2026-53573 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2026-53573?via=ask-ai-copy and https://cve.bz/cve/CVE-2026-53573?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2026-53573 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.

Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.

Affected

Versions

From the CNA's record in the CVE List.

ProductAffected
geonetwork core-geonetwork>= 3.12.0, <= 3.12.12
geonetwork core-geonetwork>= 4.0.0-alpha.1, <= 4.0.6
geonetwork core-geonetwork>= 4.2.0, < 4.2.16
geonetwork core-geonetwork>= 4.4.0, < 4.4.11

Packages (OSV)

AdvisoryEcosystemPackageAffectedFixed in
GHSA-pjp7-q6wp-97qxMavenorg.geonetwork-opensource:geonetwork>=3.12.0 <=3.12.12no fix published
GHSA-pjp7-q6wp-97qxMavenorg.geonetwork-opensource:geonetwork>=4.0.0-alpha.1 <=4.0.6no fix published
GHSA-pjp7-q6wp-97qxMavenorg.geonetwork-opensource:geonetwork>=4.2.0 <4.2.164.2.16
GHSA-pjp7-q6wp-97qxMavenorg.geonetwork-opensource:geonetwork>=4.4.0 <4.4.114.4.11

Attack patterns (CAPEC)

  • CAPEC-178 Cross-Site Flashing Likelihood: Medium · Severity: Medium

The attack patterns MITRE's CAPEC relates to this record's weaknesses, as MITRE names them. Credits.

References

Check your stackJSON