CVE-2026-63219
Unauthenticated file upload allows arbitrary files to be written to GeoNetwork formatter directory.
Is CVE-2026-63219 being exploited?
Not confirmed. CVE-2026-63219 does not appear in CISA's Known Exploited Vulnerabilities catalog, which records only exploitation that has been observed and reported publicly. That is evidence of absence of a report, not evidence the flaw is unattacked. EPSS currently estimates a 0.47% probability of exploitation in the next 30 days.
How severe is CVE-2026-63219?
CVE-2026-63219 is rated High. Severity describes how bad exploitation would be, not how likely it is: pair it with exploitation evidence before deciding what to patch first.
Is there a patch for CVE-2026-63219?
Yes. A fix has been recorded for CVE-2026-63219. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.
What does CVE-2026-63219 affect?
CVE-2026-63219 affects GeoNetwork < 4.4.12, GeoNetwork < 4.2.17. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.
What should I do about CVE-2026-63219?
Upgrade to GeoNetwork 4.4.12 or 4.2.17; block uploads until patched.
Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.
Unauthenticated attacker can upload .xsl/.zip, write arbitrary files to server storage, enabling persistent code execution, file tampering, or site compromise.
Immediate action required
- affected>= 4.3.0 and < 4.4.12
- affected< 4.2.17
As published in the CVE Program record. A version outside these ranges is not a statement that it is unaffected — vendors sometimes understate a range, and distribution-backported builds carry upstream numbers that do not reflect what was patched into them.