Skip to main content
Menu
CVEs

CVE

Samsung Open Source mTower out-of-bounds write in HOTP trusted application

CVE-2026-129606EUVD-2026-126176GHSA-XFMM-86VR-X3PJ

CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:H

7.1HighCNA
Exploited
No known exploitation
Fix
No fix listed
Who is exposed
Specific setups only

Do first: Check whether your setup matches what the bug needs. The HOTP trusted application's register_shared_key path copies a Non-Secure caller-supplied buffer into a fixed 64-byte secure buffer K[]

Published
Last modified
Reference
Last checked
0.14% · 3rd percentile
17/100 · provisional
Specific setups only
None on Exploit-DB, Metasploit or GitHub
  • Exploitation: none
  • Automatable: no
  • Technical impact: partial

Summary

Samsung Open Source mTower contains an out-of-bounds write flaw in its HOTP trusted application, caused by copying input into a buffer without checking its size. An attacker with local access and low-privilege credentials could overwrite memory to affect data integrity and availability.

Written by anthropic/claude-haiku-5.5 from the sources below. Verify against them.

Original description

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

Who should check

Teams building or shipping Samsung Open Source mTower firmware that includes the HOTP trusted application.

“Firmware version: master @ 102d3dc (mTower v0.6.0)”

github.com

cve.now Index

17Pcve.now Index 17 of 100 · methodology v3 · provisional
  • Exploitation0/40No signal
  • Exposure5/25Specific setups only
  • Reach?/20Unknown. No tracked technology or package matched
  • Severity7.1/10CVSS 7.1
  • No patch5/5No patch listed yet

What would change the score

  • Would score about 67 if added to CISA KEV
  • Would score about 62 if CISA's SSVC rates exploitation active
  • Would score about 27 if CISA's SSVC rates it automatable

What to do

  • Check whether your setup matches what the bug needs.

    The HOTP trusted application's register_shared_key path copies a Non-Secure caller-supplied buffer into a fixed 64-byte secure buffer K[]
  • Workaround: The checked facts list no workaround. The affected feature is the HOTP trusted application's register_shared_key path, and the vendor's advisory should be consulted for any mitigation.

Check your systems with an agent

Paste this into a coding or ops agent. It checks your systems read-only and reports a table per asset.

Check whether my systems are affected by CVE-2026-129606 (Out-of-bounds write in HOTP trusted application of Samsung Open Source mTower), using the cve.now data below.

Rules: work read-only. Do not run exploit code, proof-of-concept scripts or scanners that send attack payloads, and do not change any configuration, package, image or deployment. Report findings only.

What cve.now has for CVE-2026-129606 (entry last updated 2026-11-16):
Affected:
- Samsung Open Source mTower: version range not reported
Fixed versions: none listed yet.
Conditions (all must be true for the bug to be hit):
- The HOTP trusted application's register_shared_key path copies a Non-Secure caller-supplied buffer into a fixed 64-byte secure buffer K[] (source: https://github.com/Samsung/mTower/pull/254)
Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory.
Attacker needs: local access, low-privilege login, no user action.
CISA KEV: CVE-2026-129606 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-129606 only. If you also check another CVE, look up its own KEV status; never assume it from this one.

How to check:
- Installed software: check what is actually running, not what a repo declares. Read the version from each host, container image and Kubernetes node (the binary's version output, the OS package database, image layers), and check whether the conditions above hold there. Distribution packages may carry a backported fix under an older version number; confirm against the distribution's own advisory.

Verify against the linked advisories before concluding, and cite the date you read each one:
- https://github.com/Samsung/mTower/pull/254
Do not conclude an asset is unaffected unless you checked it and the evidence covers both its version and the conditions above. If you could not check something, mark it unknown and say what is missing.

Report a table with one row per asset and these columns: Asset | Version or build | Status (affected, fixed, not applicable, unknown) | Compensating controls | Exposure (internet-facing, internal, none) | Evidence | Next action.

Entry: https://cve.now/CVE-2026-129606
For follow-up questions, use the cve.now MCP server at https://mcp.cve.now/mcp (no authentication), for example execute with name cve.get and arguments {"id": "CVE-2026-129606"}.

Timeline

  1. CVE published
  2. First seen by cve.now
  3. CISA SSVC assessment

    Exploitation: none · Automatable: no · Technical impact: partial

  4. Record last updated

Affected versions

  • Samsung Open Source mTower

    Version range not reported

Evidence 3

CVE record · 2

Establishes: The identifier and description.

  1. Record
  2. Record

Other links · 1

  1. Repository

Corrections

None so far.

Something wrong on this page? Report an error. Every fix is listed here.

Questions about CVE-2026-129606

Is CVE-2026-129606 being exploited?

It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.Source: cve.now feed data

What does this mean?

A Non-Secure caller can pass a buffer to register_shared_key() in the HOTP trusted application, which copies params[0].memref.size bytes into a fixed 64-byte secure buffer K[]. The copy can overflow a secure .bss buffer with attacker-controlled data.Source: github.com

Am I affected, and how do I check?

The checked facts name Samsung Open Source mTower and its HOTP trusted application's register_shared_key path, but list no affected version ranges. To check a build, confirm whether it includes the HOTP trusted application and that register_shared_key path.Source: github.com

How do I fix CVE-2026-129606?

The checked facts give no fixed version and no vendor patch identifiers, so no upgrade target can be stated. Check the vendor's advisory for a fix.Source: github.com

What if there's no patch?

The checked facts list no workaround. The affected feature is the HOTP trusted application's register_shared_key path, and the vendor's advisory should be consulted for any mitigation.Source: github.com