Skip to main content
Mallory
HighPublic exploitVulnerability

CVE-2026-63219: Missing authorization in GeoNetwork formatter upload API

Published Sep 3, 2026 · Updated 1 month ago
Trending this weekNot trendingOutside this week’s top 100
Mention activity · 30 daysNo mention activity in the last 30 days.
CVSS8.6High · v3.1
EPSS0.47%41st percentile
CISA KEVNoNot listed
In the wildReported2 exploitation records in Mallory
IdentifiersCVE-2026-63219CWE-862 · Missing Authorization

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.

Do you run this?See affected versions in your environment and whether adversaries are exploiting this vulnerability against assets like yours.
Check your exposure
Analyst brief

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.

Public exploits

Exploits

1 exploit validated by Mallory's analysis.

View more in app →
GNSShellThe repository contains README.md and two standalone Python clients, gns_rce.py and gnshell.py, with embedded XSLT and shell payloads. The supplied file sizes total 36,081 bytes; no repository URL, revision, or archive size was supplied. Repository archive size is therefore recorded as 0 (unknown). The exploit chains an allegedly missing authorization check on formatter uploads with unsafe Saxon Java extension execution. The clients obtain a CSRF token, upload a malicious stylesheet, discover or accept a readable metadata UUID, and render that record through the uploaded formatter. Uploading alone does not execute the payload. The README attributes these issues to CVE-2026-63219 and CVE-2026-58400, identifies 4.4.11 as affected, and claims fixes in 4.4.12 and 4.2.17. These identifiers and affected/fixed-version claims were not independently verified; source comments also make a broader <=4.4.11 claim. gns_rce.py is fully visible and implements version discovery, token acquisition, CSW UUID discovery, one-time upload, formatter reuse, single-command execution, and line-by-line piped commands. Each command starts a separate sh process, so shell state is not preserved between commands. HTTP success is reported rather than the remote command's exit status. TLS certificate verification is disabled by default. Its distinctive User-Agent is 'Mozilla/5.0 GNSShell-RCE'. gnshell.py adds a shell agent that uses script(1), a named pipe, an output file, and offset-based base64 polling to relay an interactive bash PTY over HTTP rather than opening a reverse-shell connection. Its visible agent supports initialization, input, output polling, terminal resizing, liveness checks, and cleanup. Output chunks are capped at 262,144 bytes. The middle of this file is truncated in the supplied content, preventing complete inspection of its stylesheet and client-side transport implementation. The formatter remains installed after use; the README states deleting it requires administrative authorization. PTY session files are normally removed unless retention is requested. The scoped rm -rf operations target the PTY session directory and are consistent with session initialization/cleanup, not evidence of a fake exploit. No external exfiltration destination or framework integration is apparent.c0gnit00 · Disclosed Nov 17, 2026 · python · xslt · webOperational
FAQ

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.
Activity feed

Recent activity

9 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.

View more in app →
Do you run this?See affected versions in your environment and whether adversaries are exploiting this vulnerability against assets like yours.
Check your exposure
Mallory platform

The version that knows your environment.

This page is what’s public. Mallory adds the parts that aren’t: which of your assets are affected, which adversaries are exploiting it right now, and which detections to deploy tonight.
Exposure mappingQuery your assets running an affected version, and investigate the blast radius.
Threat actor evidenceEvery report linking this CVE to a named adversary.
Associated malwareMalware families linked to this CVE, with evidence and IOCs.
Detection signaturesYARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Vendor-by-vendor mappingCross-references every affected SKU, including bundled OEM variants.
Social activity4Community discussion across Reddit, Mastodon, and other social sources.