# CVE-2026-54634: Hamlib: rigctld `send_raw` Stack Out-of-Bounds Write and Uninitialized Memory Disclosure

> Remote attackers can crash the rigctld daemon or leak stack memory via a malformed send_raw command in Hamlib.

- **Severity:** High 7.3 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:L`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 17 Sep 2026
- **Updated:** 18 Sep 2026
- **Also known as:** DEBIAN-CVE-2026-54634, GHSA-gpcq-c37x-pr46, MGASA-2026-0475, UBUNTU-CVE-2026-54634, openSUSE-SU-2026:11089-1, openSUSE-SU-2026:21155-1

## What is CVE-2026-54634?

CVE-2026-54634 is a high-severity memory corruption vulnerability in Hamlib, published on 17 Sep 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Hamlib is a ham radio control library for radios, rotators, and amplifiers. Prior to 4.7.2, the unauthenticated rigctld send_raw command on TCP port 4532 reaches rigctl_send_raw() in tests/rigctl_parse.c, which writes a NUL byte at buf[buf_len + 1] outside its 200-byte stack buffer, and rig_send_raw() in src/rig.c, which copies reply_len - 1 bytes instead of the actual nbytes received. A remote client can send the CR terminator with a short payload to trigger both flaws in one command under the default no-password configuration. The out-of-bounds write can crash the daemon or corrupt adjacent stack memory, while the oversized copy can return up to 198 bytes of uninitialized stack data to the client. This issue is fixed in version 4.7.2.

Weakness: CWE-908 (Use of Uninitialized Resource), CWE-787 (Out-of-bounds Write)

## Which versions are affected by CVE-2026-54634?


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `hamlib` | openSUSE:Leap 16.0 | All versions | 4.7.2-bp160.1.1 |
| `hamlib` | openSUSE:Tumbleweed | All versions | 4.7.2-1.1 |

## How do I fix CVE-2026-54634?

Upgrade to a fixed version.

## Is CVE-2026-54634 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-54634 and fix it if it is affected.

What it is: CVE-2026-54634 is a high-severity memory corruption vulnerability in Hamlib, published on 17 Sep 2026. 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-2026-54634 in the wild and no public exploit code.

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

## Sources

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

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