Read the docs

Arbitrary file write in termux-sync restore via malicious manifest

Priority LOW 28CWE-22Published · Updated

Key facts

Attack vector
Local
Privileges required
None
User interaction
Required
Attack complexity
Low
Impact type
—
Confidentiality · integrity · availability
None · High · High
Fix status
Fixed

Attack profile from CVSS 3.1 · CNA. Fix status from CNA and GitHub.

Summary

termux-sync, a tool for backing up and restoring Termux environments, is affected before 1.2.4. Its restore path uses the parent directory of an untrusted manifest.json source value as the extraction destination and does not confine archive members to that destination, which is a path traversal flaw (CWE-22). A user who restores a malicious or tampered backup from local, shared, GitHub, or Google Drive storage can have files written anywhere the Termux user can write, including shell startup files or executable scripts that can lead to code execution.

Written with Claude Haiku 5.5 from the sources below · 2026-11-16

Description from the CNA

termux-sync is an open source tool for backing up and restoring a Termux environment across devices. Prior to 1.2.4, termux-sync restore uses the parent directory of the untrusted manifest.json files.*.source value as an extraction destination, and extract_archive calls tarfile.extract on archive members without enforcing a destination boundary. A victim who restores a malicious or tampered backup from local, shared, GitHub, or Google Drive storage can have files written anywhere the Termux user can write, including shell startup files or executable scripts that can lead to code execution when later used. The restore path also accepts unsafe backup_name values for temporary paths, and archive members are not constrained to the intended destination. This issue is fixed in version 1.2.4.

Why it matters now

Exploitation None reported CISA SSVC · not in CISA KEV
Fix Fixed termux-sync (djunekz): 1.2.4termux-sync (PyPI): 1.2.4

SSVC decision points

CISA ADP · SSVC 2.0.3

Exploitation
None
Automatable
No
Technical impact
Partial

The decision (Track, Attend, Act) also depends on your mission and well-being impact; see CISA's SSVC guide.

Affected products

VendorProductAffected versionsFixed inStatusSource
djunekztermux-syncbefore 1.2.41.2.4Patch availableCNA
—termux-sync (PyPI)before 1.2.41.2.4Patch availableGHSA-259w-wmqg-fp76
  • termux-sync Vendordjunekz Affected before 1.2.4 Fixed in 1.2.4 Patch available CNA
  • termux-sync (PyPI) Vendor— Affected before 1.2.4 Fixed in 1.2.4 Patch available GHSA-259w-wmqg-fp76

Remediation

Upgrade termux-sync to version 1.2.4, which fixes the issue in both the djunekz termux-sync product and the PyPI termux-sync package.

Written with Claude Haiku 5.5 from the sources below · 2026-11-16

  • Fix · CNA termux-sync (djunekz) Fixed in 1.2.4
  • Fix · GHSA-259w-wmqg-fp76 termux-sync (PyPI) Fixed in 1.2.4 Advisory →

Timeline

  1. 2026-11-16 Threatist record created from CVE-2026-86046
  2. 2026-11-16 CISA SSVC decision points changed
  3. 2026-11-16 Alias added: GHSA-259w-wmqg-fp76
  4. 2026-11-16 Fix available: PyPI/[email protected] · GHSA-259w-wmqg-fp76
  5. 2026-11-16 CVSS score added · GHSA-259w-wmqg-fp76
  6. 2026-11-16 Weakness changed · GHSA-259w-wmqg-fp76
  7. 2026-11-16 5 new references · GHSA-259w-wmqg-fp76

References

Sources