# CVE-2025-34458: wb2osz/direwolf <= 1.8.1 Reachable Assertion DoS

> Remote attackers can cause denial of service in Dire Wolf by sending malformed APRS frames that trigger an assertion failure.

- **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-34458, GHSA-r4wq-665p-whrq, UBUNTU-CVE-2025-34458

## What is CVE-2025-34458?

CVE-2025-34458 is a high-severity denial of service 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 3658a87, contain a reachable assertion vulnerability in the APRS MIC-E decoder function aprs_mic_e() located in src/decode_aprs.c. When processing a specially crafted AX.25 frame containing a MIC-E message with an empty or truncated comment field, the application triggers an unhandled assertion checking for a non-empty comment. This assertion failure causes immediate process termination, allowing a remote, unauthenticated attacker to cause a denial of service by sending malformed APRS traffic.

Weakness: CWE-617 (Reachable Assertion)

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


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

Apply the vendor's patch.

## Is CVE-2025-34458 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2025-34458 is a high-severity denial of service 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: It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-34458 exists.

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

## Sources

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

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