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

> Authenticated attackers can upload malicious web.config files to achieve remote code execution on Aranda Service Desk Web Edition servers.

- **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:** 5 Mar 2026
- **Updated:** 21 Apr 2026
- **Also known as:** GHSA-qg2h-86fw-x9x4

## What is CVE-2025-70995?

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

### Official description

An issue in Aranda Service Desk Web Edition (ASDK API 8.6) allows authenticated attackers to achieve remote code execution due to improper validation of uploaded files. An authenticated user can upload a crafted web.config file by sending a crafted POST request to /ASDKAPI/api/v8.6/item/addfile, which is processed by the ASP.NET runtime. The uploaded configuration file alters the execution context of the upload directory, enabling compilation and execution of attacker-controlled code (e.g., generation of an .aspx webshell). This allows remote command execution on the server without user interaction beyond authentication, impacting both On-Premise and SaaS deployments. The vendor has fixed the issue in Aranda Service Desk V8 8.30.6.

Weakness: CWE-94 (Improper Control of Generation of Code)

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


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

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

## Is CVE-2025-70995 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-70995 exists.

Public exploit code:

- CVE-2025-70995 (github_poc): https://github.com/0xcronos/CVE

## Fix prompt for AI coding agents

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

What it is: CVE-2025-70995 is a high-severity vulnerability in n/a, published on 5 Mar 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-70995 exists.

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-70995/ (Markdown: https://insights.sbomify.com/CVE-2025-70995/index.md)
```

## Sources

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

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