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

> Attackers can execute arbitrary code by uploading a crafted PDF file to the ARIS application.

- **Severity:** Medium 6.8 (`CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:U/C:H/I:H/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 7 Jan 2026
- **Updated:** 7 Jan 2026
- **Also known as:** GHSA-9f4w-fmcx-4c8w

## What is CVE-2025-66837?

CVE-2025-66837 is a medium-severity vulnerability in n/a, published on 7 Jan 2026. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.

### Official description

A file upload vulnerability in ARIS 10.0.23.0.3587512 allows attackers to execute arbitrary code via uploading a crafted PDF file/Malware

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

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

It affects 1 product.


Products: Softwareag Aris.

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

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

## Is CVE-2025-66837 being exploited?

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

Public exploit code:

- https://github.com/saykino/CVE-2025-66837 (github_poc): https://github.com/saykino/CVE-2025-66837

## Other vulnerabilities in n/a

- [CVE-2025-66838](https://insights.sbomify.com/CVE-2025-66838/): Denial of service in n/a (medium 6.5)

## Fix prompt for AI coding agents

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

What it is: CVE-2025-66837 is a medium-severity vulnerability in n/a, published on 7 Jan 2026. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2025-66837 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-66837/ (Markdown: https://insights.sbomify.com/CVE-2025-66837/index.md)
```

## Sources

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

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