GeoNetwork up to 3.12.12/4.0.6/4.2.15/4.4.10 redirect

Summaryinfo

A vulnerability has been found in GeoNetwork up to 3.12.12/4.0.6/4.2.15/4.4.10 and classified as problematic. This vulnerability affects the function GeonetworkOAuth2LoginAuthenticationFilter/KeycloakAuthenticationProcessingFilter. The manipulation leads to redirect. This vulnerability is uniquely identified as CVE-2026-53573. The attack is possible to be carried out remotely. No exploit exists.

Detailsinfo

A vulnerability, which was classified as problematic, has been found in GeoNetwork up to 3.12.12/4.0.6/4.2.15/4.4.10. This issue affects the function GeonetworkOAuth2LoginAuthenticationFilter/KeycloakAuthenticationProcessingFilter. The manipulation with an unknown input leads to a redirect vulnerability. Using CWE to declare the problem leads to CWE-601. A web application accepts a user-controlled input that specifies a link to an external site, and uses that link in a Redirect. This simplifies phishing attacks. Impacted is integrity. The summary by CVE is:

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.

The advisory is shared at github.com. The identification of this vulnerability is CVE-2026-53573 since 06/09/2026. The exploitation is known to be easy. The attack may be initiated remotely. No form of authentication is needed for a successful exploitation. It demands that the victim is doing some kind of user interaction. Technical details are known, but no exploit is available. MITRE ATT&CK project uses the attack technique T1204.001 for this issue.

Upgrading to version 4.2.16 or 4.4.11 eliminates this vulnerability.

If you want to get the best quality for vulnerability data then you always have to consider VulDB.

Productinfo

Name

• GeoNetwork

Version

• 3.12.0
• 3.12.1
• 3.12.2
• 3.12.3
• 3.12.4
• 3.12.5
• 3.12.6
• 3.12.7
• 3.12.8
• 3.12.9
• 3.12.10
• 3.12.11
• 3.12.12
• 4.0.0
• 4.0.1
• 4.0.2
• 4.0.3
• 4.0.4
• 4.0.5
• 4.0.6
• 4.2.0
• 4.2.1
• 4.2.2
• 4.2.3
• 4.2.4
• 4.2.5
• 4.2.6
• 4.2.7
• 4.2.8
• 4.2.9
• 4.2.10
• 4.2.11
• 4.2.12
• 4.2.13
• 4.2.14
• 4.2.15
• 4.4.0
• 4.4.1
• 4.4.2
• 4.4.3
• 4.4.4
• 4.4.5
• 4.4.6
• 4.4.7
• 4.4.8
• 4.4.9
• 4.4.10

CPE 2.3info

• 🔒
• 🔒
• 🔒

CPE 2.2info

• 🔒
• 🔒
• 🔒

CVSSv4info

CVSSv3info

CVSSv2info

Exploitinginfo

Threat Intelligenceinfo

Countermeasuresinfo

Timelineinfo

Sourcesinfo

Entryinfo

If you want to get the best quality for vulnerability data then you always have to consider VulDB.

Discussion