Skip to main content
VulnerabilityPublished

CVE-2026-86046: termux-sync · Arbitrary file write during restore via attacker-controlled manifest source path

Affects termux-syncSource GCVE Database

0
Compare
Authoritative record:CVE-2026-86046· High 7.1

Not known to be exploited · CVSS 7.1 High : upgrade to 1.2.4 soon.

Data as of 16 Nov 2026, 23:12 UTC

CVSS 3.1 base score
7.1High
How severe the flaw is on the 0–10 CVSS scale.

Thin evidence

One scorer or none
CVSS scores by source
CNA (GitHub_M)CVSS 3.17.1
Patch
Available – fixed in 1.2.4
CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:N/I:H/A:H

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 16 Nov 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 16 Nov 2026.

What to do

Upgrade termux-sync to 1.2.4.

Affected software

ProductAffectedFixed in
PyPItermux-syncAffected
  • <1.2.4
Fixed in
  • 1.2.4

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

A fix is available in termux-sync version 1.2.4. Users should upgrade to version 1.2.4 or later to mitigate this vulnerability. The fix involves not trusting the manifest 'source' field for extraction roots, sanitizing backup names to reject '..' and path separators, and enforcing extraction boundaries to prevent path traversal. Until upgraded, users should treat backups as untrusted input and avoid restoring backups from untrusted or compromised sources.

Description

termux-sync versions prior to 1.2.4 contain a vulnerability in the restore functionality where the backup manifest's 'source' field is not validated. This allows an attacker to control the extraction destination path during restore, leading to arbitrary file writes anywhere the Termux user can write. Malicious backups can overwrite shell startup files or executable scripts, enabling local code execution upon later use. The vulnerability arises because the restore process trusts untrusted manifest fields and does not enforce path restrictions or sanitize backup names.

References

Community reviews

Loading reviews…