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.
CVE-2026-53573
This medium-severity CVE scores 4.8 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.4%, top 69% of all CVEs by exploit prediction. GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).
- Lower severity and no public exploit yet
No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.
- CVSS v3
- 4.8
- EG Score
- 4.8(medium)
- EG Risk
- 22(Track)EG Risk 22/100SSVC: Track
EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).
How it’s computedSeverity48% × 45%Exploitation0% × 40%Automatability0% × 15%Action: Routine — remediate on your standard cadence. - EPSS PROB
- 0%
- EPSS %ILE
- 31%
- KEV
- Not listed
Published
July 31, 2026
Last Modified
August 3, 2026
Advisory Details (7)
Auto-updated Jul 31, 2026GeoNetwork v4.4.11
Patch available: geonetwork/core-geonetwork 4.4.11
https://github.com/geonetwork/core-geonetwork/releases/tag/4.4.11GeoNetwork v4.2.16
Patch available: geonetwork/core-geonetwork 4.2.16
https://github.com/geonetwork/core-geonetwork/releases/tag/4.2.16commit cde9b6481a29 (geonetwork/core-geonetwork)
Patch available: geonetwork/core-geonetwork 4.4.11 (contains commit cde9b6481a29)
https://github.com/geonetwork/core-geonetwork/commit/cde9b6481a29e2473b7b74479b4e3fd6843bac4ecommit 0d74f673dfc9 (geonetwork/core-geonetwork)
Patch available: geonetwork/core-geonetwork 4.2.16 (contains commit 0d74f673dfc9)
https://github.com/geonetwork/core-geonetwork/commit/0d74f673dfc926bde935819ed34636d789b2fecd[Backport 4.2.x] Harden login redirect URL validation
Patch available: geonetwork/core-geonetwork 4.2.16 (PR #9309 merged 2026-06-01)
https://github.com/geonetwork/core-geonetwork/pull/9309Harden login redirect URL validation
Patch available: geonetwork/core-geonetwork 4.4.11 (PR #9307 merged 2026-06-01)
https://github.com/geonetwork/core-geonetwork/pull/9307Open Redirect Bypass in core-geonetwork OAuth2/OIDC and Keycloak login filters · Advisory · geonetwork/core-geonetwork · GitHub
https://github.com/geonetwork/core-geonetwork/security/advisories/GHSA-pjp7-q6wp-97qxVendor Advisories for CVE-2026-53573(1)
These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.
Affected Packages
(1 across 1 ecosystem)
Maven(1)
| Package | Vulnerable range | Fixed in | Dependents |
|---|---|---|---|
| org.geonetwork-opensource:geonetwork | — | 4.4.11 | — |
Weakness Classification(1)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
Data Freshness Timeline
(refreshed 14× in last 7d / 40× in last 30d)
Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.
- 2026-08-21 02:19 UTCEG score recompute
- 2026-08-20 22:55 UTCEPSS rescore
- 2026-08-20 00:17 UTCEG score recompute
- 2026-08-19 17:04 UTCEPSS rescore
- 2026-08-18 22:15 UTCEG score recompute
- 2026-08-18 13:48 UTCEPSS rescore
- 2026-08-17 20:13 UTCEG score recompute
- 2026-08-17 13:47 UTCEPSS rescore
- 2026-08-16 18:07 UTCEG score recompute
- 2026-08-16 14:56 UTCEPSS rescore
- 2026-08-16 02:14 UTCEPSS rescore
- 2026-08-15 16:05 UTCEG score recompute
- 2026-08-15 01:30 UTCEPSS rescore
- 2026-08-14 14:02 UTCEG score recompute
- 2026-08-13 22:00 UTCEPSS rescore
- 2026-08-13 12:00 UTCEG score recompute
- 2026-08-12 13:51 UTCEPSS rescore
- 2026-08-12 09:58 UTCEG score recompute
- 2026-08-11 07:55 UTCEG score recompute
- 2026-08-11 00:00 UTCEPSS rescore
- 2026-08-10 05:54 UTCEG score recompute
- 2026-08-09 13:46 UTCEPSS rescore
- 2026-08-09 03:52 UTCEG score recompute
- 2026-08-08 16:37 UTCEPSS rescore
- 2026-08-08 01:50 UTCEG score recompute
Show 15 moreShow fewer
- 2026-08-06 23:48 UTCEG score recompute
- 2026-08-06 13:47 UTCEPSS rescore
- 2026-08-05 21:46 UTCEG score recompute
- 2026-08-05 19:17 UTCEPSS rescore
- 2026-08-04 19:45 UTCEG score recompute
- 2026-08-04 15:10 UTCEPSS rescore
- 2026-08-04 10:39 UTCEPSS rescore
- 2026-08-03 17:42 UTCEG score recompute
- 2026-08-03 17:12 UTCEG score recompute
- 2026-08-03 10:36 UTCEPSS rescore
- 2026-08-03 03:35 UTCEG score recompute
- 2026-08-02 02:27 UTCEPSS rescore
- 2026-07-31 23:31 UTCEG score recompute
- 2026-07-31 22:28 UTCEG score recompute
- 2026-07-31 22:28 UTCMITRE cvelistV5first tracked
Frequently asked(5)
What is CVE-2026-53573?
When was CVE-2026-53573 disclosed?
Is CVE-2026-53573 actively exploited?
What is the CVSS score of CVE-2026-53573?
How do I remediate CVE-2026-53573?
Dependency Blast Radius
See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-53573
Is Your Infrastructure Affected by CVE-2026-53573?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.