# CVE-2025-67706: Unvalidated File Upload vulnerability in ArcGIS Server.

> Remote attackers can upload arbitrary files to ArcGIS Server, though execution and privilege escalation are prevented by server controls.

- **Severity:** Medium 5.6 (`CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:L/A:L`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 31 Dec 2025
- **Updated:** 19 Feb 2026
- **Also known as:** GHSA-mvxv-qjhv-59fg

## What is CVE-2025-67706?

CVE-2025-67706 is a medium-severity vulnerability in Esri Arcgis Server, published on 31 Dec 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

ArcGIS Server versions 11.5 and earlier on Windows and Linux do not sufficiently validate uploaded files, enabling a remote unauthenticated attacker to upload arbitrary files to the server’s designated upload directories.

However, the server’s architecture enforces controls that restrict uploaded files to non‑executable storage locations and prevent modification or replacement of existing application components or system configurations. Uploaded files cannot be executed, leveraged to escalate privileges, or used to access sensitive data.

Because the issue does not enable execution, service disruption, unauthorized access, or integrity compromise, its impact on confidentiality, integrity, and availability is low. Note that race conditions, secret values, or man‑in‑the‑middle conditions are required for exploitation.

Weakness: CWE-434 (Unrestricted Upload of File with Dangerous Type)

## Which versions are affected by CVE-2025-67706?

It affects 1 product.


Products: Esri Arcgis Server.

## How do I fix CVE-2025-67706?

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

## Is CVE-2025-67706 being exploited?

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

## Other vulnerabilities in Esri Arcgis Server

- [CVE-2025-57870](https://insights.sbomify.com/CVE-2025-57870/): BUG-000179884 - There is a security vulnerability in ArcGIS Server Feature Services. (critical 10.0)
- [CVE-2026-9181](https://insights.sbomify.com/CVE-2026-9181/): Directory Traversal in ArcGIS Server (critical 9.8)
- [CVE-2026-9182](https://insights.sbomify.com/CVE-2026-9182/): Unvalidated File Upload vulnerability in ArcGIS Server. (critical 9.8)
- [CVE-2020-35712](https://insights.sbomify.com/CVE-2020-35712/): Server-side request forgery in n/a (critical 9.8)
- [CVE-2021-29102](https://insights.sbomify.com/CVE-2021-29102/): There is a Server-Side Request Forgery (SSRF) vulnerability in Esri ArcGIS Server Manager version 10.8.1 and below. (critical 9.1)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2025-67706 and fix it if it is affected.

What it is: CVE-2025-67706 is a medium-severity vulnerability in Esri Arcgis Server, published on 31 Dec 2025. 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-2025-67706 in the wild and no public exploit code.

Affected product: Esri Arcgis Server. 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-2025-67706/ (Markdown: https://insights.sbomify.com/CVE-2025-67706/index.md)
```

## Sources

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

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