# CVE-2025-66838: Denial of service in n/a

> Attackers can exhaust server resources by uploading files at an unrestricted rate due to missing rate limiting in the file upload functionality.

- **Severity:** Medium 6.5 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/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:** 7 Jan 2026
- **Updated:** 7 Jan 2026
- **Also known as:** GHSA-2xw3-m2wf-5r5m

## What is CVE-2025-66838?

CVE-2025-66838 is a medium-severity denial of service vulnerability in n/a, published on 7 Jan 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

In Aris v10.0.23.0.3587512 and before, the file upload functionality does not enforce any rate limiting or throttling, allowing users to upload files at an unrestricted rate. An attacker can exploit this behavior to rapidly upload a large volume of files, potentially leading to resource exhaustion such as disk space depletion, increased server load, or degraded performance

Weakness: CWE-770 (Allocation of Resources Without Limits or Throttling)

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

It affects 1 product.


Products: Softwareag Aris.

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

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

## Is CVE-2025-66838 being exploited?

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

Public exploit code:

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

## Other vulnerabilities in n/a

- [CVE-2025-66837](https://insights.sbomify.com/CVE-2025-66837/): File upload in n/a (medium 6.8)

## Fix prompt for AI coding agents

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

What it is: CVE-2025-66838 is a medium-severity denial of service vulnerability in n/a, published on 7 Jan 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-66838 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-66838/ (Markdown: https://insights.sbomify.com/CVE-2025-66838/index.md)
```

## Sources

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

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