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

> Attackers can cause a denial of service in GNU Unrtf by injecting crafted input into the filename parameter, leading to a stack overflow.

- **Severity:** Medium 6.2 (`CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 23 Dec 2025
- **Updated:** 30 Dec 2025
- **Also known as:** DEBIAN-CVE-2025-65410, GHSA-h793-prqc-9r54, OESA-2026-1012, OESA-2026-1013, OESA-2026-1014, OESA-2026-1015, OESA-2026-1016, OESA-2026-1017, UBUNTU-CVE-2025-65410

## What is CVE-2025-65410?

CVE-2025-65410 is a medium-severity denial of service vulnerability in n/a, published on 23 Dec 2025. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

A stack overflow in the src/main.c component of GNU Unrtf v0.21.10 allows attackers to cause a Denial of Service (DoS) via injecting a crafted input into the filename parameter.

Weakness: CWE-121 (Stack-based Buffer Overflow)

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

It affects 1 product.


Products: Unrtf Project Unrtf.

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

Upgrade to a fixed version.

## Is CVE-2025-65410 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2025-65411](https://insights.sbomify.com/CVE-2025-65411/): Null dereference in n/a (high 7.5)
- [CVE-2016-10091](https://insights.sbomify.com/CVE-2016-10091/): Memory corruption in n/a (high 7.5)
- [CVE-2014-9275](https://insights.sbomify.com/CVE-2014-9275/): Memory corruption in n/a (high 7.5)

## Fix prompt for AI coding agents

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

What it is: CVE-2025-65410 is a medium-severity denial of service vulnerability in n/a, published on 23 Dec 2025. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2025-65410 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-65410/ (Markdown: https://insights.sbomify.com/CVE-2025-65410/index.md)
```

## Sources

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

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