Is CVE-2026-63219 exploited in the wild?

No. Junglewise Threat Intelligence has no report of CVE-2026-63219 being exploited in the wild.

How severe is CVE-2026-63219?

High severity, with a CVSS score of 8.6, published 3 September 2026.

Which products and versions are affected?

GeoNetwork GeoNetwork before 4.4.12 and 4.2.17.

Is there a fix for CVE-2026-63219?

A patch was published on 2026-09-03: Fixed in GeoNetwork 4.4.12 and 4.2.17 Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.

How is CVE-2026-63219 attacked?

It is attacked over the network, in a web application.

Am I affected by CVE-2026-63219?

Check whether anything you run is named in the advisory. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

CVE-2026-63219: GeoNetwork unauthenticated file upload via missing authorization in formatter endpoint

CVE-2026-63219 · Severity: high · CVSS 8.6 · Published 2026-09-03

GeoNetwork is a catalog application used to manage and discover geospatial data resources. An unauthenticated attacker can upload arbitrary files (such as `.xsl` or `.zip` formatters) to the server through an unprotected API endpoint, gaining unauthorized write access to the GeoNetwork formatter directory. This could enable file system manipulation and potentially lead to further attacks on the application.

Quick answers

Is CVE-2026-63219 exploited in the wild?: No. Junglewise Threat Intelligence has no report of CVE-2026-63219 being exploited in the wild.
How severe is CVE-2026-63219?: High severity, with a CVSS score of 8.6, published 3 September 2026.
Which products and versions are affected?: GeoNetwork GeoNetwork before 4.4.12 and 4.2.17.
Is there a fix for CVE-2026-63219?: A patch was published on 2026-09-03: Fixed in GeoNetwork 4.4.12 and 4.2.17 Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
How is CVE-2026-63219 attacked?: It is attacked over the network, in a web application.
Am I affected by CVE-2026-63219?: Check whether anything you run is named in the advisory. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

Technical details

The vulnerability is an authorization bypass (missing authentication/authorization checks) in the formatter file upload API endpoint. The vulnerable component is the formatter upload functionality, which accepts `.xsl` and `.zip` files without proper access control. An unauthenticated attacker can invoke this API endpoint over the network to write arbitrary files directly into the GeoNetwork formatter directory. While file upload alone constitutes unauthorized write access, combined with other vulnerabilities (such as CVE-2026-58400 for unsafe XSLT processing), it may enable remote code execution. The vulnerability is patched in GeoNetwork versions 4.4.12 and 4.2.17.

Affected products

GeoNetwork GeoNetwork before 4.4.12 and 4.2.17

Timeline

2026-09-03: disclosed
2026-09-03: patched: Fixed in GeoNetwork 4.4.12 and 4.2.17

References

This page as Markdown. Free to reuse under CC BY 4.0 with a link back.