CVE-2026-63219: Missing authorization in GeoNetwork formatter upload API
CVE-2026-63219 is a missing-authorization vulnerability in GeoNetwork's API for creating formatters through file uploads. Affected versions expose this functionality without authorization checks, allowing unauthenticated attackers to upload arbitrary XSL or ZIP formatter files into the server-side formatter directory. The vulnerability independently provides unauthorized write access to server storage. When chained with CVE-2026-58400, an unsafe Saxon XSLT processor configuration, it enables unauthenticated remote code execution. Fixes are available in GeoNetwork 4.4.12 and 4.2.17.
Impact, mitigation & remediation
What it means and what to do now: patch path, interim mitigations, and the assume-compromise checklist.
Impact
What an attacker gets, and what they’ve been doing with it.
Unauthenticated attackers can write attacker-controlled formatter files into the GeoNetwork formatter directory, compromising the integrity of server-side storage. Remote code execution is established for a chain with CVE-2026-58400: an uploaded malicious stylesheet can invoke operating-system commands when processed, executing with the privileges of the GeoNetwork process user. One account attributes remote code execution directly to the upload vulnerability, but the more detailed technical explanation distinguishes unauthorized file writes from the separate unsafe-processing vulnerability.
Mitigation
If you can’t patch tonight, do this now.
Until upgrading, block POST, PUT, and PATCH requests to the GeoNetwork formatter API at the reverse proxy, permitting only GET, HEAD, and OPTIONS. This restriction also prevents legitimate formatter uploads through the administrative console. Where operationally feasible, disable or restrict the file-upload API and XSLT processing, review upload permissions, and monitor for unexpected formatter uploads and command execution.
Remediation
Patch, then assume compromise.
Upgrade GeoNetwork to version 4.4.12 or 4.2.17, as appropriate for the deployed release branch. These releases also address the unsafe XSLT processing vulnerability used in the remote-code-execution chain.
Exploits
1 exploit validated by Mallory's analysis.
References
Frequently asked questions
- Is CVE-2026-63219 exploited in the wild?
- Yes. As of Oct 9, 2026, Mallory has reports of exploitation in the wild.
- Is there a public exploit for CVE-2026-63219?
- Yes. Mallory tracks 1 public exploit or proof of concept for CVE-2026-63219, the earliest disclosed Nov 17, 2026.
- Is there a patch for CVE-2026-63219?
- Upgrade GeoNetwork to version 4.4.12 or 4.2.17, as appropriate for the deployed release branch. These releases also address the unsafe XSLT processing vulnerability used in the remote-code-execution chain.
- How severe is CVE-2026-63219?
- CVE-2026-63219 has a CVSS v3.1 score of 8.6 (High) and an EPSS score of 0.47% (41st percentile) as of Oct 9, 2026.
Recent activity
9 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.