# CVE-2025-34457: wb2osz/direwolf <= 1.8.1 Stack-based Buffer Overflow DoS

> Remote attackers can cause denial of service in Dire Wolf via stack-based buffer overflow in KISS frame processing.

- **Severity:** High 8.7 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:N/VA:H/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 22 Dec 2025
- **Updated:** 29 Oct 2026
- **Also known as:** DEBIAN-CVE-2025-34457, GHSA-28g2-hxcm-j3q2, UBUNTU-CVE-2025-34457

## What is CVE-2025-34457?

CVE-2025-34457 is a high-severity memory corruption vulnerability in wb2osz Dire Wolf, published on 22 Dec 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

wb2osz/direwolf (Dire Wolf) versions up to and including 1.8.1, prior to commit 694c954, contain a stack-based buffer overflow vulnerability in the function kiss_rec_byte() located in src/kiss_frame.c. When processing crafted KISS frames that reach the maximum allowed frame length (MAX_KISS_LEN), the function appends a terminating FEND byte without reserving sufficient space in the stack buffer. This results in an out-of-bounds write followed by an out-of-bounds read during the subsequent call to kiss_unwrap(), leading to stack memory corruption or application crashes. This vulnerability may allow remote unauthenticated attackers to trigger a denial-of-service condition.

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

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


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

Apply the vendor's patch.

## Is CVE-2025-34457 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2025-34457 is a high-severity memory corruption vulnerability in wb2osz Dire Wolf, published on 22 Dec 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2025-34457 in the wild and no public exploit code.

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

## Sources

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

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