# CVE-2025-67260: File upload in n/a

> Attackers can upload malicious files to Terrapack components to execute arbitrary code, posing a critical risk to GIS infrastructure.

- **Severity:** High 8.8 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 20 Mar 2026
- **Updated:** 5 Jul 2026
- **Also known as:** GHSA-wjmh-wmx9-9v38

## What is CVE-2025-67260?

CVE-2025-67260 is a high-severity vulnerability in n/a, published on 20 Mar 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

The Terrapack software, from ASTER TEC / ASTER S.p.A., with the indicated components and versions has a file upload vulnerability that may allow attackers to execute arbitrary code. Vulnerable components include Terrapack TkWebCoreNG:: 1.0.20200914, Terrapack TKServerCGI 2.5.4.150, and Terrapack TpkWebGIS Client 1.0.0.

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

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

It affects 3 products.


Products: Aster-Te Terrapack Tkservercgi, Aster-Te Terrapack Tkwebcoreng, Aster-Te Terrapack Tpkwebgis.

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

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

## Is CVE-2025-67260 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2025-67260 is a high-severity vulnerability in n/a, published on 20 Mar 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2025-67260 in the wild and no public exploit code.

Affected product: n/a. 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-67260/ (Markdown: https://insights.sbomify.com/CVE-2025-67260/index.md)
```

## Sources

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

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