# CVE-2026-129606: Out-of-bounds write in HOTP trusted application of Samsung Open Source mTower

> An out-of-bounds write in Samsung mTower's HOTP trusted application may let attackers corrupt memory; users of mTower should care.

- **Severity:** High 7.1 (`CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Harmful if only installed:** No
- **Needs a specific call:** No
- **Fix available:** No
- **Published:** 16 Nov 2026
- **Updated:** 16 Nov 2026
- **Also known as:** GHSA-xfmm-86vr-x3pj

## What is CVE-2026-129606?

CVE-2026-129606 is a high-severity memory corruption vulnerability in Samsung Open Source mTower, published on 16 Nov 2026. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

Buffer Copy without Checking Size of Input ('Classic Buffer Overflow') vulnerability in Samsung Open Source mTower allows Overflow Buffers.

Weakness: CWE-120 (Buffer Copy without Checking Size of Input)

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

An affected version is exposed as installed. No special setting or call is needed.


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

No fix has been published for CVE-2026-129606 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-129606 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-129606 is a high-severity memory corruption vulnerability in Samsung Open Source mTower, published on 16 Nov 2026. 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-2026-129606 in the wild and no public exploit code.
Exposure: An affected version is exposed as installed. No special setting or call is needed.

Affected product: Samsung Open Source mTower. 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-129606/ (Markdown: https://insights.sbomify.com/CVE-2026-129606/index.md)
```

## Sources

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

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