# CVE-2025-13654: CVE-2025-13654

> A stack buffer overflow in the duc disk management tool allows out-of-bounds reads, potentially leading to code execution or crashes.

- **Severity:** High 7.5 (`CVSS:3.1/AV:N/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:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 5 Dec 2025
- **Updated:** 29 Jan 2026
- **Also known as:** DEBIAN-CVE-2025-13654, GHSA-9fqr-94hm-qxr9, UBUNTU-CVE-2025-13654, openSUSE-SU-2025:15835-1

## What is CVE-2025-13654?

CVE-2025-13654 is a high-severity memory corruption vulnerability in Duc, published on 5 Dec 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

A stack buffer overflow vulnerability exists in the buffer_get function of duc, a disk management tool, where a condition can evaluate to true due to underflow, allowing an out-of-bounds read.

Weakness: CWE-787 (Out-of-bounds Write)

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

It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `duc` | openSUSE:Tumbleweed | All versions | 1.4.6-1.1 |

Products: Zevv Duc.

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

Apply the vendor's patch.

## Is CVE-2025-13654 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2025-13654 is a high-severity memory corruption vulnerability in Duc, published on 5 Dec 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-13654 exists.

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

## Sources

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

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