# CVE-2026-63219: Unauthenticated file upload via missing authorization on formatter upload endpoint

> Unauthenticated attackers can upload arbitrary files to the GeoNetwork formatter directory due to missing authorization on the upload endpoint.

- **Severity:** High 8.6 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:N/I:H/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 3 Sep 2026
- **Updated:** 3 Sep 2026
- **Also known as:** GHSA-mh22-prqr-vf42

## What is CVE-2026-63219?

CVE-2026-63219 is a high-severity missing authorization vulnerability in core-geonetwork, published on 3 Sep 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

GeoNetwork is a catalog application to manage spatially referenced resources. Prior to versions 4.4.12 and 4.2.17, the API endpoint for creating a new formatter via file upload is unprotected and allows the upload of external uncontrolled files. An unauthenticated attacker can upload arbitrary `.xsl` or `.zip` formatter files to the server.  An unauthenticated attacker can write arbitrary files into the GeoNetwork formatter directory. On its own this constitutes unauthorized write access to server storage. The issue is patched in GeoNetwork versions 4.4.12 and 4.2.17.

Weakness: CWE-862 (Missing Authorization)

## Which versions are affected by CVE-2026-63219?


## How do I fix CVE-2026-63219?

No fix has been published for CVE-2026-63219 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-63219 being exploited?

There is no known exploitation of CVE-2026-63219 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-63219 and fix it if it is affected.

What it is: CVE-2026-63219 is a high-severity missing authorization vulnerability in core-geonetwork, published on 3 Sep 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-63219 in the wild and no public exploit code.

Affected product: core-geonetwork. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-63219/ (Markdown: https://insights.sbomify.com/CVE-2026-63219/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-63219
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-63219
- OSV: https://osv.dev/vulnerability/CVE-2026-63219

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-63219/
Summaries are generated and may contain mistakes; the official description above is the record.