Live Exposure Defense: From CVE to Confirmed Exposure in 12 Hours – See more

Back
New CVE Detected

CVE-2026-63219 – Unauthenticated File Upload leading to RCE – GeoNetwork core-geonetwork < 4.2.17 /

Be the first to know when new zero-days emerge:

Subscribe to Email Alerts
Subscribe to RSS Feed

Summary

CVE-2026-63219 is a missing-authorization vulnerability (CWE-862) in GeoNetwork, an open-source geospatial metadata catalog widely used by government Spatial Data Infrastructure programs. The formatter upload API endpoint is exposed without any authentication or authorization check, letting a remote, unauthenticated attacker write arbitrary files into the server’s formatter directory. The issue carries a CVSS v3.1 base score of 8.6 (High).

Technical details

  • Root cause: the API endpoint responsible for creating a new formatter via file upload is missing an authorization/@PreAuthorize check, so it does not require any credentials.
  • Trigger condition: an attacker sends an unauthenticated request to the formatter upload endpoint (/geonetwork/srv/api/formatters) with a crafted .xsl or .zip formatter file.
  • Attack vector: network-facing HTTP API, no privileges and no user interaction required (AV:N/AC:L/PR:N/UI:N).
  • Impact: unauthorized write access to server storage (formatter directory); the CVSS vector reflects High integrity impact with no direct confidentiality or availability loss. Publicly discussed research also notes that chaining this upload with a separately-tracked XSLT processing weakness in GeoNetwork can enable unauthenticated remote code execution, though that secondary flaw is a distinct CVE and its own preconditions apply.

Affected software

  • geonetwork/core-geonetwork (gn-services and gn-web-app artifacts): versions ≤ 4.2.16 and versions 4.3.0 through ≤ 4.4.11.
  • Fixed in versions 4.2.17 and 4.4.12.

Severity

CVSS v3.1 Base Score: 8.6 (High)
Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:N/I:H/A:N

Mitigation and recommended actions

  • Immediate: Upgrade GeoNetwork to version 4.2.17 (for 4.2.x deployments) or 4.4.12 (for 4.3.x/4.4.x deployments).
  • If immediate patching is not possible: block write operations to the /geonetwork/srv/api/formatters endpoint at a reverse proxy (e.g., Apache httpd or Nginx) until the upgrade can be completed. Note this will also block legitimate administrative formatter uploads.
  • Review the formatter directory and any recently uploaded .xsl/.zip files for unauthorized or unexpected content.

How IONIX identifies potentially affected assets

IONIX matches the following signal against data already collected when it crawled the asset; identifying the technology sends no request beyond that crawl.

  • Raw response body: href="...gn_search_default.css"

References

Are you exposed?

Get a free report of your organization’s exposure to this CVE and threat

  • Mapping of all Assets with this Technology
  • Identification of potentially exposed assets to this CVE
  • Confirmation of verified exploitable assets
Get Exposure Report

How IONIX’s External Exposure Management Platform Detects and Validates
Zero-Days to Shrink MTTR

1

Map your entire attack surface (continously)

IONIX uses multi-factor discovery methods, including DNS analysis, certificate mapping, metadata inspection, and more, to automatically map every internet-facing asset across your environment. This includes cloud instances, third-party platforms, shadow IT, and even forgotten infrastructure that traditional tools miss.

2

Monitor for new CVEs

Dozens of threat intel feeds using agentic technology are continuously analyzed to detect the appearance of proof-of-concept code, exploit kits, and indicators of active targeting. IONIX goes further by applying AI to proactively evaluate whether emerging vulnerabilities are likely to be exploited, even before PoCs go public.

3

Identify Potential External Exposures

Not all CVEs matter. IONIX filters vulnerabilities by asking attacker-centric questions: Can it be reached from the internet? Does it require authentication? Is it being exploited in the wild? This dramatically reduces noise and focuses teams on threats that can actually be weaponized.

4

Create Safe, Scalable Exploit Validations

IONIX transforms real-world PoCs into safe, non-intrusive test payloads that can be run in production environments without disruption. These simulations are precisely targeted to the systems that are vulnerable, ensuring rapid validation without unnecessary load.

5

Execute Exploit Validations

By combining context about software stack, versioning, exposure status, and reachability, IONIX ensures that only the right payloads are executed against the right assets, maximizing efficiency and minimizing risk.

6

Drive Fast and Actionable Remediation

Results are routed through integrations with ticketing, SOAR, and SIEM tools. Issues are written in plain language, bundled into remediation clusters, and prioritized based on asset criticality, exploitability, and blast radius. This shortens mean time to remediation (MTTR) and empowers teams to act with confidence.

Are you exposed?

Get a free report of your organization’s exposure to this CVE and threat

  • Mapping of all Assets with this Technology
  • Identification of potentially exposed assets to this CVE
  • Confirmation of verified exploitable assets
Get Exposure Report
Close

Subscribe to Threat Center RSS

Copy/paste the link below into your preferred RSS reader or follow these instructions to subscribe to Slack alerts.

Open RSS feedSlack setup instructions

Close

Get Real-Time CVE Alerts to Your Email

Be the first to know when new zero-days emerge